AcdntlPoet 2700019V2G Visits (2387)
Rational DOORS-Team Concert Integration: Lessons Learned-Lessons learned from Raytheon about Rational DOORS-Team Concert Integration with Steve Grossman and Jo Alamares
AcdntlPoet 2700019V2G Visits (1383)
Installing Rational License Key Server Administration and Reporting Tool v8.1.4- Installing Rational License Key Server Administration and Reporting Tool v8.1.4 by Ravinder Panwar, IBM Rational/Lotus Information Developer.
What you need to know about the CA Endevor "actions" used by the Rational Developer for System z CARMA Enhanced Edit feature
SteveSpirk 060001UESP Visits (1712)
Rational Developer for System z added the CARMA Enhanced Edit feature for CA Endevor SCM users in the 8.5.1 release. This CARMA Enhanced Edit feature is RDz's implementation of CA Endevor's Fast/Quick Edit. This feature allows RDz users to edit elements in the Endevor repository without having to retrieve/extract element out of repository into external file. When performing changes to a program, user will start by selecting the "version" of program/element within Endevor that they want to change. This usually is the "production" version of the program/element. When working with RDz CARMA, user would select (right-click on) element to be opened and select Edit/'Edit with' from the context menu.
When the CARMA Edit Element UI screen appears, user indicates to CARMA where they want element copied. This would typically be the "entry" environment/stage where they are allowed to edit element.
So what Endevor "actions" does CARMA use to copy "production" element into entry/editing environment/stage? That is a very important question because there are several different Endevor "actions" to do this, but not all RDz users are authorized to perform all Endevor "actions". The Endevor "actions" to handle this copy are generated from the RDz host Endevor RAM. These "actions" are run in foreground mode because of the unpredictable nature of running "action" as a batch job (CARMA has no idea when job will run/complete). Below I've listed how this "copy" of the element to "entry" environment/stage is handled in the available 8.5 releases and 9.0.
RDz 8.5.1 Endevor RAM: This was the initial implementation of the CARMA enhanced edit feature. In this release, the copy of the element to "entry" environment/stage is done using the Endevor GENERATE ELEMENT "action", with the "copyback" option. We have found that foreground GENERATEs are not allowed or are problematic in some customer environments.
RDz 22.214.171.124/9.0 Endevor RAM: In these releases, the copy to "entry" environment/stage was changed to use the Endevor TRANSFER ELEMENT "action". The element is opened in the RDz editor after the foreground Transfer has completed. In many cases, when the element is opened, some/all dependencies are not resolved until a GENERATE is done for the element being edited in this Environment/stage. We have also found that some customer sites do not allow RDz users to run Transfer "action".
RDz 126.96.36.199 Endevor RAM: In this release, the default way that CARMA handles this "copy" is still with the Endevor TRANSFER ELEMENT "action", however, we also allow you to configure RDz to use the RETRIEVE ELEMENT (from "prod") and ADD ELEMENT (to "test") "actions" to handle this "copy". To configure CARMA to use RETRIEVE-ADD "actions" for program/element "copy", you need to un-comment the 'ENT
To resolve dependencies when an element is opened using CARMA Enhanced Edit, a GENERATE ELEMENT request was added (188.8.131.52) following the TRAN
When you select this option, keep in mind there is good chance all dependencies will not be resolved by the RDz editor until a GENERATE is done on the element being opened, in the Endevor environment it is being opened from. This option should only be selected if you have trouble running foreground GENERATEs.
The current versions of RDz are 184.108.40.206 and 9.0 (Nov. 2013). The APAR mentioned in the previous paragraph will be delivered in the 8.5.1.next and 9.0.next RDz host PTFs. To verify what CA Endevor "actions" are being used in your environment, you can view the Endevor "actions" used in the MSG3FILE. The MSG3FILE is allocated in the user's CARMA server who performed the CARMA Enhanced Edit on element.
CandyLane 270000WFPX Visits (1808)
APAR PM96642 is fixed in Rational Developer for System z (RDz) v220.127.116.11 fixpack. This APAR picks up a fix from the Rational Common Licensing (RCL) product, and is not listed as one of the APARs fixed in that fixpack since it is an internal APAR.
AcdntlPoet 2700019V2G Visits (1998)
Rational Team Concert: Packaging and deploying with Enterprise Extensions- The Enterprise Extensions packaging and deployment features allow you to package build outputs and deploy the packages to runtime environments on other systems. This video includes demonstrations of ship list and work item packaging and rollback deployments.