Testing and logging related policies #2067
Conversation
Signed-off-by: Jakub Balhar <[email protected]>
Signed-off-by: Jakub Balhar <[email protected]>
Quality Assurance - Focus on possible team work. Signed-off-by: Jakub Balhar <[email protected]>
Signed-off-by: Jakub Balhar <[email protected]>
Signed-off-by: Jakub Balhar <[email protected]>
Signed-off-by: Jakub Balhar <[email protected]>
Signed-off-by: Jakub Balhar <[email protected]>
Signed-off-by: Jakub Balhar <[email protected]>
Signed-off-by: Jakub Balhar <[email protected]>
Signed-off-by: Jakub Balhar <[email protected]>
Signed-off-by: Jakub Balhar <[email protected]>
Signed-off-by: Jakub Balhar <[email protected]>
Signed-off-by: Jakub Balhar <[email protected]>
|
|
||
| An example of a message is: *ZWEAG123E An error with z/OSMF authentication* | ||
|
|
||
| ## What do we log |
There was a problem hiding this comment.
perhaps a subtle distinction - this section starts with "Message Management" but discusses "What do we log". Should it be "When to Issue Messages?"
I wonder if messages are something that are presented to a user to convey information while a log is something to help diagnose a previous problem. The difference being that backend logs for a component wouldnt need to prepend all of their log messages with a ZWE identifier
| #### Client Side | ||
|
|
||
| C - Zowe CLI | ||
| E - Zowe VSCode Explorer |
There was a problem hiding this comment.
In practice, does this mean Zowe Explorer messages like job submission failed would be presented as a ZWEExxxxE message? The benefit being that we could distinguish this type of error from an extension error or some other error message?
|
|
||
| **nnnn** - is a linear sequence starting from 0001 to 9999. | ||
|
|
||
| **t** - is a Type. One of (I, E, A, W) General conventions by IBM are **I**nform, **E**ventual Action (often construed as error), **A**ction, **W**arning or **S**evere error |
There was a problem hiding this comment.
"One of (I, W, E, S)"? Unless we think we have a need for "A"...
|
|
||
| ### Message Formats | ||
|
|
||
| ZWEcnnnnt, ZWEcsnnnt or ZWEcsxnnt {Actual message} where: |
There was a problem hiding this comment.
perhaps a note that WTO messages should be 8 characters with proper route and descriptor codes according to the message. we probably don't want to duplicate what's proper and rather refer to IBM publications?
No description provided.