FOCUS Scanning Utility: SCANFOC

In this section:

Introduction to SCANFOC

FOCUS upgrade releases include new functionality for the core language and fixes to known issues, while providing compatibility with applications created and running in previous releases. Behavioral changes and major structural changes that are introduced as a result of this upgrade process and require attention, are documented in the Release Notes for each release. One example is the introduction of the new IBM C compiler to build the FOCUS product in Release 7.6 that created more efficient code, but which also required that FOCUS be a fully IBM LE-compliant product.

Chapter/Appendix	Contents
1	Upgrade Considerations Found by SCANFOC	Describes tests used to find upgrade considerations by FOCUS release.
2	Running the FOCUS Scanning Utility	Describes how to run SCANFOC.

Introduction to SCANFOC

The FOCUS Scanning Utility is designed to assist customers who are upgrading FOCUS applications by identifying potential instances of known behavioral changes in their Master Files, Access Files, procedures (FOCEXECs), JCL, CLISTs, and TRF files, that could possibly impact the running of their applications. The FOCUS Scanning Utility identifies the areas that need to be examined. It is up to the customer to review that code and make any adjustments, if necessary.

For information about gaining access to the files needed for running SCANFOC, contact Customer Support Services at customer_support@ibi.com.

Master File testing should be done using the release to which you are upgrading because the parsing engine in the upgraded product is used to validate the structure of the Master File.
FOCEXEC testing can be done with either the release that you are currently running or the release to which you will be upgrading. Instead of executing the FOCEXEC, the FOCUS Scanning Utility reads the FOCEXEC line by line as data, looking for individual strings or more complex combinations that may cause an issue. When a condition is found, the FOCEXEC should be run in the current release and in the upgrade release to verify the behavior change. At this point, you can make a determination about how best to adjust the existing code for the upgrade.