Normally, we have mainly seen it when the client job has allocated multiple sub-tasks. But, the client is specific to a subtask. (We don't expect one subtask to send and another to receive.) During the testing we are currently doing, the client has multiple subtasks, but subtasks are not being terminated or started when the error appears.
Tony Thigpen -----Original Message ----- From: Martin Trübner Sent: 09/20/2010 10:06 AM > Tony, > > I have a question and a comment... > > I think VSE-L would have given you good answers as well (we will see > after issue is resolved or at least narrowed) > >>> the ALET for the client partition changes. This causes the reply >>> write back to fail. > > The way you phrased it sounds like you are servicing a partition with > multitasking (private as in CICS when there was only QR) or officical > (with the help of the op-sys). Is that right? Is it happening with the > same the same (multitasking) system? > > Who did issue the ALESERV? with what parameters? > > .................................................... > > How it this for a start (from a VSE person?) > -- > Martin > > Pi_cap_CPU - all you ever need around MWLC/SCRT/CMT in z/VSE > more at http://www.picapcpu.de > >
