Re: What commands should have ALWLMTUSR(*YES)?

[Peter Dow <petercdow@xxxxxxxxx>]

Hi Rob,

To disprove what Mark said, you need to change authority on the DSPMSG 
command to DUMMY *EXCLUDE, then try it.

--
*Peter Dow* /
Dow Software Services, Inc.
909 793-9050
petercdow@xxxxxxxxx <mailto:petercdow@xxxxxxxxx>
pdow@xxxxxxxxxxxxxx <mailto:pdow@xxxxxxxxxxxxxx> /


On 10/26/2017 1:07 PM, Rob Berendt wrote:
> I do not think you do.  Read my message again.  Or let me explain below
> CHGCMD QSYS/SNDMSG           ALWLMTUSR(*NO)
> Command SNDMSG in library QSYS changed.
> CHGCMD QSYS/DSPMSG           ALWLMTUSR(*NO)
> Command DSPMSG in library QSYS changed.
> CHGCMD QSYS/DSPJOB           ALWLMTUSR(*NO)
> Command DSPJOB in library QSYS changed.
> CHGCMD QSYS/DSPJOBLOG        ALWLMTUSR(*NO)
> Command DSPJOBLOG in library QSYS changed.
> CRTUSRPRF DUMMY LMTCPB(*YES)
> Special authorities granted *NONE.
> User profile DUMMY created.
>
> Sign on as DUMMY
> >From the real command line
> DSPMSG
> Command DSPMSG in library *LIBL not allowed.
> SysReq 4, Messages for:   DUMMY screen appears.
> SysReq 6, Messages for QSYSOPR screen appears.
> SysReq 3, DSPJOB screen appears, and, 10. Display job log works just fine.
> SysReq 5, SNDMSG screen appears, and I sent a message.
>
> ROB sees:
> >From  . . . :   DUMMY          10/26/17   16:07:01
> hi dude
>
>
> Rob Berendt