Shutdown Process ID Inconsistences

book

Article ID: 206796

calendar_today

Updated On:

Products

CA OPS/MVS Event Management & Automation

Issue/Introduction

Why during our shutdown process it seems OPS is using the ID of BPXOINIT and at other times an ID that has access to ROPR authority?

OPS7902O STATEMAN ACTION FOR STCTBL.DBXXMSTR: UP_DOWN MVSCMD=$QD,DBXXPROD
OPS1181H OPSMAIN       (*Local*) MVS N/A userid $QD,DBXXPROD
OPS7902O STATEMAN ACTION FOR STCTBL.DBXXMSTR: UP_DOWN MVSCMD=$QD,XXXPROD
OPS1181H OPSMAIN       (*Local*) MVS N/A userid $QD,XXXPROD
ACF04056 ACCESS TO RESOURCE JES2.DELETE.OSEM TYPE ROPR BY BPXOINIT NOT AUTHORIZED $QD,XXXPROD
IEF196I ACF04056 ACCESS TO RESOURCE JES2.DELETE.OSEM TYPE ROPR BY
IEF196I BPXOINIT NOT AUTHORIZED
OPS7902O STATEMAN ACTION FOR STCTBL.DBXXMSTR: UP_DOWN MVSCMD=$QD,ZXXX
OPS1181H OPSMAIN       (*Local*) MVS N/A userid $QD,ZXXX
$HASP000 FXXXNNNN COMMAND REJECTED - AUTHORIZATION FAILURE

Cause

OPS/MVS does not change the userid that is assigned to it. A rule was using the SETUID command before using USS services and this was the cause of the problem. The instruction was:


UID = OPSUSS('SET','EUID',0)

Environment

Release : 13.5

Component : OPS/MVS

Resolution

Removing this instruction from the rule solved this problem.