EGL: A COBOL Process Calling Journal Edit and Post ABENDED at Step GL_JCOBOL.MAIN.COBOL (Action PeopleCode) With RC 8. (Doc ID 1087879.1)

Last updated on MARCH 16, 2023

Applies to:

Symptoms

[Applies to  Net Express COBOL compiler on windows platform.  Issue does not occur on UNIX/LINUX platforms.]

Issue:
-------
A COBOL process calling Journal Edit (GL_JEDIT) and Post (GLPPPOST) ABENDED at Step GL_JCOBOL.MAIN.COBOL (Action PeopleCode) With RC 8.

Error:
------
1) Error presented in journal edit AE trace (i.e. AE_GL_JEDIT2_XXXX.AET).

(GL_JCOBOL.MAIN.COBOL) (PeopleCode)
Process 269 ABENDED at Step GL_JCOBOL.MAIN.COBOL (Action PeopleCode) -- RC = 8
ROLLBACK

2) Error presented in the journal edit PC/SQL trace (i.e. AE_GL_JEDIT2_XXXX.trc)

Stmt=INSERT INTO PSBATCHAUTH (GUID, CMDLN, CREATED_DTTM, TIMETOLIVE, HASH_SIGNATURE) VALUES (:1, :2, :3 ,:4, :5)
Bind-1 type=2 length=36 value=4edcfe97-226e-11df-b9fd-dce6da9aa226
Bind-2 type=2 length=35 value=Remote Call Command Line Irrelevant
Bind-3 type=25 length=23 value=2010-02-25 16:31:40.000
Bind-4 type=6 length=4 value=5
Bind-5 type=2 length=28 value=yeA5GkG7W0YoqRlyKslQT+8vEio=
Commit
Disconnect
Rollback

3) Error presented in the log ( GL_JEDIT2_XXXX.log)

COBOL Program PTPECOBL aborted (2,-1) GL_JCOBOL.MAIN.GBL.default.1900-01-01.COBOL.OnExecute PCPC:647 Statement:2
Do Step Actions [1798] Exception logged: RC=100.
Process 269 ABENDED at Step GL_JCOBOL.MAIN.COBOL (PeopleCode) -- RC = 8 (108,524)

4) No error presented in below remote call log/output file if remote call trace is turned on.
PTPECOBL_xxxxxx.err
PTPECOBL_xxxxxx.out

What Is Working
-----------------------------
1) The journal from the COBOL process was edited and posted in a separate batch later on, which proved that there was no data issue with the journal itself.
2) If the same COBOL process ran without journal edit and post options or with journal edit option only, it would run to success without any error returned.
3) COBOL remote call test completed successfully on page PeopleTools -> Debug - > PeopleTools Test Utilities.

Steps to replicate
--------------------
By following these steps the issue can be reproduced On-Site or DEMO:
1. Confirm that COBOL remote call test has run to success on PeopleTools > Debug > PeopleTools Test Utilities.
2. Run a COBOL process which creates journal(s) with journal edit and post options.
3. Process fails with above errors presented in the Journal Edit AE and PC/SQL trace.

Note: Issue may not be consistently replicable if on some process scheduler domains ULP is applied && not applied on some.

Changes

Cause

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