MRIOPSSC Job producing no output

Products

• OPS/MVS Event Management & Automation

Issue/Introduction

Despite messages indicating otherwise, no datasets are being allocated by the job MRIOPSSC.

OPSMRI002I Processing subsys OPSS                                                                              

OPSMRI003I MRI SCAN DATA SAVED IN DSNAME('outhlw..OPSSCAN.<sysplex>.<system>.<ssid>')

Environment

OPS/MVS MRI

Cause

Wrong allocation parameters. In this case, it was a storage class that did not exist in the environment.

Resolution

Using a valid storage class for the environment solved this problem.
The allocation parameters are defined in the job MRIOPSSC:

//  SET TYPE=STORCLAS   
//  SET SUBTYPE=xxxx    

d. TYPE     - type of disk allocation.  For SMS managed       
              storage, specify STORCLAS or DATACLAS, otherwise
              specify UNIT                                    
e. SUBTYPE  - For SMS managed storage, specify the name of    
              the storage class or data class, otherwise      
              specify the desired device/unit type.