There are new CREATE qualifiers:

 	    /TRACKS=nnn
 	    /SECTORS=nnn
 	    /CYLINDERS=nnn
 	    /MAXBLOCKS=nnn

 	  These settings will be stored in the containerfile as metadata
 	  (in the fileheader), and if present will be used when the
 	  containerfile is connected (unless /NOAUTOGEOMETRY is specified).

 	    /LBN=nnn

 	  Allows placement of the containerfile on a specific LBN. If that
 	  LBN is not available an error will be returned. Notice that when
 	  /CONTIGUOUS is not specified and the request succeeds the file
 	  may be split in multiple segments at the discretion of the XQP,
 	  in that case only the first part of the file will be on the
 	  specified LBN.

 	    /CLONE=device

 	  Allows size and geometry to be cloned from the specified device.
 	  This device has to be mounted for this to function. The geometry
 	  will automatically be saved in the containerfile.

 	New CONNECT qualifiers:

 	    /CLONE=device

 	  Allows size and geometry to be cloned from the specified device.
 	  This device has to be mounted for this to function. Other geometry
 	  data may be overruled when specified on the commandline.

 	    /AUTOGEOMETRY

 	  This is the default. On a connect the containerfile is checked if
 	  there's geometry info available, and if true that's used for
 	  connect unless /NOAUTOGEOMETRY is specified.

 	    /SAVE

 	  Updates the geometry data in the containerfile.

 	New [NO]PROTECT qualifiers:

 	    /PERMANENT

 	  Save writelock status in the containerfile so that it may be used
 	  during CONNECT (like emulating a 'hardware write protect' button).

 	Other features:

 	Interactive help is available with the LD HELP command.

 	If a shared file is connected and an error is returned due to
 	incompatibilities with sharing of other nodes, a more verbose error
 	message is given with the reason for the failure, like invalid
 	allocation class, unit number, etc.

 	The following will automatically connect the right unit if it's not
 	specified and file sharing is wanted:

 	  $ LD CONNECT DISK:[DIR]FILE.DSK/SHARE

 	This way of connecting needs CMKRNL privilege. If this privilege is
 	lacking a clear error message will be displayed about that.

 	There's no problem anymore in using an ODS5 volume for the
 	containerfile, this restriction has been lifted.

 	Using a containerfile exceeding 4Gb will not crash the system
 	anymnore.