How to set which level of messages to include in the processing report in EngageOne Enrichment, formerly Streamweaver

Product Affected: EngageOne Enrichment
Product Feature: Installation / Upgrade
You can use the <Messagelevel> tag to determine which level of StreamWeaver messages to include in the processing report.  And you can use <SETMSGLEVEL> to determine what level of error message will stop the processing.  Both are used in Environment tag group.
Identifies which level of StreamWeaver messages to include in the processing report.  The /R run-time argument overrides the <MESSAGELEVEL> tag setting.

Tag Group
Environment tag group


Parameters for <MESSAGELEVEL>
LevelOne of the following:
N[ONE]—Report no messages.
D[ETAIL]—Report all messages. This is the highest level of detail.
S[EVERE]—Report only severe messages. Severe messages reflect conditions that cause StreamWeaver processing to stop.
W[ARNING]—Report warning and severe messages. Warning messages reflect error conditions that need not cause StreamWeaver to stop, but may produce unexpected results.
I[NFORMATION]—Report information, warning, and severe messages. Information messages indicate progress during StreamWeaver processing. They require no corrective action.
P[ROCESSING]—Report processing, information, warning, and severe messages. Processing messages are more specific than information messages, and may be helpful as troubleshooting aids.
Lets the user change the error level of a message so that the user can halt processing for conditions that currently cause a Detail, Warning, or Informational message. This tag also lets the user make a Warning message less severe so that it does not cause a general return code of 4 from StreamWeaver.

Note that the message level you specify with <SETMSGLEVEL> does not affect the message count that appears with message PDR0700I in the compile section of the report (at the top of the report). This count will always include all messages encountered at compile time.
UPDATED:  April 27, 2020