CompilingIn the directories for standard cycles: _N_CST_DIR, _N_CMA_DIR and user cycles:Subprograms (_SPF file extension) located in _N_CUS_DIR, and, if necessary, thesubprograms marked with PREPRO are compiled. The name of the compilation correspondsto the original cycle with extension _CYC.NoteProgram changes to precompiled programs do not take effect until the next POWER ON.Access rightsThe preprocessed program can only be executed, but not read or written. The compilationcannot be modified or archived. The original cycles _SPF files are not deleted.The compilation is not changed when the ASCII cycle is altered, i.e. changes do not take effectuntil after the next POWER ON.Memory requirementsThe memory requirement for compiled cycles is approximately factor 2 in addition to the ASCIIpart program.The memory requirements for variables defined in the part programs are defined by thefollowing machine data:MD28020 $MC_MM_NUM_LUD_NAMES_TOTAL (number of local user variables)MD28010 $MC_MM_NUM_REORG_LUD_MODULES (number of modules for local uservariables with REORG)MD28040 $MC_MM_LUD_VALUES_MEM (memory size for local user variables)MD18242 $MC_MM_MAX_SIZE_OF_LUD_VALUE (memory block size for LUD/GUDvalues)References:Function Manual, Extended Functions; Memory Configuration (S7)While preprocessing is in progress, the amount of memory required is the same as if thepreprocessed program were called on the first subprogram level.When programs are preprocessed after POWER ON, a name is counted for each branchdestination/label as if it were a variable. These names must be taken into account in thefollowing machine data:MD28020 $MC_MM_NUM_LUD_NAMES_TOTAL (number of local user variables)Example:Program code CommentPROC NAMES ; 1 nameDEF INT VARIABLE, ARRAY[2] ; 2 namesSTART: ; 1 name, only for preprocessingFOR VARIABLE = 1 TO 9 ; 1 name, only for preprocessingV2: Preprocessing22.2 Program handlingSpecial functions762 Function Manual, 01/2015, 6FC5397-2BP40-5BA2