How to fix Endevor E2E Element Logging format issue
Article ID: 112659
Updated On:
Products
Issue/Introduction
Noted that there are two different formats for the E2E Element Log.
Format one log:
BROWSE /xxxxxx/xxxxxx/xxxxxx/elmlog/201804201 Line 0000000000 Col 001 080
Command ===> Scroll ===> CSR
********************************* Top of Data **********************************
{"actiontype":"ELM","action":"ADD","actiondate":"20180420","actiontime":"10011932",<remaining content remove>
******************************** Bottom of Data ********************************
Format two log:
BROWSE /xxxxxx/xxxxxx/xxxxxx/elmlog/201804201 Line 0000000000 Col 001 080
Command ===> Scroll ===> CSR
********************************* Top of Data **********************************
{
"actiontype":"ELM",
"action":"ADD",
"actiondate":"20180420",
"actiontime":"10032755",
<remaining content removed>
}
Format two is the correct JSON format according to Endevor document, how to fix the format one issue ?
Environment
Release 18.0 Only
Resolution
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
Feedback
