| Previous | Contents | Index |
Specify an existing Volume Set onto which additional Volumes will be added.
LJKCÑ LINK GROUP device-name
| Command Qualifiers | Defaults |
|---|---|
| None. | None. |
device-name
A ISO-9660 CDROM or disc image from the highest existing Volume Group of the existing Volume Set.
Specify an existing Volume Set onto which additional Volumes will be added.LJK/CDROM reads the existing Volume Set to gather existing metadata that must be included on the Volumes it writes in order to make those new Volumes be part of the Volume Set.
The LINK GROUP command automatically defines within LJK/CDROM all the Hierarchies that exist on preceding members of the Volume Set, so those Hierarchies will be written to subsequent Volumes. Those Hierarchies, however, do not have names, so a subsequent DEFINE HIERARCHY command with matching Volume Identifier and Escape Sequences will affix its name to the inherited Hierarchy.
None.
LJKCÑ LINK GROUP file-name
|
Specify a Volume from the final existing Volume Group of the Volume Set to which additional new Volumes will be added.
Create default values for subsequent CREATE HIERARCHY commands.
LJKCÑ SET DEFAULT
- This command is only effective from the subsystem prompt (LJKCÑ).
None.
Set default values in advance for the qualifiers would otherwise be specified with the CREATE HIERARCHY command.The CREATE HIERARCHY command can take so many qualifiers of such potential length that it would be impossible to specify them all within DCL limits, or for that matter, the limits of accurate human typing.
The SET DEFAULT command creates accumulative values for the various qualifiers it shares with the CREATE HIERARCHY command, and those values take effect on subsequent CREATE HIERARCHY commands until the next WRITE command.
/ABSTRACT_FILE=d- or d1-characters
Specifies the Abstract File Identifier for this Hierarchy on each Volume in the Volume Group being written.This field is interpreted as the File Identifier for a file in the Root Directory of each Volume being created. The field must follow the syntax rules for a File Identifier in this Hierarchy and must represent a file that exists in that Directory. The File Name must have a maximum length of 8 and the File Name Extension must have a maximum length of 3.
/APPLICATION=a- or a1-characters
Specifies the Application Identifier for this Hierarchy on each Volume in the Volume Group being written.If this field starts with the character underscore (_), the rest of the field is interpreted as the File Identifier for a file in the Root Directory of each Volume being created. That remainder of the field after the underscore must follow the syntax rules for a File Identifier in this Hierarchy and must represent a file that exists in that Directory. The File Name must have a maximum length of 8 and the File Name Extension must have a maximum length of 3.
/APPUSE=input-filespec
Specifies a file containing data that is to be included in the Application Use field for this Hierarchy on each Volume in the Volume Group being written./BIBLIOGRAPHIC_FILE=d- or d1-characters
Specifies the Bibiographic File Identifier for this Hierarchy on each Volume in the Volume Group being written.This field is interpreted as the File Identifier for a file in the Root Directory of each Volume being created. The field must follow the syntax rules for a File Identifier in this Hierarchy and must represent a file that exists in that Directory. The File Name must have a maximum length of 8 and the File Name Extension must have a maximum length of 3.
/CHARACTER_SET=name
Specifies the Character Set for this Hierarchy./COPYRIGHT_FILE=d- or d1-characters
Specifies the Copyright File Identifier for this Hierarchy on each Volume in the Volume Group being written.This field is interpreted as the File Identifier for a file in the Root Directory of each Volume being created. The field must follow the syntax rules for a File Identifier in this Hierarchy and must represent a file that exists in that Directory. The File Name must have a maximum length of 8 and the File Name Extension must have a maximum length of 3.
/CREATION=date-time
Specifies the Volume Creation Date and Time for this Hierarchy on each Volume in the Volume Group being written./DATA_PREPARER=a- or a1-characters
Specifies the Data Preparer Identifier for this Hierarchy on each Volume in the Volume Group being written.If this field starts with the character underscore (_), the rest of the field is interpreted as the File Identifier for a file in the Root Directory of each Volume being created. That remainder of the field after the underscore must follow the syntax rules for a File Identifier in this Hierarchy and must represent a file that exists in that Directory. The File Name must have a maximum length of 8 and the File Name Extension must have a maximum length of 3.
/EFFECTIVE=date-time
Specifies the Volume Effective Date and Time for this Hierarchy on each Volume in the Volume Group being written./EXPIRATION=date-time
Specifies the Volume Expiration Date and Time for this Hierarchy on each Volume in the Volume Group being written./LOGICAL_BLOCK_SIZE=value
Specifies an alternate Logical Block Size to the standard 2048 bytes with which Hierarchies are created. The Logical Block Size must be the same for all the Hierarchies on a Volume./POSIX=IEEE_P1282 (D)
RRIP_1_09
Specifies the POSIX Rock Ridge version to be used in this Hierarchy. If no value is specified for the /POSIX qualifier, IEEE_P1282 is used. If the /POSIX qualifier is not specified, no Rock Ridge format will be used. Using a Rock Ridge format does consume extra space on the Volume./MODIFICATION=date-time
Specifies the Volume Modification Date and Time for this Hierarchy on each Volume in the Volume Group being written./PUBLISHER=a- or a1-characters
Specifies the Publisher Identifier for this Hierarchy on each Volume in the Volume Group being written.If this field starts with the character underscore (_), the rest of the field is interpreted as the File Identifier for a file in the Root Directory of each Volume being created. That remainder of the field after the underscore must follow the syntax rules for a File Identifier in this Hierarchy and must represent a file that exists in that Directory. The File Name must have a maximum length of 8 and the File Name Extension must have a maximum length of 3.
/SET_IDENTIFIER=string
Specifies the Volume Set Identifier for this Hierarchy on each Volume in the new Volume Set being created. This qualifier should not be specified when the command LINK GROUP has previously been given, since the Volume Set Identifier in that case must come from the prior Volume Group.The default value for this qualifier is the current VMS date-time with punctuation removed and truncated to 13 characters, for example: "09SEP20021234".
For those using the VMS Hobbyist license, an identification number will be appended to the specified (or defaulted) Volume Set Identifier.
/SETSIZE=maximum
Specifies the maximum number of Volumes that can be included in the Volume Set, including both those being created now and any used to create previous Volume Groups within the Volume Set. If the files specified with the commands LINK GROUP, ADD and WRITE exceed the capacity of this number of Volumes, an error message will be displayed before any output data is written.The ISO-9660 specification limits the maximum Volume Set Size to 65535.
/SPACE=logical-block-count
Specifies the number of logical blocks on the output Volume. When the output Volume is a volume image file, this is the size with which it will be created (taking into account the difference in size between Logical Blocks and VMS blocks.The maximum number of Logical Blocks that can be specified is the number that would result 2**31 (about 2 billion) VMS blocks.
/SYSTEM=character-list
Specifies the System Identifier that is to be included in this Hierarchy, identifying the system which is able to act on the System Area (Logical Sectors 0-15) of the created Volume.Generally this qualifier should be omitted.
/VOLUME=volume-name-list
Specifies the list of Identifiers to be used as the Volume Identifier in this Hierarchy on successive Volumes of the Volume Group being written in this session.If a single name is provided for the list and it contains an asterisk (*), the asterisk will be replaced by the Volume Sequence Number in each Volume Identifier as it is written.
If a single name is provided for the list and it contains no asterisk (*), that name will be used intact for the Volume Identifier in this Hierarchy on each Volume of the current Volume Group. There is no requirement in ISO-9660 that the Volume Identifier of various Volumes differ from one another.
LJKCÑ SET DEFAULT/VOLUME=(ONE,TWO)/POSIX=IEEE_P1282
LJKCÑ SET DEFAULT/PUBLISHER="LJK Software"
LJKCÑ SET DEFAULT/COPYRIGHT_FILE=COPYING.TXT
LJKCÑ SET DEFAULT/EFFECTIVE=14-DEC-2525
|
Those commands store their qualifier values into memory for use on the next CREATE HIERARCHY command.
LJKCÑ CREATE HIERARCHY MY_NAME/POSIX=RRIP_1_09
|
Create a Hierarchy which will use the values specified via the SET DEFAULT command except substituting the other Posix Rock Ridge format for the one specified via SET DEFAULT.
Display the version of LJK/CDROM currently being used.
$ LJK/CDROM SHOW VERSION
orLJKCÑ SHOW VERSION
| Command Qualifiers | Defaults |
|---|---|
| /OUTPUT=output-filespec | None. |
None.
None.
Display the version of LJK/CDROM currently being used.
/OUTPUT=output-filespec
Specifies a file to which the output of the SHOW VERSION command is to be written. Typically this qualifier would be used as an aid to automating operations with DCL command procedures.
$ LJK/CDROM SHOW VERSION
LJK/CDROM V1.0
|
Enter the LJK/CDROM command subsystem mode.
$ LJK/CDROM
| Command Qualifiers | Defaults |
|---|---|
| None. | None. |
None.
None.
The following commands preset information for use by the WRITE command, so they are only effective if entered from the subsystem prompt (LJKCÑ) prior to the WRITE command to which they apply. To terminate subsystem mode, enter the command EXIT.
None.
$ LJK/CDROM
LJKCÑ
|
Enter LJK/CDROM subsystem mode.
Test the software structural integrity of an existing ISO-9660 CDROM or disc image.
$ LJK/CDROM VERIFY file-1
orLJKCÑ VERIFY file-1
| Command Qualifiers | Defaults |
|---|---|
| /COPY_COMMANDS=output-filespec | None. |
| /OUTPUT=output-filespec | None. |
| /SHOW=(keyword[,...]) | See below. |
| /TOLERATE=keywords | None. |
None.
Test the software structural integrity of an existing ISO-9660 CDROM or disc image.
/COPY_COMMANDS=filespec
Specifies a file to which a DCL command procedure will be written, suitable for using LJK/CDROM to make a logical copy of the volume being verified.The purpose of generating such a command procedure is to make at least some modifications to the resulting command procedure, since a binary copy is the best way to make an exact copy of a disc. For instance, one might use it to add some VMS-specific files (including RMS attributes) to disc contents created on a non-VMS system.
/OUTPUT=output-filespec
Specifies a file to which the normal output of the VERIFY command is to be written./SHOW=DEBUG
DETAILS
MULTIPLE_ERRORS (D)
PROGRESS (D)
SUMMARY (D)
Specifies what information should be displayed during the command.
- DEBUG
Display extremely detailed information suitable for submitting a bug report.- DETAILS
Display detailed information suitable for analyzing a problem.- MULTIPLE_ERRORS
Display even those errors that were encountered on a previous file.- PROGRESS
Display indications of progress in processing the command.- SUMMARY
Display a summary of major results of the command./TOLERATE
=ISO9660=A_TRAILING_NULL
=ALL=A1_TRAILING_NULL
=MICROSOFT=A1_TRAILING_NULL
=ISO9660=D_TRAILING_NULL
=ALL=D1_TRAILING_NULL
=MICROSOFT=D1_TRAILING_NULL
Suppress error messages due to mistaken implementations of ISO-9660 : 1988 (E) 7.4.5 that pad fields with nulls rather than the required spaces./TOLERATE
=MICROSOFT=ESCAPE_TRAILING_TRASH
Suppress error messages due to mistaken implementations of ISO-9660 : 1988 (E) 8.5.6 that pad fields with spaces rather than the required nulls./TOLERATE
=ISO9660=A_CHARACTERS=character-list
=ALL=A1_CHARACTERS=character-list
=MICROSOFT=A1_CHARACTERS=character-list
=ISO9660=D_CHARACTERS=character-list
=ALL=D1_CHARACTERS=character-list
=MICROSOFT=D1_CHARACTERS=character-list
Suppress error mesages due to mistaken implementations of ISO-9660 : 1988 (E) 7.4 that include particular illegal characters./TOLERATE
=ISO9660=D_MISSING_SEPARATOR_1
=ISO9660=D_MISSING_SEPARATOR_2
=ALL=D1_MISSING_SEPARATOR_1
=ALL=D1_MISSING_SEPARATOR_2
=MICROSOFT=D1_MISSING_SEPARATOR_1
=MICROSOFT=D1_MISSING_SEPARATOR_2
Suppress error messages due to mistaken implementations of ISO-9660 : 1988 (E) 7.5.1 that fail to include SEPARATOR 1 (.) or SEPARATOR 2 (;) characters in File Identifiers./TOLERATE
=ISO9660=D_DIRECTORY_SEPARATOR_1
=ISO9660=D_DIRECTORY_SEPARATOR_2
=ALL=D1_DIRECTORY_SEPARATOR_1
=ALL=D1_DIRECTORY_SEPARATOR_2
=MICROSOFT=D1_DIRECTORY_SEPARATOR_2
Suppress error messages due to mistaken implementations of ISO-9660 : 1988 (E) 7.5.1 that incorrectly include SEPARATOR 1 (.) or SEPARATOR 2 (;) characters in Directory Identifiers.There is no /TOLERATE=MICROSOFT=D1_DIRECTORY_SEPARATOR_1 since Microsoft's Joliet specification allows Directory Identifiers to contain SEPARATOR 1 (.).
/TOLERATE
=ISO9660=DIRECTORY_DEPTH=n
=ALL=DIRECTORY_DEPTH=n
Suppress error messages due to mistaken implementations of ISO-9660 : 1988 (E) 6.8.2.1 that incorrectly create directory depths greater than 8.There is no /TOLERATE=MICROSOFT=DIRECTORY_DEPTH=n since Microsoft's Joliet specification allows greater directory depths.
/TOLERATE
=ISO9660=SELF_RECORDING_DATE_MISMATCH
=ISO9660=PARENT_RECORDING_DATE_MISMATCH
=ALL=SELF_RECORDING_DATE_MISMATCH
=ALL=PARENT_RECORDING_DATE_MISMATCH
=MICROSOFT=SELF_RECORDING_DATE_MISMATCH
=MICROSOFT=PARENT_RECORDING_DATE_MISMATCH
Suppress error messages due to mistaken implementations of ISO-9660 : 1988 (E) 6.8.2.2 that include a Recording Date field in one of the first two Directory Records that differs from the Recording Date of the main Directory Record describing the same Directory./TOLERATE=ISO9660
=CREATION_DATE_MISMATCH
=MODIFICATION_DATE_MISMATCH
=EXPIRATION_DATE_MISMATCH
=EFFECTIVE_DATE_MISMATCH
Suppress error messages due to mistaken implementations of ISO-9660 : 1988 (E) 9.5 and 4.1.6 of one of the Rock Ridge specifications such that a different date is included in the Extended Attribute Record (ISO) structure from that in the TF System Use Entry (Rock Ridge) structure./TOLERATE=ALL
=CREATION_DATE_MISMATCH
=MODIFICATION_DATE_MISMATCH
=EXPIRATION_DATE_MISMATCH
=EFFECTIVE_DATE_MISMATCH
Suppress error messages due to mistaken implementations of ISO-9660 : 1988 (E) 9.5 and 4.1.6 of one of the Rock Ridge specifications such that a different date is included in the Extended Attribute Record (ISO) structure from that in the TF System Use Entry (Rock Ridge) structure./TOLERATE=MICROSOFT
=CREATION_DATE_MISMATCH
=MODIFICATION_DATE_MISMATCH
=EXPIRATION_DATE_MISMATCH
=EFFECTIVE_DATE_MISMATCH
Suppress error messages due to mistaken implementations of ISO-9660 : 1988 (E) 9.5 and 4.1.6 of one of the Rock Ridge specifications such that a different date is included in the Extended Attribute Record (ISO) structure from that in the TF System Use Entry (Rock Ridge) structure.
$ LJK/CDROM VERIFY DKA100: /TOLERATE=(ISO=(DIRECTORY_DEPTH=11,D_MISSING_SEPARATOR_2), microsoft=(d1_trailing_null,escape_trailing_trash)) |
VERIFY a Volume but do not complain about:
).
| Previous | Next | Contents | Index |