Re: Full save with IASP -- MIDRANGE-L

Subject: Re: Full save with IASP
From: Nathan Andelin <nandelin@xxxxxxxxx>
Date: Thu, 26 Apr 2018 06:48:57 -0600
List-archive: <https://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

I've never had an independent ASP, so I don't know what my options are.
Is there a good way to handle this?

The ASPDEV parameter on the SAVSYS command defaults to *ALLAVL (all
available). If you want to exclude an IASP from GO SAVE 21, you just VRYCFG
CFGOBJ(IASP_NAME) CFGTYPE(*DEV) STATUS(*OFF) prior to the save.

That's one of the advantages to IASPs. You can shorten IPL and SAVE times,
because IASPs can be varied on and off.

This mailing list archive is Copyright 1997-2026 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.