Troubleshooting
Problem
This document intends to clarify what symbolic links are supported using the QFileSvr.400 file system.
Resolving The Problem
This document intends to clarify what symbolic links are supported using the QFileSvr.400 file system.
http://www.ibm.com/support/knowledgecenter/ssw_ibm_i_73/ifs/rzaaxrfsfs.htm?lang=en
The document located at the URL above states:
"The QFileSvr.400 file system supports only one link to an object. Symbolic links cannot be created or stored in QFileSvr.400. However, files in QFileSvr.400 can be accessed by using a symbolic link from the "root" (/), QOpenSys, or user-defined file systems."
In other words, the QFileSvr.400 file system does not support creating or accessing symbolic links on remote systems. The QFileSvr.400 file system can be accessed using a symbolic link on the local file system.
Consider SystemA, SystemB, and SystemC:
On SystemA:
| Example 1. | ADDLNK OBJ('/QFileSvr.400/SystemB') NEWLNK('/LinkToB') This is supported because it is only creating a symbolic link to QFileSvr.400. |
| Example 2. | WRKLNK '/LinkToB' This is supported. |
| Example 3. | ADDLNK OBJ('/home') NEWLNK('/QFileSvr.400/SystemB/invsymlnk') This is not supported. It is attempting to create a symbolic link in QfileSvr.400. It may generate the following error: Message ID . . : CPFA0AD Message . . . . : Function not supported by file system. Cause . . . . . : An attempt was made to use a function which was not supported by the file system for path /home. The path selected may not be valid for the function, or it may not be in the same file system. Recovery . . . : Check the path name for accuracy. You may need to use another path for the operation. Check the job log for possible additional messages. |
| Example 4. | WRKLNK '/QFileSvr.400/SystemB/SymbolicLink') Assume "SymbolicLink" on SystemB is mapped to '/QNTC/SystemC" This is not supported. Informal testing has shown that, if executing WRKLNK '/QFileSvr.400/SystemB/*' on SystemA and the TYPE for "SymbolicLink" is "SYMLNK->DIR", displaying "SymbolicLink" will succeed. However, If the TYPE is "SYMLNK", it is likely to fail. The difference in behavior is due to whether SystemA already has directory "/QNTC/SystemC" created and accessible or not. The path that the file system operation will use in Example 4 is an absolute path. The paths are not concatenated from system to system. For example, the following path is not generated: /QFileSvr.400/SystemB/QNTC/SystemC Another cause of unpredictable behavior when accessing symbolic links using QFileSvr.400 is the TCP/IP network configuration. Specifically, if the LOOPBACK interface is the first hop, that will influence what symbolic links are resolved to. |
For these reasons, accessing symbolic links using QFileSvr.400 is not supported.
Historical Number
518608568
Was this topic helpful?
Document Information
Modified date:
11 November 2019
UID
nas8N1013087