How do I use kernel logging with Batch Standalone?

Document type: Tech doc  
Associated product(s): Product name: Batch Version: 1.0 - 3.x Implementation: Standalone
Views: 75  |  Created: 2 years agoLast updated: 2 years ago
Countries: United Kingdom United Kingdom 

Summary

Standard Error logging, which gives details of how a QAS program is opening and reading data files, can be turned on in the configuration (*.ini) file of any version 2 or 3 QAS program.

Solution

In the case of Batch Standalone, the file is called qabatch.ini.

For details of how to turn on logging, please see:

How do I use kernel logging to establish why QAS is not running?

If logging is turned on for QAS Batch and the program is then run via Batch Control, attempting to press the “Configure” or “Automatic Clean” button will result in the error Could not create log file. The reason for this is that the log file has already been opened by Batch Control and cannot be re-opened by Batch Configuration or Batch Automatic.

As a result, error logging lines as specified in the above linked document will prevent the use of Control to it’s full extent and will also prevent proper logging. If logging is required, the individual components of Batch must be run separately. These components are:

  • Batch Configuration (qbcfgn.exe)
  • Batch Automatic (qbauton.exe)
  • Batch Interactive (qbintern.exe)
  • Batch Extract (qbextn.exe)
  • Batch Finisher (qbfinshn.exe) – this converts the *.00a interactive file into a *.qbo output file.

Was this document helpful?

What can we do to improve this information?