|
> > message: 6 > date: Fri, 13 Jan 2006 13:50:14 -0500 > from: rob@xxxxxxxxx > subject: Restricting a command vs QCMDEXC > > I have a command that I ran > CHGCMD CMD(SNDBRKMSG) ALLOW(*IMOD *BMOD *IREXX *BREXX *BPGM *IPGM > *EXEC > *BATCH) > Basically it has everything but *interact because I had users that > went > nuts with SNDBRKMSG to all users. > I have a utility program called SNDBRKUSR that finds all the > sessions for > a user, using api's, and then sends a break message to those > sessions. > However, since I took away *INTERACT this code: > cmd='SNDBRKMSG MSG(' + Apostrophe + %Trim(BrkMsg) + > Apostrophe + > ') TOMSGQ(' + %trim(JLJobNam) + ')'; > qcmdexc(cmd:%len(%trim(cmd))); > generates this: > CPD0031-Command SNDBRKMSG not allowed in this setting. > > I take it I either add *INTERACT back in, or replace the call to > QCMDEXC > with a CL program, right? > > Rob Berendt Maybe I'm missing something but couldn't you just make a copy of the SNDBKPMSG in you library and add *INTERACT back to that version. Restrict access to you library to you and in your utility just refernece ROBLIB/SNDBKPMSG ? m.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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 copyright@midrange.com.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.