ca-endevor Questions

We have an issue with the endevor package promotion process. When more than 2 packages are promoted at the same time, we get file contentions for the component libraries. Is there a installation setting that needs to change to overcome this problem ?

Additionally, when a package is cast, the current configuration does not validate (since validate is set to 'N' by everyone) the versioning is no checked. This is leading to versioning errors during the promotions. Is there a option to continue to use validate of 'N' during package casting and at the same time, prevent casting due to out of sequence versions. We are trying to reduce casting related errors during promotion, but at the same time have to continue with validate package set to 'N' while casting.

Would appreciate any thoughts on these issues.

Just upgraded to Endevor 14. Have Endevor interfaced with RACF with appropriate values in the Name Equates table.

This item relates to the Primary Options Menu and Quick Edit. Name Equates table is coded as below:

L1=standard value=ABCD
L2=Environment
L3=PMENU
L4=PMENU Items

So RACF rule that is called for PMENU selections is: ABCD.Environment.PMENU.PMENU-Items

With the upgrade to Endevor 14, when a user uses Quick Edit, the RACF rule searched for is:

ABCD.$.PMENU.PMENU-Items

Can't find any Endevor doc on the $ character being inserted instead of the Environment value as specified in the Name Equates table....

Anyone experience this? Any insight?

Thanks....

CMCrossroads is a TechWell community.

Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.