There are four EVT files starting at different times and containing data written sequentially by Batch Execution System. The vertical axis is the file time, where the t1 is the earliest time and the t11 is the latest time. The alphabetical file name processing sequence is given in the table below. Order File Data Segments [start time end time] written by the BES in parallel EVT files – Name t1 t2 t3 t4 t5 t6 t7 t8 t9 t9 t10 t11 – – – – – – – – – – t2 t3 t4 t5 t6 t7 t8 t10 1 File 1 X X X X 2 File 2 X X X 3 File 3 X X 4 File 4 X The event time ordered processing is illustrated in the table below Order File Data Segments [start time end time] written by the BES in parallel EVT files – Name t1 t2 t3 t4 t5 t6 t7 t8 t9 t9 t10 t11 – – – – – – – – – – t2 t3 t4 t5 t6 t7 t8 t10 1 File 1 X 2 File 3 X 3 File 1 X 4 File 2 X 5 File 1 X 6 File 3 X 7 File 2 X 8 File 4 X 9 File 1 X 10 File 2 X Dealing with Irrelevant Recipes Sometimes it is necessary to exclude particular recipes from being processed into PI Server. Such recipes can be excluded from processing by using the INI file command skiprecipes. The switch contains the list of all recipes or recipe masks the interface should not evaluate. Everything related to specified recipe is not processed into PI Batch Database, PI Module database and PI Points databases. The filtering supports the following recipe types: Procedure, UnitProcedure, Operation, and Phase. For each event to be processed, the interface will check for the match in the recipe fields depending on recipe type: Procedure Recipe : [Procedure] field of event Unitprocedure Recipe: [UnitProcedure] field of event Operation Recipe: [Operation] field of the event Phase Recipe: [Phase] field of the event Multiple recipes or their masks can be specified with a comma separator. If there is a space in the recipe name, use double quotes for the entire switch (not required if specified in INI file).
There are four EVT files starting at different times and containing data written sequentially by Batch Execution System. The vertical axis is the file time, where the t1 is the earliest time and the t11 is the latest time. The alphabetical file name processing sequence is given in the table below. Order File Name Data Segments [start time – end time] written by the BES in parallel EVT files t1 – t2 t2 – t3 t3 – t4 t4 – t5 t5 – t6 t6 – t7 t7 – t8 t8 – t9 t9 – t10 t10 – t11 1 File 1 X X X X 2 File 2 X X X 3 File 3 X X 4 File 4 X The event time ordered processing is illustrated in the table below Order File Name Data Segments [start time – end time] written by the BES in parallel EVT files t1 – t2 t2 – t3 t3 – t4 t4 – t5 t5 – t6 t6 – t7 t7 – t8 t8 – t9 t9 – t10 t10 – t11 1 File 1 X 2 File 3 X 3 File 1 X 4 File 2 X 5 File 1 X 6 File 3 X 7 File 2 X 8 File 4 X 9 File 1 X 10 File 2 X Dealing with Irrelevant Recipes Sometimes it is necessary to exclude particular recipes from being processed into PI Server. Such recipes can be excluded from processing by using the INI file command skiprecipes. The switch contains the list of all recipes or recipe masks the interface should not evaluate. Everything related to specified recipe is not processed into PI Batch Database, PI Module database and PI Points databases. The filtering supports the following recipe types: Procedure, UnitProcedure, Operation, and Phase. For each event to be processed, the interface will check for the match in the recipe fields depending on recipe type: Procedure Recipe : [Procedure] field of event Unitprocedure Recipe: [UnitProcedure] field of event Operation Recipe: [Operation] field of the event Phase Recipe: [Phase] field of the event Multiple recipes or their masks can be specified with a comma separator. If there is a space in the recipe name, use double quotes for the entire switch (not required if specified in INI file).
PI_EMDVB_3.0.0.57.docx