|
I reached out to a colleague who assisted with this interpretation ...
The command
CRTDIR DIR('/asp02')
is creating a directory in SYSBAS onto which the used defined file system
(which is the IFS in ASP2) will be mounted.
The command
MOUNT TYPE(*UDFS) IFS('/dev/qasp02/qasp02.udfs') MNTOVRDIR('/asp02')
makes the IFS contents of ASP2 visible/usable by putting them inside the
/asp02 directory
The following command creates the first play directory inside asp02
CRTDIR DIR('/asp02/backup')
The IFS data in ASP2 will always be there but it isn't visible until a
mount is issued (hopefully in the startup program).
Don Brown
From: "Don Brown" <DBrown@xxxxxxxxxx>
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
Date: 20/10/2017 08:32 AM
Subject: Re: Mount from Linux to asp02
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>
Not sure Jack but it did work.
I used this link for the initial UDFS creation;
http://www-01.ibm.com/support/docview.wss?uid=nas8N1013504
If I do a wrklnk '/asp02'
then option 8=Display attributes
I can see the the object is in auxiliary pool 2 ...
Display Attributes
Object . . . . . . : /asp02
Type . . . . . . . . . . . . . . . . . : DIR
Owner . . . . . . . . . . . . . . . . : QSECOFR
System object is on . . . . . . . . . : Local
Auxiliary storage pool . . . . . . . . : 2
Object overflowed . . . . . . . . . : No
The same applies to the directory /asp02/backup
Now I did not check this before doing the MOUNT
If I get some time over the weekend I will try and test further.
Cheers
Don Brown
From: "Jack Woehr" <jwoehr@xxxxxxxxxxxxxxxxxxxxxxxx>
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
Date: 20/10/2017 05:07 AM
Subject: Re: Mount from Linux to asp02
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>
CRTUDFS UDFS('/dev/QASP02/qasp02.udfs')
Create the directories in ASP02
CRTDIR DIR('/asp02/')
CRTDIR DIR('/asp02/backup')
Mount the file system
MOUNT TYPE(*UDFS) MFS('/dev/qasp02/qasp02.udfs') MNTOVRDIR('/asp02')
Hmm, does this really work?!
If I did the equivalent in Unix this would:
1. Create the file system on QASP02
2. Create a mount point /asp02/ *in the root file system*
3. Create /asp02/backup below that /asp02 mountpoint *in the root file
system*
4. Mount the qasp02.udfs file system on root mountpoint /asp02 *leaving
the local subdirectory /asp02/backup in place*
- *(Actually this wouldn't work on Unix because you can't mount to a
mount point that has a subdirectory.)*
I don't quite get the magic by which /asp02/backup is created on the
mounted qasp02.udfs file system instead of in the root filesystem, if you
care to explain and enlighten me :)
On Wed, Oct 18, 2017 at 11:16 PM, Don Brown <DBrown@xxxxxxxxxx> wrote:
Update for archive.mounting
Recently I asked a question on this group for setting up ASP02 and using
it for backups that are subsequently saved to external storage by
a NFS directory to the IFS from an Linux backup server.after
This is now all working but had a few issues along the way.
This may assist someone else doing the same or similar.
We used a second ASP (2) that had been previously created.
Create the file system
CRTUDFS UDFS('/dev/QASP02/qasp02.udfs')
Create the directories in ASP02
CRTDIR DIR('/asp02/')
CRTDIR DIR('/asp02/backup')
Mount the file system
MOUNT TYPE(*UDFS) MFS('/dev/qasp02/qasp02.udfs') MNTOVRDIR('/asp02')
Note: Mount is not preserved across IPLs. Therefore, you must mount
every IPL. I would suggest adding the MOUNT command in the systemstart-up
program.DIR('/asp02')
Create the Image Catalogue, add an entry and load it.
CRTIMGCLG IMGCLG(BACKUP) DIR('/asp02/backup') TYPE(*TAP) CRTDIR(*NO)
ADDIMGCLGE IMGCLG(BACKUP) FROMFILE(*new) TOFILE(VOL001) VOLNAM(VOL001)
LODIMGCLGE IMGCLG(BACKUP) IMGCLGIDX(1) OPTION(*MOUNT)
Create a virtual tape and vary it on
CRTDEVTAP DEVD(TAPVRT01) RSRCNAME(*VRT)
VRYCFG CFGOBJ(TAPVRT01) CFGTYPE(*DEV) STATUS(*ON)
LODIMGCLG IMGCLG(BACKUP) DEV(TAPVRT01)
Save a library for a test
SAVLIB LIB(TESTLIB) DEV(TAPVRT01) CLEAR(*ALL)
Export the IFS Directory in ASP02
CHGNFSEXP OPTIONS('-I -F -O VERS=4:3:2,ROOT=192.168.126.4')
is
This is allowing NFS versions 4, 3 and 2 to be available. The default
versions 3 and 2 Only which is where we initially had authorityproblems.
with
ROOT access is specified for the connection.
The above command is using the ip address but that SHOULD be replaced
the hostname to avoid future issues if IP addresses change. (Just asklist
Rob!)
On the Linux box mount the drive
mount -t nfs 192.168.126.12:/asp02/backup testDirectory
Running the mount command without any options shows
192.168.126.12:/asp02/backup on /root/testDirectory type nfs
(rw,vers=4,addr=192.168.126.12,clientaddr=192.168.126.4)
Listing the directory contents shows the image catalogue and the saved
volume
ls /root/testDirectory
And the results show the files
QIMGCLG VOL001
Don Brown
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD
--
Absolute Performance, Inc.
12303 Airport Way, Suite 100
Broomfield, CO 80021
NON-DISCLOSURE NOTICE: This communication including any and all
attachments is for the intended recipient(s) only and may contain
confidential and privileged information. If you are not the intended
recipient of this communication, any disclosure, copying further
distribution or use of this communication is prohibited. If you received
this communication in error, please contact the sender and delete/destroy
all copies of this communication immediately.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD
______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
______________________________________________________________________
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD
______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
______________________________________________________________________
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.