Alert being cut by CA AP

book

Article ID: 211868

calendar_today

Updated On:

Products

CA 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 
14:25:50 AF1212E 07:37:07 PRD1 DB2AMSTR: DSNX906I PRDPGN MCDBGNG67POLLOOKUP -> OPSMVS issued START PROC Command - Contact DB
14:27:08 AF1212E 07:37:07 PRD1 DB2AMSTR: DSNX906I.PRDPGN MCDBGNG67POLLOOKUP -> OPSMVS issued START PROC Command - Contact DB
14:27:30 AF1212E 07:37:07 PRD1 DB2AMSTR: DSNX906I.PRDPGN MCDBGNG67POLLOOKUP -> OPSMVS issued START PROC Command - Contact DB
14:28:55 AF1212E 07:37:07 PRD1 DB2AMSTR: DSNX906I PRDPGN.MCDBGNG67POLLOOKUP -> OPSMVS issued START PROC Command - Contact DB

Automation is showing the alerts sometimes shortened and it is not known why this happens. The truncated once 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:25:51 PRD1 AF1212E 07:37:07 PRD1 DB2AMSTR: DSNX906I PRDPGN MCDBGNG67POLLOOKUP -> OPSMVS ISSUED START PROC COMMAND - CONTACT DB
02/15/21 15:27:09 PRD1 AF1212E 07:37:07 PRD1 DB2AMSTR: DSNX906I.PRDPGN MCDBGNG67POLLOOKUP -> OPSMVS ISSUED START PROC COMMAND - CONTACT DB
02/15/21 15:27:30 PRD1 AF1212E 07:37:07 PRD1 DB2AMSTR: DSNX906I.PRDPGN MCDBGNG67POLLOOKUP -> OPSMVS ISSUED START PROC COMMAND - CONTACT DB
02/15/21 15:28:56 PRD1 AF1212E 07:37:07 PRD1 DB2AMSTR: DSNX906I                                                                

Cause

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

Environment

Release : 11.6

Component : CA Automation Point

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 exception and are the only messages that get 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 message are passed only into logging/printing channels.

It is  recommend to restrict the length of the message sent to Automation Point on OPS/MVS side to fit into two-lines to avoid the truncation of the message.