Permission denied when attempting to access OPSMVS rules using MTC-A
search cancel

Permission denied when attempting to access OPSMVS rules using MTC-A

book

Article ID: 227350

calendar_today

Updated On:

Products

OPS/MVS Event Management & Automation

Issue/Introduction

We can logon to the MTC-A interface however both the Rule Manager and System State Manager options in the interface display a message stating that we do not have permission to view the rules/resources. There are also messages from the TOMCAT started task STDOUT such as the following;

2021-10-22 10:02:58.777 [http-nio-9080-exec-9] INFO  c.c.m.s.RulesService - RulesService.getFilterSystems: User <userID> does not have
 permission to view <identifier>:OPSS.                                                                                                      

The MTC-A user is permitted READ access to the following RACF FACILITY class profiles where OP$MVS is the value assigned to OPSMVS variable EXTSECPREFIX and EXTSECCLASS is set to FACILITY. 

OP$MVS.OPSAOF     
OP$MVS.OPSVIEW    
OP$MVS.SQL.* (G)  

There are no ICH408I messages on the log so it appears that access is not being denied by RACF. 

Additional error messages:

 [https-jsse-nio-7100-exec-9] WARN  org.springframework.web.servlet.mvc.support.DefaultHandlerExceptionResolver - Resolv
 ed [org.springframework.http.converter.HttpMessageNotReadableException: JSON parse error: Invalid UTF-8 start byte 0xa2; nested exce
 ption is com.fasterxml.jackson.databind.JsonMappingException: Invalid UTF-8 start byte 0xa2
  at [Source: (PushbackInputStream); line: 1, column: 58] (through reference chain: com.ca.esm.models.CheckRequest["resources"]->java
 .util.ArrayList[0]->com.ca.esm.models.Resource["resourceName"])]

 

 

Environment

Release : 14.0

Component : MAINFRAME TEAM CENTER AUTOMATION

Cause

There was a bad character in the EXTSECPREFIX parameter value.

Resolution

The correct value should be:

T = OPSPRM_Set("EXTSECPREFIX","OP$MVS") 

However, due to the usage of a different host code page when the "$" character was typed its hexadecimal representation was not correct.