How is a CA Endevor Processor Group selected in a Move action?

Document ID : KB000015306
Last Modified Date : 14/02/2018
Show Technical Document Details
Introduction:

We have a System and it has a Type BIND. The Type BIND has 2 Processor Groups: BIND and BINDRUN.

We have 2 Environments. Both stage 1 and stage 2 of both Environments have the Type BIND and the 2 Processor Groups: BIND and BINDRUN, defined to them.

When we created a package and moved an element with Type BIND, the Processor Group BINDRUN was used.

 

Question:

Why did Endevor select BINDRUN instead of the BIND Processor Group? 

Environment:
z/OS
Answer:

When a Type is defined, a Default Processor Group is associated with the Type.
For example, in this case, say BIND is the default Processor Group for Type BIND. 

When a Type BIND element is added for the very first time, the programmer can use the default Processor Group defined in the Type Definition - BIND, or they can manually specify a different the Processor Group to use for that specific element, in this case BINDRUN. 

Once this Processor Group association is made, Endevor remembers which Processor Group was specified for that element and uses that Processor Group from then on when processing Add, Update, Move, Generate, Delete, or Transfer actions for that element.

The Processor Group can be changed by specifying a new Processor Group during an Add/Update or Transfer of the element.