Logging System

The log directory stores the PeopleSoft Process Scheduler server logs and SQL trace files. Each server that is started in the PeopleSoft Process Scheduler server has its own set of log and trace files. The user does not normally need to review these files unless a problem occurs while running a process or some reason exists to verify that a process ran as expected.

Location of the Log and SQL Trace Files

The location and name of the PeopleSoft Process Scheduler log files depend on the operating system on which the PeopleSoft Process Scheduler Server is started.

Operating System	Log Directory
Windows	PS_CFG_HOME\appserv\prcs\<Database Name>\LOGS
UNIX	PS_CFG_HOME/appserv/prcs/<Database Name>/LOGS

The <Log Directory> corresponds to the directory that is specified in the Log/Output Directory variable in the PeopleSoft Process Scheduler configuration file (psprcs.cfg).

For each server that is started, two files are generated in the log directory:

The server log contains messages that are written by the server to the log file.

These messages are translated to the languages that are supported by the PeopleSoft system. The language of the messages is based on the language that is designated in the user profile.

The LogFence parameter, which is set in the PeopleSoft Process Scheduler configuration file, controls the detail of the message that is written to this log file.
The SQL trace file contains the traces of all SQL that is issued by the server.

This file is generated when the TraceSQL parameter in the PeopleSoft Process Scheduler configuration file has a value other than zero.

If a PeopleSoft Application Engine or Analytic Engine request is initiated by PSAESRV, the SQL traces that are generated from that process are stored in the process subdirectory that is located in the log and output directory.

Log and SQL Trace File Name in Windows and UNIX

The following table lists all the server names, log files, and SQL trace files in Windows and UNIX.

Server Name	Description	Log File	SQL Trace File
PSPRCSR V	PeopleSoft Process Scheduler Server	SCHDLR_<mmdd>.LOG	<User ID>_PSPRCSRV.tracesql
PSDSTSRV	Distribution Agent	DSTAGNT_<mmdd>.LOG	<User ID>_PSDSTSRV.tracesql
PSAESRV	PeopleSoft Application Engine Server	AESRV_<mmdd>.LOG	<User ID>_PSAESRV.tracesql
PSANALYTICSRV	Analytic Engine Server	OPTENGS<server number>.LOG	<User_ID>_PSANALYTICSRV <server number>.tracesql
PSMSTPRCS	Master Scheduler Server	MSTRSCHDLR_<mmdd>.LOG	<User ID>_PSMSTPRC.tracesql

<User_ID> is the user ID that is specified in the PeopleSoft Process Scheduler configuration file that is set to boot PeopleSoft Process Scheduler.

SQL Trace File

The SQL trace file is created when the TraceSQL variable in the PeopleSoft Process Scheduler configuration file has a value other than zero. This file contains the SQL traces that are issued by the Distribution Agent program PSDSTSRV.

Use the TraceSQL variable to set the level of SQL trace by selecting the numerical value representing each degree of tracing as described. The list of trace levels from which you can choose appears in the configuration file as shown:

1=SQL Statements
2=SQL statment variables
4=SQL connect, disconnect, commit and rollback
8=Row Fetch (indicates that it occurred, not data)
16=All other API calls except ssb
32=Set Select Buffers (identifies that attributes of columns
		to be selected)
64=Database API specific calls
128=COBOL statement timings
1024=SQL Informational Trace
4096=Manager information
8192=Mapcore information

If you want SQL Statements, SQL statement variables, and SQL connect, disconnect, commit, and rollback information, specify TraceSql=7 (1+ 2 + 4).

Note:

The SQL trace file doesn’t delete existing traces that are written from prior runs of the PSPRCSRV program, and it appends new SQL activity to the end of the file. Because the file can grow quite large and might fill up your file server, you should reset the TraceSQL to zero after you finish debugging the PeopleSoft Process Scheduler Server Agent.