Problems running Restore Archived History (Mapics/DB Rel4)

Trying to restore MAPICS payroll history via menu AMPM14 option 3 "Restore
Archived History"

We don't run this often, but have run it before with no problems.  Today,
however, it's hanging up on an authority issue.  From the job log:

3 > mapics
    Current library changed to *CRTDFT.
    Library list changed.
    Library list changed.
    Current library changed to *CRTDFT.
    Data area ZZLDA created in library QTEMP.
    Object Q5728SS1 in library QSYS not found.
    Object ACTJOBLST in QTEMP type *USRSPC deleted.
              JOB AMPM14-03  (AMPPWC) INITIATED
    Object PRHS09 in *LIBL type *FILE not found.
    Object PRHD09 in *LIBL type *FILE not found.
    Volume PRHIST found on device TAP01.
    Volume PRHIST found on device TAP01.
    File PRHS09 in library QTEMP restored.
    File PRHD09 in library QTEMP restored.
    PRHD09 restored with public authority *EXCLUDE.
    1 security or data format changes occurred.
    2 objects restored. 0 not restored to QTEMP.
    S AX-9999 APPLICATION FUNCTION CHECK
    S AX-9999 APPLICATION FUNCTION CHECK
    Object PRHS09 in QTEMP type *FILE deleted.
    Object PRHD09 in QTEMP type *FILE deleted.
    W AM-2222 JOB CANCELED F24
    E AM-0937 PROGRAM MALFUNCTION
    OVRPRTF FILE() OUTQ() COPIES() LPI() CPI() FORM...
      DEVTYPE() PRTQLTY() FONT() USRDTA()
      AM-0228 JOB IS CANCELED
    S AX-9999 APPLICATION FUNCTION CHECK
    Object UJBHLD in library QTEMP not found.
    File AMZMENU was already closed, never op...

FYI, the signed-on user is QSECOFR.  Apparently, MAPICS is hiccuping on
PRHD09's authority.

It is my understanding that both PRHx09 are derived from PRHxWK.  Both of
the PRHxWK files are owned by AMAPICS with *PUBLIC *EXCLUDE.  There is also
an authorization list that our I.S. director has *ALL authority assigned,
and the HR users authorized to *USE.  *PUBLIC is *EXCLUDEd here as well.
QSECOFR is not on this list.

I am not a security gury, but my first guess is that QSECOFR is not allowed
to run this job.  I suppose it should be run by one of the users in the
authorization list (is *USE sufficient for this job?) or by the AMAPICS sign
on.

Advice welcomed.

db