PATH Examples
The following examples assume a disk tree structure as such:
|
|
C:\ |
|
|
C:\PLB |
|
|
C:\PLB\PROG |
|
|
C:\PLB\TESTDATA |
|
|
C:\PLB\LIVEDATA |
Example 1:
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
C:•••••••••• |
|
| |||||
|
|
|
|
|
|
C:\PLB•• |
No Condition Flags are set (all FALSE).
Example 2:
|
|
|
|
|
|
|
Variable |
PL |
FP |
LP |
Contents |
|
Before: |
PATHVAR |
12 |
1 |
2 |
C:•••••••••• |
|
| |||||
|
After: |
PATHVAR |
12 |
1 |
12 |
C:\PLB\P |
The EOS Condition Flag is set. PATHVAR could not contain all of the information.
Example 3:
|
|
|
|
No Condition Flags are set (all FALSE) because the CHANGE was to a valid path.
Example 4:
|
|
|
|
|
The OVER Condition Flag is set because the given path (C:\PLB\DUMMY) did not exist.
Example 5:
|
|
|
|
|
No Condition Flags are set (all FALSE). C:\PLB\NEWDATA was created since it did not already exist as a file or directory.
Example 6:
|
|
|
|
|
The OVER Condition Flag is set because the given path (C:\PLB\PROG) already existed as a directory (same error would have occurred if it had been a file).
Example 7:
|
|
|
|
Since C:\PLB\TESTDATA exists, it is deleted only if it is empty (no files or subdirectories contained therein) and no Condition Flags are set. However, if it contained files or subdirectories that had not been previously deleted, it is not deleted, even though a valid path, and the OVER Condition Flag is set.
Example 8:
|
|
|
|
|
The OVER Condition Flag is set. C:\PLB\DUMMY does not exist.
Example 9:
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
These examples show PATH instructions executed at the Data Manager.
|
|