NonStop JMS User's Manual (H06.03+, J06.03+, NonStop JMS 3.0+)

NSJMS Installation and Configuration for TNS/R
NonStop Server for Java Message Service User’s Manual—522356-006
2-9
Install and Configure NSJMS
volume.subvol of the existing or newly created SQL catalog specified in Step
7 on page 2-8. For example:
Change:
VOLUME;
To:
VOLUME $volume.subvol;

If the NSJMS SQL tables reside on a different subvolume than the SQL
catalog, using an editor of your choice, add the SQL catalog location to the
/usr/tandem/nsjms/version/creatsql file by adding a CATALOG
command referring to the catalog from Step 7 on page 2-8, and update the
VOLUME command to refer to the volume.subvol where the database tables
will reside. For example:
Change:
VOLUME;
To:
CATALOG $volume1.subvol1
VOLUME $volume2.subvol2
9. Use this command to create the NSJMS SQL tables. For example:
10. Update the Property Files:
a. Using an editor of your choice, update these properties in the
nsjms.properties file:
1. Set the Deadmsg.deletecount property value to 100. For example:
Deadmsg.deletecount=100
2. Set the Database.volsubvol property to the location of the NSJMS
SQL tables from Step 8
on page 2-8. For example:
Database.volsubvol=$volume.subvol
The nsjms.properties file is described on page 2-12 and contains
properties that are used to configure NSJMS. The property values are read by
the NSJMS implementation once during startup.
b. If the JNDI objects will be stored in a directory other than the default directory
(file:////usr/tandem/nsjms/version/jndi_object_store), using an
OSH: gtacl -p sqlci < creatsql
Note. Database tables, by default, support a maximum of 2 gigabytes (GB) on each
partition. If larger partitions are required, use the FORMAT2ENABLED attribute when
creating the tables. For information about using the FORMAT2ENABLED attribute within
the CREATE TABLE statement, see the SQL/MP Reference Manual.