Error: EDC5141I Read-only file system when using OPSREST opsrexx endpoint - OPS/MVS

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 /opsrest/data/ directory must reside on a Read-Write (R/W) filesystem. Use one of the following methods to resolve the error:

1. Mount a dedicated R/W filesystem: Mount a separate ZFS or HFS filesystem in R/W mode specifically at the /usr/lpp/oem/opserver/opsrest/data mount point.
2. Use a Symbolic Link:
   • Create a directory on an existing R/W filesystem.
   • Create a symbolic link from the .../opsrest/data path to the new R/W directory.
   • Ensure the OPSREST started task user ID has Read, Write, and Execute (RWX) permissions for the target directory.

Note: Output files are temporary. The opsmvs:rexxExecOutputTimeout setting in application.yml determines how long files remain before automatic deletion (default is 60 minutes).