472,145 Members | 1,607 Online
Bytes | Software Development & Data Engineering Community
Post +

Home Posts Topics Members FAQ

Join Bytes and contribute your articles to a community of 472,145 developers and data experts.

Calling Concurrent Program from UNIX

2,367 Expert 2GB
There is always a requirement that in Oracle Applications, the Concurrent Program need to be execute programatically based on certain conditions/validations:

Concurrent programs can be executed programatically either from UNIX or Oracle PLSQL. In this Section, I will be explaining about calling a Concurrent program from UNIX using the CONCSUB Command.


1. Concurrent Program should be registered in oracle Applications before you can call the same from UNIX using the CONCSUB Command

CONCSUB Utility:

Syntax of CONCSUB utility is shown below:

Expand|Select|Wrap|Line Numbers
  2. CONCSUB <APPS username>/<APPS password> \
  3. <responsibility application short name> \
  4. <responsibility name> \
  5. <Oracle Applications username> \
  6. [WAIT=N|Y|<n seconds>] \
  8. <program application short name> \
  9. <program name> \[PROGRAM_NAME=”<description>”]\
  10. [REPEAT_TIME=<resubmission time>] \
  11. [REPEAT_INTERVAL= <number>] \
  12. [REPEAT_INTERVAL_UNIT=< resubmission unit>] \
  13. [REPEAT_INTERVAL_TYPE=< resubmission type>] \
  14. [REPEAT_END=<resubmission end date and time>] \
  15. [START=<date>] \
  16. [IMPLICIT=< type of concurrent request> \
  17. [<parameter 1> ... <parameter n>]
Note that the Slash "\" used at the end of each line is Unix Line Continuation Character and not all operating system support "\". If the Continuation Line Character is not supported in Unix, then provide all the parameter values in a single line seperated with Spaces to CONCSUB Command.

Most of the Input Parameters to the CONCSUB Command is SELF-Explanatory. Though let me provide brief description of the INPUT Parameters of CONCSUB Command:

<username/password> Required. The ORACLE username and password that provides access to the data that your program uses.

<responsibility application short name> Required. The application short name of the responsibility whose concurrent processing options you want to use.

<responsibility name> Required. The name of your responsibility. If the name of your responsibility includes spaces, enclose that name in double quotes.

<username> Required. The uppercase username of the application user whose concurrent processing options you want to use.

<WAIT> Optional. A flag that indicates whether to wait for the submitted request to complete. If you leave this parameter out, the default value of N makes CONCSUB return you to the operating system prompt without waiting for your request to complete.

Set WAIT=Y to have CONCSUB check the request status every 60 seconds and return you to the operating system prompt when your request is completed. You can also enter an integer value for a number of seconds, as in WAIT=30, for CONCSUB to check for request completion every <number> seconds.

<CONCURRENT> Required. A flag that separates the program–specific parameters from the operating system parameters.

<program application short name> Required. The application short name of your concurrent program.

<program name> Required. The uppercase name of your program. It must be the short name that you enter in the Concurrent Programs window when defining a concurrent program.

<PROGRAM_NAME> Optional. A descriptive name for your program. The program field on the View Requests form displays this as the user–friendly program name. The concurrent program short name passed to CONCSUB is often hard for end users to understand, so the PROGRAM_NAME parameter allows you to pass a more easily remembered name for your concurrent program. If you do not specify a PROGRAM_NAME, the View Requests form displays the user–friendly program name specified in the Concurrent Programs window.

You may also use the PROGRAM_NAME parameter to indicate the batch that your request processes for programs that process a set of data, where there could be several requests for a given program that are active at the same time.

<REPEAT TIME> Optional. The time of day to resubmit the request. The format for the time is HH24:MI or HH24:MI:SS. For example, REPEAT_TIME=14:30 resubmits your request daily at 2:30 p.m.

<REPEAT_INTERVAL> Optional. The interval between resubmission (a positive integer or real number). Use this parameter along with REPEAT_INTERVAL_UNIT to specify the time between resubmissions.

<REPEAT_INTERVAL_UNIT> Optional. The unit of time used for the interval between resubmissions. The available units are MINUTES, HOURS, DAYS or MONTHS. Use this parameter along with REPEAT_INTERVAL to specify the time between resubmissions. For example, setting REPEAT_INTERVAL=12 and REPEAT_INTERVAL_UNIT=HOURS resubmits your request every twelve hours. The default value is DAYS.

<REPEAT_INTERVAL_TYPE> Optional. Whether to time the resubmission interval from the requested start time of the request or from its completion. Set this parameter either toSTART or END. The default value is START.

<REPEAT_END> Optional. The date and time to stop resubmitting the concurrent request. Use one of the following for the format of the end date:
’”DD–MON–RR HH24:MI:SS”’ (as in ’”07–APR–02 18:32:05”’)
or ’”DD–MON–RRRR HH24:MI:SS”’ (as in ’”07–APR–2002 18:32:05”’)
Note that because this date format includes a space, you must enclose the date in double quotation marks and single quotation marks. You can also specify just the date: ’DD–MON–RR’

<START> Optional. A start date and time for your program in this format: ’”DD–MON–RR HH24:MI:SS”’ (as in ’”07–APR–02 18:32:05”’)

Because this date format includes a space, you must enclose the date in double quotation marks and single quotation marks. If you do not specify a start time, your program submits immediately and is processed by the next available concurrent manager. The default value is the current time.

<IMPLICIT> Optional. Whether to show this concurrent request on the View Requests form. Specify NO, YES, ERROR or WARNING. The value IMPLICIT=NO allows the request to appear on the View Request form. The default value is NO. The value IMPLICIT=YES means that only the System Administrator’s privileged View Concurrent Requests form displays this request. Use this value if the request is not interesting to the user. Specify IMPLICIT=ERROR or IMPLICIT=WARNING, respectively, if you want the request to appear only if it fails or completes with warnings.

<REPEAT_DAYS> Optional. The number of days after which to repeat the concurrent request, calculated from the last requested start date. The number can be a positive integer or real number. For example,
REPEAT_DAYS=1.5 resubmits your request every 36 hours.

<parameter 1> ...<parameter n> Optional. Your program–specific parameters. If a parameter includes spaces, enclose that parameter in double quotes, then in single quotes. If a parameter contains a double quotation mark as part of the argument, precede that mark with a backslash [\].
Dec 22 '09 #1
0 13014

Post your reply

Sign in to post your reply or Sign up for a free account.

Similar topics

9 posts views Thread by Jon Slaughter | last post: by
6 posts views Thread by David | last post: by
1 post views Thread by notregister | last post: by
reply views Thread by Sam | last post: by
11 posts views Thread by Emmanouil Angelakis | last post: by
2 posts views Thread by John Wright | last post: by
reply views Thread by Saiars | last post: by

By using Bytes.com and it's services, you agree to our Privacy Policy and Terms of Use.

To disable or enable advertisements and analytics tracking please visit the manage ads & tracking page.