|
On 08-May-2015 19:06 -0500, James H. H. Lampert wrote:
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 RSTxxx I remember RSTASP from previous work with "basic user ASPs," but I'm not quite sure I understand what RSTASPDEV expects (and don't have a box with iASPs to experiment with). Am I to understand that ASPs can have names now?
The implementation object for the Independent ASP (iASP) is the Device Description (*DEVD), for which the mnemonic DEV is included in the naming of the Restore To ASP Device (RSTASPDEV) parameter. Thus the specification is to name a Device Description with the Object Attribute of ASP; or in Work With Device Descriptions, with the "Type" appearing as *ASP (auxiliary storage pool).
The iASP device is created with a CRTDEVxxx command just like other devices; the Create Device Description [Of Type] ASP (CRTDEVASP) command is used to create. And just like other device descriptions, the device then can be /varied/ on and off using the Vary Configuration (VRYCFG) command; specifying the *DEV as the Configuration Type (CFGTYPE). To vary-off the iASP device suggests those disks will be taken off-line from access, and to vary-on the iASP brings on-line accessibility to the database and the data on those disks.
Unlike the Create Library (CRTLIB) for which the old-style Auxiliary Storage Pool (ASP) parameter specification redirects to the ASP Device (ASPDEV) parameter, the Restore Library (RSTLIB) command has the Restore To ASP Device (RSTASPDEV) parameter that simply overrides the old-style Restore To ASP Number (RSTASP) parameter either if applicable [i.e. the save was taken from an iASP] or if a device is explicitly named; similarly for the other RSTxxx, except the Restore Object (RST) command for which iASP specification is effected in directory-naming.
Some specific references of possible value [the last link is to a Redbooks document that may give an overview; and perhaps the Redbooks document that Mark apparently did not want to share publicly, <www.redbooks.ibm.com/abstracts/sg246802.html> "IBM eServer iSeries Independent ASPs: A Guide to Moving Applications to IASPs" also would have an overview]:
<http://www.ibm.com/support/knowledgecenter/ssw_ibm_i_71/cl/crtdevasp.htm>"The Create Device Description (ASP) (CRTDEVASP) command creates a device description for an auxiliary storage pool (ASP) device."
<http://www.ibm.com/support/knowledgecenter/ssw_ibm_i_71/rzaly/rzalycreatestandaloneiasp.htm> _Creating an independent disk pool_ <http://www.ibm.com/support/knowledgecenter/ssw_ibm_i_71/rzaly/rzalyapplications.htm> _Application considerations for independent disk pools_ <http://www.ibm.com/support/knowledgecenter/ssw_ibm_i_71/cl/vrycfg.htm> _Vary Configuration_ (VRYCFG) <http://www.redbooks.ibm.com/abstracts/sg247811.html>IBM i 6.1 Independent ASPs: A Guide to Quick Implementation of Independent ASPs
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
