named STRTCPSVR to further control the behavior of the ENDTCPSVR command. Create the data area as described in “Starting the servers” on page 37. For more information about the data area, see IBM Content Manager OnDemand for iSeries - Administration Guide , SC41-5325. Even though the data area is named STRTCPSVR, it controls both the STRTCPSVR and ENDTCPSVR commands. This is by design so that *DFT starts and ends the same instance. Without the STRTCPSVR data area, the values of *DFT and *ALL work identically. All instances that are active are ended. You can also specify the name of a single instance to end, for example: ENDTCPSVR SERVER(*ONDMD) INSTANCE(ONDTEST) With the data area, the value of *DFT ends only the instance that is named in the data area. The data area must be named STRTCPSVR and in library QUSRRDARS . Running STRTCPSVR start *DFT *ALL *AUTOSTART Named instance Without the data area All instances set to autostart All instances configured on the system All instances set to autostart The named instance With the data area Only the instance named in the data area All instances configured on the system All instances set to autostart The named instance
40 IBM Content Manager OnDemand Guide Table 2-2 summarizes the behavior of the ENDCPSVR command with and without the data area. Table 2-2 Behavior of the ENDCPSVR command with or without the data area Server work management Server jobs are started by using a job description with the name of the instance (which must be found in the instance library). If a job description with that name is not found in the instance library, then job description QOND400 in library QRDARS is used (and can be changed if necessary). The job description controls the following attributes of the server job: JOBQ JOBPTY OUTPTY PRTDEV OUTQ INLLIBL LOG LOGCLPGM INQMSGRPY HOLD DATE SWS JOBMSGQMX JOBMSGQFL 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 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. Running ENDCPSVR ends *DFT *ALL Named instance Without the data area All active instances All active instances The named instance With the data area Only the instance that is named in the data area All active instances The named instance
Chapter 2. Setting up a Content Manager OnDemand instance 41 To change the run priority of all server jobs for all instances to 40, you could add the following routing entry to subsystem QSYSWRK. (You 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 making this change, you must stop and restart all your servers.
You've reached the end of your free preview.
Want to read all 536 pages?
- Winter '16
- Willy Brown
- Test, Enterprise content management, IBM System i, Content Manager, Content management system, IBM Content Manager OnDemand