VERIFIED SOLUTION i

Resolve error CEE9901 Escape error when running a CL using Merge/Purge Plus

Environment Details  Product Feature:  calling job run a CL

Operating System:   IBMi

Version:  MPP 6.6.0

Issue

After submitting the cl job in the Merge/Purge Plus step on the iSeries, the QPJOBlog has this error -
 

CEE9901    Escape                  30   07/29/13  03:14:42.464664  QLEAWI       QSYS        *STMT    CMRUNJOB    G1CMPGMS    002B

                                     From module . . . . . . . . :   QLEDEH

                                     From procedure  . . . . . . :   Q LE leDefaultEh

                                     Statement . . . . . . . . . :   205

                                     Message . . . . :   Application error.  RNX0233 unmonitored by CMSBMRUN at

                                       statement *N, instruction X'0000'.

                                     Cause . . . . . :   The application ended abnormally because an exception

                                       occurred and was not handled.  The name of the program to which the

                                       unhandled exception is sent is CMSBMRUN CMSBMRUN _QRNP_PEP_CMSBMRUN.

Cause

The CL job is submitted and when the job is running in the Merge/Purge Plus step, a user forces the job to end before it has ended on its on.  After this happens, the job always ends abnormally in the Merge/Purge Plus step.  Before this, the job was running daily with no problems.

Resolution

UPDATED: August 28, 2017
When a job is in use ("locked"), it generates JBID_xxxxx  (xxxxx is the name of the job) as a data area in the G1xxPGMS library (G1MPPGMS default product library name). One should look for this in order to determine if a job is currently locked or not. "xx" in this case would be "CM". Then when you find it locked you could delay calling the job or take other action.

By deleting that data area you would remove the lock on a job.

Then submit the job again and it will run to completion.