RE: wrkimgclg, no output(*print) option

Rob,

<I think it is the DUPMEDBRM command defaults. IIRC, the source media is always *UNLOAD.>

What are current defaults for DUPMEDBRM?
Did you have any custom changes that may have been lost on unload/reload?
Check the joblogs for DUPMEDBRM job, compare before and after?
Check the FROMENDOPT and TOENDOPT.

Message . . . . : -QSYS/DUPMEDBRM VOL(*LIST) FROMDEV(TAPMLB01)
TODEV(TAPMLB01) FROMSEQNBR(0000030313 0000030719) MEDPCY(CYCBRC35D)
FROMVOL(001196) FROMENDOPT(*LEAVE) TOENDOPT(*LEAVE) SAVMEDINF(*LIB)

Paul

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Sue Baker
Sent: Monday, August 18, 2014 1:03 PM
To: midrange-l@xxxxxxxxxxxx
Subject: RE: wrkimgclg, no output(*print) option

rob@xxxxxxxxx wrote on Mon, 18 Aug 2014 14:33:57 GMT:

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?

I think it is the DUPMEDBRM command defaults. IIRC, the source media is always *UNLOAD.