Agent as400 crashes with Function DSPOVR not allowed
search cancel

Agent as400 crashes with Function DSPOVR not allowed

book

Article ID: 258644

calendar_today

Updated On:

Products

CA Automic One Automation CA Automic Workload Automation - Automation Engine

Issue/Introduction

The Agent crashes with the following messages in the QPJOBLOG:

MCH3601    Escape                  40   03/01/23  06:16:44.911170  UCXJO41      UC4         *STMT    UCXJO41     UC4         *STMT‬
‭                                     From module . . . . . . . . :   AGENTCONTE‬
‭                                     From procedure  . . . . . . :   poll__21ConcurrentLinkedQueueXTPQ2_3uc414Physi‬
‭                                       calPacket_FRPQ2_3uc414PhysicalPacket‬
‭                                     Statement . . . . . . . . . :   18‬
‭                                     To module . . . . . . . . . :   AGENTCONTE‬
‭                                     To procedure  . . . . . . . :   poll__21ConcurrentLinkedQueueXTPQ2_3uc414Physi‬
‭                                       calPacket_FRPQ2_3uc414PhysicalPacket‬
‭                                     Statement . . . . . . . . . :   18‬
‭                                     Thread  . . . . :   00000001‬
‭                                     Message . . . . :   Pointer not set for location referenced.‬
‭                                     Cause . . . . . :   A pointer was used, either directly or as a basing‬
‭                                       pointer, that has not been set to an address.‬
‭CPF1892    Escape                  40   03/01/23  06:16:45.116149  QDMDSPOV     QSYS        1912     QWCCDSJC    QSYS        05A7‬
‭                                     Thread  . . . . :   00000001‬
‭                                     Message . . . . :   Function DSPOVR not allowed.‬
‭                                     Cause . . . . . :   Function DSPOVR is not allowed in a job which is capable‬
‭                                       of running with multiple threads.‬
<...>
C2M1601    Escape                  50   03/01/23  06:17:01.806971  QC2UTIL1     QSYS        *STMT    UCXJO41     UC4         *STMT‬
‭                                     From module . . . . . . . . :   QC2SIGNL‬
‭                                     From procedure  . . . . . . :   raise‬
‭                                     Statement . . . . . . . . . :   6‬
‭                                     To module . . . . . . . . . :   UCEX‬
‭                                     To procedure  . . . . . . . :   __crashHandler__FP21_INTRPT_Hndlr_Parms_T‬
‭                                     Statement . . . . . . . . . :   57           *PRCLT‬
‭                                     Thread  . . . . :   00000001‬
‭                                     Message . . . . :   Signal SIGABRT raised (abnormal termination).‬
‭                                     Cause . . . . . :   The signal SIGABRT was raised to indicate an abnormal‬
‭                                       termination.‬
‭CPF3698    Information             00   03/01/23  06:17:01.815964  QSCPUTR      QSYS        005E     QMHAPD      QSYS        0507‬
‭                                     Thread  . . . . :   00000001‬
‭                                     Message . . . . :   Dump output directed to spooled file 3, job‬
‭                                       362077/WLAPROD/UC4AGENT created on system S44E0341 on 03/01/23 06:17:01.‬
‭                                     Cause . . . . . :   Dump output is being directed to a spooled file.‬
‭CPF1892    Escape                  40   03/01/23  06:17:01.910236  QDMDSPOV     QSYS        1912     QWCCDSJC    QSYS        05A7‬
‭                                     Thread  . . . . :   00000001‬
‭                                     Message . . . . :   Function DSPOVR not allowed.‬
‭                                     Cause . . . . . :   Function DSPOVR is not allowed in a job which is capable‬
‭                                       of running with multiple threads.‬
‭CEE9901    Escape                  30   03/01/23  06:17:02.088504  QLEAWI       QSYS        *STMT    QCMD        QSYS        01C8‬
‭                                     From module . . . . . . . . :   QLETOOL‬
‭                                     From procedure  . . . . . . :   Q LE AWIRaise‬
‭                                     Statement . . . . . . . . . :   176‬
‭                                     Thread  . . . . :   00000001‬
‭                                     Message . . . . :   Application error.  *N unmonitored by *N at statement *N,‬
‭ 5770SS1 V7R3M0 160422                           Job Log                     S44E0341  03/01/23  06:17:02 UTC+02:00S     Page 3361‬
‭  Job name . . . . . . . . . . :   UC4AGENT        User  . . . . . . :   WLAPROD      Number . . . . . . . . . . . :   362077‬
‭  Job description  . . . . . . :   UC4AGENT        Library . . . . . :   UC4‬
‭MSGID      TYPE                    SEV  DATE      TIME             FROM PGM     LIBRARY     INST     TO PGM      LIBRARY     INST‬
‭                                       instruction X'4000'.‬
‭                                     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 *N *N . The program was stopped at the‬
‭                                       high-level language statement number(s) *N at the time the message was sent.‬
‭                                        If more than one statement number is shown, the program is an optimized ILE‬
‭                                       program.  Optimization does not allow a single statement number to be‬
‭                                       determined.  If *N is shown as a value, it means the real value was not‬
‭                                       available. Recovery  . . . :   See the low level messages previously listed‬
‭                                       to locate the cause of the exception.  Correct any errors, and then try the‬
‭                                       request again.‬
‭CPC2402    Completion              50   03/01/23  06:17:02.104756  QCMD         QSYS        066F     *EXT                    *N‬
‭                                     Thread  . . . . :   00000001‬
‭                                     Message . . . . :   Job ended. Cancel message received at command processor.‬
‭                                     Cause . . . . . :   A message with a severity equal to or exceeding the end‬
‭                                       severity was received at the command processor. Recovery  . . . :   See the‬
‭                                       messages previously listed to determine the message that caused the job to‬
‭                                       be ended. Correct the errors, and then try the request again.‬
‭CPF1164    Completion              00   03/01/23  06:17:02.133972  QWTMCEOJ     QSYS        0161     *EXT                    *N‬
‭                                     Thread  . . . . :   00000001‬
‭                                     Message . . . . :   Job 362077/WLAPROD/UC4AGENT ended on 03/01/23 at 06:17:02;‬
‭                                       427.172 seconds used; end code 20 .‬
‭                                     Cause . . . . . :   Job 362077/WLAPROD/UC4AGENT completed on 03/01/23 at‬
‭                                       06:17:02 after it used 427.172 seconds processing unit time. The maximum‬
‭                                       temporary storage used was 29 megabytes. The job had ending code 20. The job‬
‭                                       ended after 1 routing steps with a secondary ending code of 0.  The job‬
‭                                       ending codes and their meanings are as follows:  0 - The job completed‬
‭                                       normally. 10 - The job completed normally during controlled ending or‬
‭                                       controlled subsystem ending. 20 - The job exceeded end severity (ENDSEV job‬
‭                                       attribute). 30 - The job ended abnormally. 40 - The job ended before‬
‭                                       becoming active. 50 - The job ended while the job was active. 60 - The‬
‭                                       subsystem ended abnormally while the job was active. 70 - The system ended‬
‭                                       abnormally while the job was active. 80 - The job ended (ENDJOBABN command).‬
‭                                       90 - The job was forced to end after the time limit ended (ENDJOBABN‬
‭                                       command). Recovery  . . . :   For more information, see the Work management‬
‭                                       topic collection in the Systems management category in the IBM i Information‬
‭                                       Center, http://www.ibm.com/systems/i/infocenter/.‬

Environment

Release :

Agent AS/400

v12.2.x

v12.3.4 - 12.3.8HF1

Cause

This is a defect

Resolution

The issue has been fixed in Agent AS/400 v12.3.8HF2