Troubleshooting and Maintenance

Performing Recommended Maintenance

Request records are created in the PSRCSRQST table(s) each time a process in a PeopleSoft job is submitted by TA . Gradually, these records may accumulate. Periodically, you may want to delete these old request records from the PSPRCSRQST and related tables as a routine maintenance task.

PeopleSoft provides an application engine process called PRCSYSPURGE to purge Process Scheduler tables and process files. You can configure this process to run on a regular basis within PeopleSoft from the System Purge Options tab displayed by selecting PeopleTools > Process Scheduler > System Settings. You can also schedule the process to run as a job in TA .

Best Practices

The following is a list of recommendations for maximizing your success with the PeopleSoft module:

  • Choose the PeopleSoft database owner as the database user discussed in Minimum Software Requirements.

  • Create a PeopleSoft operator called Batch (or some other identifier no more than 8 characters in length). Then, add this PeopleSoft operator ID to TA and have Batch as the runtime user for all TA PeopleSoft jobs. This will make it easy to identify jobs originating from TA in the PeopleSoft environment.

    Note: Ensure that this new PeopleSoft operator ID has the rights to run all of the processes you would like it to manage via TA.

  • A TA PeopleSoft job should optimally contain only one PeopleSoft process. This allows TA to control all dependencies, and allows greater visibility and control via TA.

  • Perform maintenance on your PeopleSoft database by running the Application Engine process, PRCSYSPURGE, to purge old request records that accumulate in the database. You can configure the Peoplesoft Process Scheduler server to run the PRCSYSPURGE on a regular basis.

Troubleshooting

This section lists some error conditions and how to determine possible causes and remedies for the conditions:

If the Master cannot Connect to the PeopleSoft Database

TA checks the installed version number of PeopleSoft. If the version does not match one of the supported PeopleSoft releases, you will be unable to connect. The connection status light will be red. You can check TA’s logs or the Event log for error messages. In this case, the error message will specify “invalid version.”

If You cannot See the Output from a TA PeopleSoft Job

If you cannot see the output from a TA PeopleSoft job, verify that the Save Output option on the Options tab of the Job Definition dialog is set to either the Append or Replace option.

Another possibility when you cannot see output from a TA PeopleSoft job is that the master service is configured as the local system account. This is a problem if a mapped drive is used to specify the location of PeopleSoft job output and the master service on Windows does not have access to that path. In this case, you must add the drive, by mapping from the TA master machine and setting the master service to logon to an account with access to the same drive letter as specified in the output location path.