The reservation file contains information on the features of the tapes needed when a tape is initially reserved. The following information can be stored in each record of the reservation file:
- location;
- tape number range (start and end archive numbers);
- device type;
- user ID;
- jobname;
- reservation rejection;
- utilization type (for a directory or a file);
- file name (directory or file);
- free pool name (name of a free tape pool);
- info.
When a free tape is requested, the reservation file is read sequentially. When an entry is found that matches the comparison criteria, the read operation is terminated. This means that the order of the entries is important. A more detailed description is provided in the section “Evaluation of the reservation file”.
The entries in the reservation file have the following format (see also the figure “Structure of the MARENLM basic form” (The MARENLM basic form) and “Layout of the data edited for printing” (The menu options of MARENLM)). Each field of an entry is defined by its position.
- Location
<alphanum 1..8> determines the location at which a tape or a device (in the case of SECURE-RESOURCE-ALLOCATION) is to be reserved.*ANY (or 8 blanks) in place of a location name means that the location is defined elsewhere:
- The location specified explicitly or implicitly in the RESERVE-FREE-VOLUME statement applies.
- Otherwise the location specified by the user with ADD-MAREN-FILE-ENTRY LOCATION= ... or via ARCHIVE or HSMS applies. If it has not been specified in this way, the location is defined as described under “Location definition without MAREN exits and reservation file” (Automatic location definition).
- Start VSN
<alphanum 1..6> is the archive number of the first tape in a number range. A number range is defined by specifying another tape in the field “End VSN”. - End VSN
<alphanum 1..6> is the archive number of the last tape in the range of tapes. The start VSN and end VSN must both contain an archive number or blanks. - Vol.type
<alphanum 1..8> defines the type of the requested tape. This entry is evaluated by BS2000 NDM. The device type cannot be truncated (for example T-C4 may not be specified instead of TAPE-C4). - Userid
<alphanum 1..8 with-wild> defines the user identification of the task which issued the tape request. The user ID can be specified fully-qualified (without $) or partially-qualified (* at the end of the substring). Beginning with *, all following characters are treated as concordant. - Jobname
<alphanum 1..8 with-wild> defines the job name of the task which issued the tape request. The job name can be specified fully-qualified or partially-qualified (* at the end of the substring). Beginning with *, all following characters are treated as concordant. This field corresponds to the request name in HSMS statements. - Rej.
<alphanum 1..1> defines whether the request is rejected.
With “R” the request is rejected.
With “O” the operator is requested to specify an archive number.
If this field contains a blank, the request is accepted. - A/F
<alphanum 1..1> defines whether a reservation is to be allocated to a directory (A) or to a file (F). If this field is not set, then the following Directory/Filename field will not be ignored, no matter what the content is. Directory/Filename (ARCHIVE Directory/Filename)
<filename 1..54> defines a directory file if the tapes are requested with HSMS/ARCHIVE, or a file is to be created on specific tapes.Depending on the A/F field contents, a file name with catalog ID and user ID has to be specified for a directory file and a file name without catalog ID and user ID for a file.
Whether the partially-qualified specification of Directory or Filename is possible also depends on A/F:
With A/F= A (HSMS/ARCHIVE application):
The name of the directory file is a fully-qualified file name and is divided into CATID, USERID und FILENAME (e.g. :CATD:$SYSHSMS.DIRECTORYSYSBACKUP). The parts can be individually specified as partially-qualified (with * at the end) or they can be omitted.Possible specifications (examples) for CATID, USERID und FILENAME:
CATID :ABC: fully-qualified specification :A*: partially-qualified specification: has to begin with A in this example (or only A) <empty> will not be checked, i.e. always valid USERID $ABC fully-qualified specification $A*. partially-qualified specification: has to begin with A in this example (or only A) $. must conform to the DEFLUID of the CLASS2OP <empty> will not be checked, i.e. always valid FILENAME ABC fully-qualified specification A*. partially-qualified specification: has to begin with A in this example (or only A) <empty> will not be checked, i.e. always valid - With A/F =F:
The filename can be specified partially-qualified (* at the end). Beginning with *, all following characters are treated as concordant.The system-specific MAREN parameter CID-UID specifies whether the catalog ID and the user ID have to be specified for a file.
- Free-Pool-Name
<alphanum 1..54> defines the free tape pool from which the requested tape is to be reserved. 54 blanks designate the free tape pool *NO. - Info
<alphanum 1..16> for user information.
The following table shows examples for the specification of partially-qualified values of the fields Userid, Jobname, Filename and Directory described above:
| Field in reservation file | Valid values | Invalid values |
| Userid | USERID* *ANY <only blanks> * and rest with blanks | *ANYX *ANY x USER*DXX *A |
| Jobname | JOBNAMEX JOBNA* *ANY <only blanks> * and rest with blanks | *ANYX *ANY x JOB*XX *A |
| Filename | FILE.NAME FILE.NAME* FILE.* *ANY <only blanks> * and rest with blanks | FILE.NAME* A *ANY x FILE*XX *A |
| Directory | :X:$USER.DIR-NAME :XAB*:$USER*.DIR* :*:$USER.DIR-NAME* $USERID.DIR-NAME DIR-NAME :YAB:$.DIR-NAME :CATD:DIR-NAME | :ABCDX*:$USERID.DIR-NAME :CATD:$USER*XXX.DIR-NAME DIR-NAME* XXX :C*TD:$X...DIR-NAME :CAT:$*ABC.DIR-NAME |