Controlling the Internal Concurrent Manager from the Operating System (User, System Administrator, and Flexfields Help)


	Previous	Next		Contents	Index	Navigation	Glossary	Library

Controlling the Internal Concurrent Manager from the Operating System

There are two commands you may use from the operating system to control the Internal Concurrent Manager: STARTMGR, which starts the Internal Concurrent Manager; and CONCSUB, which can be used to deactivate or abort the Internal Concurrent Manager, or to instruct the Internal Concurrent Manager to verify the operating system process for each individual manager.

Table 1 - 20 compares the Internal manager control states displayed by the Administer Concurrent Managers form with their corresponding operating system command. Not all arguments are shown.

Controlling the Internal Manager from the OS

From the Administer Concurrent Managers Form From the Operating System (not all arguments shown)

Activate concurrent manager STARTMGR (syntax may vary with platform)

Verify concurrent manager status CONCSUB FND VERIFY

Deactivate concurrent manager CONCSUB FND DEACTIVATE

Terminate requests and deactivate manager CONCSUB FND ABORT

Table 1 - 20. (Page 1 of 1)

From the Administer Concurrent Managers Form	From the Operating System (not all arguments shown)

Activate concurrent manager	STARTMGR (syntax may vary with platform)
Verify concurrent manager status	CONCSUB FND VERIFY
Deactivate concurrent manager	CONCSUB FND DEACTIVATE
Terminate requests and deactivate manager	CONCSUB FND ABORT
Table 1 - 20. (Page 1 of 1)

Starting the Internal Concurrent Manager from the Operating System

To start the concurrent managers, you can invoke the STARTMGR command from your operating system prompt. This command starts the Internal Concurrent Manager, which in turn starts any concurrent managers you have defined.

You must have write privileges to the "out" and "log" directories of every application so that the concurrent managers can write to these directories. You can start the concurrent managers with many different options. An option on some operating systems is to send an electronic mail note to a given user when the concurrent managers shut down. See your installation guide for a discussion of this command.

See: Oracle Applications Installation Guide for your operating system

Use the STARTMGR command:

during installation of Oracle Applications

after you shut down the concurrent managers

after MIS restarts the operating system

after the database administrator restarts the database

The STARTMGR command is platform-dependent, so refer to your Oracle Applications Installation Guide for the specific syntax to use.

See: Concurrent Managers - Appendix: System Reference Material, Oracle Applications Installation Guide for your operating system

The STARTMGR command takes up to ten optional parameters.

Each parameter except PRINTER has a default.

You can modify the STARTMGR command and your environment to set your own defaults.

Enter the following command at your system prompt to start the Internal Concurrent Manager:

$ startmgr  <optional parameters>

You can pass the parameters in any order. For example:

$ startmgr sysmgr="applsys/fnd"  mgrname="std" 
 printer="hqseq1"  mailto="jsmith"  restart="N" 
 logfile="mgrlog"  sleep="90"  pmon="5"  quesiz="10"

Viewing the Internal Concurrent Manager startup parameters

The Internal Concurrent Manager's log file displays startup parameter values executed by the STARTMGR command. An example is shown below. You cannot change the parameter values.

	logfile=/fnddev/fnd/6.0/log/FND60.mgr  (path is port-specific)
	PRINTER=hqunx138  
	mailto=appldev  
	restart=N    
	diag=N   
	sleep=60 (default)  
	pmon=20 (default)    
	quesiz=1  (default)

Shutting down the Internal Concurrent Manager from the Operating System

From the operating system prompt, you can use the CONCSUB utility to submit a concurrent request, under the SYSADMIN username and the System Administrator responsibility.

The CONCSUB utility submits a concurrent request and returns you to the operating system prompt. You must wait until the concurrent request completes.

To check on the status of your concurrent request, use the Concurrent Requests form.

CONCSUB applsys/pwd 'Responsibility application shortname'
 'Responsibility name' 'Username' [WAIT={Y|N|n}] CONCURRENT
 'Program application shortname'  PROGRAM

Parameters

applsys/pwd	The ORACLE username and password that connects to Oracle Application Object Library data.
Responsibility application shortname	The application shortname of the responsibility. For the System Administrator responsibility, the application shortname is SYSADMIN.
Responsibility name	The name of the responsibility. For the System Administrator responsibility, the responsibility name is System Administrator.
Username	The application username of the person who submits the request. For example, SYSADMIN is the username of the System Administrator.
WAIT={Y\|N\|n}	Set WAIT to Y if you want CONCSUB to wait until the request you submitted completes before CONCSUB returns you to the operating system prompt.
	Set WAIT to N (the default value) if you do not want CONCSUB to wait.
	You can also enter an integer value of n seconds for CONCSUB to wait before it exits.
	When used, WAIT must be entered before CONCURRENT.
Program application shortname	The application shortname of the program. For the DEACTIVATE, ABORT, and VERIFY programs, the application shortname is FND.
PROGRAM	To submit the Shutdown All Managers concurrent request, use the program DEACTIVATE.
	To submit the Shutdown Abort Managers concurrent request, use the program ABORT.
	To submit the Verify All Managers Status concurrent request, use the program VERIFY.

Example Syntax using CONCSUB

CONCSUB <Username/Password> SYSADMIN 'System Administrator'
 SYSADMIN  CONCURRENT FND DEACTIVATE

CONCSUB <Username/Password> SYSADMIN 'System Administrator'
 SYSADMIN  CONCURRENT FND ABORT

CONCSUB <Username/Password> SYSADMIN 'System Administrator'
 SYSADMIN  CONCURRENT FND VERIFY

Using CONCSUB to shut down your managers

Use CONCSUB to shut down the concurrent managers:

before MIS shuts down the operating system

before the database administrator shuts down the database

when you want concurrent manager and concurrent program definitions to take effect

Then, use the STARTMGR command to restart the Internal Concurrent Manager, which starts the concurrent managers.

Example - nightly shutdown using CONCSUB

You can use the token WAIT with value Y ( WAIT=Y ) if you want to use CONCSUB to issue a concurrent request from within a shell script containing a sequence of steps. Using the token WAIT insures the managers deactivate, abort, or verify status before the shell script proceeds to the next step.

See: Controlling the Internal Concurrent Manager from the Operating System

1. Shell script customized for specific operating system starts.

CONCSUB applsys/pwd SYSADMIN 'System Administrator' SYSADMIN WAIT=Y CONCURRENT FND DEACTIVATE

When the shell script passes control to CONCSUB, CONCSUB waits until the program DEACTIVATE is complete before it returns control to the shell script.

3. Script issues the command to shut down the database.

4. Script issues the command to backup the database.

5. Script issues the command to startup the database.

$ startmgr sysmgr="applsys/fnd" mgrname="std" printer="hqseq1" mailto="jsmith" restart="N" logfile="mgrlog" sleep="90" pmon="5" quesiz="10"

The shell script passes control to STARTMGR, which starts up the Internal manager (and all the other managers).

7. Shell script completes.

Hiding the password using CONCSUB

If username/password are still supplied, the CONCSUB utility will work as usual.

If username only is supplied (no '/pwd' in the first argument), it will prompt you for the password:

ORACLE Password:

The echo is turned off. For example, the command below does not include the ORACLE Password.

CONCSUB applsys SYSADMIN 'System Administrator' SYSADMIN
 CONCURRENT FND
FNDMNRMT Y 0 20221
ORACLE Password:
Submitted request 32157 for CONCURRENT FND FNDMNRMT Y 0 20221

Now, the first argument has to be the application username as usual (for example, SYSADMIN).

The user can put the password in a file, and then redirect it to standard input (stdin). In UNIX the command would be executed as follows:

CONCSUB applsys SYSADMIN 'System Administrator' SYSADMIN
 CONCURRENT FND
FNDMNRMT Y 0 20221 < password.file

where password.file is an ASCII file that contains the password. This method is recommended for use in shell scripts or batch processes.