RE: wrkimgclg, no output(*print) option -- MIDRANGE-L

Subject: RE: wrkimgclg, no output(*print) option
From: rob@xxxxxxxxx
Date: Mon, 18 Aug 2014 10:33:57 -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>

Definitely use BRMS (hence the STRBKUBRM command).
How can we tell if MOVMEDBRM is the culprit? The last save (I've been on
vacation) on this endpoint was 8/14 at 03:00. The MOVMEDBRM was on the
network system at 7am. The name of the virtual tape was not on the
QP1AVMS report. The DUPMEDBRM one was.
If it was MOVMEDBRM, I am wondering why the MOVMEDBRM would start
affecting this virtual tape? What changed to make it start doing it?

Rob Berendt

Follow-Ups:

RE: wrkimgclg, no output(*print) option , 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.