It's worth bearing in mind that I'm developing under SMSQ/E on QPC2, which post-date Pennel and Dickens, either environment may have an effect. In any case, my job definitely continued to execute after the Trap #1 and even doing the "kill_me" looping branch didn't solve the problem - it just kept calling mt.frjob ad infinitum!
I'll need to dig further into this because even though I now have a solution, I don't like not understanding why the behaviour is there in the first place. Or why, in the same job, calls to mt.susjb or mt.prior all return 0 in d0, apparently indicating success, but don't actually do anything! Adrian -----Original Message----- From: ql-users-boun...@lists.q-v-d.com [mailto:ql-users-boun...@lists.q-v-d.com] On Behalf Of gdgqler Sent: 30 January 2011 17:07 To: ql-us...@q-v-d.com Subject: Re: [Ql-Users] Help! Reasons for MT.FRJOB Failing On 30 Jan 2011, at 16:47, Norman Dunbar wrote: >> >> Interesting. I've never to my knowledge needed the final branch in any of my programs. With the branch in, the program is not going to do very much until it eventually decides to stop. Without that anything may presumably occur. > I have a funny feeling you called me to task many years ago in QL > Toady when I wrote some code with it in! ;-) > That is highly unlikely. In fact I often use for testing a small program which ends by running through to the suicide code. Each time I look at this I remind myself that nothing can happen after the Trap #1. But it appears it can! Both Pennel and Dickens say that the only error that can occur with mt.frjob is -2, invalid job. So "not complete" can't occur. Hmmmm! George _______________________________________________ QL-Users Mailing List http://www.q-v-d.demon.co.uk/smsqe.htm _______________________________________________ QL-Users Mailing List http://www.q-v-d.demon.co.uk/smsqe.htm
