Previous Topic: REXX Interface for JCLNeatNext Topic: Troubleshooting


Maintenance

CA JCLCheck maintenance is provided from the following sources:

Business Value:

Application of regular maintenance is critical to minimize product problems.

As a best practice, keep CA JCLCheck current with all published solutions applied using CA MSM. Visit the CA JCLCheck product home page frequently for Product News, and check the Maintenance Grid under the Product Status section. If CA MSM is not used to apply maintenance, then the Maintenance Grid is useful. The Maintenance Grid contains links to the Aggregate Maintenance fix, fixes since the last Aggregrate Maintenance, the SMP/E Error HOLDDATA bucket, HIPERs, and product documentation changes.

When downloading solutions from support.ca.com, both component name "CA JCLCheck" and "CA JCLCheck Common Component" must be selected. When a PTF has a ++HOLD action, be sure to review it thoroughly before applying the PTF. As best practice, always run APPLY CHECK first and never force BYPASS (ID) on any PTFs. Also, PTFs can be ACCEPTed, but APARs (test fix) and USERMODs must never be ACCEPTed.

CA JCLCheck does not require an IPL after installing PTFs. If a PTF was for the SUBCHEK and/or JESCHEK modules, you may need to execute CAIRIM. If CA JCLCheck is in the LINKLIST, the LINKLIST must be refreshed.