× 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.



If the library is type *PROD then you have to have the proper authorities to
debug.

Put the object in a library with *TEST instead and try to debug it there.

You might want to spend 10 minutes reviewing the debug restrictions.


--
Jim Oberholtzer
Agile Technology Architects

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Rishi
Seth
Sent: Wednesday, February 27, 2019 6:52 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: Message Monitor Command Substitution Parameter Lengths (RPGLE)

Hi,

How to avoid 'Not authorized to debug' error?
It's bit urgent could some experts please advise soon may it's profile
related issue can we change some settings using chgusrprf to avoid this
error as it's not allowing to file this STRDBG command itself and popping up
above mentioned error message on screen.

Thanks

On Tue, Feb 26, 2019 at 10:18 PM Justin Taylor <JUSTIN@xxxxxxxxxxxxx> wrote:

Does anyone know where I can find the parameter definitions for
Navigator for i Message Monitors? This document (
https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki
/IBM%20i%20Technology%20Updates/page/System%20Monitors)
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
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To
subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link:
https://amazon.midrange.com


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.