SNAPBLK

Under the Full Checking technique, PCP can snap bad blocks to the PLUSSNAP data set if the block is in memory when PCP detects the error.

Use the SNAPBLK option to control the number of blocks PCP snaps and the format of the Bad Block Snap report.

The Bad Pointer report always provides the RBA of the error. Instead of using a hardcopy of the block in error, you might prefer to display and work with the block interactively with the Database Zap utility, as described in Using-the-Database-Zap-utility. The batch DL/I Block Dump utility can also provide block information after the completion of the pointer checking process; it is described in Using-the-DL-I-Block-Dump-utility.

Note

This option is not available under the Hash Checking technique.

Uses

You can set the SNAPBLK option at the following levels:

  • Global options module
  • Generated JCL
  • GLBL control statement

ISPF panel field

Snap Bad Block Options

  • Maximum Number of Blocks to Snap
  • DL/I Format

PCPSYSIN keyword

SNAPBLK(number,format)

Values

Specify one or both of the following positional values:

  • number

    Specify the maximum number of bad blocks to snap:

    • 0

      Snap no bad blocks.

    • 1-9998

      Snap 1-9998 bad blocks.

    • 9999

      Snap up to 32767 bad blocks detected.

  • format

    Specify the format of the bad block snap report:

    • DLI

      Report the bad blocks in DL/I format.

    • DUMP

      Report the bad blocks in OS/VS dump format.

Default

0,DUMP

Example

The following example tells PCP to snap 200 bad blocks in DL/I format:

GLBL SNAPBLK(200,DLI)

 

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