Mounting file systems

IBM® Integration Bus requires several directories to be defined on the file system at run time.

About this task

++HOME++ is the location of the environment file (ENVFILE) used to create the runtime environment in which IBM Integration Bus runs.

++INSTALL++ refers to the IBM Integration Bus installation directories.

++COMPONENTDIRECTORY++ is the location where all deployed configuration is written to and read from by the IBM Integration Bus runtime libraries.

++JAVA++ is the location of the Java™ installation.

++MQPATH++ is the location of theIBM MQ installation.

Because IBM Integration Bus can run in a shared file system sysplex environment, it is important for performance reasons that these directories are mounted locally to the LPAR in which IBM Integration Bus is started. This is particularly important for startup performance; if the IBM Integration Bus installation directories are not mounted locally, startup times can increase significantly.

You can check file system ownership from USS using the command df -v. For example, the following output shows that the IBM Integration Bus installation file system is owned by MVS1:
  /usr/lpp/mqsi/V9R0M0:>df -v .
  Mounted on     Filesystem                Avail/Total    Files      Status
  /usr/lpp/mqsi/V9R0M0 (OMVS.PLEXS.MQSI.V800.WBIMB) 7984/806400    4294966503 
  HFS, Read/Write, Device:89, ACLS=Y
  File System Owner : MVS1        Automove=Y      Client=N
  Filetag : T=off   codeset=0
To create a directory in an already mounted file system use the mkdir command. For example:
 mkdir -p /mqsi/brokers/integrationNodeName

To mount a new file system, follow the instructions given in the z/OS UNIX System Services Planning manual.

From USS, use the following instructions:
 mkdir -p /mqsi/brokers/integrationNodeName
 mount -f MQSI.BROKER.integrationNodeName /mqsi/brokers/integrationNodeName 
From TSO, use the following instructions:
 FREE DATASET('MQSI.BROKER.integrationNodeName')
The preceding ALLOCATE command is an example; the dataset should be allocated the correct amount of storage as described in IBM Integration Bus system requirements.

IBM Integration Bus on z/OS® does not support the configuration of a shared file system for multiple integration nodes on different LPARs.

Access to a z/OS integration node configuration store is protected by operating system semaphores, which are shared memory constructs designed only for inter-process communication. An attempt to access the shared configuration store from one LPAR, by using an mqsi command for example, can result in it trying to access state information that reflects the memory of a different LPAR. Such an action can lead to failure to obtain the locks, corruption of the persisted state in the semaphore files, and subsequent abends in either the command process, or the active process on the other LPAR.