Entire Net-Work Diagnostic Utilities

#### Search Results

Search

# Entire Net-Work Diagnostic Utilities

This section describes the Entire Net-Work diagnostic utilities, which are provided in the Entire Net-Work load library.

- NETPFIL1 Utility

- NETPFIL2 Utility

- Example JCL

The Adabas modules required by the utilities are provided in the WALvrs library distributed with Entire Net-Work. See the section Product Code Description in Entire Net-Work Release Notes and the Software GmbH product Delivery Report.

## NETPFIL1 Utility

The NETPFIL1 utility is used to select the information to be printed from the Entire Net-Work NETPRNT file. The Entire Net-Work NETPRNT file contains tracing, logging, and dump output. The NETPRNT file should be used as input to the NETPFIL1 utility for the NETFILE file.

NETPFIL1 can be used to select

- only those records that fall within a certain date and time frame,

- only logging and dump records that match the title or any desired portion of the title,

- only trace records that match the title or any desired portion of the title, or

- any combination of the above.

The output from NETPFIL1 can be used as input to the NETPFIL2 Utility to perform additional filtering.

### NETPFIL1 Parameters

This section describes the parameters for the NETPFIL1 utility.

> DATE

>       DATE=yyyymmdd

>   Only records created on the specified date are written to DDPRINT. The default value is all dates.

> STARTTIME

>       STARTTIME=hhmmssth

>   Records created before the specified time are not written to DDPRINT and are not checked for other selection criteria. The default is no restriction on the start time.

> ENDTIME

>       ENDTIME=hhmmssth

>   Records created after the specified time are not written to DDPRINT and are not checked for other selection criteria. The default is no restriction on the end time.

> LOG

>       LOG=log-title

>   Log and dump records with a title that matches the specified log title are written to DDPRINT.

>   The log title must be specified exactly as it appears in the NETPRNT file; the value specified can be limited to the number of characters necessary to select the desired records. All characters following the last nonblank character are considered wild cards. Spaces are valid in the log title, but the check is performed only up to the last nonblank character.

>   LOG= selects all log and dump records. The default value is that no log or dump records are written.

> TRACE

>       TRACE=trace-title

>   Trace records that have a title matching the specified trace title are written to DDPRINT.

>   The trace title must be specified exactly as it appears in the NETPRNT file; the value specified can be limited to the number of characters necessary to select the desired records. All characters following the last nonblank character are considered wild cards. Spaces are valid in the trace title, but the check is performed only up to the last nonblank character.

>   TRACE= selects all trace records. The default value is that no trace records are written.

>   Anything else is written to the output file as a comment along with the parameters specified to the beginning of the DDPRINT file.

>   An asterisk (*) in column 1 causes this parameter record to be ignored.

#### Examples

The following selects all records for a five minute period with a comment:

    ALL INFORMATION FROM 2:23 to 2:29
    STARTTIME=14230000
    ENDTIME=14290000
    LOG=
    TRACE=

The following selects log records for IDDDATA and IDDBLK using implied wild cards:

    LOG=IDD

The following selects log records for IDDDATA only:

    LOG=IDDDATA

The following selects dump records for M Y B L K, D R I V B L K, and L I N K B L K:

    LOG=M Y B L K
    LOG=D R I V B L K
    LOG=L I N K B L K

## NETPFIL2 Utility

The NETPFIL2 utility is used to search for a control block or storage area snapped by either the logging function or a dump. When the desired dump entries are found, they are printed.

Optionally, NETPFIL2 can also print all non log entries, including the trace and time stamp records. NETPFIL2 is therefore suitable as a second step in a job where NETPFIL1 is run first.

To summarize, NETPFIL2 can be used to

- find and print a control block or data area that contains a specified value at a specified offset,

- optionally print all non logging and dump records, and

- find multiple control blocks and multiple values.

The Entire Net-Work NETPRNT file contains tracing, logging, and dump output. The NETPRNT file should be used as input to the NETPFIL2 utility for the NETFILE file.

### Parameters

This section describes the parameters for the NETPFIL2 utility.

> NONLOG

>       NONLOG={Y | N }

>   The NONLOG parameter specifies whether all non log and dump records should be written to DDPRINT.

>   NONLOG=Yes | Writes all non log and dump records.
>   NONLOG=No | Ignores all non log and dump records. This is the default value.

> FIND

>       FIND=log-title (OFFSET=xxx {VALUE=characters | VALUE=X`hex values'})

>   Log and dump records that have a log title matching the specified log title are evaluated to determine whether the hexadecimal offset matches either the character or hexadecimal value specified. If it matches, the whole dumped area is written to DDPRINT.

>   The log title must be specified exactly as it appears in the NETPRNT file; the value specified can be limited to the number of characters necessary to select the desired records. All characters following the last non blank character are considered wild cards. Spaces are valid in the log title, but the evaluation is performed only up to the last non blank character. To select all log and dump records, use the LOG= parameter.

>   OFFSET=xxx must be specified as a valid hexadecimal number. This number specifies the first byte of the location in the dumped area to compare. The comparison is performed in such a way that the value must start at this location. Each additional character of the value is checked at the next logical position in the dump, even if the next logical position is on the next record.

>   VALUE=characters specifies the right hand portion of the value, which is in character format. The character form of the value is compared to the interpreted part of the dumped records.

>   VALUE=X`hex values' specifies the left hand portion of the value, following the address and offset. The hexadecimal form of the value is compared to the hexadecimal part of the dumped records.

>   The following example finds the driver block (D R I V B L K) for the TCP/IP (NETTCPI) driver.

>       FIND=D R I V B L K,OFFSET=10,VALUE=NETTCPI
>       FIND=D R I V B L K,OFFSET=10,VALUE=X`D5C5E3E3C3D7C9'

## Example JCL

### Running in z/OS Environments

The following example JCL can be used to run NETPFIL1 or NETPFIL2 in a z/OS environment.

    //YOURJOB  JOB (0),'NET-WORK',
    //         CLASS=A,MSGCLASS=X,MSGLEVEL=(1,1)
    //FILTER1  EXEC PGM=NETPFIL1                               <--- see Note 1 //STEPLIB  DD  DSN=NETWRK.vrs.LOAD,DISP=SHR                <--- see Note 2
    //         DD  DSN=WAL.vrs.LOAD,DISP=SHR                <--- see Note 3
    //NETFILE  DD  DSN=NETWRK.vrs.NETPRNT,DISP=SHR             <--- see Note 4
    //DDCARD   DD  *                                           <--- see Note 5
      THIS COMMENT WILL BE PRINTED AT THE BEGINNING OF THE OUTPUT
      DATE=20000316
      STARTTIME=12570000
      ENDTIME=12580000
      LOG=T R A C E
    * LOG=IDDDATA
      TRACE=
    * TRACE=SENDOUT
    //DDPRINT  DD  SYSOUT=*,DCB=(LRECL=121,BLKSIZE=1210,RECFM=FBA)
    /*

Notes:

1. 1. Specify the utility program you want to run.
2. 2. This is the same load library you use to run Entire Net-Work.
3. 3. This is the same Adabas or WAL load library you use to run Entire Net-Work.
4. 4. This is the file that was created by Entire Net-Work with DDNAME NETPRNT.
5. 5. This is the parameter file and may be any sequential file with LRECL=80.

### On this page

- NETPFIL1 Utility
- NETPFIL2 Utility
- Example JCL