OPS/MVS

 View Only

  • 1.  EOM - Tasks failing with bad CC

    Posted Jun 13, 2019 12:49 PM
    Hello,

    As more and more started task use USS and other connections, started task fail with Cond Code instead of abending.  How do you handles these types of task in SSM.


  • 2.  RE: EOM - Tasks failing with bad CC
    Best Answer

    Broadcom Employee
    Posted Jun 14, 2019 02:45 AM
    HI Randy,
    For controlling an STC under control of SSM, you have the SSMEOM rule (CCLXRULM) to check the status at the end.

    This rule will process EOM events for all SSM managed STC resources, and set their CURRENT_STATE values based on specific state conditions and/or the type of job. These conditions are outlined in the processing section below.

    This rule demonstrates:
     1) Use of EOM rules.
     2) Utilizing the SELECT/WHEN/OTHERWISE REXX instruction to perform condition checking
     3) Utilizing the Address Sql Host Environment to manipulate RDF tables.

    Steps needed for implementation using as is logic.
    1) Review and customize the SSMFAIL rule. Logic within this SSMEOM rule will detect abnormal terminations of STCs
        (result of abend, JCL, etc) and set the CURRENT_STATE to TERM triggering SSMFAIL from the TERM_UP action.
    2) Ensure this rule is enabled/auto-enabled in a production AOF ruleset.

    ------------------------------
    Hennie Hermans
    Principal Support Engineer
    Broadcom
    ------------------------------

    Original Message


  • 3.  RE: EOM - Tasks failing with bad CC

    Posted Jun 14, 2019 08:13 AM
    Depending on your environment, could you not go with an EOJ rule and check the MAXCC value to determine if the state should be "ABEND" or simply "DOWN"? An EOJ rule would eliminate having to account for all the various MVS abend messages

    ------------------------------
    Michael Dixon
    Perspecta
    ------------------------------

    Original Message


  • 4.  RE: EOM - Tasks failing with bad CC

    Posted Jun 14, 2019 10:38 AM
    I don't think EOM will catch it  there is no EOM.MAXCC for eom variables.  

    example:

    07.14.21 S0019987 XACT# STARTING ARHJMAIN ARHMAIN 96 0:05.06 0:00.03
    07.14.21 S0019987 IEF404I ARHJMAIN - ENDED - TIME=07.14.21
    07.14.21 S0019987 XACT1 *-*-*-*-*- J O B S T E P S U M M A R Y -*-*-*-*-*-
    07.14.21 S0019987 XACT2 JOB PROC PROGRAM CC EXEC-TIME CPU-TIME
    07.14.21 S0019987 XACT3 STEP STEP NAME @MMM:SS.TH @MMM:SS.TH
    07.14.21 S0019987 XACT5 STARTING ARHJMAIN ARHMAIN 96 0:05.06 0:00.03
    07.14.21 S0019987 $HASP395 ARHJMAIN ENDED - RC=0096
    Original Message