TECO AIDS TECO UTILITY FILES A) "MUN" oriented files: 1) LIST.TEC lists a file on the LP with page heading and form feeds on page breaks. FORMAT: MCR>MUN LIST,filespec where "filespec" is the file to be listed. The specification can contain wildcards in any field but device. LIST tells the user how many pages are output for each file. EXAMPLE: MCR>MUN LIST,*.CMD;* 2) UPCASE.TEC converts a file from lower to uppercase. FORMAT: MCR>MUN UPCASE,filespec where "filespec" is the file to be converted. UPCASE does NOT use TECO's ^X-type conversion. EXAMPLE: MUN UPCASE,[20,20]TEXT 3) READ.TEC reads a file and counts the records. FORMAT: MCR>MUN READ,filespec where "filespec" is the file to be counted. EXAMPLE: MCR>MUN READ,TEST.DAT 4) RAD.TEC converts an ASCII character string into RAD50 (octal) words. FORMAT: MCR>MUN RAD,asciistring where "asciistring" is the string to be converted. Note that the string can be of any length. EXAMPLE: MCR>MUN RAD,ABC A DEF$.$ 5) DAR.TEC converts octal words from RAD50 to ASCII characters. FORMAT: MCR>MUN DAR,num1[,num2,...,numn] where "num1,num2,etc." are the octal word which are to be converted into ASCII. EXAMPLE: MCR>MUN DAR,3223,50,14716,126473 6) CALC.TEC performs the arithmetic operation provided using TECO's arithmetic rules (^O means octal base, no priority, TECO bit operators) and gives the result in decimal and octal. FORMAT: MCR>MUN CALC,operationstring where "operationstring" is the expression to be evaluated. EXAMPLES: MCR>MUN CALC,^O100 MCR>MUN CALC,(50-100)/(40+25) MCR>MUN CALC,^O^F MCR>MUN CALC,^O 100#340^_ 7) LISTTEC.TEC performs as LIST.TEC except that all non- significant control charactes (e.g. CR,LF,VT,etc.) are converted into ^ ala TECO's normal type out. LISTTEC should only be used for TECOish files due to the slow conversion process. B) TEC oreiented files: 1) STATUS.TEC reports on the current status (interpret flags, give buffer status and Q register usage). FORMAT: *ei[1,1]status$$ 2) QSINUSE.TEC reports on the use of Q register text areas. FORMAT: *ei[1,1]qsinuse$$ NOTES The MUN oriented command files all exit upon completion and should not be performed from within TEC or MAK. Also, the MUN operations must be done under the UIC in which the .TEC file is stored. This is because MUN interprets the comma in a UIC string as the break between the file and the input string. The TEC oriented command files don't exit and should only be used from within a TEC or MAK.