Why is hlq.PROJDEFS.LOAD recalled whenever I edit a data set starting with hlq?

This is part of SCLM co-awareness processing. When you edit, we want to make sure that you are not editing members controlled by SCLM while you are in native ISPF. The hlq.PROJDEFS.LOAD data set stores the project definition for a project called hlq. The first thing that ISPF does to ensure that you are not using native ISPF to edit an SCLM-controlled data set is look for a project definition with a high level qualifier that matches the data set you are editing.

Even if you are not currently using SCLM for a project called hlq, if there is a data set called hlq.PROJDEFS.LOAD, there is a high probability that someone at some time created SCLM controls for some subset of the data sets with high level qualifier hlq.

There are a few options for avoiding the data set recall.

1) If this SCLM project is not in use, and is never likely to be used, you might want to delete the entire project. If this project was built through the SCLM Sample option (10.7), you can use SCLM 10.7 to delete the entire project including the project definition. Look to see if there is a data set called hlq.PROJDEFS.DATASETS. If this data set exists, it has a list of all the data sets that will be deleted when you use the Delete option of the SCLM Sample function. If the data set does not exist, you will not be able to use option 10.7 to delete the data set.

2) If you are not using this SCLM project, you can just delete hlq.PROJDEFS.LOAD.

3) If you just want to avoid the recall, you can update the ISPF configuration table to ignore SCLM coawareness. If you want to take this route, when you type ISPCCONF, and select 1 to Create/Modify Settings and Regenerate Keyword File. You should then select 1 Editor Settings. Scroll down until you see:

SCLM Warning Level
1 1. None
2. Warn
3. Error

Make sure that the level is set to 1 for None. After you build the load module or usermod, everyone who uses that configuration table should be able to edit these files without recalling any associated PROJDEFS.LOAD data set.

The downside of this strategy is that if anyone is using SCLM and this configuration table, they will be able to accidentally update their project data sets outside of SCLM, which could cause them problems later on.