Our JES2 can not be taken down because of ACF2 or an ACF2 faility has DD statements that are allocated with JES SYSOUT files, what is causing this?

Products

• ACF2
• ACF2 - z/OS
• ACF2 - MISC

Issue/Introduction

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?

 

Resolution

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 xxxx

*$HASP715 ADDRESS SPACES WAITING FOR RETURN JOBID 587 

ASID JOBNAME 

-------- -------- 

00nn ACF2 

 

 

ACF2 or an ACF2 facility 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. 

 

CEEDUMP 

SYSOUT 

SYSPRINT 

STDERR 

STDOUT 

 

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 

of JES2. 

 

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.

 

ACF

SET CONTROL(LDS)

CHANGE OPTIONS NODEBUG

F, ACF2,LDS(STOP)

F ACF2,LDS(START).

 

Note: The Control LDS OPTIONS, LDAP, AND Control LDS XREFLDAP records are automatically refreshed during initialization of LDS.