Take the following requirements into account when configuring WebSphere MQ
Everyplace for use with 4690.
- Terminal Applications are restricted to 24 char maximun path length, but
Store Controller Applications can have 127 chars. Java Apps may are
also restricted to the 24 length.
- The virtual file system (VFS) cannot hold greater than 64000 files.
With GB disk sizes being used, the C: drive may not have a limit on the
number of files, depending on your operating system.
- When you want to access a file, you must specify the path that leads to
it. The path consists of directory names that are separated by a
backslash character "\" or a forward slash "/".
- Note:
- Although your system accepts both the "\" and the "/" character, it is
probably less confusing to use one or the other.
- Examples elsewhere in this manual demonstrate how to configure your queue
manager such that the data describing its' resources, certificates, and
other configuration data is stored in files with long filenames. These
filenames are for a single top-level directory, which can also be located on
the VFS drive namespace.
- YUsing the 8.3 format, the total character length of the
fully-qualified filename exceeds the allowable limits imposed by the 4960
native file system. Therefore, in VFS :
- The maximum length of a filename is 256 characters.
- The maximum path length, including directories and files, is 260
characters.
- The maximum directory depth is 60 levels including the root
directory.
- WebSphere MQ Everyplace classes can be stored in long format names in
VFS. However, for performance and convenience, as there are lots of
class files, we would reccomend that the application and WebSphere MQ
Everyplace classes are packaged into a .jar files and deployed.
- According to the VFS manual "The operating system provides support for
file names greater than eight characters in length through the use of a 4690
Virtual File System (VFS)".
- The VFS manual states: "The VFS drive setting must be enabled
through system configuration. On enabling VFS drive settings, the
operating system creates two logical drives. C: and
D:. The drive determines where the VFS directory is
located. However, the information is actually stored on drives C:
and D:. Drive M: information is stored on drive C:,
and drive N: information is stored on drive D:. Once you
have enabled VFS, you can use drives M: and N: to provide long
file name support locally."
It is recommended that you use the MQeCaseInsensitiveDiskAdapter
on the 4690 OS. This class implements a disk adapter that is
insensitive to the 'case' of the filename used during
matching. Some JVM or OS combinations list files with different case to
that in which they were created. This means that the simple filtering
in the superclass ignores them. This class converts both the compator
and the comperand to lowercase before performing the comparison. This
ensures the best chance of finding a valid match. Note that the
conversion to lower case may be innapropriate on platforms where the case is
honoured, and where there are non-mqe files stored that could be confused by
case. In summary, as this adapter is more suited for use with the 4690
due its filesystem.
© IBM Corporation 2002, 2003. All Rights Reserved