File names in the DMS file system are formed in accordance with this file system’s rules (see manual “Introductory Guide to DMS” [8]. Partially qualified file names and wildcard specifications are not supported at any of the JRIO interfaces with the exception of the specifications permissible as a directory and the file identifier in policy files (see also section "Security").
Only the specification of a lone catalog ID (Catid) which is enclosed in colons, a user ID (Userid) with a leading dollar character and a closing period or a combination of the two are regarded as directories in the DMS file system. The customary special way of specifying the system standard ID is also permitted. Consequently only the following specifications are possible for directories in DMS:
:catid: $userid. :catid:$userid. $. :catid:$.
As DMS is a flat file system and actually has no directory concept, directories cannot be set up or deleted with the interfaces provided here. Neither do they have attributes such as modification date or a size. Only the methods for listing directory contents are practical for the above-mentioned artificial directories of DMS.
As in the DMS interfaces, the so-called logical system files (SYSFILE environment) are not supported. In addition, JRIO does not support EAM files, either.
Normalized path names
When generating a RecordFile object and at locations where the user can specify a file or path name at the JRIO interfaces, not only the syntax and semantics check is performed, but also what is known as normalization. For DMS files this normalization of the name means that any lower-case letters contained in the name are converted to upper-case letters. In addition, file names which contain no periods but begin with a dollar character ($) are converted into names with a leading system standard ID in accordance with the DMS conventions:
Example
$EDT => $.EDT
Absolute path names
A path name in DMS is regarded as absolute if it begins with a catalog ID. Thus when an absolute path name is generated this means that if a catalog ID is not already contained in the name, the default catalog ID of any user ID specified or of the calling program is added (see section "RecordFile").
Canonical path names
A path name in DMS is canonical if it consists only of a catalog ID or contains both a catalog ID and a user ID. Thus when a canonical path name is generated, this means that (if it is not already included) the default catalog ID of any specified user ID or that of the calling program (see section "RecordFile").