RE: CPP6316 - Hardware configuration change detected, followed by CPF414C

Subject: RE: CPP6316 - Hardware configuration change detected, followed by CPF414C - Command not allowed
From: rob@xxxxxxxxx
Date: Wed, 1 Apr 2015 15:21:36 -0400
List-archive: <http://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: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

CPP6316 suggests doing an IOP reset because a configuration change may
have occurred without doing an IOP reset. Or it just may be a hardware
issue.

We do not autoclean. And I think that was because of issues like this. We
just do a manual clean every so many weeks.

You could add more tape drives, we have 10 in one library and four in
another.

Rob Berendt

Follow-Ups:

RE: CPP6316 - Hardware configuration change detected, followed by CPF414C - Command not allowed , Steinmetz, Paul

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.

RE: CPP6316 - Hardware configuration change detected, followed by CPF414C - Command not allowed