You may also want to restrict commands AREXEC and RUNRMTCMD use as well.
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of fbocch2595@xxxxxxx
Sent: Wednesday, May 16, 2012 1:22 PM
Subject: Re: RMTCMD's security?
Right, so I figured making SBMRMTCMD public *exclude should put an end to anyone using it.
From: Monnier, Gary <Gary.Monnier@xxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Sent: Wed, May 16, 2012 4:19 pm
Subject: RE: RMTCMD's security?
It depends upon you have your commands secured. Would you give the person ccess to a command line? Would you want them running PWRDWNSYS, DLTF, DLTPGM, tc.?
With the way IBM has set up servers you can run SBMRMTCMD on your test box. All ou do is create the DDM file so it points to your test system then run BMRMTCMD.
rom: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx]
n Behalf Of fbocch2595@xxxxxxx
ent: Wednesday, May 16, 2012 1:11 PM
ubject: RMTCMD's security?
i Folks, are many of you securing these commands, SBMRMTCMD, etc. so as to hange from the default of *USE for public? Do you see a risk in your users sing RMTCMD's from a test i to a production i?
his is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To
ost a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or
hange list options,
r email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment
o review the archives at http://archive.midrange.com/midrange-l