Re: Lock on command processing program ignored

Hello Vernon,

Locking the program does work but only if you do it the way they intended.

When a program is run the OS does not attempt to lock it** therefore a
separate process holding a lock on the program will not stop it from
running.  For example,

JOBA locks PGMX *EXCL
JOBB runs PGMX - runs OK

What you are supposed to do is have the program lock ITSELF.  For example:

JOBA runs PGMX
PGMX locks itself *EXCL - runs OK
JOBB runs PGMX
PGMX locks itself *EXCL - fails.

Of course, if you ignore the CPF1002 exception message it won't fail.  Any
MONMSG CPF0000 do nothing type statements in the program?

Doing the lock in the validity checking program is silly unless the VCP
also indicates failure to the Command Anlayzer by sending the appropriate
*ESCAPE message -- see the CL Programming Guide -- and thus stops the
program running.  However that will not stop the program being called
directly.

** Interesting aside.

        ALCOBJ OBJ((QCMD *PGM *EXCL))

and then try to sign on at another workstation.  Hmm, want to keep
everyone off your AS/400?  Check the joblog of the subsystem (probably
QINTER) for the details.  MCH2601 and CPF9999.

Regards,
Simon Coulter.

--------------------------------------------------------------------
   FlyByNight Software         AS/400 Technical Specialists
   http://www.flybynight.com.au/

   Phone: +61 3 9419 0175   Mobile: +61 0411 091 400        /"\
   Fax:   +61 3 9419 0175   mailto: shc@flybynight.com.au   \ /
                                                             X
                 ASCII Ribbon campaign against HTML E-Mail  / \
--------------------------------------------------------------------