E-COB: Visual Cobol Uses the Service Account Instead of the User OPRID Running the Process
(Doc ID 2887814.1)
Last updated on AUGUST 05, 2022
Applies to:
PeopleSoft Enterprise PT PeopleTools - Version 8.57 and laterInformation in this document applies to any platform.
Symptoms
After upgrading from Net Express to Visual Cobol, cobol processes run through Process Scheduler use the Service Account instead of the user OPRID who actually ran the process. When inspecting the process's command line parameters, the OPRID used is the system service account in PSADMIN. The issue only occurs if the process is run as part of a PsJob. If a cobol process is run individually, it uses the correct user OPRID.
Site confirmed the issue did not occur when using Net Express. This impacts backend permissions for reporting as a system account is not set up to handle posting transactions.
ENVIRONMENT
---------------
PeopleTools: 8.57.15
Visual Cobol 6.0
Windows 2019 Server
Sample Replication:
1. Log in as VP1 and navigate to PeopleTools > Process Scheduler > Process Type
Select Cobol SQL, then the process scheduler O/S, and the Database Type. It should show:
Changes
Upgraded to Visual Cobol.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |