Patterns for allocating packet trace files (PTF BPN2471 applied)


MainView for IP allows you to specify a name pattern for automatically allocating packet trace files. When you use the WRITE, RAW, or SNIFF action on the PKTTRACE view to write packet traces to files, MainView for IP generates the file name by using the name pattern specified on the MVIPCNFD view. The file names that the pattern generates must adhere to the naming conventions and limitations for IBM MVS data sets:

  • The generated name cannot exceed 44 characters.
  • Each qualifier cannot exceed 8 characters.
  • The first character of any qualifier must be an alphanumeric character or or a special character such as $, #, or @. 

The product rejects any pattern that would violate the naming conventions for MVS data sets by highlighting the field in red.

The product allows the following symbols only for the file names. As shown in the table, each symbol must begin with an ampersand (&) and end with a period (.).

Symbols

Description

&USERID.

TSO user ID of the user who is invoking the packet trace action on the PKTTRACE view

&SYSNAME.

4-character system name

&TYPE.

Type of packet trace file being written (WRITE, RAW, or SNIFF)

&SEQN.

Sequence number that increments with every successful file allocation

&YYMMDD. or &MMDDYY.   

Date when the file is allocated

&HHMMSS.

Time when the file is allocated

Use the date, time or sequence symbols to ensure uniqueness. You can also use an existing packet trace file. You can modify the file name on the Multi Platform Dialog (MPD) after the packet trace action is invoked.

The default file name pattern is &USERID..MVIP.&SYSNAME..&TYPE..D&YYMMDD..T&HHMMSS.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

MainView for IP 3.6