Idea Details

OPSLOG - Robust Wildcarding of MSGID Parm in PROFILE & OPSLOG() Function

Last activity 12-29-2017 10:50 AM
Anon Anon's profile image
02-21-2014 09:42 AM

As a user of OPSLOG for diagnosing problem activity, I would like the OPSLOG PROFILE to support message wildcarding.

============================================================================================================

1. When in opslog profile if a msgid is specified, one or more '*' may be present at any position.

2. The '*' will match 0 or more characters of any value.

3. All messages with matching ids (based on the rules of * usage) must be returned/visible

4. No messages that do not match the id specified (based on the rules of  * usage)  may be returned

5. All functionality of profile must also available in the OPSLOG() function

6. The user must be able to change the wild card character with an OPS/MVS parameter


Comments

12-29-2017 10:50 AM

Seems like the same nomenclature used by OPSLIKE would suffice - at least for me.

05-11-2016 01:44 PM

In CA OPS/MVS backlog as:

US99799 - OPSLOG - Robust Wildcarding of MSGID Parm in PROFILE & OPSLOG() Function

06-18-2014 03:44 AM

I assume you mean extended wildcarding, as MSGID* is already possible.

MS*ID would be nice or M%%ID*