OPS/MVS MSF Issue STATESET FAILED RESULT=24
Article ID: 132585
Updated On:
Products
OPS/MVS Event Management & Automation
Issue/Introduction
Customer applied recent maintenance to OPS/MVS 13.0 for MSF and continues to encounter STATESET errors in his log:
For a recent MSF connectivity issue, i applied PTFs SO03909 and SO04984. During system shutdown one of the task switch from A lpar to B Lpar, and while A Lpar was starting, that task again moved to A Lpar. Today i applied the maintance, and it seems like same issue is occurring. Please find the below error message.
01:38:28 OPS0997T *-* 1522: call stateset rsrc "DESIRED(UP) ACTMODE(RESUME)",
01:38:28 OPS0997T >V> AD10STRT
01:38:28 OPS0997T >L> DESIRED(UP) ACTMODE(RESUME)
01:38:28 OPS0997T >O> AD10STRT DESIRED(UP) ACTMODE(RESUME)
01:38:28 OPS0997T >L> SYSTEM( 01:38:28 OPS0997T >O> AD10STRT DESIRED(UP) ACTMODE(RESUME) SYSTEM(
01:38:28 OPS0997T >V> SYSE 01:38:28 OPS0997T >O> AD10STRT DESIRED(UP) ACTMODE(RESUME) SYSTEM(SYSE
01:38:28 OPS0997T >L> ) 01:38:28 OPS0997T >O> AD10STRT DESIRED(UP) ACTMODE(RESUME) SYSTEM(SYSE)
01:38:39 OPS3092H STATESET01 OPS/REXX EXEC LPR008 FAILED - DIAGNOSTIC DATA FOLLows
01:38:39 OPS3092H STATESET02 OPS/REXX EXEC LPR008 FAILED - FAILING STMT # - 1 : 421 01:38:39 OPS3092H STATESET03 OPS/REXX EXEC LPR008 FAILED - FAILING STMT - 1 : End 01:38:39 OPS3092H STATESET02 OPS/REXX EXEC LPR008 FAILED - FAILING STMT # : 422 01:38:39 OPS3092H STATESET03 OPS/REXX EXEC LPR008 FAILED - FAILING STMT : If xrc > 0 Then 01:38:39 OPS3092H STATESET04 OPS/REXX EXEC LPR008 FAILED - FAILING STMT RC : 0 01:38:39 OPS3092H OPSPRM/OPSPARM COMMAND GENERATED NO OUTPUT
01:38:39 OPS0997T >F> 24 01:38:39 OPS0997T >>> RESULT=24
01:38:39 OPS0997T *-* 1524:exit 0 01:38:39 OPS0997T >L> 0 01:38:39 OPS3092H READY
For a recent MSF connectivity issue, i applied PTFs SO03909 and SO04984. During system shutdown one of the task switch from A lpar to B Lpar, and while A Lpar was starting, that task again moved to A Lpar. Today i applied the maintance, and it seems like same issue is occurring. Please find the below error message.
01:38:28 OPS0997T *-* 1522: call stateset rsrc "DESIRED(UP) ACTMODE(RESUME)",
01:38:28 OPS0997T >V> AD10STRT
01:38:28 OPS0997T >L> DESIRED(UP) ACTMODE(RESUME)
01:38:28 OPS0997T >O> AD10STRT DESIRED(UP) ACTMODE(RESUME)
01:38:28 OPS0997T >L> SYSTEM( 01:38:28 OPS0997T >O> AD10STRT DESIRED(UP) ACTMODE(RESUME) SYSTEM(
01:38:28 OPS0997T >V> SYSE 01:38:28 OPS0997T >O> AD10STRT DESIRED(UP) ACTMODE(RESUME) SYSTEM(SYSE
01:38:28 OPS0997T >L> ) 01:38:28 OPS0997T >O> AD10STRT DESIRED(UP) ACTMODE(RESUME) SYSTEM(SYSE)
01:38:39 OPS3092H STATESET01 OPS/REXX EXEC LPR008 FAILED - DIAGNOSTIC DATA FOLLows
01:38:39 OPS3092H STATESET02 OPS/REXX EXEC LPR008 FAILED - FAILING STMT # - 1 : 421 01:38:39 OPS3092H STATESET03 OPS/REXX EXEC LPR008 FAILED - FAILING STMT - 1 : End 01:38:39 OPS3092H STATESET02 OPS/REXX EXEC LPR008 FAILED - FAILING STMT # : 422 01:38:39 OPS3092H STATESET03 OPS/REXX EXEC LPR008 FAILED - FAILING STMT : If xrc > 0 Then 01:38:39 OPS3092H STATESET04 OPS/REXX EXEC LPR008 FAILED - FAILING STMT RC : 0 01:38:39 OPS3092H OPSPRM/OPSPARM COMMAND GENERATED NO OUTPUT
01:38:39 OPS0997T >F> 24 01:38:39 OPS0997T >>> RESULT=24
01:38:39 OPS0997T *-* 1524:exit 0 01:38:39 OPS0997T >L> 0 01:38:39 OPS3092H READY
Environment
Release:
Component: OPSMVS
Component: OPSMVS
Resolution
We recommended adding SYSWAIT (20) to his CALL STATESET statement in his program to aid with the time constraint, which was interferring.
Ensure that SO00534 is also applied.
Customer had to review the security rules on both applicable systems.
Ensure that SO00534 is also applied.
Customer had to review the security rules on both applicable systems.
Feedback
Yes
No
Powered by
