Endevor maintenance applied, no access to receive order output or hold data

Products

• Endevor

Issue/Introduction

An external team applied the PTFs including a long list of prerequisite PTFs. The receive order or hold data was not shared. Unable to access Endevor. Tables replaced with sample versions without customization. What components needs compared, and updated with customization to restore and access Endevor?

Resolution

1. The first step to compare OLD (back up) to NEW (delivered post maintenance) components below. You would want review previous customization, validate it is still desired and apply it in the NEW version. This includes reviewing potential newly delivered fields and making a decision how or if to customize. 

If you cannot find your tables, run a batch job including //EN$TROPT DD SYSOUT=*, this is a trace which will give you the top level information for the C1DEFLTS table, the options you have enabled in the ENCOPTBL, the symbolics you have in the ESYMBOLS table, etc..

Capture Options & Features from the old release

Review tables as appropriate from the old release and make a copy of them in a PDS for safe keeping. Tables that typically need to review:

BC1TNEQU          (ESI - Security table)      
C1DEFLTS            (Site Defaults Table)
C1GTAPGM         (Authorized Program Table)
C1UEXITS             (User Exit Table)
ENCOPTBL           (Optional Features Table)
ENDICNFG           (Dialog Configuration Table)
ESMTPTBL           (EMAIL notification Table)
ESYMBOLS          (Site Symbols Table)

2. Review any exits, API programs, skeletons, panels, package ship modifications and/or customizations. (hlq.CSIQ*)

3. When ready to test, Assemble and link all the customized Endevor tables using the BC1JTABL or the SMP/E USERMOD process.