RE: GO SAVE 21 to virtual tape? -- MIDRANGE-L

Subject: RE: GO SAVE 21 to virtual tape?
From: Rob Berendt <rob@xxxxxxxxx>
Date: Wed, 5 Oct 2022 16:09:13 +0000
List-archive: <https://archive.midrange.com/midrange-l/>
List-post: <mailto:midrange-l@lists.midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=unsubscribe>

ALWSAV(*NO) means that particular directory is not saveable. It can still be used to serve as virtual tape. The only time it is an issue is if you then try to use SAV DEV(...) OBJ('/vtape') to save it to physical media as some weird method. Then that will fail. You should use DUPMED or DUPMEDBRM instead.
But you should have no trouble saving to that directory.
We flag all image catalog directories as ALWSAV(*NO). The only exceptions are some planned unload/reload situation to a new Power system. Otherwise it's expendable data.

Rob Berendt

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.