BRMS Media Move Problem

[Kevin Monceaux <Kevin@xxxxxxxxxxxxxx>]

System formerly known as AS/400 fans,

To make a long story not terribly long - we use BRMS with the network
feature on a host and four guest LPARs where I work.  Recently I copied our
existing media and move policies to create new media and move policies to
test some changes on our DEV LPAR.  Everything worked as expected.  I
switched the other two guest LPARs to the new media and move policies.  So
far only our daily backups have been tested with the new policies so far.
Everything is working as expected, except for a duplicate tape created on
one of our guest LPARs.  We use the auto dup feature.  The duplication job
is using the correct media policy.  If I display the duplicate tape's
attributes before running tape movements it shows the correct move policy is
set, and that it's scheduled to be moved to the correct location with the
next tape movement:

    Current location  . . . . . . . . :   TAPMLB01 
    Last moved date . . . . . . . . . :   12/07/16 
    Scheduled location  . . . . . . . :   DAILY_VLT
    Scheduled move date . . . . . . . :   12/07/16 
    Exempt from move until date . . . :   *NONE    
    Container ID  . . . . . . . . . . :   *NONE    
    Move policy . . . . . . . . . . . :   DAILY_VLT

But, when I run the tape movements its move policy gets changed to *NONE and
it gets moved to *HOME instead of DAILY_VLT.  Movements for tapes from the
other guest LPARs using the same DAILY_VLT move policy are working
correctly.  Does anyone have any idea what might be causing this?