Alerts truncated by Automation Point

Products

• Automation Point

Issue/Introduction

When sending messages from OPS/MVS to Automation Point like these:

14:22:41 AF1212E 07:37:07 PRD1 DB2AMSTR: DSNX906I PRDPGN.MCDBGNG67POLLOOKUP -> OPSMVS issued START PROC Command - Contact   
14:23:47 AF1212E 07:37:07 PRD1 DB2AMSTR: DSNX906I PRDPGN.MCDBGNG67POLLOOKUP -> OPSMVS issued START PROC Command - Contact DB
14:24:29 AF1212E 07:37:07 PRD1 DB2AMSTR: DSNX906I PRDPGN.MCDBGNG67POLLOOKUP -> OPSMVS issued START PROC Command - Contact D  

Automation is showing the alerts sometimes shortened and it is not known why this happens. The truncated ones are in bold.

02/15/21 15:22:41 PRD1 AF1212E 07:37:07 PRD1 DB2AMSTR: DSNX906I PRDPGN.MCDBGNG67POLLOOKUP -> OPSMVS ISSUED START PROC COMMAND - CONTACT
02/15/21 15:23:47 PRD1 AF1212E 07:37:07 PRD1 DB2AMSTR: DSNX906I
02/15/21 15:24:30 PRD1 AF1212E 07:37:07 PRD1 DB2AMSTR: DSNX906I PRDPGN.MCDBGNG67POLLOOKUP -> OPSMVS ISSUED START PROC COMMAND - CONTACT D 
02/15/21 15:28:56 PRD1 AF1212E 07:37:07 PRD1 DB2AMSTR: DSNX906I    

Environment

Release : 11.6

Component : Automation Point

Cause

The message is a multi-line WTO (MLWTO) and Automation Point has a certain method to handle them.

Resolution

This is indeed a result of clamping multiline messages of 3 lines to only one line. This is intended behavior. Two-line messages are exceptions and are the only messages that get the whole two lines passed to scripts through rules. Messages with 3 or more lines have only the first line passed to the scripts. The remaining lines from such multiline messages are passed only into logging/printing channels. It is recommend to restrict the length of the message sent to the Automation Point on the OPS/MVS side to fit into two-lines to avoid the truncation of the message.