Message queue – Break Handling Program
I should get a break message instead of giving DSPMSG every time,
Created message in my lib (TSTMSGQ/TSTLIB) added this in my user prf (TSTPRF).
I'm getting completed normally messages whenever a job completes. But every time
I should check by giving DSPMSG cmd.
Can anyone tell me how to make it into *break mode.
CHGMSGQ MSGQ(TSTLIB/TSTMSGQ) DLVRY(*BREAK) PGM(*SAME) was already tried but i didn't get break message when job completes.
So please suggest any other way to do it.
Where the default Break Handling Program will reside in AS/400 system and what its
name?
Software/Hardware used:
AS400 , V5R4
Software/Hardware used:
AS400 , V5R4
ASKED:
November 26, 2012 11:20 AM
UPDATED:
November 26, 2012 1:09 PM
Answer Wiki:
You need to run the CHGMSGQ MSGQ(TSTLIB/TSTMSGQ) DLVRY(*BREAK) command on your interactive session, not in the job that is being submitted. If you have a signon program associated with your USRPRF, you can put the command in there and never have to worry about it again.
All Answer Wiki Contributors:
CharlieBrowne 
32,785 pts. ,
Michael Tidmarsh 11,380 pts. ,
Explorer1910 225 pts.
32,785 pts. ,
Michael Tidmarsh 11,380 pts. ,
Explorer1910 225 pts. To see all answers submitted to the Answer Wiki: View Answer History.
What is the DLVRY() attribute for the TSTPRF user profile? How was the job submitted? Which user ran the SBMJOB command?
The CHGMSGQ DLVRY(*BREAK) command will allocate the message queue in break mode for the job that runs the command. When that job ends, break mode also will end.
Tom
About the ‘Answer’, if DLVRY(*BREAK) is specified on the TSTPRF user profile and TSTPRF is submitting the job, the CHGMSGQ is not needed. There wouldn’t seem to be much reason to assign TSTMSGQ to TSTPRF otherwise. — Tom
Hello frnds,Thanks for the reply.How was the job submitted? Which user ran the SBMJOB command?Job was ran on the same user profile(TSTPRF) delivery mode was mention as *Break. But the mistake i have done is ‘Severity’ which i was given as ’70′ instead of ’0′.After changing it to ’0′ i got the break msg.
But the mistake i have done is ‘Severity’ which i was given as ’70′ instead of ’0′.
Yes, good catch. The user profile SEV() attribute defaults to 0, and it’s unusual for anyone ever to have reason to change it. Usually if a change is wanted, the message queue severity is changed and the user profile attribute is left alone.
Tom