IBM RDz (7.6) with CA Endevor Eclipse Plug-In (The Latest Update). Helping customers achieve the consistent Application Lifecycle Management ‘workflow’ with measurable returns. Keith Allen CA EMEA Team Lead ALM Activities. Objective.
Helping customers achieve the consistent Application Lifecycle Management ‘workflow’ with measurable returns
Team Lead ALM Activities
Search Map View
Endevor Log View
The Element View
Schematic of Eclipse RDz à CA CMEW à CA Endevor
Package EGL Source and Store In Endevor
Within the RDz Project Explorer it is a simple Copy from the EGL Package and Paste over the Endevor Project to prepare to add EGL into CA Endevor on z/OS. Then Update the Endevor Project with the appropriate Change Control Identifier (CCID to relate all objects) from your existing Change number for the new application (or enhancement). Then use the Team (drop-down) to add to Endevor). The only prompt is for the Processor Group – EGL. Then the egl (with the long or short names) are propagated to CA Endevor. The Endevor Log will identify the results.
Ensure Relationship Between EGL Source and Generated Cobol
As part of the RDz Generate – COBOL source (and any ancillary files) are passed to a JCL processes executed on the z/OS. This process has an Endevor step that adds these objects into Endevor and runs a Process (Pre-compile, Compile and optional Bind) using the CCID specified as a comment. Now the EGL and COBOL source is related with the CCID. All elements (current and previous) can be returned to RDz via this unique CCID.
(Note: DB2 DDL can also be implemented as objects in CA Endevor from RDz).