Endevor ENSRVATD error: #ENDEVOROPTS and ABEND=U0400

Products

• Endevor

Issue/Introduction

Trying to get into Endevor via TSO / ISPF. The TSO session is cancelled and see the following in the syslog:

ENSRVATD RETRIEVE TOKEN NAME: #ENDEVOROPTS
IEA989I SLIP TRAP ID=xxxx MATCHED. JOBNAME=xxxxxxx , ASID=xxxx.
IEF450I xxxxxxx SYSPROC SYSPROC - ABEND=S000 U0400 REASON=00000000
C726812 SYSPROC : 00:00:13/ 00:00:00/ 1,891 - U0400
IEF170I 3 xxxxxxx xxxxxxx SYSPROC : 00:00:13/ 00:00:00/ 1,891 -
$HASP395 xxxxxxx ENDED - ABEND=U0400

There are some msgs that flash by rather quickly but unable to capture them.
Is there a batch IVP provided to be able to see the real error?

Environment

All supported releases 

Cause

The message "ENSRVATD RETRIEVE TOKEN NAME: #ENDEVOROPTS" means that:
     - Endevor initialization has failed for some reason so it has not created the name/token pair named #ENDEVOROPTS (which is created at the end of the           initialization)
     - Due to the failed initialization, Endevor has driven the termination logic
     - The termination logic is trying to clean things up so it's trying to delete the #ENDEVOROPTS token and fails because the token is not there.

Quite possibly some error messages are displayed to the screen showing the initialization error, but they are not seen because Endevor abends the TSO session right after the message.

Resolution

The typical reason for a #ENDEVOROPTS token error is one or more of the parameter fields defined in the C1DEFLTS like ACMROOT, ACMXREF or PARMLIB is incorrectly specified resulting in allocation errors: Defaults Table C1DEFLTS

If the problem cannot be easily found try running the following batch job: 

//PRTELMNT EXEC PGM=NDVRC1,DYNAMNBR=1500,PARM='C1BM3000',REGION=4096K
//STEPLIB  DD DISP=SHR,DSN=hlq.mlq.CSIQAUTU                               
//         DD DISP=SHR,DSN=hlq.mlq.CSIQAUTH                        
//CONLIB   DD DISP=SHR,DSN=hlq.mlq.CSIQLOAD                        
//C1PRINT  DD SYSOUT=*                                               
//C1MSGS1  DD SYSOUT=*                                               
//SYSOUT   DD SYSOUT=*
//EN$TROPT DD SYSOUT=*                                      
//*                                                                  
//BSTIPT01 DD *                                                      
  PRINT ELEMENT 'element'                                                  
   FROM ENV 'xxxx'                                                     
        SYSTEM 'xxxx'                                                    
        SUBSYSTEM 'xxxx'                                            
        STAGE *                                                      
        TYPE *                                                       
   TO FILE C1PRINT                                                   
   OPTIONS NOCC                                                      
.                                                                    
/*                                                                   

If still unable to determine the cause of the error from the batch job output, please open an Endevor support case on the Broadcom Support Online Portal and attach the complete output listing from the above batch job.

Additional Information

Also, the following can be tried in order to determine why the initialization fails in foreground:
 
1. Issue command TSO PROFILE WTPMSG MSGID before starting Endevor to see any messages displayed to the screen (they may or may not remain on the screen since the TSO session is dropped)
 
2. Issue command TSO ALLOC FI(BSTERR) SYSOUT(X) before starting Endevor. This way, even though the TSO session is finished, error messages will be kept in the JES2 output from the TSO session under ddname BSTERR
 
3. Take an Endevor module trace which will show the progress of the initialization and hopefully where it fails. The steps are:
- TSO ALLOC FI(EN$TRMOD) SYSOUT(X)
- Try to start endevor
- Find the module trace in the JES2 output from the TSO session under ddname EN$$$MOD