Purpose of Endevor *NOPROC* processor and processor group.
search cancel

Purpose of Endevor *NOPROC* processor and processor group.

book

Article ID: 381471

calendar_today

Updated On:

Products

Endevor

Issue/Introduction

In the definition of a processor group, Endevor allows the specification of special name *NOPROC* for the generate, move or the delete processor.

Likewise, Endevor allows the definition of a processor group named *NOPROC*

What is their purpose?

Resolution

Processor name *NOPROC*

*NOPROC* stands for 'no processor', and means that no processor is executed.

When an element is added or updated or generated and the generate processor is set to *NOPROC*, no processor is executed but the element record in the MCF is updated exactly as if a generate processor had been executed for it. For example, the generate timestamp is set. This information allows, for example, to subsequently reference the element in a component list and perform correct component validation.

Processor *NOPROC* can be used when needed. A clear example would in case of elements that don't need compilation nor any special processing, like for example copybooks.

Processor group *NOPROC*

If an element does not need any type of processor processing, It is possible to define a processor group having its three processors (generate, move and delete) set to *NOPROC*. Endevor will accept that.

However, an abbreviated way would be to define a processor group with name *NOPROC*.  When a processor group has this name, Endevor:

  • Forces the names of its 3 processors to *NOPROC* and does not allow to change them
  • Does not allow to define symbolic overrides for it
  • Allows to set the 'foreground execution' flag for each processor
  • Allows to define the processor output type to be used in element registration