You configure a single instance of Content Manager OnDemand by configuring the control files that are used to initialize and operate the server.
You can mount the Content Manager OnDemand installation directory at some point besides /usr/lpp/ars/V9R5M0. This support allows installations to run at different service levels. For example, SMP might be used to install into SERVICE/usr/lpp/ars/V9R5M0. SERVICE/usr/lpp/ars/V9R5M0 might be copied into /usr/lpp/ars/V9R5M0/alt for testing. When testing is complete, the /usr/lpp/ars/V9R5M0/alt might be copied into /usr/lpp/ars/V9R5M0 for production.
By default, programs started with JCL search /usr/lpp/ars/V9R5M0 and any subdirectories for files that are needed. For example, /usr/lpp/ars/V9R5M0/locale. To use an alternate location to locate these file, an ARSBIN DD statement might be specified that has the path for the Content Manager OnDemand bin directory. For example, //ARSBIN DD PATH='/usr/lpp/ars/V9R5M0/alt/bin'. This command causes Content Manager OnDemand to use, for example, the /usr/lpp/ars/V9R5M0/bin/alt/locale locale instead of the /usr/lpp/ars/V9R5M0 locale.
Programs started from a UNIX System Services shell locate necessary files relative to where they were invoked from. For example, running /usr/lpp/ars/V9R5M0/bin/arsdoc uses /usr/lpp/ars/V9R5M0/alt/locale.
Be careful if the Content Manager OnDemand bin directory is in the path. The relative location is determined based on where the UNIX System Services actually fetches the file. For example, if PATH=/usr/lpp/ars/V9R5M0/bin:/usr/lpp/ars/V9R5M0/bin and an unqualified command like arsdoc is used, the copy of arsdoc from /usr/lpp/ars/V9R5M0/alt/bin is fetched, even if the current working directory is /usr/lpp/ars/V9R5M0/bin. This causes arsdoc to use /usr/lpp/ars/V9R5M0/alt/locale. If the arsdoc from the current directory should be used, specify ./arsdoc.
This support requires that you copy the entire Content Manager OnDemand directory structure before you copy the executable files to random directories. For example, if /usr/lpp/ars/V9R5M0/alt/bin/arsdoc was copied to /u/fred/arsdoc, and /u/fred/arsdoc was executed, the /usr/lpp/ars/V9R5M0 directory is used for any necessary files, and unpredictable results might occur.
It is strongly recommended that all configuration directories be linked to the same directory, and that they use the same ars.ini file. This setup reduces the possible duplication of definitions. For example, both /usr/lpp/ars/V9R5M0/alt/config and /usr/lpp/ars/V9R5M0/config point to the same directory. The ars.ini file has two instances defined, ARCHIVE and TEST. The normal ARSSOCKD command uses the /usr/lpp/ars/V9R5M0 directory. The TEST ARSSOCKD PROC command has a PARM='TEST', and a //ARSBIN DD PATH='/usr/lpp/ars/V9R5M0/alt/bin'. Similarly, the ARSLOAD command used for production specifies a -h ARCHIVE in the parm or be omitted. The ARSLOAD command for test specifies a -h TEST parm, and have a //ARSBIN DD PATH='/usr/lpp/ars/V9R5M0/alt/bin'.