Overview

The performance of the JCL verifications can be significantly improved by loading basic site related information into a shared object allocated in "above the bar" memory. The loaded information is later accessed by all subsequent invocations of Control-M JCL Verify until the shared object is removed. Loading the information is optional and the user can choose whether to use it to gain the performance boost.

Each invocation of Control-M JCL Verify scans the shared object for the information and if it exists will use it. If the shared object does not exist (either it was not loaded or already removed) then each invocation gathers its own copy of the information with transparency to the user (although a significant increase in the response time might be noticed).

The information loaded into the shared object includes:

• Programs found in the system's LINKLIST and LPA
• Mounted disk volumes
• Available device units
• JES procedures libraries
• JES input and output classes
• JES destinations
• Printers and punches
• NJE nodes
• FCB images
• Additional JES2 or JES3 information that is required to check JCL and JES statements
• Site standard rules
• Enforcement rules
• Reformatting rules

The loaded data is static and is not refreshed automatically. For example, if a new module is added to the LPA after the shared object was loaded, it will not be recognized by the subsequent verifications unless the data is refreshed. Therefore, although the nature of the data kept in the shared object is static, it is recommended that the data is refreshed on a periodic basis.