Re: QS36F file format error after migrating LPAR -- MIDRANGE-L

Subject: Re: QS36F file format error after migrating LPAR
From: Rob Berendt <rob@xxxxxxxxx>
Date: Mon, 9 Apr 2018 10:21:51 -0400
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>

The sad thing is so many people ignore a thread thinking they didn't ask
it therefore it doesn't apply to them, and right while we're trying to
help you through this, ask about trying to do the same thing.

Upgrades and migrations can be done. Even by those who don't do this for
a living. However, following the instructions is HIGHLY recommended.

Rob Berendt

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: QS36F file format error after migrating LPAR , Jack Woehr

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