Write the currently specified input-filespecs along with any previously specified by the ADD command.

Format

$ LJK/CDROM WRITE output-filespec input-filespec,...

or

LJKCÑ WRITE output-filespec input-filespec,...

restrictions

• You must have write access to the ISO-9660 CDROM or disc image.
• If the output-filespec is a device rather than a file image, it must be mounted foreign.

Parameters

file-name

Name of the ISO-9660 CDROM or disc image to which data will be written.

Description

Write the currently specified input-filespecs along with any previously specified by the ADD command.

Aside from /VERIFY, the qualifiers apply to the input filespecs.

Note The LJK/CDROM WRITE command takes the target file specification before the source file specifications because the source file specifications are optional.

Qualifiers

/EFFECTIVE=date

Specifies the date that should be recorded for the effective date of the file(s). Such a date will be recorded in the ISO-9660 Extended Attribute Record, and in Hierarchies for which Rock Ridge information is being recorded the date will also be recorded in the TF System Use Entry.

/EXPIRATION (D)

/NOEXPIRATION

Specifies that the expiration date from the VMS file is to be recorded for the expiration date of the file on the Volume being written. Such a date will be recorded in the ISO-9660 Extended Attribute Record, and in Hierarchies for which Rock Ridge information is being recorded the date will also be reported in the TF System Use Entry.

This qualifier is provided because the meaning of an Expiration Date on a VMS file is locally defined and such a date may not be appropriate for distribution to other sites.

/NAMES=([hierarchy-name=]ISO-filespec[,...])

Specifies the File Identifiers and Directory Identifiers under which files are to be stored on various Hierarchies of the Volume being created.

The Directory Identifiers and File Identifiers for the Primary Hierarchy must consist of D-Characters (no dollar signs allowed) while the Directory Identifiers and File Identifiers for supplementary Hierarchies must consist of D1-Characters (as specified by the Character Set for the Hierarchy).

If the "[hierarchy-name=]" string is omitted, LJK/CDROM attempts to store under the specified filespec in all Hierarchies, producing an error message if that effort fails in any Hierarchy.

If this qualifier is not provided, LJK/CDROM attempts to use the input Directory Identifiers and File Identifiers for all Hierarchies, producing an error if any of the characters are illegal for any of the Hierarchies.

Besides the VMS-style, specification of Directory Identifiers for a Hierarchy can also be done in two other manners, if the initial character is not "[" or "<":

• Colon separations
  Each Directory Identifier is followed by a colon, similar to Macintosh filespecs.
• Slash separations
  Each Directory Identifier is followed by a left angle bracket, similar to Unix filespecs.

If no directory is specified, the directory from the input filespec is used for the output volume. To put a file into the root directory, as is required for files specified on the CREATE HIERARCHY or SET DEFAULT command qualifiers:

• /ABSTRACT_FILE=file.ext;version
• /APPLICATION=_file.ext;version
• /BIBLIOGRAPHIC_FILE=file.ext;version
• /COPYRIGHT_FILE=file.ext;version
• /DATA_PREPARER=_file.ext;version
• /PUBLISHER=_file.ext;version

specify the directory as [] in the /NAMES qualifier.

/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.

/VERIFY (D)

/NOVERIFY

Indicates a VERIFY operation is to be run against the completed Volume.

/VMS_ATTRIBUTES (D)

/NOVMS_ATTRIBUTES

Specifies that VMS-specific RMS attributes are to be stored on the Volume being created. This is the default.

Omitting the VMS-specific RMS attributes will inhibit reading of relative and indexed files from the Volume, but will not interfere with sequential files, including those with variable-length records.

Omitting the VMS-specific RMS attributes will not save any space on the Volume. The major use for omitting the VMS-specific RMS attributes would be to test on VMS (by mounting the resulting Volume) that the standard ISO-9660 support for sequential file record formats are working correctly. That is the purpose for which LJK Software uses the /NOVMS_ATTRIBUTES form of this qualifier.

Example

LJKCÑ  WRITE DKA100:
      

Write a Volume containing the collected results of ADD commands to the disk DKA100: (which has been mounted /FOREIGN).

$ LJK/CDROM WRITE SYS$LOGIN:FOO.DAT A.B
      

Write a Volume containing all files named FOO to the disc image at SYS$LOGIN:FOO.DAT.

This appendix shows how to install LJK/CDROM.

There are two available methods to install LJK/CDROM:

• Section A.1, VMSINSTAL Installation Commands
• Section A.2, PCSI Installation Commands

But regardless of which method you use, the very first installation of LJK/CDROM on a system disk should be followed by a special step if you want to use the HELP/MESSAGE data specific to LJK/CDROM.

• Section A.3, Enabling HELP/MESSAGE After Installation

A.1 VMSINSTAL Installation Commands

$ MOUNT ddcu: LJK /MEDIA_FORMAT=CDROM /UCS_SEQUENCE="(B" $ @SYS$UPDATE:VMSINSTAL LJK_CDROM DISK$LJK:[KITS] OPTIONS I

Note the use of the qualifier:

/UCS_SEQUENCE="(B"

on the MOUNT command in order to access an ISO-9660 hierarchy that contains dollar signs in certain Directory Identifiers and File Identifiers---[DECW$BOOK] in particular.

A.2 PCSI Installation Commands

$ MOUNT ddcu: LJK /MEDIA_FORMAT=CDROM /UCS_SEQUENCE="(B" $ BACKUP DISK$LJK:[KITS]LJK_CDROM_PCSI_KITS.BCK/SAVE []/NEW_VERSION $ PRODUCT INSTALL LJK_CDROM /SOURCE=SYS$DISK:[]

Note the use of the qualifier:

/UCS_SEQUENCE="(B"

on the MOUNT command in order to access an ISO-9660 hierarchy that contains dollar signs in certain Directory Identifiers and File Identifiers---[DECW$BOOK] in particular.

A.3 Enabling HELP/MESSAGE After Installation

$ DEFINE/SYSTEM MSGHLP$LIBRARY - SYS$HELP:MSGHLP$LIBRARY.MSGHLP$DATA,- SYS$HELP:LJK$LIBRARY.MSGHLP$DATA

VMS provides no automated mechanism for layered products to merge their HELP/MESSAGE data such that it will persist beyond the next VMS upgrade. If LJK/CDROM were to attempt to modify the definition of that logical name on the fly, it would certainly fail at a site where the number of HELP/MESSAGE files to be included exceeded some limit like the maximum number of equivalence names for a logical name.

A.4 Sample VMSINSTAL Installation

$ MOUNT DKA400: LJK /MEDIA_FORMAT=CDROM /UCS_SEQUENCE="(B" %MOUNT-I-WRITELOCK, volume is write locked %MOUNT-I-CDROM_ISO, LJK:LJK_CDROM (1 of 1) , mounted on _NODE$DKA400: $ @SYS$UPDATE:VMSINSTAL LJK_CDROM DISK$LJK:[KITS] OPTIONS I OpenVMS AXP Software Product Installation Procedure K7.2 It is 1-NOV-2002 at 15:40. Enter a question mark (?) at any time for help. The following products will be processed: LJK_CDROM V1.0 Beginning installation of LJK_CDROM V1.0 at 15:40 %VMSINSTAL-I-RESTORE, Restoring product save set A ... %VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP. The following files will be added or replaced: SYS$COMMON:[SYSEXE]LJK$CDROM.EXE; SYS$COMMON:[SYSHLP]LJK$CDROM010.RELEASE_NOTES; SYS$COMMON:[SYSHLP]LJK$LIBRARY.MSGHLP$DATA; SYS$COMMON:[SYSLIB]LJK$CDROM_SHARE.EXE; SYS$COMMON:[SYSMSG]LJK$MESSAGES.EXE; The following files will be modified: SYS$COMMON:[SYSHLP]HELPLIB.HLB; SYS$COMMON:[SYSLIB]DCLTABLES.EXE; (new version created) All questions have been asked. %VMSINSTAL-I-RESTORE, Restoring product save set B ... The remainder of the installation will take 5 minutes on a stand-alone MicroVAX-II. %LJK_CDROM-I-DCLTABLES, Adding command LJK/CDROM to DCL tables %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... Installation of LJK_CDROM V1.0 completed at 15:40 Adding history entry in VMI$ROOT:[SYSUPD]VMSINSTAL.HISTORY Creating installation data file: VMI$ROOT:[SYSUPD]LJK_CDROM010.VMI_DATA VMSINSTAL procedure done at 15:41 $

A.5 Sample PCSI Installation

Here is a sample of LJK/CDROM installation using PCSI, with /LOG qualifiers added to the BACKUP command, just for illustrative purposes:

$ MOUNT DKA400: LJK /MEDIA_FORMAT=CDROM /UCS_SEQUENCE="(B" %MOUNT-I-WRITELOCK, volume is write locked %MOUNT-I-CDROM_ISO, LJK:LJK_CDROM (1 of 1) , mounted on _NODE$DKA400: $ BACKUP DISK$LJK:[KITS]LJK_CDROM_PCSI_KITS.BCK/SAVE []/NEW_VERSION/LOG %BACKUP-S-CREATED, created DISK$LOGIN:[LJK]LJK-AXPVMS-LJK_CDROM-T0001--1.PCSI;1 %BACKUP-S-CREATED, created DISK$LOGIN:[LJK]LJK-VAXVMS-LJK_CDROM-T0001--1.PCSI;1 $ PRODUCT INSTALL LJK_CDROM /SOURCE=SYS$DISK:[] 1 - LJK AXPVMS LJK_CDROM V1.0 Layered Product 2 - LJK VAXVMS LJK_CDROM V1.0 Layered Product 3 - All products listed above 4 - Exit Choose one or more items from the menu separated by commas: 2 The following product has been selected: LJK VAXVMS LJK_CDROM V1.0 Layered Product [Installed] Do you want to continue? [YES] Configuration phase starting ... You will be asked to choose options, if any, for each selected product and for any products that may be installed to satisfy software dependency requirements. LJK VAXVMS LJK_CDROM V1.0: LJK/CDROM ISO-9660 Formatter Copyright 2002 LJK Software, All Rights Reserved. LJK Software, Cambridge, MA USA A license PAK might be needed after installation. Do you want the defaults for all options? [YES] Do you want to review the options? [NO] Execution phase starting ... The following products will be installed to destinations: LJK VAXVMS LJK V2.9 DISK$VAX96A073:[VMS$COMMON.] LJK VAXVMS LJK_CDROM V1.0 DISK$VAX96A073:[VMS$COMMON.] Portion done: 0%...20%...30%...60%...70%...80%...90%...100% The following products have been installed: LJK VAXVMS LJK V2.9 Layered Product LJK VAXVMS LJK_CDROM V1.0 Layered Product $

The product named LJK which is automatically installed provides HELP/MESSAGE, HELP, Message and DCL Command information that is shared between products from LJK Software.

This appendix tells how to report LJK/CDROM defects.

There is opportunity for lengthy debate over what is a "bug", what is a "feature", when a "bug report" is really an "enhancement request" and similar issues.

Rather than semantic nit-picking, however, the purpose of this appendix is to discuss communications between you, the user of LJK/CDROM, and LJK Software, the vendor and maintainer.

Even in cases where there is no problem with the software, user reports of difficulties give LJK Software information as to where documentation or training can be improved, so we appreciate your input.

At the same time, both parties want to make these interactions as productive as possible, and it is to that purpose that these rules are directed.

B.1 Who Can Submit Bug Reports ?

• Standard licensees whose right-to-use-new-versions has not expired.
• Select others who provide particularly useful bug reports (in the sole judgement of LJK Software).

Bug reports for a particular version of LJK/CDROM are only accepted until 30 days after the successor version is released. Bug reports should be addressed to:

• LJK Software
• Attention: LJK/CDROM Bug Reports
• 1 Broadway, Suite 600
• Cambridge, MA 02142-1100

• For problems with the commands VERIFY, COMPARE or LINK GROUP
  An ISO-9660 CD-R which can be used to demonstrate the problem.
• For problems with the commands ADD or WRITE commands
  A CD-R containing a VMS Backup save set of the files needed to reproduce the problem.

1. Describing the problem in English
2. showing a log demonstrating the problem, including the LJK/CDROM command SHOW VERSION.
3. for standard licensees giving the Product Authorization Key authorization number.

Standard licensees will be given an individual email address for asking simple questions for the duration of their right-to-use-new-versions.