Our JES2 can not be taken down because of ACF2 or an ACF2 facility has DD statements that are allocated with JES SYSOUT files, what is causing this?
Our JES2 can not be taken down because of ACF2 or an ACF2 facility has DD statements that are allocated with JES:
$HASP263 WAITING FOR ACCESS TO JES2 CHECKPOINT. 139
LOCK HELD BY MEMBER SC10
*$HASP715 ADDRESS SPACES WAITING FOR RETURN JOBID 587
ACF2 or an ACF2 faility has DD statements that are allocated with JES SYSOUT files
causing the issue.
The problem with JES2 stopping can be related to ACF2 LDS being active with debug set.
If the ACF2 LDS component is active you cannot stop JES2 until LDS or ACF2 is stopped. The following DD statements are allocated with JES SYSOUT files for debugging LDS debugging.
The ACF2 LDS code will only allocate the files and allow for LDS debug by NODE if the
GSO LDS DEBUG option is active, so if the debug option active it will hold up the closing
Changes to the debug setting on the Options record will not become effective until the Options record is refreshed, LDS is stopped and restarted, or CA ACF2 is stopped and restarted. To turn off LDS DEBUG the
following can be done from TSO ACF.
CHANGE OPTIONS NODEBUG
Note: The Control LDS OPTIONS, LDAP, AND Control LDS XREFLDAP records are automatically refreshed during initialization of LDS.
Details on ACF2 LDS and the ACF2 LDS OPTIONS DEBUG|NODEBUG can be found in the CA ACF2 for z/OS Administration Guide in Chapter 25: LDAP Directory Services (LDS).