Thanks for the tip!
Turns out that 'openvm debug msg' provided a little more info.
('openvm debug mount' and 'openvm debug all' did not change the result any.)
So with 'openvm debug msg', I now also get "DMSOVZ2134E Return code
157 and reason code 2114 (X'842') given on call to BPX1MNT". Digging
through the 5.4 OE CSL reference, this RC 157 is just "ECMSERR". The
reason code 2114 is slightly more explanative: "connection to file
pool has been severed".
Looks to me as though IPGATE gets part of the way through the
transaction and then terminates it. (the transaction, not necessarily
itself) I wish I knew how to drag more diagnostics out of IPGATE.
-- Rick; <><
Q: Isn't filtering stupidity elitist?
A: Yes. Yes, it is. That's sort of the whole point. -- Ortiz and Starr
On Fri, Feb 20, 2009 at 9:12 AM, Mary Ellen Carollo <marye...@us.ibm.com> wrote:
> On Wed, 18 Feb 2009 14:50:11 -0500, Richard Troth <vmcow...@gmail.com>
> wrote:
>
> Richard -
> Try the OPENVM DEBUG command to see if that will give a clue about what is
> going wrong. I would start with OPENVM DEBUG MSG or OPENVM DEBUG MOUNT.
> The command is documented in the OpenExtensions Command Reference.
>
> Mary Ellen Carollo
> z/VM Development
> IBM Endicott
>
>>
>>The first three commands all work fine and as expected. The last
>>command fails ... always. Hard to tell what is happening. What I see
>>in IPGATE's console is RC=8 and Reason=108. Tried to walk through
>>OPENVM SEXEC, but it eventually drives DMSOVZ MODULE, which was
>>further than I had opportunity to dig.
>>
>>
>>Thoughts?
>>
>>
>>-- R; <><
>>=========================================================================
>
