Hi Monica,
For a V18 upgrade, there are a couple things we need to check before you start the upgrade.
1) Are you using External Security (ESI) or Native security?
V18 requires ESI. If you are still using Native security, you must first convert to External security.
- Check your C1DEFLTS. If the keyword ESSI is set to Y, then you are already using ESI and no conversion necessary.
2) Are you using Global Type Sequencing?
Again V18 requires Global Type Sequencing and if you are not using it, you will first have to convert to GTS.
- Check your C1DEFLTS and see if you the PARMLIB and TYPESEQMBR keywords specified. If they are specified, GTS is enabled and you are all set.
If no conversions are needed, then we move on to assembling the Endevor tables with V18.
1) C1DEFLTS: There have been some keywords that have been obsoleted and need to be removed before assembling it with V18.
See the Release Notes article Customization Table Changes After Version 17.0
https://docops.ca.com/ca-endevor-SCM/18-0/en/release-notes/customization-table-changes-after-version-17-0
2) We will want to use your current BC1TNEQU and ESYMBOLS table as is. Just reassemble them using the V18 libraries.
3) We will want to use the V18 version of the ENDICNFG and ENCOPTBL tables and just update the new tables with the options you currently have turned on.
- The easiest way of getting a list of your current table options is to run a batch job with the Options trace - EN$TROPT, turned on. The option trace lists out the current contents of the Endevor tables and that can be used for updating the new tables.
Once all the Endevor tables have been reassembled for V18, we are ready to proceed with the Checklist:
Updated Endevor Upgrade and Conversion checklist - CA Knowledge
June