Custom Search

ENDEVOR OPERATION/ACTION

Endevor actions are generally performed in the following order:

RETRIEVE - also signs element out to retriever (refer to section V for more detail)

ADD/UPDATE - executes generate processor for program, creates obj and/or dbrm

and/or load module (refer to section V for more detail); simply adds

element if generate processor is *NOPROC*

*NOPROC* = PROCS, UTLS, BINDDECKS, COPYBOOKS, AND MFS

(NOPROC doesn’t mean no processing. It means that it’s added to

Stage U datasets without any action taking place on the element,

it’s an “as is” move…

GENERATE - executes generate processor for:

Type = Telon, then a compile will take place or

Type = Cobol, then a compile and possibly a link will take place

Type = Linkcard, then a link will take place

- Create either an obj, obj & load module, or just a load module

(refer to sections VI and VII for more detail)

******** - VERIFY STAGE U LIBRARIES

MOVE - executes move and delete processors

- copies from Stage U to Stage C libraries

- deletes from Stage U; signs element back in to Stage C

(refer to section V.7 for more detail)

******** - VERIFY STAGE C LIBRARIES

EXTERNAL TO ENDEVOR - copy jobs execute to copy dbrms and load modules to production libraries; bind job executes; deletes from Stage C