Many variations for naming files and directories exist. Two types of naming conventions are supported by CANDE: the traditional CANDE file naming convention and the long node file naming convention. Only a selected set of CANDE commands support both conventions.
File names consist of a series of name nodes separated by slashes (/).
With traditional file names
-
There can be at most 12 nodes.
-
Each node can have at most 17 characters.
With long node names
-
There can be up to 20 nodes.
-
Each node can have up to 215 characters.
-
The total number of characters including slashes is limited to 215.
CANDE commands that take traditional file names as parameters truncate long name nodes. Furthermore, unless the administrator has configured the system to enable the use of long names, all commands truncate long name nodes to the traditional name limits. That is, nodes longer than 17 characters are truncated to 17 characters even in commands that are capable of accepting long names.
Because CANDE provides limited integration with long file names, avoid using long file names unless necessary.
Workstation programs can create files in the MCP environment of ClearPath systems. These files are generally byte-stream files and follow the long node file naming convention. The contents of these files are not intended to be manipulated by CANDE, and so such files cannot be retrieved as work file, listed, printed, or run as an MCP environment program. Instead, these types of operations are supported using workstation programs such as Notepad that access these files within an MCP directory share.
The following CANDE commands support using long node file name parameters because these commands can be used to manipulate nontextual files:
ADD ALTER CHANGE COPY LFILES PRINT REMOVE SECURITY TITLE ?FA
The intent is to minimize the impact of the long file name capability on the existing job decks and DO files.
