Trace in PeopleSoft COBOL & AppEngine

Action Requested: FYILink: http://www.peoplesoft.com/psp/portprd/CUSTOMER/CRM/c/CALLCENTER.RC_CASE_MAP.GBL?page=RC_CASE_NOTE&BUSINESS_UNIT=GBLSC&CASE_ID=4113114Message Text:Note Created Date : 24/01/2006 7:41PMNote Summary : Email to customerNote Detail:SergeyI have attached two resolutions for you to familiarize when setting up a trace file. If the issue resurfaces again, try and set a trace and then we could try and isolate the issue by looking at the insert statement from the trace file. I hope this helps. Since the issue did not resurface in your current payprocess and as per your suggestion iam closing this case at this point of time. Resolution 694679 -- TRACE & LOG FILES FOR COBOL, REMOTE CALL & APPLICATION ENGINE=> ISSUE:FINDING TRACE & LOG FILES FOR COBOL, REMOTE CALL & APPLICATION ENGINEANSWERS:=> APPLICATION ENGINEApplication Engine Execution Log file:Client:%TEMP%\PS\DBName\AEADHOC_.log%TEMP%\PS\DBName\PTPEMAIN_.log%TEMP%\PS\DBName\_.logServer:$PS_HOME/appserv/prcs/DBName/logs/AEADHOC_.log$PS_HOME/appserv/prcs/DBName/logs/PTPEMAIN_.log$PS_HOME/appserv/prcs/DBName/logs/_.logApplication Engine SQL Trace:This trace file is generated by the Application Engine at your request from Go, PeopleTools, Application Engine, Use, Application Engine, Application, Update/Display. Setting TRACE to an option other than OFF will create a trace file during your test run. It generates a trace of the sequence of application SQL your application used.Before you can view trace files on the client in the Application Engine viewer, you must set the AETRACE environment variable to the client trace file location. In general you will set AETRACE=%TEMP%\PS\DBName where DBName is the name of the database you are working with. AETRACE should be defined as an NT System Environment or within the AUTOEXEC.BAT for Windows 95/98. The Application Engine SQL Trace file will have the following naming convention: .aetThe Application Engine viewer can only view the Application Engine SQL Trace files on the Client. If you're running your application on the Server however, these SQL Trace files exist on the Server and not on the Client. On the Unix Server, trace files will reside in $PS_HOME/appserv/prcs/DBName/logs.COBOL SQL Trace:On the Client, check EVERYTHING on the left hand side under SQL Trace on the Trace tab of the Configuration Manager (except for the Sybase Information). On the Unix Server, set TraceSQL to 255 in the $PS_HOME/appserv/prcs/DBName/psprcs.cfg file (the configuration file used by PSADMIN) and then re-boot the Process Scheduler. The COBOL SQL Trace file will reside in the directory structure below with the following naming convention:Client:%TEMP%\PS\DBName\cobsql_ae_.trcServer:$PS_HOME/appserv/prcs/DBName/logs/cobsql_ae_.trc=> REMOTE CALL:Remote Call Redirect Output:If running a Remote Call process in TWO TIER, on the Remote Call tab of the Configuration Manager is a "Remote Call Redirect Output" flag. Check the flag and rerun the Remote Call process. This will create two files in your %TEMP% directory, one ending with .out, the other with .err (program-name_oprid.out and program-name_oprid.err). The program-name_oprid.out file will more than likely contain the reason why the process didn't complete successfully.If running a Remote Call process in THREE TIER, the COBOL process runs on the Application Server. Therefore, the same flag is set, but this time in the Application Server configuration file ($PS_HOME/appserv/Domain-Name/psappsrv.cfg). The parameter RCCBL Redirect (Remote Call child process output redirection) is defaulted to 0. If it is changed to 1 (RCCBL Redirect=1) and the AppServer re-booted, the same two files will be written to the Application Server logs directory ($PS_HOME/appserv/Domain-Name/logs), providing additional information as to why the Remote Call process failed.COBOL SQL Trace:To generate a cobsql trace of the COBOL program in TWO TIER, check EVERYTHING on the left hand side under SQL Trace on the Trace tab of the Configuration Manager (except for the Sybase Information). Also, check the Redirect Output box on the Process Scheduler tab of the Configuration Manager too. The cobsql trace file will reside under %TEMP%\PS\DBName in the format cobsql_program-name_datetime.trc.To generate a cobsql trace in THREE TIER, set TraceSQL equal to 255 in the $PS_HOME/appserv/Domain-Name/psappsrv.cfg (the configuration file used by PSADMIN). You must also add a section for the Process Scheduler. For example:[Process Scheduler]Log Directory=%PS_SERVDIR%/logsThen re-boot the AppServer. The cobsql trace file will reside under $PS_HOME/appserv/Domain-Name/logs in the format cobsql_program-name_datetime.trc.=> COBOLCOBOL Execution Log File:On the Server, the COBOL Log file will reside under $PS_HOME/appserv/prcs/DBName/logs in the format PROGRAM-NAME_instance#.log.On the Client using PT7.5x, check the Redirect Output box on the Process Scheduler tab of the Configuration Manger. The COBOL Log file will reside under %TEMP%\PS\DBName in the format PROGRAM-NAME_instance#.log.On the Client using PT7.0x and Micro Focus v4.0, make sure the environment variable COBSW is set to +L,+S5. If using NetExpress, please refer to Incident #T-RBOLEL-9D4QY / NetExpress PT7.03, 7.04 and 7.05 doesn't have a way to keep the MS-DOS window open. This is targeted to be resolved in PT7.06. Workarond is to run the COBOL program from MS-DOS and pipe the output to a file.COBOL SQL Trace:On the Client, check EVERYTHING on the left hand side under SQL Trace on the Trace tab of the Configuration Manager (except for the Sybase Information). On the Unix Server, set TraceSQL to 255 in the $PS_HOME/appserv/prcs/DBName/psprcs.cfg file (the configuration file used by PSADMIN) and then re-boot the Process Scheduler. The COBOL SQL Trace file will reside in the directory structure below with the following naming convention:Client:%TEMP%\PS\DBName\cobsql__.trcServer:$PS_HOME/appserv/prcs/DBName/logs/cobsql__.trcADDITIONAL RESOURCES:Resolution 689883 -- Preliminary Remote Call questions -- What customers should do before calling the GSCResolution 42114 -- Where do Remote Call processes run? How can a customer determine where a Remote Call process runs?Resolution 43481 -- INFO: Online Checks -- Where does the process run? Where does the output go? (Version 7.x+)Resolution 39654 -- INFO: Where is the Log file for Online Check error messages? How to debug Online Check errors?Resolution 610752 -- Remote Call Error: "Could not open file [path]\rmtcall_out.nnn to read child return data" -- MASTER Resolution=================================================================================Resolution #44268 How to create a COBOL trace that shows dynamic SQL when executing on UNIX serverYou are able to trace all SQL activity generated by PeopleSoft COBOL programs executed on a Unix server.The COBOL SQL trace on the server is your best tool to figure out why a program failed if: - you are running a COBOL program on a Unix server - you know the COBOL program has started - the COBOL program fails for some reason=> Enabling COBOL SQL trace on the Unix server: You can enable COBOL tracing on Unix servers by setting a variable in the pstools.ini file on the server. On the Unix server, open (edit) the file $PS_HOME/bin/pstools.ini. Under the section [PSTOOLS], you will find a line saying: TraceSql=0. Comments above this line explain how you can set TraceSql to a value other than zero in order to generate COBOL SQL tracing information.=> Location of COBOL SQL trace output file on the Unix server:On Unix machines, the COBOL SQL trace files are written to the $PS_HOME directory in the subdirectory log/. The trace file will start with 'COBSQL_' and have an extension of '.trc'. After 'COBSQL_', the file name may have the program's name and/or the process instance.Here is a sample file name with the process instance: $PS_HOME/log/FSDMO/COBSQL_1914.trc=> LOG files -- Naming convention and where to find them:In addition to the creation of a trace (.trc) file, there is a log file created on the Unix server whenever you execute a PeopleSoft COBOL process. The log file contains the processing status and program error/abend messages that are normally written by the program, even when tracing is not turned on. You should find the log file in the following directory: $PS_HOME/log/. The log file will have the following naming convention: _.log Here is a sample file name for the AP posting program: /apps/psoft/log/FSDMO/APPPVCHR_12638.logFor more information on COBOL SQL tracing on the server, see the following section in the PeopleTools 7.x PeopleBook: Administrative Tools Performance Tuning Batch Program Monitoring and Tuning Utilities SQL Trace=> Additional Resources: Customer Connection > Support > Tips & Techniques > Keyword COBOL: GSC COBOL Answer Book for PeopleTools 6, 7 & 7.5 Tracing in PeopleSoft for PeopleTools [your release]Santhosh PintoORACLE Global Support Center