Re: CLP logging level -- MIDRANGE-L


On 22/07/2005, at 2:41 AM, rob@xxxxxxxxx wrote:

Why am I getting those low level messages?  Anyone?

I see you've come close to understanding this in later appends andothers have guessed at the answer.

All messages sent to a call stack message queue end up in the jobmessage queue (or job log). The LOGLVL attribute of the job is simply afilter over the view of those messages. The filter is applied byDSPJOBLOG. So messages are hidden but not removed. Reducing the filterwhile the job is active will allow those hidden messages to be seen.One drawback of an increased filter is that important error messagesmay not be in a spooled job log if the job ends abnormally.

You can't stop messages from being logged except by not sending them inthe first place. Once a message is in the job log the only way you canremove it is by receiving it (with the remove option) or removing it bykey (if you know the message key). In your case you can do one of thefollowing:1) Run CHKOBJ to verify the object exists before deleting it (but ifit's not found you'll just have a different message to remove)

        2) Run RCVMSG after trying to delete it.

3) Only create the user space if it doesn't exist. If it alreadyexists then just use it.


The normal way to remove "not found" messages is:
        DLTUSRPSC lib/space
        MONMSG CPF2105 EXEC(DO)
                RCVMSG MSGTYPE(*EXCP) /* Not found */
        ENDDO

However, in your case because the DLTUSRSPC command sends an "objectdeleted" message which you also probably don't care about you couldcode:

        DLTUSRSPC lib/space
        MONMSG CPF2105 /* Not found */
        
        RCVMSG MSGTYPE(*LAST) /* Either: not found */
                                                  /*     or: object deleted */

If you take the third option (which is they way I'd do it) then you'dcode:

        CHKOBJ qtemp/qwcljobl *usrspc
        MONMSG CPF9801 *N DO
                RCVMSG MSGTYPE(*EXCP) /* Not found */
                CRTUS qtemp/qwcljobl
        ENDDO

And as for the idiot at IBM telling you CL doesn't pause on a CALLstatement well that just beggars belief. CALL is a synchronousoperation. That means the caller stops while the callee is processing.The caller doesn't resume until the callee returns control. I suggestyou avoid this particular support person in the future.


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                                   \ /
                                                             X
                 ASCII Ribbon campaign against HTML E-Mail  / \
--------------------------------------------------------------------