Beginner’s Guide : Concurrent program/Manager output and log file- Part - IV

Posted on August 19th, 2007 by Sanjit Anand | Print This Post | Email This Post

Once Concurrent program get complete, there are two file generated as follow:

• The Log File

Log files are stored under $APPLCSF/$APPLLOG if $APPLCSF is set and under $APPLLOG for each application if $APPLCSF is not set. The log file naming convention is the letter L, followed by the concurrent request ID, followed by the extension .req .

• The output File

Output files are stored under $APPLCSF/$APPLOUT if $APPLCSF is set and under $APPLOUT for each application if $APPLCSF is not set. The output file naming convention is Application User name.Request ID.

For the Information purpose, here are few for your interest.

• APPL_TOP - this is the top level directory for the Applications
• APPLCSF - the top level directory where the concurrent manager stores the log and out files of concurrent requests
• APPLLOG - concurrent request log files( As describe above)
• APPLOUT - concurrent request out files( As describe above)
• APPLTMP - Applications temporary files
• APPLPTMP - PL/SQL temporary files

Is there any naming conventions for the log file and output file?

Request log files: l<request id>.req
Output files:

• If $APPCPNAM is not set: <username>.<request id>
• If $APPCPNAM = REQID: o<request id>.out
• If $APPCPNAM = USER: <username>.out

Where: <request id> = The request id of the concurrent request And: <username> = The id of the user that submitted the request

Where are the managers logfiles goes:

Similar to concurrent requset output and log, the concurrent manager does also generate some files and typical naming convention are as below:

ICM logfile: Default is std.mgr, can be changed with the mgrname

• Concurrent manager log: w<XXXXXX>.mgr
• Transaction manager log: t<XXXXXX>.mgr
• Conflict Resolution manager log: c<XXXXXX>.mgr

Where: <XXXXXX> is the concurrent process id of the manager.