(From a program.) GOOD: When you execute a CREATE.FILE and the file does not exist in the VOC nor in the underlying OS, the file is created.
GOOD: When you execute a CREATE.FILE and tile file does exist in both the VOC and in the underlying OS, the file create is ignored and the program continues, no harm no foul. GOOD. GOOD: When you execute a CREATE.FILE and a VOC exists which is NOT a file, an error is reported and the process fails. PROBLEM: When you execute a CREATE.FILE and the VOC exists as an F/DIR/LD/Q pointer but there is no underlying OS file, the process fails. Likewise if the underlying OS exists and there is no VOC pointer to it, the process fails. The CREATE.FILE could be smart enough to recognize these latter two situations and rectify them: CREATE.FILE finds a VOC but no underlying file - delete the VOC and create fresh. CREATE.FILE finds an underlying file but no VOC pointer - create the VOC pointer to the existing file. Ideally it will stop and report what is happening and ask, but there could be a FORCE type option that did not stop for the question. Susan Joslyn ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
