Caveat: getting the daily digest implies response delays... Jasi: the Knowledge Centre page for BPXF135E showed up at the top of the Google search for me. If you research the message further, you find it indicates 'can't reach host'.
Perhaps the list shouldn't be your first stop. [1] Common courtesy, really. [1] if it wasn't, you should indicate what research you did so we don't have to repeat it. --------> signature = 8 lines follows <-------- Neil Duffee, Joe Sysprog, uOttawa, Ottawa, Ont, Canada telephone:1 613 562 5800 x4585 fax:1 613 562 5161 mailto:NDuffee of uOttawa.ca http:/ /aix1.uOttawa.ca/ ~nduffee “How *do* you plan for something like that?” Guardian Bob, Reboot “For every action, there is an equal and opposite criticism.” “Systems Programming: Guilty, until proven innocent” John Norgauer 2004 "Schrodinger's backup: The condition of any backup is unknown until a restore is attempted." John McKown 2015 -----Original Message----- From: Jasi Grewal [mailto:[email protected]] Sent: June 21, 2016 16:48 Subject: Mounting NFS Directory on zOS as Binary Greetings, I am trying to mount this zLinux Filesystem on zOS using NFS with the following command and it seems that either is not supported as Binary or I am missing something. mount filesystem('lozlnx00:/sandbox') type(nfs) mountpoint('/nfsmnts/lozlnx00/sandbox') parm('lozlnx00:"/sandbox,binary",xlat(y),vers(3)') I get the following error: BPXF162E ASYNCHRONOUS MOUNT FAILED FOR FILE SYSTEM LOZLNX00:/SANDBOX. BPXF135E RETURN CODE 0000046A, REASON CODE 6E2A1003. THE MOUNT FAILED FOR FILE SYSTEM LOZLNX00:/SANDBOX. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
