OPSREST - Calling opsrexx GET with token returns error EDC5141I Read-only file system.
search cancel

OPSREST - Calling opsrexx GET with token returns error EDC5141I Read-only file system.

book

Article ID: 410858

calendar_today

Updated On:

Products

OPS/MVS Event Management & Automation

Issue/Introduction

Using address USS WEBREQ to call OPSREST with /opsrexx/{token} endpoint to query for the output of an OPS/REXX.  Here is a dump of the response body:

WEBREQ.BODY.TEXT: Length= 374 of 374
    {"instanceToken":"xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx","program":"pppppp.ppp.REXX(
    jjjjjjjjjj)","arg":"parm1 parm2 parm3","subsystem":"OPSS","output":[],"errorMessag
    e":"OPS$6399E Error reading output from REXX program. Cause = '/sample/user_path/
    /opsrest/data/xxxxxxxxxxxxxxxxxxxxxxxxxxxx.stdout: EDC5141I Read-only file system.
    (errno2=0x05620060)'","returnCode":"10013"}

Environment

OPS/MVS

Cause

The file system where the .../opsrest/data directory resides was mounted as read-only 

Resolution

The output of a REXX execution is supposed to be temporary data so it is deleted after it is retrieved using the GET /opsrexx/{token} endpoint

If the output is not retrieved in an interval of time set in the application.yml file it is automatically deleted. From documentation:

opsmvs:rexxExecOutputTimeout
The number of elapsed minutes after a launched OPS/REXX program completes execution before deleting any stored program output. The default time is 60 seconds.