×
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.
On 06/05/2010, at 5:48 AM, Peter Dow wrote:
But notice that the send message program (QMHDLVMS or QMHDSMSS?) is
followed in the stack by the QWSGET + QT3REQIO, which are the last 2
in
the stack when sitting at a command line. I agree that it's not
waiting
for a response to a message (WRKACTJOB showed it with a status of
DSPW,
not MSGW), so what is it doing?
QMHDLVMS - Deliver Message
QMHDSMSS - Display Message
Note also the CPP for DSPMSG is QMHDSMSS. Thus the job has sent and
attempted to display a message to the user.
I'm not sure the problem is related to *STATUS messages given the
presence of QT3REQIO at the end of the stack. Although it's possible
that attempting to display CPYF status messages registered an I/O
error and what you see in the stack is the result of that problem.
QWTPECTL indicates an "event" of some sort has occurred which has then
caused the system to likely display a message about that event.
So, what's in the job log of the failing job prior to the "Device
MISPC02S2 session not active." message?
Proper job log with message IDs and from/to program information--not a
next to useless copy/paste from a screen.
Regards,
Simon Coulter.
--------------------------------------------------------------------
FlyByNight Software OS/400, i5/OS Technical Specialists
http://www.flybynight.com.au/
Phone: +61 2 6657 8251 Mobile: +61 0411 091 400 /"\
Fax: +61 2 6657 8251 \ /
X
ASCII Ribbon campaign against HTML E-Mail / \
--------------------------------------------------------------------
midrange.com
