Agilent Technologies 8960 10 Series Reference Manual page 121

Dealing With Semicolon Separated Response Data Lists
In the Rocky Mountain Basic programming environment the above ENTER statement will fail with an
'Insufficient data for ENTER' error. Some programming languages, Rocky Mountain Basic for example, cannot
use the semicolon character as a data item terminator for string variables. In this example Rocky Mountain
Basic will attempt to enter data into Imsi$ until it sees an LF (line feed) data item terminator. The test set
does not send the LF until all the data has been sent. Consequently when Rocky Mountain Basic sees the LF it
terminates entry of data into Imsi$ and starts to look for data to enter into Pcl. Since the test set is no longer
sending any data the error message 'Insufficient data for ENTER' is generated.
One possible workaround is to enter all the data into a single string variable, replace all semicolons with line
feeds and then enter the data from the string into the individual data items. For example:
DIM Response$[500]
!
!
OUTPUT 714;"CALL:MS:REP:IMSI?;PCL?;REV?;SBAN?;ONUM?;MCC?;MNC?;LAC?"
ENTER 714;Response$
Semicolon=POS(Response$,";")
WHILE Semicolon
Response$[Semicolon,Semicolon]=CHR$(10)
Semicolon=POS(Response$,";")
END WHILE
ENTER Response$;Imsi$,Pcl,Rev$,Sban$,Onum$,Mcc,Mnc,La
Semicolon Separated Response Data Lists Containing Only Numeric Data Types
Semicolon separated response data lists containing only numeric data types do not present the types of
problem associated with semicolon separated response data lists containing mixed data types. The number
building routines in most languages will use any non-numeric character (that is, anything other than +/-
0123456789 E .) as the data item terminator. Consequently when the number building routines encounter the
semicolon the data item is terminated. The following example illustrates this:
OUTPUT 714;"FETCH:TXP:INT?;POW:MIN?;MAX?"
ENTER 714;Integrity,Min_power,Max_power
121
S:\Hp8960\E1960A GSM Mobile Test Application\A.04 Release\Reference_Manual\Chapters\prog_gen_compound.fm