×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
First I have to say that I am not well experienced with the way the i's
messaging system works. But digging around did not shine the light to me.
I have arranged some CL code for a batch job to bring the system to
restricted state and do a SAVSYS.
All working well, I can intercept the message which tells that the system
has reached restricted state, and continue to the save procedure.
But before the ENDSBS I need to send an other message to the MSGQ of
QSYSOPR. When I thus invoke for example:
SNDUSRMSG MSG(&MYMSG) +
MSGTYPE(*INFO) +
TOMSGQ(*SYSOPR)
And then the routine is no longer functioning. The WAIT loop then keeps
running until the BCHTIMLMT has expired.
So it seems to be caused by my sending of that before message to the msgq of
QSYSOPR. But I don't understand why, and also cannot find a good solution
for it.
This is driving me nuts. I must be doing something wrong, but what?
Thanks in advance,
Arco Simonse
--
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.