Hello,
With the release date for Endevor V19 getting closer I want to make sure again you are aware of a few small changes we decided to make as a part of the new release, either because they require to be made on a release boundary or they would introduce incompatibility. These changes have been discussed on multiple occasions with our validation customers and no concerns were brought up. If you have any concerns now, please reach out to me so we can address those.
V19 Changes:
- BATCHID values 0 and 2 are no longer supported, defaulted to 1 (Find more details below*)
- Package "Superusers" can now perform any package action against a package with the possible exception of the review action. To be able to review (approve/deny) a package, a Superuser must be an approver of that package. Superusers can be defined in the Optional Feature table, ENCOPTBL.
- Base FMID CSIQJ00 now contains Endevor Web Services and the installation was adjusted so there are no prerequisites and no initial Web Services configuration required.
- Base FMID CSIQJ00 now contains MF Webhook server binary with a deploy JCL.
- Product was rebranded from "CA Endevor SCM" to "Endevor"
Note: As of V19 GA date, new features will be delivered only for V19, V18.1 will run in maintenance mode. (EOS for V18.0 is planned 18 months after the V19 GA date)
*BATCHID
What is BATCHID?
BATCHID is a parameter in the C1DEFLTS table, which determines what user ID Endevor considers to be the Endevor user during any Endevor processing. Up to release 18.1 including, BATCHID has three possible values:
· 0 - The job name is used as Endevor user ID. This is the default value.
· 1 - The value of USER parameter of the JOB statement is used as Endevor user ID, or, if not present, the user ID of the submitter is used.
· 2 - In majority of cases, this is equivalent to value 1. If your site does not use any security product (like RACF or Top Secret) then it is equivalent to value 0.
BATCHID parameter affects all Endevor processing, not only batch.
Why did we decide to remove support for BATCHID=0
- It could pose a potential security exposure
- The usage of job name as Endevor user ID is not 100% consistent. Submitter's user ID is used instead of the job name
- Endevor documentation discourages using BATCHID=0.
- BATCHID must not be set to 0 when using Endevor Web Services or CMEW.
- UIDLOC, a parameter closely related to BATCHID, is impossible to be set properly when a site uses user IDs of different lengths.
Note: After removing support for BATCHID=0, the meaning of BATCHID=2 would be identical to BATCHID=1, so we also removed support for BATCHID=2.