Hi Kevin,
In my shop, all of our support staff have access to view syslog/operlog , both the active and previous. W e would want to see the messaging in the syslog/operlog AND the joblog , but would want to have the ability to filter the verbose lines off of the console. This is not an effort on my par t to avoid looking up messages, but lean budgets have hit us hard, and we have lost a lot of staff. Those few of us who are left are happy for things that could save us time, especially when we are called to support a problem and have to do it on our own time. We are not at 1.13 yet and I have not seen examples of the messaging yet. Some of our customers use our central sysout repository, but our staff generally does not have access to the joblog there, except for the responsible application programmer, who would not be likely to be able use the information. Sysprogs do not have access to customer batch. For our customers who use a remote or off platform sysout respository, we have little or no access there . Thanks, Linda ----- Original Message ----- From: "W. Kevin Kelley" <[email protected]> To: [email protected] Sent: Thursday, May 3, 2012 6:46:29 PM Subject: Comments on DFSMS verbose messages? In z/OS R13, DFSMS changed approximately 400 of their rather cryptic IEC error messages to include additional lines of explanation. Feedback from R13 ESP customers indicated that the additional lines of explanation were appreciated for end-users but were not wanted in the SYSLOG/OPERLOG or on consoles. A suggestion was made that the additional lines of explanation be written only to the JOBLOG and not to other places that the message might go. z/OS OA37957 and DFSMS OA37505 provide the suggested support: the additional lines of explanation -- now referred to as "verbose message lines" -- are written only to the JOBLOG; they are not included with the message if it is written to the SYSLOG/OPERLOG or queued to a console. A new .MSGOPTION statement has been added to MPFLSTxx to allow you to enable or disable verbose message support at a system level: if the support is disabled (the default), the DFSMS error messages will not include additional lines of explanation; if the support is enabled, the DFSMS error messages will include the additional lines of explanation, but the verbose message lines will be written only to the JOBLOG. The DISPLAY MPF command response now displays the MSGOPTION enablement state. If verbose message support is enabled, the additional message lines are visible in MPF exits and are visible on the Subsystem Interface (SSI). The following control blocks have been modified to provide an indication if a verbose message line is present: WPL, WQE, CTXT and MDB. We have been in contact with the various automation venders and they are all aware of how to recognize verbose message lines. We expect that most venders will choose to ignore the verbose message lines. Any comments/criticisms/suggestions? W. Kevin Kelley -- IBM POK Lab -- z/OS Core Technical Development ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
