Duplicate Email Notifications for Uprocs in "Could not Submit"

book

Article ID: 222767

calendar_today

Updated On:

Products

CA Automic Dollar Universe

Issue/Introduction

Some odd behavior occurs with SMTP notifications when a Uproc fails with a "Could not Submit" error. 

According to universe.log it appears to have attempted to execute twice as there are two log entries for this error.  This is causing us to receive duplicate notifications for these types of errors. 

We would like to know why this is happening only when we get a "Could not Submit" error, and how to fix it so that we only receive one notification when this fails.

 

universe.log excerpt for the node where this uproc executes:

| 2021-08-20 11:17:04 |ERROR|X|DQM|pid=28045.4102028144| u_dqm_sub_job             | dqm_ecriture_article_job returns 6 [762014                                                                   SYS_BATCH                       9000000000A000000002                2021082011170400                100   100   PNO U000000003  XA000000002U000001047000                                                                                        ]
| 2021-08-20 11:17:04 |ERROR|X|DQM|pid=28045.4102028144| owls_dqm_job_submit       | u_dqm_sub_job returns 6
| 2021-08-20 11:17:04 |ERROR|X|DQM|pid=28045.4102028144| process_fnc_obj           | process_create in error: 6
| 2021-08-20 11:17:04 |ERROR|X|DQM|pid=28045.4102028144| u_dqm_process_client_requ | Error handling job request: owls_dqm_handle_job returns 104
| 2021-08-20 11:17:04 |ERROR|X|IO |pid=28017.4075809648| email_notification_build_ | Job log /orsyp/universe/aporsp2/CGPROD/log/exp/XS0000002087335033A000000002U000001047.6469713 not found.
| 2021-08-20 11:17:04 |ERROR|X|IO |pid=28017.3830438768| email_notification_build_ | Job log /orsyp/universe/aporsp2/CGPROD/log/exp/XS0000002087335033A000000002U000001047.6469713 not found.
| 2021-08-20 11:17:04 |ERROR|X|IO |pid=28017.3830438768| NOTIFY_SMTP               | Could not attach job log.
| 2021-08-20 11:17:04 |ERROR|X|IO |pid=28017.4075809648| email_notification_build_ | Job log /orsyp/universe/aporsp2/CGPROD/log/exp/XS0000002087335033A000000002U000001047.6469713 not found.
| 2021-08-20 11:17:04 |ERROR|X|IO |pid=28017.3693026160| email_notification_build_ | Job log /orsyp/universe/aporsp2/CGPROD/log/exp/XS0000002087335033A000000002U000001047.6469713 not found.
| 2021-08-20 11:17:04 |ERROR|X|IO |pid=28017.3693026160| NOTIFY_SMTP               | Could not attach job log.
| 2021-08-20 11:17:04 |INFO |X|IO |pid=28017.3830438768| NOTIFY_SMTP               | [aporsp2] NOTIFICATION_EMAIL [SEND OK] / Dollar Univer$e: [Aborted] [] [BRPT_E4045_LOADER_APP_PNW] [TRAILER BRPT_E4045_LOADER_APP_PNW] [A_BIRPT] [5788883] [6469713] [7335033] [X]
| 2021-08-20 11:17:04 |INFO |X|IO |pid=28017.3693026160| NOTIFY_SMTP               | [aporsp2] NOTIFICATION_EMAIL [SEND OK] / Dollar Univer$e: [Aborted] [] [BRPT_E4045_LOADER_APP_PNW] [TRAILER BRPT_E4045_LOADER_APP_PNW] [A_BIRPT] [5788883] [6469713] [7335033] [X]

 

Cause

Outdated entry in u_jobfile.dta was provoking the "Could not Submit" issue.

Environment

Release : 6.x

Component : DOLLAR UNIVERSE

Resolution

After reviewing the universe.log it seems that the issue occurs with a particular DQM batch entry(762014) andoccurs around once per month:

| 2021-05-12 17:26:23 |ERROR|X|DQM|pid=28045.4102028144| u_dqm_sub_job             | dqm_ecriture_article_job returns 6 [762014
| 2021-06-14 23:02:27 |ERROR|X|DQM|pid=28045.4102028144| u_dqm_sub_job             | dqm_ecriture_article_job returns 6 [762014
| 2021-07-17 22:09:19 |ERROR|X|DQM|pid=28045.4102028144| u_dqm_sub_job             | dqm_ecriture_article_job returns 6 [762014
| 2021-08-20 11:17:04 |ERROR|X|DQM|pid=28045.4102028144| u_dqm_sub_job             | dqm_ecriture_article_job returns 6 [762014

When I look into the DQM data files, being u_prmfile.dta and u_jobfile.dta, it seems that in u_jobfile.dta there was an old record from 2017 and the error (dqm_ecriture_article_job returns 6) is generated because it cannot overwrite it:

762014                                                                   SYS_BATCH                          0000000A000000016201712211754450020171221175445002017122117544500100   100   ENO U000000011  XA000000016U000000217000                                                                        11521           

Hence, the solution would be simply deleting the entry 762014 from Monitoring - Activity Logging - Queued Jobs and that should not occur anymore.

Else, you could also reinitialize the batch queue SYS_BATCH when no jobs are running via the command "uxresetque queue=SYS_BATCH"