a_cm_long_reqs.sql

	Prints concurrent requests that ran for over "X" minutes.
	Calls analyzereq.sql that can analyze conc request of your choice.

a_conc_cleanup.sql

     Resets concurrent managers/processes.
	Use if you killed any of the FND processes.
    

a_conc_man.sql

	Prints concurrent managers and
	allows drilldown to running requests

a_conc_man_prog_R11.sql

	Reports program names for a given concurent
	manager based on the library link

a_conc_reqd.sql

     Prints concurrent request ID, ORA_PID, ORA_SID
	log and output files for a given APPS REQid
    

a_conc_reqs_by_user.sql

	ALL APPS Conc requests by USERNAME and/or PROGRAM
	sorted by date DESC
    

a_conc_reqsch.sql

	11i: reports all pending and running requests from
	FND_CONCURRENT_REQUESTS table with details of USER
	START TIME, ARGS and PROG NAME.  Allows to limit the
	list to a certain PROGRAM.
    

a_ses_by_pid.sql

	** SHOULD BE RUN AS APPS **
	Reports the following:
	----------------------
	- session detail from v$session, v$process
	   by PID (from backend).
	- any running requests from apps.FND_CONCURRENT_REQUESTS
	   output includes REQ_ID, Phase, Status, O-PID, A-PID, OUT File
	- calls analyzereq.sql to print details of a REQ_ID
	NOTE:
	   to link request id to a session use one of the following
	      o fnd_concurrent_requests.oracle_session_id = v$session.audsid
	      o fnd_concurrent_requests.oracle_process_id = v$process.spid
	        (v$process.addr = v$session.paddr)
	      o fnd_concurrent_requests.os_process_id     = v$session.process
    

analyzereq.sql

--
--      analyzereq.sql
--      Analyze a concurrent request
--
--      USAGE: sqlplus apps_user/apps_passwd @analyzereq request_id
--      EX:    sqlplus apps/apps @analyzereq 304504
--