Re: Changing to security level 40.

Sorry, I spend so much time testing other stuff for other list posters 
that I don't have time to eat my own cooking - thanks.  :-)

We figured out two main culprits.  One is a job that submits jobs like 
crazy.  It involved a rpg call to java that then did some data transfer to 
SQL Server.  Apparently there is a job description associated with the 
user that does the transfer that has extra libraries not really needed, 
and, that the person doesn't have access to.

The other is a modified program from a canned software package that has a 
lot of monmsg's in it that are ignored and "assumed" to have worked.
The problem is that they don't have enough authority on the object being 
duped that the CRTDUPOBJ fails.  (And why they then assume that the 
CRTDUPOBJ worked and try to do a CHGDSPF on a nonexistant object escapes 
me.)  I also wonder if an OVRDSPF would do the same thing.

             CRTDUPOBJ  OBJ(SWS110) FROMLIB(&LIBRARY) OBJTYPE(*FILE) +
                          TOLIB(QTEMP)
             MONMSG     MSGID(CPF3012 CPF2130)
/*-----*/

             CHGVAR     VAR(&DSPSEC) VALUE(&SEC)
             CHGDSPF    FILE(QTEMP/SWS110) WAITFILE(&DSPSEC) +
                          WAITRCD(&DSPSEC)
             MONMSG     MSGID(CPF0000)

Rob Berendt