RE: Change Command Parameter -- MIDRANGE-L

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

Instead of running the QSYS/RMVMSG command it could do a TFRCTL to the QSYS/QMHDLMS program from a CLP OPM program.

Paul

Principal Programmer Analyst
IS Supply Chain/Replenishment

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Douglas Handy
Sent: Tuesday, September 14, 2010 1:37 PM
To: Midrange Systems Technical Discussion
Subject: Re: Change Command Parameter

Giuseppe,

I'm trying to prevent the command 'RMVMSG PGMQ(*ALLINACT) MSGQ(*PGMQ)

CLEAR(*ALL)' being executed.

In case the user tries to run a program that has this command inside,
nothing should happen (no escape messages or other action, just command
skipped).

Have you considered placing your own RMVMSG command in a library higher in
the library list? If a program qualifies the call to RMVMSG it would not
work, but otherwise you should be able to intercept the call and silently
return in those cases where you want to skip the command, and call
QSYS/RMVMSG in those cases where you want to allow it to continue.

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.