BAD_NDX_VALUE [CV C>] When a $validate NDX fails to find the entered value in the index, the value is assigned to this variable so that further processing can be performed on it. The variable is cleared when a validation succeeds.
BAUD[CV C>] Set after a fax operation is complete, this value contains the baud codes listed in Appendix E. Actual baud rates are available as TXBAUD and RXBAUD.
BCF_LIMIT[CV >J] Specifies a maximum number of list columns.  It a job broadcast list has more than the specified number, the job launch will fail.  This prevents a job starting if a badly-formed list is accidentally specified with hundreds or thousands of columns.  The default value if not specified is 1000.  For Excel lists handled by the built-in Excel handler, specifying a negative value, for example -30, will just cause the columns numbered above 30 (AD in Excel) to be discarded, and the launch will not fail.  Negative values are also supported in this way when USE_EXCEL is in force, but do not prevent a noticeable delay in loading the list.  Positive values of BCF_LIMIT are also supported in an FFBC template file.
BCFx [CV JB> >CVG] These variables contain FFBC or Job Admin broadcast-generated field data are created for all broadcasts in the FS file. They are 'special' control variables because their value is retrieved using the special rules described here.
The x is the column number and the value of the created variable is the value from the corresponding column for the specific job item.  BCFx variables are special in that they are an exception to the rule that the longest possible variable name is always expanded. Variable expansions of the form @BCFx are processed specially, and only an exact match is expanded. Thus if you have defined BCF3 in an FS file, but have not defined BCF30, then writing @BCF30 in a cover sheet template file will not cause the value of BCF3 followed by a zero to be expanded. This feature allows you to include a large number of @BCFx expansions in a cover sheet template file, and have them correctly expand to blank if a smaller number of $var_def BCFx commands have been created in the FS file by either FFBC or another FS file generation program. In addition these variables may be written with a negative field number (for example @BCF-4) to cause the substituted field value, if not empty, to have a 'newline' appended at the end. A succession of such variables written on a text line will then be transformed into a list on expansion, with no empty lines inserted for empty fields.
The special syntax BCF%n (for example `BCF%3) will cause the value of the variable to be url-expanded, using for example %20 to represent a space character.  The URI Encoding syntax is now recommended for use in e-mail applications instead of this special syntax.
In template files for FFBC, these variables have a different purpose: they act as a list filter so that lines are excluded unless they match all the values defined for such variables in the template.
BCHx[CV J> >CV]  These variables contain Job Admin broadcast generated field data  and are created when the $job_options keyword WordMerge is used or  when both CreateBCXvars and OmitListHeader are used. The x is the column number and the value is the field name from the column header of the list containing the job item.  BCHx variables are used to create temporary single-data-row lists for WordMerge operations.
BCX_fieldname[CV J>] These variables contain Job Admin broadcast generated field data  and are created when the $job_options keywords CreateBCXvars and either WordMerge or OmitListHeader are used. The 'fieldname' is the field name from the column header of the list containing the job item, and the value of the created variable is the value from the corresponding column for the specific job item.
The special syntax BCX%fieldname will cause the value of the variable to be url-expanded, using for example %20 to represent a space character. The URI Encoding syntax is now recommended for use in e-mail applications instead of this special syntax.
BLADEWARE_RECEIVE_TIMEOUT_MINUTES[CV >C] The assignment of a value (in minutes) to this variable will change the default limit of 30 minutes for the receipt of a fax on a BladeWare port or board. Assignment of values less than 5 minutes will be silently ignored and will result in the default value being used. Outcome 7308 results when the time is exceeded.
BLANK_ROWS_LIMIT[CV >J] This variable specifies the number of job list rows with a blank destination column (phone/address) after which writing FS files will be suppressed on launch until a non-blank column entry is encountered.  It is intended to prevent carelessly-created XLS list files from generating many thousands of unusable job items.  The default value if this variable is not specified is 10.  See also the $job_options keyword CheckDestination.
BM_DISABLE_V34[CV >C] Assignment of a non-empty value to this variable will disable outbound V34 on Brooktrout TR1034.
BM_RECEIVE_BAUD_MAX [CV >C] An assignment to this variable in the USR file controlling the receive will limit the negotiated rate on Brooktrout TR1034.
BM_RECEIVE_DISABLE_V34[CV >C] Assignment of a non-empty value to this variable in the USR file controlling the receive will disable V34 on Brooktrout TR1034.
BPAGE [SRO] For a special "retry cover sheet", this variable indicates the page number in the original document which is the starting page for the retry operation. Otherwise the value is 1. See the example retry cover sheet for more information.
BREAK_DTMF[SRO] After an SC-Bus call transfer where $allow_interrupt has been specified, this variable will contain the DTMF code(s) that terminated the link. The value is empty if the LINK_TERM value is neither 4 nor 5.
BROADCAST_TYPE[CV J> >J] A variable which is created in a job properties file to define the type of broadcast: FB: fax broadcast; EB: e-mail broadcast; PB: outbound poll broadcast; VB: voice broadcast; FEB1: fax numbers and e-mail addresses in a single column; FEB2: fax numbers and e-mail addresses in two separate columns. The value of this variable is normally maintained automatically by reference to the presence or absence of the corresponding FS template commands. However for a FEB1 broadcast, this variable must be specified explicitly, because in this case only a $fax_phone will be present, and the case is otherwise indistinguishable from a normal fax broadcast.
BT_FONT/BT_FP [SRO] These variables return the font filename and a 1/0 'full page' indicator respectively. They are provided for CF8GCOVER to use in the pre-conversion of ASCII files to TIF.
BT_...[CV] Values can be assigned to these variables to specify non-standard parameters for ASCII files to be pre-converted to TIF for Brooktrout transmissions. This requires the 'pre-convert ASCII to TIF' run time option for COPIAFACTS.EXE to be set. These variables can be set using $var_def in FS, USR, UJP or CFG files, or by means of $set_var in an infobox preprocess operation. The following variables are provided:
BT_TMTop margin in tenths of an inch (default 3)
BT_BMBottom margin in tenths of an inch (default 3)
BT_LMLeft margin in tenths of an inch (default 5)
BT_RMRight margin in tenths of an inch (default 0)
BT_LSPACEInterline space in low-resolution scan lines (default 0)
BT_LENGTH Page length in low-resolution scan lines (default 1143)
BW_SIP_DNIS[CV C>] Records the 'DNIS' of an incoming BladeWare SIP call.
BYTE_COUNT [SRO] The approximate number of bytes transmitted in an outbound e-mail operation.