36 IBM Content Manager OnDemand Guide
/SM590000INLLIBL 
/SM590000LOG 
/SM590000LOGCLPGM 
/SM590000INQMSGRPY 
/SM590000JOBMSGQMX 
/SM590000JOBMSGQFL 
For example, if you want to change the job queue that instance TEST uses, you create a job 
description that is called TEST in the TEST library that specifies the job queue that you want to 
use. 
To change the run priority of the server jobs, you must add a routing entry to the subsystem. 
The server job is always submitted with routing data QRLMSERVER. 
To change the run priority of all server jobs for all instances to 40, add the following routing 
entry to subsystem QSYSWRK. (Y ou must choose a sequence number (SEQNBR) that is not 
already in use.) 
ADDRTGE SBSD(QSYSWRK) SEQNBR(1841) CMPVAL(QRLMSERVER) PGM(QSYS/QCMD) 
CLS(QSYS/QSYSCLS40) 
After you make this change, you must stop and restart all of your servers. 
Automatically starting instances 
To enable an instance to start automatically each time that the system restarts, you must add 
one of the commands that are described in 2.4.3, “Starting and stopping servers” on page 33 
to your QSTRUP program. Y ou can also add the commands to a job scheduler. 
2.5  Implementing a Content Manager OnDemand instance on 
z/OS
Instances on z/OS do not differ greatly from instances on Multiplatforms. The concept is the 
same. In this section, we explain how to set up a new instance and provide background 
information about the UNIX System Services implementation. Always refer to the product 
documentation of your release for the specific steps to follow.
Before you set up your z/OS instance of Content Manager OnDemand, understand the 
different types of configurations and the components that make up the Content Manager 
OnDemand instance. A source for determining this information is the IBM Content Manager 
OnDemand for z/OS - Introduction and Planning Guide, SC19-365.
Instances are logical implementations for the separation of administration functions, users, 
and data on the same server. Instances have the same physical access to the program 
libraries, but they have different databases with a separate system log and separate file 
systems. Instances are typically used to separate different customers on one z/OS server to 
separate the test and production environments, or to use different code pages on different 
databases. 
A Content Manager OnDemand instance on a z/OS server is a separately started task 
(ARSSOCKx) that uses different databases, users, and application groups. Every user on the 
instance must be defined for the instance. Every instance has its own security if internal 
security is used. If an external security exit is used, it is common over all of the instances.
Figure 2-6 on page 37 shows an overview of the single instance on z/OS.