E1: UBE: Enhancement Request for No UBE Log Created in AS/400 Printqueue When UBE Goes to Error Status
(Doc ID 1914043.1)
Last updated on MAY 30, 2017
Applies to:JD Edwards EnterpriseOne Tools - Version 9.1 to 9.1 [Release 9.1]
IBM i on POWER Systems
When a report completes on the AS/400 (IBM i) platform, e.g., R0006P, the IBM i tries to move and rename the JDE log for the printube process from the log folder to the printqueue folder, but if any process has the printqueue locked, then not only does the log file *not* get moved to the printqueue, but the original log in the log folder gets deleted.
This appears to happen in module: JDEKRNL, function: MoveErrorLogs (see trace file QPSRVTRCJ236645.txt, which shows R0006P when E1 failed to move/rename the printube log to the print queue, but did not retain the original log in the log folder).
Requesting a change in E1 functionality that, if the move/rename of the original log file to the printqueue for the printube (runbatch) process fails, E1 should actually be checking to determine whether the move succeeded, and if not, it should retain the original log file in the log folder.
STEPS TO REPRODUCE ISSUE
- Fast Path: BV
- Batch Application: R0006P
- Select version XJDE0001 (check the box and click the Select check mark button)
- Enter desired Processing Options
- Select printer or accept default printer
- The UBE appears to run on the AS/400, but it ends in Error (E) status in WSJ, and no log is created in the printqueue folder for the job
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