File system on HP Integrity NonStop Server

Before you install the IBM MQ client for HP Integrity NonStop Server, make sure that the file system is set up correctly.

Review Hardware and software requirements on HP Integrity NonStop Server systems to make sure that you understand the approximate amount of disk space in the OSS and Guardian file systems that is required for an installation. The OSS file set that is used for the installation requires enough free space for the installation files and the files you create in the installation. The Guardian volume that we use for installation does not require auditing.

Work with the systems administrator to verify the OSS file set and Guardian file system storage requirements, at least for an initial estimate of the storage. The best way to determine more precisely how much storage you would eventually need in production is to produce a prototype configuration and model the message storage requirements, scaling up as necessary for the production system.

OSS file system objects

For the OSS file system objects, this section concentrates on the differences between the HP Integrity NonStop Server installation, and the standard UNIX installation. Multiple independent installations are supported.

The opt and var trees must be present in a common root directory, which is selected at installation time. The opt tree contains files that do not change. For example, this tree contains program, library, dll, header files, and "static" data files. The var tree contains files that might change, and do hold status about the installation itself. Examples of files that this tree holds are configuration files, and log files.

Both the opt and var directories contain a single directory named mqm. The content of both trees is rooted in the opt/mqm and var/mqm directories.

Directory	Purpose	Contents
bin	Contains the OSS programs and libraries for an installation	G is a symbolic link file that locates the Guardian installation subvolume amq* files, containing the product executables for the client lib* files, containing product dll files Files containing control commands, and other utilities and scripts
inc	Contains the header files for building IBM MQ applications	.h files, which are C language header files .tal files which are pTAL header files .cpy files which are COBOL copy file cobcpy32 and cobcpy64 directories for the individual COBOL copy files
lib	Contains the import libraries needed to link applications	G is a symbolic link file that locates the Guardian installation subvolume amq* files, containing product dll files iconv is a directory that contains data conversion tables lib* files, which are product dll files mqicb used for supplying to a CONSULT directive for compiling COBOL programs
license	Contains text versions of the IBM License for the IBM MQ client for HP Integrity NonStop Server, which is translated into each supported national language	Lic_.txt files, which are the individual national language translations of the license. notices.txt is a file that contains any additional license terms from non-IBM software that is included with IBM MQ, if any.
mq.id	Single file that contains information about the build level and installation package	All contents in this directory might be used by IBM Support personnel.
msg	Contains globalization files for use by IBM MQ, in logging and displaying output in the supported national language translations	The contents include: amq.cat globalization message catalog currently in use by the installation, created by the OSS utility "gencat" amq.msg unprocessed globalization data that is used as input by gencat to create the catalog Other minor files and directories that support the different translations
samp	Contains sample code and executables to illustrate the use of IBM MQ	*.cbl sample COBOL language source files *.c sample 'C' language source files *.tal sample pTAL language source files ccsid.new backup file of ccsid.tbl ccsid.tbl file that contains a table of supported CCSIDs *.ini sample configuration files java directory that contains source for sample Java applications jms directory that contains source for sample JMS applications bin directory that contains executable versions of the samples dlq directory that contains a source for the sample Dead Letter Queue Handler preconnect directory that contains source for preconnect exit

For more information about the samples that are provided, see Samples for the IBM MQ client for HP Integrity NonStop Server.

Directory	Purpose	Contents
conv	Contains data conversion files	Binary data that supports the data conversion function for IBM MQ
errors	Contains installation-wide error logs and FDC files	Standard content, for example: AMQERR01.LOG - current system-wide error log file AMQERR02.LOG - previous system-wide error log file AMQERR03.LOG - oldest system-wide error log file *.FDC FFST files
exits	Stores DLLs containing exit code that is loaded by the queue managers in the installation	This file is empty at installation
log	Contains log files for recording and controlling units of work	Standard content
mqs.ini	The installation configuration file	Standard content
qmgrs	Directory beneath the location where all of the queue manager directories are created	Standard content
sockets	Directory tree that contains various queue manager control files	Standard content
trace	Defined location to which trace data is written by IBM MQ	Standard content

Guardian installation subvolume

The Guardian single installation subvolume contains both the programs and libraries needed at runtime.

File	Description
AMQINST	Internal file that describes installation configuration
AMQS*	Samples that are built for Guardian
B*SAMP	Sample build files for the various supported languages
CMQ*	Header files for the various supported languages, where files ending in: h are C headers T are pTAL headers L are COBOL headers
MQ*	Product libraries
MQS*C	Sample C language source files
MQS*T	Sample pTAL language source files
MQS*L	Sample COBOL language source files

Control commands are also included, for a list, see IBM MQ client for HP Integrity NonStop Server client commands.

Parent topic: Plan your client installation on HP Integrity NonStop Server