Selecting end-to-end server messages

The output devices for the end-to-end server messages are the following:
  • The server MLOG; this file records the EQQ-prefixed messages issued by IBM Z Workload Scheduler and most of the EQQPT-prefixed messages issuing from the end-to-end with fault-tolerance capabilities environment.
  • The stdlist directory in the workdir (TWSMERGE.log, E2EMERGE.log, and NETMAN.log); these files record all the EQQPT-prefixed messages issuing from the end-to-end with fault-tolerance capabilities environment and all the messages issuing from the IBM Workload Scheduler processes (prefixed by AWS).

You can edit the TWSCCLog.properties file located in the end-to-end work directory in UNIX™ Systems Services to specify that some or all of these messages are re-directed to either or both the MLOG and the system output console (SYSLOG). To use this functionality, you must apply the fix for APAR PK11341 on IBM Z Workload Scheduler.

To specify the messages, you can modify the following TWSCCLog.properties keywords:
console.msgIdFilter.msgIds
Where you list the messages that are to be sent to the syslog upon issue.

If you leave blank, it implies no messages are to be sent to the syslog.

tws.console.msgIdFilter.msgIds
Where you list the messages that must be prevented from being sent to the syslog upon issue. This keyword can be useful when you use the wildcard character in console.msgIdFilter.msgIds.

If you leave blank, it implies no messages are to be prevented from being sent to the syslog.

ServerMlog.msgIdFilter.msgIds
Where you list the messages that are to be sent to the end-to-end server mlog upon issue.

If you leave blank, it implies no messages are to be sent to the mlog.

tws.ServerMlog.msgIdFilter.msgIds
Where you list the messages that are not to be sent to the end-to-end server mlog upon issue. This keyword can be useful when you use the wildcard character in ServerMlog.msgIdFilter.msgIds.

If you leave blank, it implies no messages are to be prevented from being sent to the mlog.

The changes made to TWSCCLog.properties become active when the server task is restarted.