Expand all | Collapse all

Interfacing with Endevor

  • 1.  Interfacing with Endevor

    Posted 08-17-2019 06:43 PM
    Is anyone interfacing OPS/MVS with Endevor ? If so, please describe how you are doing it ?

    If not, would anyone be interested in an interface with Endevor, such that...
    • When a program Abends, OPS/MVS is able to find the Endevor footprint
    • The footprint identifies the Endevor Element and Package and developer userid
    • OPS/MVS sends an email to the userid with detailed Endevor information

  • 2.  RE: Interfacing with Endevor

    Posted 08-18-2019 12:33 PM
    Hi Dan,

    Yes we are interested in a different way. We keep production JCL that CA7 uses housed within Endevor. Along with the JCL element, we keep documents within Endevor that contain instructions on what to do during a job failure.  (restartt job, page out, wait next day, etc).  Our automation team wants a way for OPS/MVS to be able to read the Endevor element and/or the output component file that contains this information.  This document can then be included as part of the incident that is created. But OPS/MVS wants to do the READ.

    We have Endevor 18.0.12 installed, but the webservices are not yet operational (just brought it up on our sysplex for sysprogs only). .

  • 3.  RE: Interfacing with Endevor

    Posted 08-19-2019 10:13 AM
    Edited by John Slenska 08-19-2019 10:15 AM
    Hi Angel,
    Some suggestions that would not involve any new interface, which I think is what Dan has in mind.
    All of these solutions would require that OPS/REXX know the name of the Element and its Endevor location (ENV/SYSTEM/SUBSYS/STAGE):
    - If you know the name of the data set where the Element is housed, OPS/REXX can read the data set just like any other data set.
    - If the Element output component is compressed, there is an Endevor utility to read it into plain text.
    - If the name data set where the Element is housed is unknown, there is an existing Endevor API that OPS/REXX can use to RETRIEVE the Element.
    Just some ideas ...  Dan might have other ideas.

    Broadcom, Inc

  • 4.  RE: Interfacing with Endevor

    Posted 08-19-2019 06:26 PM
    You were reading my mind, John.
    Endevor API programs can allow the response from OPS/REXX to collect valuable information from Endevor - even when Endevor is running on an older release.

    In Angel's case, if a job abends and the job is also the name of an Endevor element, then an API can retrieve the job instructions. Although not needed in Angel's situation, additional data that can be pulled from Endevor may include things like:
    • The Date and Time of the last move to production for the element
    • The Userid of the person who made the last change
    • The Endevor package name that installed the last change