Home
Fault Analyzer installation and administration
Providing compiler listings or Fault Analyzer side files
IDISBLKO
The IDISBLKO utility converts compiler listings generated with the BLKOFF option into a format simulating the required NOBLKOFF option.

Fault Analyzer installation and administration
- Migrating from an earlier version of Fault Analyzer
- Preparing to customize Fault Analyzer
- Customizing the operating environment for Fault Analyzer
- Using the Fault Analyzer IDIS subsystem
  Fault Analyzer uses a subsystem known as IDIS for services that can otherwise not be performed or which might cause incomplete analysis if not started.
- Modifying your ISPF environment
- Customize Fault Analyzer by using USERMODs
- Customize Fault Analyzer by using an IDIOPTLM configuration-options module
- Setting up history files
  Fault Analyzer requires at least one PDS or PDSE data set to be allocated as a fault history file.
- Setting and changing default options for the site
- Providing compiler listings or Fault Analyzer side files
  - COBOL Report Writer Precompiler
  - Required compiler options for IDILANGX
  - Naming compiler listings or side files
    Store compiler listings or side files in sequential data sets, or as members of PDS or PDSE data sets.
  - Naming CSECTs for Fault Analyzer
    To facilitate source code information, Fault Analyzer must be able to match CSECT names with the compiler listings or side files provided.
  - Locating compiler listings or side files
  - Compiler listings and side file access requirements
    Compiler listings and side files are read by Fault Analyzer module IDIDA.
  - Using the IDIXSFOR compiler listing/side file search and override exit
    If the IDIXSFOR exit is available, Fault Analyzer invokes it to allow programmatic specification of the location of compiler listing or side file data.
  - Compiler listings and side file attributes
  - Using the IDIRLOAD DDname for CSECT mapping
  - IDIDATST side file availability test utility
  - ISPF-packed compiler listings
  - Providing Java source information to Fault Analyzer
    There are two options for providing Java™ application source information to Fault Analyzer.
  - IDISBLKO
    The IDISBLKO utility converts compiler listings generated with the BLKOFF option into a format simulating the required NOBLKOFF option.
- Customizing the CICS environment
- Customizing the DB2 environment
- Customizing the IMS environment
- Customizing the Java environment
- Customizing the Fault Analyzer Japanese feature
- Verifying Fault Analyzer customization
- Managing history files (IDIUTIL utility)
  The IDIUTIL batch utility can be used to perform history file management functions, such as listing and deleting history file fault entries.
- Providing application-specific explanations and descriptions
- Maintaining Fault Analyzer
- Disabling Fault Analyzer
- Customizing Fault Analyzer by using user exits
- Installing non-ISPF interfaces to access Fault Analyzer history files

IDISBLKO

The IDISBLKO utility converts compiler listings generated with the BLKOFF option into a format simulating the required NOBLKOFF option.

The NOBLKOFF option is required for Enterprise PL/I as described in Required compiler options for IDILANGX. If your compiler listings were created using BLKOFF, you can use the sample REXX utility IDISBLKO provided to attempt to convert the listing to appear as if it were created with NOBLKOFF. This sample is provided as a member IDISBLKO in the IDI.SIDISAM1 data set.

This sample EXEC can be invoked either as a Fault Analyzer compiler listing user exit or it can be used against a listing file data set or a specific member within that data set. Complete usage instructions are provided in the IDISBLKO sample.

Note:

While this sample has been tested using different PL/I compiler versions and programs, it is not guaranteed to work in all scenarios. You must review the modified output to ensure accuracy.