Document Type | Troubleshooting
Category | Monitoring/Inspection
Applicable Product Versions | 6FS05, 6FS06, 6FS07, 6FS07PS, 7FS01, 7FS02, 7FS02PS
Document Number | TMOTS031
Issue
In a TAS environment, when archive log files do not exist, executing ls on the archive ds (disk space) path results in the following no such path (rc=-19) message.
ASCMD> cd archive current path = +DS/archive ASCMD> ls <File_name> log-t0-r0-s5.arc - Number of files found: 1 ASCMD> rm log-t0-r0-s5.arc rm complete: +DS/archive/log-t0-r0-s5.arc --> archive deleted ASCMD> ls ERROR: no such path '+DS/archive/' (rc=-19)
Cause
In the TAS environment, when creating files in disk space, the entire path string is recognized as a single filename.
For example,
+DS0/test path with a file named testfile, TAS treats it as a single filename +DS0/test/testfile.TBASCMD is a command tool provided to allow users to query disk space information, check, and manage stored files through simple commands.
This tool receives the file list from TAS, analyzes the path, and presents it to users in a structured format as if a directory hierarchy exists.
Therefore, if all DB files under a specific directory are deleted, files including that path no longer exist on TAS, and
TBASCMD will also show that directory as if it has automatically disappeared, which is normal behavior.However,
mkdir created directories manually may still appear in path queries even if they contain no files.Solutions
In the TAS environment, before archive log files are created, it is normal to receive a no such path error when executing ls on the archive disk space path.
After archive log files are created, you can confirm that executing ls on the archive disk space path returns results normally as shown below.
ASCMD> ls <File_name> log-t0-r0-s6.arc Number of files found: 1