cDSCHEDULE Automated Job Submission System Guide and Reference �ManualD

SCHEDULE
Automated Job Submission System
Guide and Reference Manual


 o T Y  
PreviousContentsIndex

4

3.3.2.1 General rules



The general rules of syntax are:

    >
  1. The "((" and "))" must appear on the same line of text.H
  2. White space inside is ignored. The template file is treated as a D continuous character sequence include newline characters with the 8 exception of control tokens which must be on one line.7
  3. Variable and control names are case insensitive.G
  4. Ending a control sequence with "*" suppresses the next newline. & (i.e. ((IF_ZERO*)), ((DO abc*)) ...)J
  5. Ending a control sequence with "-" prevents the echoing out of the = sequence if it is unknown. (i.e. ((ABC-)), ((DO ABC-)) ...)E
  6. Ending a control sequence with "+" causes any interior single J quote mark " to be replaced by a pair of quote marks "". (i.e. ((ABC+))  )H
  7. Anywhere a variable can be placed a string constant "xxx" can be  used.J
  8. Ending a control sequence with "%" Ex: ((xxxx%)) indicates replace $ all single "\" with a double "\\".
5

3.3.3 Single Variables



There are two type of variables:

CGlobal - those that are in the EnterpriseSCHEDULE database.

FLocal - those that are only present for the duration of the pre-processing.

rThere is also a set of job specific local variables (see Section 3.3.1.1. @Additional local variables can be created using the SET command described below.

 

" 
    (( name_of_variable ))  



GIn a command file this is any variable known to the EnterpriseSCHEDULE Hsystem. If it is the same directory as the job, the path portion of the name can be left off.

For example:

 

" 
  (( TEST_VARIABLE_1 ))  (( /SYS/FRIDAY ))  (( [MASTER]CONTROL_DATE ))  (( \SP\START_FLAGS ))  (( SC_NAME ))  (( $P1 ))  

4

3.3.4 ARRAY variables



HWhen creating array variables, the variable name is computed using a DO Floop counter and then treated in the same manner as a SINGLE variable.

Example:

 

" 
 (    (( name_of_variable_in_heap_!4ZL ))  



E"_!4ZL" (or any numeric fao formating code can be used) is evaluated Eusing the name string as a formatting string to the fao service with the do counter as the variable.

:

3.3.5 Job Command Examples

EThe following examples illustate the syntax for commands within jobs.
    D
  1. Comments - A block of COMMENTS can be placed B anywhere. Any text within a comment is not writen to the output.

     

    " 
     '    ((COMMENT)) comment ((ENDCOMMENT))  
        
    
    Example:

     

    " 
         ((COMMENT)) 8    This is the headcommand and will not be written out     ((ENDCOMMENT))  
        
    +
    An alternate form for a comment is:

     

    " 
         ((! comment ))  
        
    
    Example:

     

    " 
     7    ((!This is a command and will not be written out))  
        
    B

  2. IF Statement - An IF section can delineate - conditional statements. The variations are:

     

    " 
     5    ((IF_BLANK variable)) ... ((ELSE)) ... ((ENDIF)) 9    ((IF_NOT_BLANK variable)) ... ((ELSE)) ... ((ENDIF)) 4    ((IF_ZERO variable)) ... ((ELSE)) ... ((ENDIF)) 8    ((IF_NOT_ZERO variable)) ... ((ELSE)) ... ((ENDIF)) >    ((IF_EQUAL variable variable)) ... ((ELSE)) ... ((ENDIF)) B    ((IF_NOT_EQUAL variable variable)) ... ((ELSE)) ... ((ENDIF))  
        
    K
    In this example, the words "All finished" be written to the output 0 file only if the count is zero.
    Example:

    

     o V T Y  
    PreviousNextContentsIndex