SSMSHUT command does not bring down resources in STCTBL after upgrade to newest release of OPS/MVS

Products

• OPS/MVS Event Management & Automation

Issue/Introduction

After upgrading OPSMVS, when SSMSHUT is called from a console via !OI SSMSHUT, it is not shutting down any resources.

Environment

 OPS/MVS 14.0 and subsequent releases 

Resolution

Check to see if there is a security rule preventing the USERID, that issued the !OI command, from executing the OPSSSMTBL function.

The OSFCHAR command prefix was changed. In previous releases, if you issue a command using the OSFCHAR (default is "!") the USERID checked would be the one set in the parameter OSFCONSOLE.  As of release 14.0 it is the actual USERID that issued the command or the USERID assigned to the console where it was issued.

When parameter OSFALLOW is set to YES, such commands that originate from any source other than an MCS console are secured using the credentials of the USERID of that issuing unit of work. In prior releases of OPS/MVS, those commands are secured using the credentials of the USERID specified by the OSFCONSOLE parameter.

Example:

Suppose that parameter OSFCHAR is set to '!' (the default) and a TSO user issues the command TSO OPSCMD COMMAND(!OI rexx arg).  In OPS/MVS version 14.0, the credentials of the TSO user are used to authorize their use of the OSF. In prior releases of OPS/MVS, the credentials of the USERID specified by the OSFCONSOLE parameter are used.