Create a New Hiperstation for WebSphere MQ Search Rule

The MQ Search tab allows you to access, create, modify, save search rules and submit search requests. You can specify complex search conditions for locating 3270 sessions based on the content of output window data within the selected archive. You can make this search request local (for yourself only), or, with the proper authorization, you can make a global search request that any authorized user can use.

To Create a New Search Rule:

1. Double-click Search Rules on the MQ Application Auditing bar. A blank MQ Search tab will open allowing you to create a search request. The tab also lists the mainframe machine the rule is created for.

2. Type a name for your search rule in the Request Name text box.

   Request names must follow standard ISPF naming conventions. The name can be alphanumeric, up to eight characters in length, and must start with a letter.

3. Check or clear the Globally Available box. If unchecked, only the originator will be able to view the search request. Global requests can be viewed by all authorized users.

   Warning

   Note

   Only users with Global Recording Administrator authority on the mainframe are authorized to create global search requests. If you do not have Global Recording Administrator authority, this field does not appear on your window.

4. The information you can search on is located in an archive that has previously been created. Select an archive from the Archive list. You can click Refresh to update the Archive list or the Archive Properties button to view the properties for the selected archive.

   If you select an existing search request, you must still select an archive. There is no default archive.

5. If desired, specify a date range by filling in the From Date and Time and the To Date and Time fields. This will limit the archive search to a specific time period rather than the entire archive repository set.
6. To narrow the search, you can specify one or more of the filters. To select all data that meets the other criteria, put an asterisk (*) in each of these fields. Asterisk is the default for these filters. Wildcards are supported.
   • Qmgr: The queue manager to include.
   • Queue/Object: The queue or object name to include.
   • Job Name: This can be a specific job name, range of job names, or all job names to include.
   • PutApplName: The name of the application responsible for putting the message on the queue to include.
   • User Identifier: the user identifiers associated with the events to include.

7. Type the information that you want to search for in the Search String text box and click Add.

   The search string will now appear in the search table. The search strings are executed in the order they appear in the list. The buttons Move Up, Repeat Row, Delete Row, and Move Down allow you to rearrange, add, or delete search strings. The combined search strings create a search rule.

   • If you add more than one search string, select AND or OR from the list.
   • The right and left parentheses ( ) can be used to build conditional searches.

   • Select an Operator from the list. The list contains standard relational operators.

     For filters with relational operators CO (Contains) or NC (Not Contains), length will designate which portion of the repository message data is to be searched. If a 0 (zero) length is given, the message data area to be searched is from the start position to the end of that data record. If a non-zero length is specified, the searched section is from the start position for the length specified (for example, if start=10 and length=20, message positions 10..29 are selected for searching. This allows you to search specific fields only with a captured data message. The length of the data to be searched for is determined by the length of the entered search string (for example, if the search string is "street", the length of the searched for string is 6).

     Note: Previously, specifying a length longer than the length of the search string caused the search string to be padded to the entered length. This function can be replicated by utilizing HEX type data and explicitly adding the hexadecimal equivalent of the required pad characters.

   • Type is the format of the search string.
   • Start is the position to start searching.
   • Len is the length of the search string padded with blanks.
8. Save or Clear your search rule:
   • Click  (Submit) to save your search rule, start your search immediately and create your report. A message will appear giving a date and time when the report was submitted. When execution is complete, the report will appear in the tree view. You may need to click the refresh button in the tree view to refresh the Reports list with your report when it has finished executing.
   • Click  (Queue) to save your search rule and queue your report for later submission.
   • Click  (Save) to save your search rule for future use. It will be saved with the name you entered in the Request Name field. After it is saved, it will appear in the tree view with either a local rule icon or a global rule icon depending on the choice you made when you created the rule.
   • Click  (Clear) to start over without saving your search rule.

Related Topics

Using Hiperstation for WebSphere MQ Search Rules