Endevor Natural Interface EINE V19 Upgrade Checklist
Article ID: 261389
Updated On:
Products
Issue/Introduction
Any special considerations when upgrading EINE to V19?
Environment
Release : 19.0
Resolution
Yes, a couple of V18.0 PTFs (SO07588 and SO08873) updated and added fields to the EINE Adabas files.
If upgrading from EINE V18.1, skip to Step 4.
1) Run an ADAREP report for the EINE Message Queue file (LFILE 125) and the EINE System Profile file ( LFILE 126).
//ADAREP EXEC PGM=ADARUN,REGION=3M
//STEPLIB DD DSN=ADAVVV.LOAD,DISP=SHR
//DDASSOR1 DD DSN=ADA.DBXXX.ASSOR1,DISP=SHR
//DDDATAR1 DD DSN=ADA.DBXXX.DATAR1,DISP=SHR
//DDWORKR1 DD DSN=ADA.DBXXX.WORKR1,DISP=SHR
//SYSUDUMP DD SYSOUT=*
//DDDRUCK DD SYSOUT=*
//DDPRINT DD SYSOUT=*
//DDCARD DD *
ADARUN PROG=ADAREP,MODE=MULTI,DEVICE=8390,DBID=DDDD,SVC=YYY
//DDKARTE DD *
ADAREP FILE=EINE125,EINE126,NOSTD
/*
If unsure what the physical file numbers are for the EINE LFILE files, check the EINE Server for the following:
File Name DBID FNR Type
FUSER 90 290 ADABAS V82
LFILE 125 90 215 ADABAS V82
LFILE 126 90 216 ADABAS V82
In the above example, run the ADAREP for files 215 and 216
2) In the EINE MQ file check field BG has been updated to LA with length of zero :
2 I BG I 0 I A I LA,NU
2.2) If it has not been updated, run the following ADADBS job against the V19 test EINE files:
//ADADBS EXEC PGM=ADARUN,REGION=2008K
//STEPLIB DD DSN=ADAVVV.LOAD,DISP=SHR
//*
//DDASSOR1 DD DSN=ADA.DBXXX.ASSOR1,DISP=SHR
//DDDATAR1 DD DSN=ADA.DBXXX.DATAR1,DISP=SHR
//DDSORTR1 DD DSN=ADA.DBXXX.SORTR1,DISP=SHR
//DDWORKR1 DD DSN=ADA.DBXXX.WORKR1,DISP=SHR
//DDTEMPR1 DD DSN=ADA.DBXXX.TEMPR1,DISP=SHR
//*
//DDDRUCK DD SYSOUT=*
//DDPRINT DD SYSOUT=*
//*
//DDCARD DD *
ADARUN PROG=ADADBS
ADARUN DEVICE=8390,MODE=MULTI,DB=DDD,SVC=YYY
//*
//DDKARTE DD *
ADADBS CHANGE FILE=EINE125,FIELD='BG',OPTION=LA
ADADBS CHANGE FILE=EINE126,FIELD='AC',OPTION=LA
/*
** NOTE: When V19 is rolled out and deployed to Production, this ADADBS job will need to run against the Production EINE files.
3) In the EINE System Profile file, check and see if the new fields CR and CS have been added:
2 I CR I 228 I A I NU
2 I CS I 7 I P I NU
3.2) If they have not been added, run the following ADADBS job against the V19 test EINE System Profile file:
//ADADBS EXEC PGM=ADARUN,REGION=2048K
//STEPLIB DD DSN=ADAVVV.LOAD,DISP=SHR
//*
//DDASSOR1 DD DSN=ADA.DBXXX.ASSOR1,DISP=SHR
//DDDATAR1 DD DSN=ADA.DBXXX.DATAR1,DISP=SHR
//DDSORTR1 DD DSN=ADA.DBXXX.SORTR1,DISP=SHR
//DDWORKR1 DD DSN=ADA.DBXXX.WORKR1,DISP=SHR
//DDTEMPR1 DD DSN=ADA.DBXXX.TEMPR1,DISP=SHR
//*
//DDDRUCK DD SYSOUT=*
//DDPRINT DD SYSOUT=*
//*
//DDCARD DD *
ADARUN PROG=ADADBS
ADARUN DEVICE=8390,MODE=MULTI,DB=DDD,SVC=YYY
//*
//DDKARTE DD *
ADADBS NEWFIELD FILE=EINE126
ADADBS FNDEF='02,CR,228,A,NU'
ADADBS FNDEF='02,CS,7,P,NU'
/*
** NOTE: When V19 is rolled out and deployed to Production, this ADADBS job will need to run against the Production EINE file.
4) Follow and complete the instructions in the Endevor V19 TechDocs: Implementation and Customization / Implementing the Endevor Integration for the Natural Environment / How to Install the Software
Feedback
