The server was assigning a shared FILE library volume to a server or storage agent. Share FILE libraries require a matching number of directories in the PATH definition for the server or storage agent's access to FILE drives and the server's device class definition. For example, if the server has the following device class definition: DEFINE DEVCLASS SFILE DEVTYPE=FILE MOUNTL=10 SHARED=YES DIR=D:\DIR1,E:\DIR2,F:\DIR3 a FILE library name SFILE will be created along with 10 drives named SFILE1 to SFILE10 in shared library SFILE. Each of these drives might have scratch volumes created in directories D:\DIR1, E:\DIR2 or F:\DIR3. (For UNIX Platforms, substitute UNIX style names in the example).

For library clients and storage agents, the appropriate directory paths from those systems must be defined using the DEFINE PATH command. An example, in this case, might be DEFINE PATH STA1 SFILE1 SRCTYPE=SERVER DESTTYPE=DRIVE DIR=V:\DIR1,W:\DIR2,X:\DIR3 LIBRARY=SFILE which means that server (or storage agent) STA1 accesses directory D:\DIR1 using V:\DIR1 from the STA1 system, E:\DIR2 on the server is accessed using W:\DIR2 on STA1, and that F:\DIR3 is accessed using X:\DIR3 on STA1. If the number of directories between the PATH and DEVCLASS do not match, there could be problem in accessing the resulting file in the future.