I am trying to share a folder on SAP file structure to be shared with
the Application server where we want to install a dialogue instance on
another iseries system How do I map the shared folder on 1 iseries
onto another Iseries server
eg
A Iseries -----------/usr/sap/trans mapped to BIseries------/
usr/sap/trans
^-------------------------------------------------------------`
What KIND of shared folder is it? iSeries supports sharing of
directories and folders by a variety of means and protocols.
--
72. If all the heroes are standing together around a strange device and begin
to taunt me, I will pull out a conventional weapon instead of using my
unstoppable superweapon on them.
--Peter Anspach's list of things to do as an Evil Overlord
It is a shared folder on the Central instance server wher the profiles
are resident thet is /usr/sap/trans/profile For us to install the
Dialogue instance we need access or link to this folder. It is a
shared folder one AS400 machine and we want to access it from another
AS400 machine so that we finidh the installation. during the
installation we will access information and and write information to
the remote directory of the other machine
Generally files used in SAP are either in a library or in the "root" (/)
file system. I think the path you mentioned (/usr/sap/trans/profile) is in
the "root" (/) file system.
From another IBM i system, a folder/directory in the "root" can be accessed
using QFileSvr.400, QNTC or NFS. The folder (and it's contents) can be
accessed using a path just like local objects. Details of how to use them
can be found in the IBM i Information Center, but here are the basics.
(Note that each method requires the user gets authenticated on the server,
there are different restrictions for each method, and each method requires a
server/client jobs to be started on the appropriate system)
QFileSvr.400 - generally on the client side you just create a directory for
the remote system underneath /QFileSvr.400. For example, from SysA - the
client, I want to access objects on SysB - the server. On SysA create the
directory /QFileSvr.400/SysB. This will represent the "root" (/) on SysB.
Then to access /usr/sap/trans/profile on SysB from SysA, you use the path
/QfileSvr.400/SysB/usr/sap/trans/profile.
QNTC - similar to QFileSvr.400, except you need to define a NetServer share
on SysB. I'll pick that I want to share /usr/sap and the share name is
SAPshr. On SysA (note there's different ways to do this part), create a
directory /QNTC/SysB. To access the objects in /usr/sap/trans/profile from
SysA, then you use the path /QNTC/SysB/SAPshr/trans/profile. (SAPshr
replaces the /usr/sap part of the path)
NFS - On the server, use EXPORTFS to export the path you want to share,
again I'll use /usr/sap as an example. On the client side, MOUNT the export
over the path of your choosing, I'll use /SAPshr. Note that to specify the
exported path you prefix it with the server, in this case SysB:/usr/sap.
Then to access the objects in /usr/sap/trans/profile from SysA use the path
/SAPshr/trans/profile.
"Tendai Arnold Makumbe" <ccsp...@gmail.com> wrote in message
news:810e7eae-9887-4f89...@q14g2000vbi.googlegroups.com...
You may find that what you need is the NFS functionality, especially if
you're willing to support having a syncronized user list between the two
machines.
http://publib.boulder.ibm.com/infocenter/iseries/v5r4/index.jsp?topic=/rzamv/rzamvifsnetwork.htm
--
66. My security keypad will actually be a fingerprint scanner. Anyone who
watches someone press a sequence of buttons or dusts the pad for
fingerprints then subsequently tries to enter by repeating that sequence
will trigger the alarm system. --Peter Anspach's Evil Overlord List