OPS3092O USSSINI: spawn failed rc=129(81) rsn=93585469(594003D) after z/OS 3.1 upgrade
search cancel

OPS3092O USSSINI: spawn failed rc=129(81) rsn=93585469(594003D) after z/OS 3.1 upgrade

book

Article ID: 367132

calendar_today

Updated On:

Products

OPS/MVS Event Management & Automation

Issue/Introduction

We just upgraded from z/OS 2.4 to R3.1.   After IPL OPSUSS is failing initialization repeatedly.   We keep getting error:

OPS3092O USSSINI: spawn failed rc=129(81) rsn=93585469(594003D)

No changes were made to any PROCs.   The process ends and starts every 30 seconds.   

Environment

OPS/MVS 14.0 and higher

z/OS 3.1 

Resolution

From the IBM z/OS Unix System Services Messages and Codes manual, the RC 129 description reads "No such file, directory, or IPC member exists."   The first step is to verify that the USS path is there and exists.   

Also check that the BPXPARM datasets are configured according to the IBM z/OS 3.1.0 documentation. 

If the problem persists, OPS/MVS can be prevented from continually attempting to start the servers, until the problem is corrected, by setting the USSMIN parameter to the value of 0, and the USSALLOWRESTART to NO.   Then open a support case and provide the following for evaluation:   

  1. Information regarding the latest maintenance applied to OPS/MVS and what it was. 
  2. A tersed copy of the archived OPSLOG
  3. A copy of the log from one of the OPSUSS servers that may be involved.
  4. Also, if the region is up, go to the OPSVIEW Parameters screen (=4.1.1) and put USS in the NAME field.   Capture a screenshot of all screens of this display.