|
All iASPs have names - they are devices.RSTASP is a number - those 1st 32, as I recall - someone will have the right number if I'm off.
IASPs are the place named in RSTASPDEV - the name is also at the first level off of the root of IFS. So if it IASP01 as the device name, you will see /IASP01 in WRKLNK '/'
There will be a QSYS.LIB inside that directory, too - and in there is where the library will get restored to - AND it cannot exist there and in *SYSBAS at the same time - meaning when the IASP device is varied on.
There're manuals about IASPs that you probably need to get really familiar with - you don't NEED a system with an IASP, but it's not that hard to set up, either - just take 1 arm out of whatever your DASD is, then use that as the disk for an IASP.
Good luck! Vern On 5/8/2015 7:06 PM, James H. H. Lampert wrote:
Ladies and Gentlemen, Fellow Midrange Geeks:I just had to deal with a customer who was having a problem with software installed on an iASP (contrary to the expectations of the installer program). Researching the "snakebyte" problem brought me to the RSTASPDEV and RSTASP parameters on RSTxxxI remember RSTASP from previous work with "basic user ASPs," but I'm not quite sure I understand what RSPASPDEV expects (and don't have a box with iASPs to experiment with). Am I to understand that ASPs can have names now?-- JHHL
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.
midrange.com
