RE: Message Monitor Command Substitution Parameter Lengths (RPGLE)

How are you running this? Got any source example?

It could still be expecting a Character and you passed packed data, which may explain the strange hex.

What if it was supposed to be a null terminated - 6 character string?


Chris Hiebert
Senior Programmer/Analyst
Disclaimer: Any views or opinions presented are solely those of the author and do not necessarily represent those of the company.


-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxxxxxxxx] On Behalf Of Justin Taylor
Sent: Tuesday, February 26, 2019 9:48 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Message Monitor Command Substitution Parameter Lengths (RPGLE)

Does anyone know where I can find the parameter definitions for Navigator for i Message Monitors? This document (https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ibm.com_developerworks_community_wikis_home-3Flang-3Den-23-21_wiki_IBM-2520i-2520Technology-2520Updates_page_System-2520Monitors&d=DwICAg&c=2S-2xx8Cum_thMfWs-kOOHQTwolPvSZ4PFLhr1wDDGs&r=GYVfe7k5MogwSsRr94zbPeTDRJYpFK3WOG9BKFEwK1s&m=1cR1GDeOUzW-1UC2EAKzHkfbuQLQFcNfiKNrYRLnLEA&s=0WUq_aWs-bxcr81xuXA21CYgfC7tSYjMjMXOzqka4x8&e=) gives the parameter names and lengths, but not the data type.

Specifically, I'm having trouble with:
&FRMJOBNUMBER From job number for the message causing the trigger (length 6).

I first defined it as char(6). That came in as unreadable characters. The hex was x'000012345600', where 123456 was the actual job#. I tried packed(6), but that gave a decimal-data-error.


TIA