After assembling and linking a custom COBOL exit for Endevor, the output created by the exit is invalid with only 0's and no actual data.
search cancel

After assembling and linking a custom COBOL exit for Endevor, the output created by the exit is invalid with only 0's and no actual data.

book

Article ID: 31726

calendar_today

Updated On:

Products

Endevor Endevor Natural Integration Endevor - ECLIPSE Plugin Endevor - Enterprise Workbench

Issue/Introduction

When a COBOL program is compiled and linked for any exit point within Endevor, the following code is required on the link step:

//      DD *     
      INCLUDE SYSLIB(EPC1UEXT) *front-end program*
INCLUDE SYSLIB(exit program name) *real exit program*
ENTRY EPC1UEXT
NAME C1UEXTnn(R)
/*

 

When the ENTRY statement is missing, the user exit is not properly invoked and the output that is supposed to be created by the exit is coming out as 0's rather then actual data.

The include for EPC1UEXT is necessary for exit points 1 through 6, if writing an exit for exit point 7 (package exit) the include is not necessary.

Environment

Release:
Component: ENDBAS