IBM Support

Debugging AOFUXMON RC=08 error

Troubleshooting


Problem

AOFUXMON ends with RC=08. The return code means: The resource is inactive or OMVS is inactive. But the resource is actually up and running. How to figure out what the cause of the error is.

Symptom

Set trace 'AOCTRACE AOFUXMON ON'

The output will look like this:



19:25:25 U AOF700I CLIST AOFRSUSS EXECUTING ON AUTWRK15 WITH
PARMS > JOBNAME=VR2ADMER,/BIN/TCSH -C
'/U/VR2ADM/STARTSAP_ASCS ERS >&
/U/VR2ADM/STARTSAP_ASCS_ERS.WMV1.LOG'
19:25:35 | AOFUXMON debugging information:
19:25:35 | =>USS resource data:
19:25:35 | . Subsystem name : VR2_ERS
19:25:35 | . USS Path : ./ers.sapVR2_ASCS30
19:25:35 | . USS Filter :
19:25:35 | . USS Port :
19:25:35 | . IP Stack :
19:25:35 | . USS File :
19:25:35 | . USS UserID : VR2ADM
19:25:35 | . Monitor CMD :
19:25:35 | . Config job name : VR2ADMER
19:25:35 | . USS job name :
19:25:35 | . ASID :
19:25:35 | . PID :
19:25:35 | . Category : USS
19:25:35 | . Jobtype : MVS
19:25:35 | AOFUXMON debugging information:
19:25:35 | =>Monitored USS resource:
19:25:35 | . Affected subsystem : VR2_ERS
19:25:35 | . INGPYXSR parm #1 : ./ers.sapVR2_ASCS30
19:25:35 | . INGPYXSR parm #2 : VR2ADM
19:25:35 | . INGPYXSR parm #3 :
19:25:35 | . INGPYXSR parm #4 : yxsr_resp
19:25:35 | . INGPYXSR parm #5 :
19:25:35 | . RC of INGPYXSR : 8
19:25:35 | . Returned string :
19:25:36 U AOF702I CLIST AOFUXMON COMPLETED ON AUTWRK15
WITH RETURN CODE 8

Cause

What is happening is the startsap script is run on the UNIX side and
something is happening to make
RC=08. The reason the script failed is on the UNIX side - either in
STDOUT, STDERR or the log specified on the start command - /u/vr2adm/startsap_ascs_ERS.WMV1.log

Diagnosing The Problem

Review the INGUSS command for the APL and see that there is a FDOPEN=YES parm. INGUSS is used in Policy to easily send the command to USS for execution and start the monitor. You will need to update the POLICY to add the FDOPEN=YES parm to the UNIX Start Command, Build and Refresh to pick this change up.

UNIX Start Command before:


INGUSS JOBNAME=VR2ADMER,/bin/tcsh -c
'/u/vr2adm/startsap_ascs ERS >& /u/vr2adm/startsap_ascs_ERS.WMV1.log'

UNIX Start Command with FDOPEN coded:
INGUSS JOBNAME=VR2ADMER FDOPEN=YES,/bin/tcsh -c
'/u/vr2adm/startsap_ascs ERS >& /u/vr2adm/startsap_ascs_ERS.WMV1.log'

Resolving The Problem

Once the Policy is updated with FDOPEN and the policy is loaded, run the Monitor.

One possibility is to check is for message BPXF024I in the syslog. These messages will contain additional information as a result of the FDOPEN=YES. Also check SYSLOGD on the OMVS side for messages.

If no messages including BPXF024I show up in the SYSLOG or SYSLOGD then look in the log specified in the INGUSS Start Command. In the example shown in this technote, the log in question would be:

/u/vr2adm/startsap_ascs_ERS.WMV1.log

Reviewing this log shows the following messages:

    00Ý84084039¨: Unable to change to Directory /usr/sap//D00/work.
    (Error 129 EDC5129I No such file or directory.) [/bas/745_REL/src/proj/ntserv/ntservsserver.cpp 4154]

This message indicates a problem with the OMVS Segment not being set up correctly to allow switching to any user ID associated with z/OS UNIX resources (access to BPX.SRV.userid or BPX.SUPERUSER to start root programs).

Verify the setup to ensure AUTOTASKS have a OMVS segment and access to BPX.SUPERUSER. You do not have to make the definitions for the auto operators yourself. The INGESAF member contains all the RACF commands that are necessary to add a user and set the necessary characteristics. Included is the definition of an OMVS segment and read access to BPX.SUPERUSER for those auto operators that can automate USS processes.

INGESAF shows the following:


 * Allows users to switch to superuser authority.
 *-----------------------------------------------*
 RDEFINE FACILITY BPX.SUPERUSER UACC(NONE)
 PERMIT  BPX.SUPERUSER CL(FACILITY) ACCESS(READ) +
  ID(AUTWRK01 AUTWRK02 AUTWRK03 AUTWRK04 AUTWRK05 +
     AUTWRK06 AUTWRK07 AUTWRK08 AUTWRK09 AUTWRK10 +
     AUTWRK11 AUTWRK12 AUTWRK13 AUTWRK14 AUTWRK15 +
     AUTWRK16 AUTWRK17 AUTWRK18 AUTWRK19 AUTWRK20)

[{"Product":{"code":"SSWRCJ","label":"IBM Tivoli System Automation for z\/OS"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Component":"--","Platform":[{"code":"PF035","label":"z\/OS"}],"Version":"All Versions","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]

Document Information

Modified date:
08 August 2018

UID

swg21986301

Page Feedback