E-PRCS: Recurrence PSJob Does Not Retain User Destination Output (Doc ID 2770549.1)

Last updated on JULY 27, 2022

Applies to:

Symptoms

Destination path is not populating in PSPRCSPARMS record when the process running PSJob is scheduled through recurrence, hence recurrence PSJob does not retain user destination output correctly.
When a recurrence process is used, only the first recurrence has the correct destination populated. All recurrence processes after the first one contain "%%Log/Output Directory%%" instead, and do not retain the destination value as expected.

Steps to replicate the issue:
1. Navigate to PeopleTools > Process Scheduler > Recurrences.
2. Create a recurrence of your choice to use for scheduling any test process.
Make the recurrence to run something like every 2 minutes so you will be able to monitor and see results quickly.
3. Navigate to PeopleTools > Process Scheduler > System Process Requests.
4. Create or select a run control ID to use for this test.
5. Click the "Run" button to choose a test process to schedule for this test, choose your recurrence, choose a Process Scheduler domain, choose output type of "File", choose output format and type in a directory (example: Windows - "c:\temp\", Unix - "/tmp/") to write the output to.
6. Click the "OK" button to finally submit the request.
7. Click the "Process Monitor" link to take you to the Process Monitor tool in order to observe the recurring process.
8. Once the first recurrence of the process has completed, click the "Details" link for that request and then the "Parameters" link in order to view the "Destination" value and see the directory location is correct.
9. Once the second recurrence of the process has completed, click the "Details" then "Parameters" link for the second request in order to view the "Destination" value and see the directory location is incorrect (shows "%%Log/Output Directory%%" instead).

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.