6.1 Introduction

• cdadm attach <device> [-d <drive> ]
• cdadm byebye
• cdadm cvtree
• cdadm detach <device> [-d <drive> ]
• cdadm getpar <key>
• cdadm insert [-f] <device> [<list>]
  cdadm import [-f] <device> [<list>]
• cdadm logmsg <level> <message>
• cdadm movecd <device> <drive> [<slot>]
• cdadm null
• cdadm rename [[-<nf>] <old> [<new>]]
• cdadm remove [-f] <device> [<list>]
  cdadm export [-f] <device> [<list>]
• cdadm rescan <device>
• cdadm setpar <key> <value>
• cdadm survey <surveytype> <columns> [<restrict>] [<sortby>]
• cdadm testcd <device> <list>
• cdadm writer ...

The following pages contain brief descriptions of the commands that can be passed to the program cdadm.

Note: For reasons of clarity the optional paramter "-h <hostname>" is left out on the following pages. Using this parameter, the iXOS-JUKEMAN server can be administered from any host where the administration client cdadm is installed. See section "Network administration" on page 100.

cdadm attach <device> [-d <drive> ]

attach

Function:
Attach the specified device (or drive) to the server. The effect of this command is that the device and its volumes are controlled by iXOS-JUKEMAN. The device (or drive) cannot be accessed unless it is attached.
The parameter <device> represents a valid device description file in the JUKEMAN directory. These files have the extension .dev. The extension may be omitted in the command.
If the optional parameter -d <drive> is specified, a drive locked dynamically with cdadm detach -d... will be attached again. <drive> is the logical drive number.
To attach a device automatically when the server starts up, add it to the file server.cfg (see "Configuration file server.cfg" on page 245).
Example:
cdadm attach p18.dev
cdadm attach p18 (equivalent)
Error messages:

cdadm byebye

byebye

Function:
Terminate the iXOS-JUKEMAN daemon cdnfsd. The server will stop and accept no further requests. The server can be restarted by running cdstart.bat (under NT) or cdnfsd (under UNIX) (see "Starting iXOS-JUKEMAN" on page 91).
Example:
cdadm byebye
cdadm down (Synonym)
Error messages:

cdadm cvtree

cvtree

Function:
Rescan the configurable volume tree (views). This can be useful when views are changed in the server.cfg configuration file (see "Configuration file server.cfg" on page 245). The server does not need to be restarted, to reflect changes to the views configuration.
Example:
cdadm cvtree
Error messages:
-

cdadm detach <device> [-d <drive> ]

detach

Function:
Detach the specified device (or drive) from the server. The device and its volumes are no longer controlled by iXOS-JUKEMAN. The device (or drive) cannot be accessed until it is attached again.
The parameter <device> represents a valid device description file in the JUKEMAN directory. These files have the extension .dev. The extension may be omitted in the command.
If the optional parameter -d <drive> is specified, the drive with the logical number <drive> will be locked dynamically, while the server is running. This locked drive will not be used for any further file requests to the server. However, it is possible to move disks into this drive with cdadm movecd... and to remove disks from this drive (e. g., to use the drive for writing disks).
Example:
cdadm detach p18.dev
cdadm detach p18 (equivalent)
Error messages:

cdadm getpar <key>

getpar

Function:
Get the value of the server parameter <key>. Refer to the section "Server parameters" on page 253 for a list of all parameters. Server parameters may be set in the configuration file server.cfg or with the cdadm setpar command. Note that some parameters cannot be changed while the server is running. See "Static parameters" on page 129.
Example:
cdadm getpar loglev
Error messages:

cdadm insert [-f] <device> [<list>]
cdadm import [-f] <device> [<list>]

insert
import

Function:
Insert a disk into the specified device.
The parameter <device> represents a valid device description file in the JUKEMAN directory. These files have the extension .dev. The extension may be omitted in the command.
The optional <list> parameter may be used to specify any number and selection of slots. The following syntax is used to specify a variety of slots:

The specified slots will be scanned for empty slots and a single volume can be inserted into the first found empty slot. If there are no free slots, you will get an error message.
Note that for some devices like single drives and towers there is a dynamic drive check to detect disk changes (see server parameter dcheck in section "Server parameters" on page 125). You do not need to issue this command if you want to insert disks into these devices.
The optional -f switch can be used with the Pioneer DRM-500 and the Grundig GMS 1035. Using this switch, the command will return as soon as the door may be opened for a disk to be inserted. This is to prevent you from opening the jukebox door too early. If the switch is not specified, the command will wait, until the disk changes is finished.
Example:
cdadm insert merc 4-12
Error messages:

cdadm logmsg <level> <message>

logmsg

Function:
Add <message> to the file logfile.txt. The <level> parameter is the log level of the message. The log file is described in "Log file logfile.txt" on page 257. If <level> goes beyond the parameter loglev, the message will not be logged.
Example:
cdadm logmsg 5 This goes to logfile.txt
Error messages:
-

cdadm movecd <device> <drive> [<slot>]

movecd

Function:
Move a disk from <slot> to <drive> or remove a disk from <drive>. This command will especially be useful, if you want to move a certain (writable) disk into a recorder drive to burn data on it.
The parameter <device> represents a valid device description file in the JUKEMAN directory. These files have the extension .dev. The extension may be omitted in the command.
The <drive> parameter is a number between 1 and the total number of drives in a jukebox (e.g., 4 in a Mercury jukebox).
If the <slot> parameter is specified, the disk from that slot will be moved into the specified drive. If <slot> is omitted or specified as 0, the disk currently placed in drive <drive> will be removed from that drive (to its previous slot).

Example:
cdadm movecd merc.dev 2 8
Error messages:

cdadm null

null

Function:
Check if the server is active. If the server is active, there is no result. An error message will be produced if the server is not running.
Example:
cdadm null
Error messages:

cdadm rename [[-<nf>] <old> [<new>]]

rename

Function:
Rename a disk in the name format <nf>. There are three possible name formats (see also "Setting up views" on page 69):

If no name format is supplied, the disk name will be changed for all name formats that match the old name specified.
A single disk may have a different name for each name format. The name format that is visible to the client is set in the server.cfg configuration file (see "Configuration file server.cfg" on page 245).
The <old> parameter is the current name of the disk in the given name format.
The <new> parameter is the new name of the disk. This parameter must not be an already existing name from the volumes database. If it is omitted, the <old> name will be removed from the database, provided that the disk is not in use.
If cdadm rename is called without any parameters, all unused volume names will be removed from the database. These names can then be assigned to other volumes (see also "Rename disks" on page 121).
Example:
cdadm rename -pc demo.cd1 office.cd1
cdadm rename (removes unused volume names from the database)
Error messages:

cdadm remove [-f] <device> [<list>]
cdadm export [-f] <device> [<list>]

remove
export

Function:
Remove a volume from the specified device.
The parameter <device> represents a valid device description file in the JUKEMAN directory. These files have the extension .dev. The extension may be omitted in the command.
The optional <list> parameter may be used to specify any number and selection of slots. The following syntax is used to specify a variety of slots:

(As an alternative for the slot number, a disk name may be specified.)
The slot range will be scanned for occupied slots and a single volume will be removed from the first found occupied slot. If there are no occupied slots, you will get an error message.
Note that for some devices like single drives and towers there is a dynamic drive check to detect disk changes (see server parameter dcheck in section "Server parameters" on page 125). You do not need to issue this command if you want to remove disks from these devices.
The optional -f switch can be used with the Pioneer DRM-500 and the Grundig GMS 1035. Using this switch, the command will return as soon as the door may be opened for a disk to be removed. This is to prevent you from opening the jukebox door too early. If the switch is not specified, the command will wait, until the disk change is finished.
Example:
cdadm remove merc 2,5,6
Error messages:

cdadm rescan <device>

rescan

Function:
Reinitializes the internal memory of the jukebox, which stores information about which slot or drive contains which disk. This command is needed for some jukeboxes, if disks were changed manually. The jukebox would not know about these changes and could damage itself as it tries to move a disk in a slot which is presumed empty. The other way around the jukebox will not move disks into a drive if the slot is presumed empty according to the internal memory.
Execution of this command can take quite some time, since by default all slots are tested (e. g., about one hour for the Pioneer 5004 X), Alternatively, iXOS-JUKEMAN version 2.3 allows a partial rescan for the Pioneer 1004 X and 5004 X as well as the JVC MC-* and DISK CD CHG-* jukeboxes with the command "cdadm testcd", e. g., cdadm testcd pi500.dev 1-20. Please note, that the server parameter blanks (see page 125) must be set to 0 to guarantee that these tests are actually done.
However, the command "cdadm testcd" applied to all slots of the jukebox should not be mistaken as a substitute for cdadm rescan: A rescan refers to the internal memory of the jukebox, whereas a testcd refers to the internal volumes database of the server.
The parameter <device> represents a valid device description file in the JUKEMAN directory. These files have the extension .dev. The extension may be omitted in the command.
Example:
cdadm rescan jb.dev
Error messages:

cdadm setpar <key> <value>

setpar

Function:
Set the server parameter <key> to <value>. Refer to the section "Server parameters" on page 253 for a list of all parameters. Server parameters can also be set in the configuration file server.cfg. Note that some parameters cannot be changed while the server is running. See "Static parameters" on page 129.
Example:
cdadm setpar loglev 2
Error messages:

cdadm survey <surveytype> <columns> [<restrict>] [<sortby>]

survey

Function:
Print a survey based on devices, disks, or drives, depending on several parameters, which specify the columns, restrictions and sort criterion.
The following options may be specified:

Possible combinations:
cdadm survey -d +dnRDPMr
cdadm survey -v +dsimRauUSIvYorphBWwFfTDPMf
cdadm survey -s +dsimRauUSIvYorphBWwFfTDPMf
cdadm survey -n +iuUIorphDPM
cdadm survey -r +dnvpitrfu

Note: Any <column> name may be preceeded with :<char> to get quoted output for that parameter, where <char> is a single character. For instance cdadm survey -d +:'d lists all attached devices, where the device names will be quoted (`dev1.dev', `dev2.dev'...).

<restrict>:
This optional parameter may be used to limit the survey output to entries specified in the format:
<column>=<value> (print all lines where <columns> is <value>)
<column>!<name> (print all lines where <columns> is not <value>)
Example:

cdadm survey -v +do m=HD-image

This command will print a disk-based survey with device names and original disk names for all disks with the type HD-image.
<sortby>:
This optional parameter may be used to sort the output by one or more columns:

s:[-]<columns>

The optional - reverses the sort order.
Example:

cdadm survey -v +do m=HD-image s:dB

´This command will print a list of all hard disk images sorted by name and size of buffered data.
Example:
cdadm survey -d +d print a list of all attached devices
cdadm survey -n +oPDM u=+ s:o print disk names and statistics. Output is limited to accessible disks (u=+) and sorted by original disk names (s:o)
Error messages:

cdadm testcd <device> <list>

testcd

Function:
Test one or more slots of an attached device for their contents. Disks inserted manually will not be seen by the server, unless their corresponding slots are tested with this command. Depending on the jukebox type a rescan needs to be accomplished beforehand (see page 236).
The parameter <device> represents a valid device description file in the JUKEMAN directory. These files have the extension .dev. The extension may be omitted in the command.
The optional <list> parameter may be used to specify any number and selection of slots. The following syntax is used to specify a variety of slots:

Example:
cdadm testcd merc.dev 4,5,10-20
Error messages:

cdadm writer ...

writer...

Function:
The "cdadm writer..." commands access the incremental file system. A detailed description can be found in the section "Burning disks incrementally" on page 154.

format

(1) cdadm writer action=format location=<location>
Format a PD/MO disk or a hard disk image. This may take some time.

init

(1) cdadm writer [fsi=ifs] action=init location=<location> vname=<volume>
Initialize a writable disk. This command creates a recordable file system on the specified disk. Two small tracks will be written for initialization. One more track will be written for finalization. Therefore, up to 96 tracks can be written to a CD-R, since it is limited to 99 tracks. For PDs, WORMs, MOs and hard disk images there is no such limitation. The software will currently not check the space needed for the final table of contents track. Enough space must be left for successful finalization.

flush

(1) cdadm writer action=flush vname=<volume>
Actually write all buffered data to the specified disk.

verify

(1) cdadm writer action=verify [track=<number>]
If track=... is not specified, the last written track will be verified, otherwise the track with number <number>. If track=all is specified, all tracks will be verified.

purge

(1) cdadm writer action=purge vname=<volume>
Purge all buffered data for the disk <volume>.

finalize

(1) cdadm writer action=finalize vname=<volume>
Finalize a disk with an incremental file system. All buffered data must be flushed from the buffer to the disk with a cdadm writer flush command before it can be finalized.
<location> is in the format <device>,<slot>, where <device> is the name of a valid device description file and <slot> is the slot number.
In addition the parameter speed=1, speed=2 or speed=3 can be specified to select the writing speed (default: double speed). The parameter ring=<size> selects the ring buffer size used for writing (default: 4 MB).
Example:
cdadm writer action=init location=jb.dev,4 vname=CDR_01
cdadm writer action=flush vname=CDR_01
cdadm writer action=verify vname=CDR_01
cdadm writer action=finalize vname=CDR_01
Error messages: