search cancel

How to fix Endevor E2E Element Logging format issue


Article ID: 112659


Updated On:


Endevor Software Change Manager (SCM) Endevor Software Change Manager - Natural Integration (SCM) Endevor Software Change Manager - ECLIPSE Plugin (SCM) Endevor Software Change Manager - Enterprise Workbench (SCM)


I have noted that there are two different formats for the E2E Element Log. 

Format one log:
 BROWSE    /shared/ndvrlog/ndvrsbx/elmlog/201804201 Line 0000000000 Col 001 080
 Command ===>                                                  Scroll ===> CSR 
********************************* Top of Data **********************************
{"actiontype":"ELM","action":"ADD","actiondate":"20180420","actiontime":"10011932","actionuserid":"TSUENDC","actionccid":"111 etc...
******************************** Bottom of Data ********************************

Format two log:
BROWSE    /shared/ndvrlog/ndvrsbx/elmlog/201804201 Line 0000000000 Col 001 080
 Command ===>                                                  Scroll ===> CSR 
********************************* Top of Data **********************************
"actioncomment":"test add scripts",                                             
"sitename":"*** UNITED HEALTH GROUP ENDEVOR ***",                              

Format two is the correct JSON format according to Endevor document, how to fix the format one issue ? 


Release: ENDAE.00200-18-Endevor-Software Change Manager


APPLY PTF SO04906 & SO05387. The second PTF is just a Web Services mainframe component because of a fix to the EN$TRMOD trace.

Additional Information