All about Host Concurrent Programs

One of the things to remember while registering a host concurrent program is that the first five parameters are reserved by Oracle E-Business Suite for its own use. The sixth parameter onwards is used for user-defined concurrent program parameters. The first five parameters refer to the following:

$0: The shell script to be executed
$1: Oracle user/password
$2: Applications user_id
$3: Application user_name
$4: Concurrent program request_id

In addition to these, the environment variable FCP_LOGIN is also used to store the Oracle user/password. The steps required to register a shell script as a concurrent program are:

1. Create the shell script in the $APPLBIN directory of the specific application top. In this example, I have created the script under $CS_TOP/bin and named it myscr.prog(Oracle documentation mentions that the extension should be .prog). Its contents are listed below:


#!/bin/sh
echo 'Printing parameters....'
echo '0:'$0
echo '1:'$1
echo '2:'$2
echo '3:'$3
echo '4:'$4
echo '5:'$5

echo 'FCPLOGIN:'$FCP_LOGIN
echo 'Finished printing parameters.'

2. Define the concurrent executable with Execution Method ‘Host’. In the Execution File Name field, specify the name of the shell script without extension(‘myscr’ for this example)

3. Define the concurrent program with parameters as required. For this example, I have defined one parameter with default value ‘ABCDEF’

4. Add the concurrent program to a request group

5. Create a symbolic link to fndcpesr (which is located in the $FND_TOP/$APPLBIN directory) and give it the same name as the Execution File Name. The symbolic link is created in the same directory as the shell script.


[oracle@myapps bin]$ ln -s $FND_TOP/bin/fndcpesr myscr

Ensure that all files have execute permissions to prevent any ‘Permission denied’ errors. You should now be able to execute the concurrent program which in turn will run the shell script. Executing the concurrent program for this example results in a log file containing the following output. Note that the values of FCP_LOGIN, the reserved parameters and the user-defined parameter are all printed.

Printing parameters….
0:/u01/oracle/visappl/cs/11.5.0/bin/myscr.prog
1:APPS/APPS
2:1001530
3:EBUSINESS
4:2721361
5:ABCDEF
FCPLOGIN:APPS/APPS
Finished printing parameters.

Return codes for host concurrent program

If the script traps an error, use the UNIX exit command ‘exit 1’ to return failure (status code 1) to the Concurrent Manager running the program. Of course, code sections after the exit command will not be executed.


#!/bin/sh
echo 'Printing parameters....'
echo '0:'$0
echo '1:'$1
echo '2:'$2
echo '3:'$3
echo '4:'$4
echo '5:'$5

exit 1

echo 'FCPLOGIN:'$FCP_LOGIN
echo 'Finished printing parameters.'

The concurrent program will complete with status ‘Error’ and the log file will contain the following:

Printing parameters….
0:/u01/oracle/visappl/cs/11.5.0/bin/myscr.prog
1:APPS/APPS
2:1001530
3:EBUSINESS
4:2721405
5:ABCDEF
/u01/oracle/visappl/cs/11.5.0/bin/myscr
Program exited with status 1

There are no defined exit commands to return a warning status. However, it can be done by using the FND_CONCURRENT.SET_COMPLETION_STATUS API to set the completion status of the request to ‘Warning’. Gareth Roberts deserves a big ‘Thank You’ for posting this on Oracle Forums.


#!/bin/sh
echo 'Printing parameters....'
echo '0:'$0
echo '1:'$1
echo '2:'$2
echo '3:'$3
echo '4:'$4
echo '5:'$5

MYSTATUS=`sqlplus -s $1 &lt;&lt;!
SET HEADING FEEDBACK OFF PAGESIZE 0
declare
l_result boolean;
l_session_id number;
begin
fnd_global.INITIALIZE(l_session_id, null, null, null,null, -1, null, null, null, null, $4, null,null,null,null,null,null,-1);
l_result := fnd_concurrent.set_completion_status('WARNING','Review log file for details.');
commit;
end;
/
exit;
!`

echo 'FCPLOGIN:'$FCP_LOGIN
echo 'Finished printing parameters.'

This solution makes use of a SQL script to initialize a session with the request_id of the concurrent program using FND_GLOBAL.INITIALIZE and then sets the completion status. Upon execution, the concurrent program ends with a ‘Warning’ status and generates the following output:

Printing parameters….
0:/u01/oracle/visappl/cs/11.5.0/bin/myscr.prog
1:APPS/APPS
2:1001530
3:EBUSINESS
4:2721408
5:ABCDEF
FCPLOGIN:APPS/APPS
Finished printing parameters.

One important thing to notice is that echoing the parameters $1 and $FCP_LOGIN leads to the Oracle user/password being written to the log file. This can be prevented by using the options ENCRYPT and SECURE while defining the concurrent program. ENCRYPT signals the Concurrent Manager to pass the Oracle password in the environment variable FCP_LOGIN. The Concurrent Manager leaves the password in the argument $1 blank. To prevent the password from being passed, enter SECURE in the Execution Options field. With this change, Concurrent Manager does not pass the password to the program.

For this example specifying SECURE in the concurrent program options:

and then running the concurrent program does not set the completion status to ‘Warning’ since the Oracle user/password is not passed and the SQL script cannot run. This can be observed from the contents of the log file.

Printing parameters….
0:/u01/oracle/visappl/cs/11.5.0/bin/myscr.prog
1:APPS/
2:1001530
3:EBUSINESS
4:2721412
5:ABCDEF
FCPLOGIN:
Finished printing parameters.

If we set the options field in the concurrent program to ENCRYPT

then the Oracle user/password will be passed only to $FCP_LOGIN and not to $1. We can change the SQL script to use $FCP_LOGIN instead of $1 and execute the concurrent program. It will now complete with a ‘Warning’ status since the Oracle user/password was passed to the script through $FCP_LOGIN. This can be verified from the contents of the log file:

Printing parameters….
0:/u01/oracle/visappl/cs/11.5.0/bin/myscr.prog
1:APPS/
2:1001530
3:EBUSINESS
4:2721409
5:ABCDEF
FCPLOGIN:APPS/APPS
Finished printing parameters.

Note:

Use ${10}, ${11} instead of $10,$11 to refer to double-digit parameters
fndcpesr parses the arguments passed to the shell script. So if you don’t create the symbolic link to fndcpesr while registering the program, parameter values will not be parsed and passed automatically to the variables $0, $1, $2 etc. You will have to parse the individual parameters yourself (I think they are tab-separated).
The FND_GLOBAL.INITIALIZE procedure is used to set new values for security globals during login or when the responsibility is changed, it accepts the following parameters:

 session_id in out number,
 user_id in number,
 resp_id in number,
 resp_appl_id in number,
 security_group_id in number,
 site_id in number,
 login_id in number,
 conc_login_id in number,
 prog_appl_id in number,
 conc_program_id in number,
 conc_request_id in number,
 conc_priority_request in number,
 form_id in number default null,
 form_appl_id in number default null,
 conc_process_id in number default null,
 conc_queue_id in number default null,
 queue_appl_id in number default null,
 server_id in number default -1

Ramesh 7:34 pm on March 21, 2012

Its really useful Article…thank you..!
siva 6:28 am on August 30, 2012

good infor
Raju 7:59 am on November 16, 2012

Thanks for that {10} help.
życzenia urodzinowe śmieszne 3:18 am on April 26, 2013

Interesting blog! Is your theme custom made or did you download it from somewhere?

A theme like yours with a few simple tweeks would really make my blog jump
out. Please let me know where you got your design. Appreciate
it
sarunraj 1:55 am on April 8, 2014

good one!!
Pingback: Oracle APPS Shell Eş Zamanlı Programı İle Java Uygulaması
Ramya 7:39 pm on September 2, 2014

I have a issue.The $0 is displaying all the default parm values. Pls suggest workaround:

echo ‘Printing parameters….’
echo ‘0:’$0
echo ‘1:’$1
echo ‘2:’$2
echo ‘3:’$3
echo ‘4:’$4
echo ‘5:’$5
echo ‘FCPLOGIN:’$FCP_LOGIN
echo ‘Finished printing parameters.’
echo ‘FCP_USERID:’$FCP_USERID
————–

Printing parameters….
0:/u01/app/oracle/DEV/apps/apps_st/appl/xxabc/12.0.0/bin/xxabc
1:xxabc FCP_REQID=684095 FCP_LOGIN=”APPS/APPS” FCP_USERID=1234 FCP_USERNAME=”ABC” FCP_PRINTER=”noprint” FCP_SAVE_OUT=Y FCP_NUM_COPIES=0
2:
3:
4:
5:
FCPLOGIN:APPS/SONICDEV1
Finished printing parameters.
FCP_USERID:
- oracleappsnotes 1:18 pm on April 9, 2015
  
  I believe that you can extract the values from $0 based on the space character.
  I know the answer is pretty late 🙂
G Whiz 4:10 am on April 11, 2015

Thank you so much for posting this. It just save me a lot of headache!
Pingback: Lazy Host « Hrishikesh Joglekar
Stanislav 12:05 pm on April 20, 2016

that a good article!!
It was only one problem:
FND-CP-ESP: Child: exec:: No such file or directory
and I’ve find that remedy:
http://oracle.ittoolbox.com/groups/technical-functional/oracle-appserver-l/error-fndcpesp-child-exec-no-such-file-or-directory-1040185
let me post code from that source:

sampawar replied Dec 11, 2008
Resolve error do following steps:

1.Convert File format into unix dos2unix filename.prog

dos2unix xxg_sqldumper_interface.prog
and it was enough!
- oracleappsnotes 5:57 pm on April 20, 2016
  
  Thanks Stanislav. Yes, you would need the file in UNIX format and dos2unix is a handy utility for converting from Windows to UNIX format. However, the utility might not be available by default in all systems in which case you can use text editors such as Notepad++ to convert the file to UNIX format.
sandeep 12:37 pm on January 4, 2018

IMPORTANT**IMPORTANT

There is a double space in this line just before ‘myscr’.

[oracle@myapps bin]$ ln -s $FND_TOP/bin/fndcpesr myscr

This tiny space costed me 2 days of work.
- oracleappsnotes 12:29 pm on February 2, 2020
  
  Updated.
  Thanks a lot for pointing this out, Sandeep!