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



Simon,

You are probably right.  I am debugging the code.  In fact I am debugging 
it now, with the same user profile and no other security changes and I 
cannot duplicate the situation again.  The error no longer occurs. 
Probably sensed that I had IBM on the phone and shrunk away in fear.  I 
suppose I'll count that as a blessing.

Rob Berendt
-- 
Group Dekko Services, LLC
Dept 01.073
PO Box 2000
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





Simon Coulter <shc@xxxxxxxxxxxxxxxxx> 
Sent by: midrange-l-bounces@xxxxxxxxxxxx
02/24/2005 04:55 PM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>


To
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
cc

Subject
Re: QCAIEXIT, QMHRTMSS vs QMHRCVPM







On 25/02/2005, at 5:56 AM, rob@xxxxxxxxx wrote:

> This line of RPG
>  qmhrcvpm(rcvm0200:%len(rcvm0200):'RCVM0200':'*':StackCnt:'*PRV':
>                     MsgKey:0:'*SAME':ERRC0100);
> is generating:
> MCH1001-Attempt to use permanent system object QCAIEXIT without
> authority.
> MCH1001-Attempt to use permanent system object QMHRTMSS without
> authority.

Are you sure you're interpreting this correctly? I mean are you 
positive this line of code causes the problem? The reason I ask is 
because the MCH1001 messages are sent to the QQDAPROC program rather 
than a message handler (QMH*) program or your program.

> Both have the identical:
> From program . . . . . . . . . :   #auexcpt
>   Instruction  . . . . . . . . :     000B80
>
> To program . . . . . . . . . . :   QQDAPROC
>   To library . . . . . . . . . :     QSYS
>   Instruction  . . . . . . . . :     05E4

QQDA* stuff is something to do with a system debugger judging by the 
messages in QSYS/QQDAMSGF. Are you debugging the program? Perhaps that 
is the root cause?

However, as Bruce said changing the authority on the internal programs 
(i.e., QCAIEXIT and QMHRTMSS) is not the correct solution.

Note that QCAIEXIT is part of the command analyser component.

Regards,
Simon Coulter.
--------------------------------------------------------------------
    FlyByNight Software         AS/400 Technical Specialists

    http://www.flybynight.com.au/
    Phone: +61 3 9419 0175   Mobile: +61 0411 091 400        /"\
    Fax:   +61 3 9419 0175                                   \ /
                                                              X
                  ASCII Ribbon campaign against HTML E-Mail  / \
--------------------------------------------------------------------


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



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.