Failed to start Endevor ISPF interface - Internal Trouble Shooting Steps
Article ID: 266202
Updated On: 03-15-2024
Products
Issue/Introduction
Preparing Endevor v19 upgrade. Can use batch job to access Endevor v19 for listing elements in Endevor environment and running CSV utility. But failed to start Endevor v19 ISPF interface and got the following error messages.
BC1PINIT: $AFPCNO FAILED RC= 0004.
BC1PSM10: F000 ABEND CODE=INIT NUMBER=1005
..
ABEND U1005 OCCURRED IN PROGRAM BC1PSM10
Why do we get the above error when starting Endevor ISPF interface?
Environment
Release : 19.0
Resolution
BC1PROUT: E0003 BC1PROUT MSGP ERROR - NO RESPONSE FROM BC1PSERV
and later on
BC1PINIT: $AFPCNO FAILED RC=004
Both messages are issued, during initialization, Because Endevor has tried to start the so called 'endevor server' which is a subtask executing within the TSO session.
There is no response from the server and, moreover, the stuff that should have been done by the server is not there (which causes the internal $AFPCNO macro to fail), so apparently the server failed to start.
There are four possible reasons for this symptom:
1 - Program NDVRC1 is not defined as an authorized TSO program
This requirement has not changed with the release. This means that, if the old release has ever worked under TSO in this LPAR, the new release should work as well. Program NDVRC1 needs to be defined in the AUTHPGM, AUTHCMD and AUTHTSF tables of the IKJTSOxx member in SYS1.PARMLIB library, as documented in chapter "NDVRC1 Authorization"
2 - Libraries CSIQAUTH and CSIQAUTU are not present in STEPLIB DD or MVS linklist
These libraries should be allocated to STEPLIB DD of the TSO logon procedure. Instead of defining a separate logon procedure for the new release, it is possible to use a dynamic STEPLIB program to alter STEPLIB DD for the TSO session.
If using the ENDEVORS REXX, please see knowledge base article # 233013 for instructions.
IMPORTANT NOTE: Some dynamic STEPLIB products are known to cause issues with Endevor initialization. It depends on the technique used by the particular product to alter the STEPLIB for the TSO session. When using such a product, try setting up a TSO logon procedure with CSIQAUTU, CSIQAUTH in STEPLIB DD. This will narrow down whether the dynamic STEPLIB product may be involved in the issue.
3 - STEPLIB DD for the TSO session is not APF
This may happen if any non-APF library is concatenated to STEPLIB DD.
Note that ALL libraries in STEPLIB DD need to be APF. Note also that TSO itself does not require all the libraries in STEPLIB to be APF
4 - The server task was started but failed on its own before responding to the Endevor dialog
An abend in the server subtask would produce this symptom, but should also produce other symptoms, so it seems unlikely, although this possibility should not be discarded.
Try to run Endevor in a batch job. A batch run will also initialize the Endevor server and will clearly show any errors at this point.
Use this JCL to do that:
//STEP1 EXEC PGM=NDVRC1,PARM=C1BM3000
//STEPLIB DD DISP=SHR,DSN=your.CSIQAUTU.library
// DD DISP=SHR,DSN=your.CSIQAUTH.library
//CONLIB DD DISP=SHR,DSN=your.CSIQLOAD.library
//C1MSGS1 DD SYSOUT=*
//EN$TROPT DD SYSOUT=*
//BSTERR DD SYSOUT=*
//BSTIPT01 DD *
/*
This job should end with RC 12 and message C1BM4100: E031 NO ACTION REQUESTS WERE GENERATED.
If it does so, it proves that the endevor server subtask starts ok so it should also start correctly under TSO so the TSO startup is most probably failing due to reasons 1, 2 or 3
Feedback
