Sunday, January 22, 2017

Endevor : Processor and Processor group

Endevor uses OS JCL streams called processors to create executable forms of source code, including source modules, object modules, load modules, and listings. There are three kinds of processors:

  • Generate processors execute when an element is added or updated in Endevor, or generated in a stage. Optionally, generate processors execute when an element is restored or transferred to Endevor from an archive data set. Typically, the generate processor creates an executable form of the element, together with any associated outputs (such as listings).
  • Delete processors execute when an element is deleted, transferred, moved, or archived. Generally, the delete processor deletes any output that was created by the corresponding generate processor.
  • Move processors move elements from one stage in the life cycle to another. Move processors generally copy all the output previously created for the element, or re-create those outputs in the target stage.
A processor group identifies the specific generate, delete, and move processor Endevor should use to process a particular element type. It also specifies the symbolic overrides that Endevor should use in the processors' JCL. So, for example, you can write a set of processors for your assembly language programs, combine those processors into one processor group, and then associate that group with element type ASM. 
If you move or transfer an element from one processor group to another, Endevor executes the delete processors associated with the source location, not the target location. Processor groups allow you to handle common variations among the members of a particular type quickly and easily. If you create a single set of processors using symbolic parameters, you can create different processor groups using the same set of processors but containing different default symbolic overrides. For example, your site has applications coded in COBOL and COBOL/370. You could define a single type, COBOL, and have two processor groups, one for COBOL II and another processor group for COBOL/370.

No comments:

Post a Comment

Note: Only a member of this blog may post a comment.