1 / 12

AllFusion Endevor Change Manager R4.0 Upgrade Notes

AllFusion Endevor Change Manager R4.0 Upgrade Notes. 1. "NEXT TYPE" name can no longer differ from "this" TYPE (No type name changes across the map are allowed. )

sinjin
Download Presentation

AllFusion Endevor Change Manager R4.0 Upgrade Notes

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. AllFusion Endevor Change Manager R4.0 Upgrade Notes • 1. "NEXT TYPE" name can no longer differ from "this" TYPE (No type name changes across the map are allowed. ) • A new utility, BCIPXCAT, will be provided to create the Endevor R4.0 catalog from existing MCF control files. This is not a file conversion utility -it is a build utility.

  2. AllFusion Endevor Change Manager R4.0 Upgrade Notes • If long element names are used the LRECL of the delta library must be at least 259. • The Endevor CSP interface will no longer be available, beginning with Endevor R4.0. (CSP-related parameters have been removed from CIDEFLTS.)

  3. AllFusion Endevor Change Manager R4.0 Upgrade Notes • The Endevor Interfaces, (CA-Netman, Tivoli Information Manager (InfoMan, CA-ROSCOE, Endevor DB Bridge) will be released with the first service pack of Endevor R4.0 • The Endevor for DB2 interface for R4.0 will be released after Endevor R4.0.

  4. AllFusion Endevor Change Manager R4.0 Upgrade Notes • A special DDNAME, EN$TROPT, will cause Endevor R4.0 to format and print all option table (CIDEFLTS, ENCOTPBL, ENDICFNG, etc.) settings at Endevor start-up.

  5. AllFusion Endevor Change Manager R4.0 Upgrade Notes • RLS or CA-Lserv implementation is highly recommend for the Endevor R4.0 Catalog data set, MCFs and the PCF (package control file).

  6. AllFusion Endevor Change Manager R4.0 Upgrade Notes • Due to the key structure of the catalog, it is highly recommended that element searches are done with some sort of element and type specification. (The catalog key is element name -type name.)

  7. AllFusion Endevor Change Manager R4.0 Upgrade Notes • ACMQ is now required if ACM active. If ACMQ has not been implemented under R3.9 (or implemented at all), the ACMQ load procedure must be executed to populate the ACMQ repository. The CIDEFLTS ACMIDXUP parameter hasbeen removed. The Endevor altemate id can now be used to secure the ACMQ VSAM linear data sets.

  8. AllFusion Endevor Change Manager R4.0 Upgrade Notes • Endevor R4.0 is downward compatible with Endevor R3.9 if no Endevor R4.0 only features were implemented (long element names, etc. )

  9. AllFusion Endevor Change Manager R4.0 Upgrade Notes • The Endevor reports will no longer be available with SAS. The Endevor MCF, PCF, etc. file layouts will no longer be distributed. All Endevor information is available via the API. (In addition to the API, a utility is in the works that will produce a CSV-delimited file for additional reporting.)

  10. AllFusion Endevor Change Manager R4.0 Upgrade Notes • Endevor control tables (CIDEFLTS, ENDICNFG, ENCOPTBL, etc.) are now validated at Endevor start-up time to ensure that all tables are R4.0-compatible.

  11. AllFusion Endevor Change Manager R4.0 Upgrade Notes • The Endevor R4.0 Element Registration feature can be activated in Warn, Caution or Error mode (and switched from one mode to the other at any time). If the processor group output type registration option is activated, no conflicts will occur because the default value for the processor group output type (TYPE NAME+PROC GROUP NAME) is unique.

  12. AllFusion Endevor Change Manager R4.0 Upgrade Notes • All Environments defined in a Environment Map MUST be referenced by one Element Catalog and ONLY that Element Catalog • Component validation (occurs at Package CAST) 1ogic has been greatly improved - especially in the area of diagnostic messages.

More Related