Seeing a strange issue where out Mainframe (IBM zOS) can successfully mount volume and volume/qtree just fine, but if we mount volume/qtree/folder it fails with a "path not found error". Unix/Linux servers can mount volume/qtree/folder just fine. Are there any gotchas with NFS and IBM z/OS that we should be aware of?
#Mainframe not able to mount below qtree level
wheat mirage
warm flame
Nothing comes to mind, but I am curious what a packet trace shows since I don't have a client to test with. It may be worth a Support case.
broken blaze
does this work for other NFS servers? I can think of maybe zOS does a "showmount" before actually mounting, and if it doesn't show the folder, it won't mount it. But then again, I have no clue about zOS so I'm basically just guessing here 🙂
delicate brook
could be something as simple as ownership of "folder" ... the interweb says client needs to have uid/gid's in its "OMVS" segment... fwiw
wheat mirage
So actually we figured it out and it was all about how the path was entered on their side
Basically if it's a long path, you have to remember to type it out all the way to column 71 before continuing on the next line
otherwise it helpfully inserts spaces from the last character to column 71
meaning volume/qtree/folder/folder would become volume/qtree/folder /folder
and thus generate the path not found error
it isn't all that documented either
warm flame
Thanks for the update. Did you find any documentation on this that we could reference in a KB?
main pewter
Oof.