The SEND TEXT command

Except for the different type of formatting performed, the SEND TEXT command is very similar to SEND MAP. You specify the location of the text to be formatted in the FROM option and its length in the LENGTH option. Nearly all the options that apply to mapped output apply to text output as well, including:

Device controls
FORMFEED, ERASE, PRINT, FREEKB, ALARM, CURSOR.
Formatting options
NLEOM, L40, L64, L80, HONEOM.
Disposition options
TERMINAL, PAGING, SET.
Page formation option
ACCUM.

In general, these options have the same meaning on aSEND TEXT command as they do on aSEND MAP command. The SEND TEXT command itself requires standard BMS; options like ACCUM, PAGING and SET that require full BMS in a mapped environment also require full BMS in a text environment.

There are also options for SEND TEXT that correspond to functions associated with the map in a SEND MAP context. These are HEADER, TRAILER, JUSTIFY, JUSFIRST and JUSLAST. We explain how they work in Text pages.

Two SEND MAP options that do not carry over to SEND TEXT are ERASEAUP and NOFLUSH. ERASEAUP does not apply because text uses fields only minimally, and NOFLUSH does not apply because BMS does not raise the OVERFLOW condition on text output.

Text logical messages

The presence of either the ACCUM or PAGING option on a SEND TEXT command signals BMS that you are building a logical message, just as it does in a SEND MAP command. Text logical messages are subject to the same rules as mapped logical messages (see page Building logical messages). In particular, you can use both SEND TEXT and SEND CONTROL commands to build your message, but you cannot mix in SEND MAPs, except as noted there. You also end your message in the same way as a mapped message (see BMS logical messages).

[[ Contents Previous Page | Next Page Index ]]