Re: IPGATE -vs- BFS

2009-02-20 Thread Mary Ellen Carollo
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 i s going wrong. I would start with OPENVM DEBUG MSG or OPENVM DEBUG MOUNT. The command is documented in the OpenExtensions Command

Re: IPGATE -vs- BFS

2009-02-20 Thread Richard Troth
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.

IPGATE -vs- BFS

2009-02-18 Thread Richard Troth
So ... We're enjoying the wonderful function of IPGATE. Ahhh... Now have a habit of grabbing SFS directories remotely. File and content manglement is so much better! We also have a smattering of things in BFS land. Sharing BFS spaces is needed less frequently than sharing SFS directories, but

Re: IPGATE -vs- BFS

2009-02-18 Thread David Boyes
On 2/18/09 2:50 PM, Richard Troth vmcow...@gmail.com wrote: 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

Re: IPGATE -vs- BFS

2009-02-18 Thread Schuh, Richard
@LISTSERV.UARK.EDU Subject: Re: IPGATE -vs- BFS On 2/18/09 2:50 PM, Richard Troth vmcow...@gmail.com wrote: 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