Operand Equalities



next up previous contents
Next: Using the Preprocessor Up: Additional MPSL Language Previous: Parentheses

Operand Equalities

  Operand equalities are made up of an SLC database device address (primary, micro and unit, delimited with periods, followed by a component name, followed by `==' or '!=' , followed by a component state.

All of an operand equality must be on a singe line.

Spaces are permitted only within the quoted component name and component state, and around the `=='.

Component names and component states are not more than 8 characters long. If they are < 8, they will be blank filled to the right of the last character. If spaces precede characters in the literal they will be preserved by the compiler but it should be noted that few if any component names or values exist in the SLC database that have leading blanks.

Examples of good operand equalities.

		MPS.AB01.20."40IC" != "OK"  
		MPS.AB01.20."IC1   "=="OK      " 
		MPS.AB01.20."IC108   " =="OK"
Examples of bad operand equalities.
		MPS.AB01.20."40IC      " =="OK"  
		MPS.AB01.20." IC1" !="OK      " 
		MPS.AB01. 20."IC108   " =="OK"   
		MPS.AB01.20."IC108   " 
                   =="OK"



SLAC Controls Software
Fri Nov 4 11:47:17 PST 1994