× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



To see hex, you just right-click->Change Representation->1 Hexadecimal

The packed(15:5) command line thing just hit me while reading your last message. That's the first idea that makes any sense. I'll give that a try and see what happens.

Thanks



-----Original Message-----
From: Hiebert, Chris [mailto:chris.hiebert@xxxxxxxxxxxxxx]
Sent: Tuesday, February 26, 2019 12:33 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: RE: Message Monitor Command Substitution Parameter Lengths (RPGLE)

How did you generate the hex string?
By chance did you do a debug eval FIELD :X 12?

Try checking debug "eval field :x 30"

I'm wondering if you actually have a packed 15.5 and the hex string you sent doesn't show all the digits.

I would expect to see a trailing d or f with packed data.

Like

X'000012345600000F'


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.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.