Endevor End to End logging to be done under the alternate ID.

Idea created by EdwardMarks on Sep 3, 2018
    • Karen_Turner
    • Eoin
    • berbe02
    • SatyasaiBACI
    • Phon_Shuffitt
    • EdwardMarks

    With the current design, all Endevor users need an OMVS segment in order to use the end to end logging feature. This is because this processing is done under the security scope of the user (that is, does not swap to the alternate ID) and manages Z/OS Unix paths and files (which require the involved userid to have an OMVS segment).


    My idea is to swap the security scope of the process to the alternate ID to perform the E2E logging.