Conference vaxuum::online_bookbuilding

144.0. "%TAG-E-INT_LOGIC" by NEWS::LMELEWSKI () Thu Jun 01 1989 12:01

Searched the online notes conf for the error message, but could not
find anything related.

VAX/VMS Version:       5.1
VAX DOCUMENT Version:  T1.2
Bookreader Version:    20-MARCH-89 Baselevel

Below is the list file and the source file follows. 

Lorraine



%DOC-I-IDENT, VAX Document T1.2     6-MAR-1989 14:28:26.99
[ T a g    T r a n s l a t i o n ]...
%TAG-I-DEFSLOADD, End of Loading of Tag Definitions
%TAG-I-LCL_MSG01, Using online bookbuilding tools, 20-MAR-89 baselevel
%TAG-E-INT_LOGIC, at tag <_INCR_SECTION_NUMBER> on line 23 in file
   FS_FRONT.SDML
   Internal error processing tag <NAME>
%TAG-E-INT_LOGIC, at tag <_INCR_SECTION_NUMBER> on line 23 in file
   FS_FRONT.SDML
   Internal error processing tag <NAME>
%TAG-E-INT_LOGIC, at tag <_INCR_SECTION_NUMBER> on line 37 in file
   FS_FRONT.SDML
   Internal error processing tag <NAME>
%TAG-E-INT_LOGIC, at tag <_INCR_SECTION_NUMBER> on line 37 in file
   FS_FRONT.SDML
   Internal error processing tag <NAME>
%TAG-E-INT_LOGIC, at tag <_INCR_SECTION_NUMBER> on line 109 in file
   FS_FRONT.SDML
   Internal error processing tag <NAME>
%TAG-E-INT_LOGIC, at tag <_INCR_SECTION_NUMBER> on line 109 in file
   FS_FRONT.SDML
   Internal error processing tag <NAME>
%TAG-E-INT_LOGIC, at tag <_INCR_SECTION_NUMBER> on line 4 in file
   DEFKEY.SDML
   Internal error processing tag <NAME>
%TAG-E-INT_LOGIC, at tag <_INCR_SECTION_NUMBER> on line 4 in file
   DEFKEY.SDML
   Internal error processing tag <NAME>
%TAG-I-ENDPASS_1, End of first pass over the input
%TAG-I-FILEWRTNG, File FS_FRONT.TEX written (0 length)
%TAG-I-FILEWRTNG, File DEFKEY.TEX written (0 length)
[ T e x t    F o r m a t t i n g ]...
%TEX-E-BADMACROFMT, Fatal macro format file error
%DOC-E-ERROR_FORMATTER, Errors found by the text formatter


DOCUMENT MICHELE_PRO ONLINE.REF BOOKREADER/CONTENTS/INDEX/KEEP=TEX/LIST
Date/Time:  1-JUN-1989 09:17:36.41
CPU time: 136.79 secs.



>>>>>>SOURCE FILE

<FRONT_MATTER>(functional_spec_front)
<TITLE_PAGE>
<TITLE>(Krypton\Functional Specification)
<ABSTRACT>(March 28, 1989)
<P>
This is the Software Functional Specification of the product code-named KRYPTON.
It is the definitive description in measurable terms of the goals, capabilities,
and external characteristics of KRYPTON. It is the commitment from the
Development Team of <emphasis>(WHAT IS TO BE BUILT) as agreed by the Product
Team. No changes are to be made to the product as described here, unless
approved and documented as an amendment to this Specification.
<P>
This is an unpublished work which contains confidential and proprietary
information. The information in this document is <emphasis>(For Internal Use
Only\bold).
<ENDABSTRACT>
<ENDTITLE_PAGE>

<CONTENTS_FILE>

<PREFACE>

<HEAD1>(Conventions\23_Conventions)
<P>
The following conventions are used in this document:
<LIST>(UNNUMBERED)
<LE>Text in uppercase should be typed exactly as shown.
<LE>Text in lowercase is an item supplied by you, such as a file name or a node
name.
<LE>Square brackets ([]) enclose an optional item. 
<LE>A comma followed by a horizontal ellipsis (,...) indicates that you can
supply more than one item separated by commas.
<LE>All letters and numbers inside a box indicate keyboard keys. For example,
<key>(CTRL/G) indicates that you hold down the control key and press the G key.
<ENDLIST>

<HEAD1>(Associated Documents\37_AssociatedDocuments) 
<P>
The following documents are either referenced in this manual or contain
additional information pertaining to Krypton:

<LIST>(UNNUMBERED)

<LE>The Product/Market Requirements document, to which this specification is
Software Engineering's response, Luis Fernandez and Harold Read, November 9,
1988.

<LE>The Serviceability Requirements document, to which this specification is
Software Engineering's response, CSSE, <emphasis>(tbd).

<LE>The Component Software Product Development Plan, which describes the
development project to design, build, test, evaluate, and deliver this product,
Son VoBa, <emphasis>(tbd).

<LE>The Software Documentation Plan for Krypton, which is Software
Documentation's plan to provide documentation for this product, Documentation,
<emphasis>(tbd).

<LE>The CI Exchange (CIX64) Product Specification, Allan Kent and Harold Read
<emphasis>(et al), 12 October 1988.

<LE>Proposed DEC Standard: Representation of Time for Information Exchange,
Version X1.0.5, Michael Fine, May 28, 1987.

<LE>VAXcluster Console System Version 1.2 Software Manual, order number
AA-GV45C-TE.

<LE>VAXcluster Console System Version 1.2 Software Reference Card, order number
AV-GV46C-TE.

<LE>VAXcluster Console System Version 1.2 Hardware Installation Guide, order
number EK-VXCNC-IN.

<LE>CIX64 Operations Guide, order number EK-230AA-OG.

<LE>VAX Text Processing Utility Manual, order number AA-LA14A-TE.

<LE>VMS Utility Routines Manual, order number AA-LA67A-TE.

<LE>VMS DCL Concepts Manual, order number AA-LA10A-TE.

<LE>VMS Command Definition Utility Manual, order number AA-LA60A-TE.

<LE>Introduction to VMS System Routines, order number AA-LA69A-TE.

<LE>VMS System Services Volume, order number AA-LA68A-TE.

<LE>VMS License Management Utility Manual, order number AA-LA33A-TE.

<LE>Guide to VMS System Security, order numbers AA-LA40A-TE.

<LE>VMS System Manager's Manual, order number AA-LA00A-TE.

<LE>Introduction to VMS System Management, order number AA-LA24A-TE.

<LE>Guide to Setting Up a VMS System, order number AA-LA25A-TE.

<LE>VAX 8800/8700/8550/8500 Console User's Guide, order number AA-FH28C-TE.

<LE>VAX 8820/8830/8840 Console User's Guide, order number AA-FJ95A-TE.

<LE>DECserver 200 Hardware Installation/Owner's Guide, order number
EK-D200C-IN-001.

<LE>Guide to Terminal Server Manager, order number AA-JF99B-TE.

<ENDLIST>

<HEAD1>(Revision History\109_RevisionHistory) 

<TABLE>
<TABLE_ATTRIBUTES>(MULTIPAGE)
<TABLE_SETUP>(2\10)
<TABLE_ROW>(<LIST>(STACKED)
            <LE> 11/29/88
            <LE> Son VoBa
            <ENDLIST>\
Creation.)
<TABLE_ROW>(<LIST>(STACKED)
            <LE> 12/14/88
            <LE> Son VoBa
            <ENDLIST>\
First draft of the Introduction chapter and the Configuration Editor command
line interface section.)
<TABLE_ROW>(<LIST>(STACKED)
            <LE> 01/22/89
            <LE> Son VoBa
            <ENDLIST>\
First draft of the CI Exchange Monitor Interface command line interface
section.)
<TABLE_ROW>(<LIST>(STACKED)
            <LE> 01/23/89
            <LE> Son VoBa
            <ENDLIST>\
Revised draft of the Writing Access Interface Applications section.)
<TABLE_ROW>(<LIST>(STACKED)
            <LE> 01/25/89
            <LE> Son VoBa
            <ENDLIST>\
First draft of the Installation Procedure chapter.)
<TABLE_ROW>(<LIST>(STACKED)
            <LE> 03/21/89
            <LE> Son VoBa
            <ENDLIST>\
Final draft of the Configuration Editor command line interface section.)
<ENDTABLE>

<ENDPREFACE>
<ENDFRONT_MATTER>
<CHAPTER>(The Console Monitor Interface\console_monitor)


<HEAD1>(The Console Monitor Interface Commands\465_TheConsoleMonitorInterface)
<P>
The Console Monitor Interface commands, described in the remainder of this

<COMMAND_SECTION>


<COMMAND>(DEFINE/KEY)
<X>(DEFINE/KEY command)
<X>(Console Monitor Interface commands <XS>DEFINE/KEY)
 
<OVERVIEW>
Binds a text string to a key for the current Console Monitor Interface session.
<ENDOVERVIEW>

<FORMAT>
<FCMD>(DEFINE /KEY) <FPARMS>([/qualifier...] key-name string)
<ENDFORMAT>

<PARAMDEFLIST>
<PARAMITEM>(key-name)
<PARAMDEF>
is the name of the key or control character to which you assign a string. Use
the key names specified in <reference>(control_key_names) to define control
keys.
<TABLE>(Control Key Names\control_key_names)
<TABLE_SETUP>(4\12\12\12)
<TABLE_ROW>(CTRL_A_KEY\CTRL_H_KEY\CTRL_O_KEY\CTRL_V_KEY)
<TABLE_ROW>(CTRL_B_KEY\CTRL_I_KEY\CTRL_P_KEY\CTRL_W_KEY)
<TABLE_ROW>(CTRL_C_KEY\CTRL_J_KEY\CTRL_Q_KEY\CTRL_X_KEY)
<TABLE_ROW>(CTRL_D_KEY\CTRL_K_KEY\CTRL_R_KEY\CTRL_Y_KEY)
<TABLE_ROW>(CTRL_E_KEY\CTRL_L_KEY\CTRL_S_KEY\CTRL_Z_KEY)
<TABLE_ROW>(CTRL_F_KEY\CTRL_M_KEY\CTRL_T_KEY\LF_KEY)
<TABLE_ROW>(CTRL_G_KEY\CTRL_N_KEY\CTRL_U_KEY\BS_KEY)
<ENDTABLE>
<P>
You cannot define the RETURN key and all printable alphanumeric characters.
Also, it is recommended that you do not re-define the control characters
specified in <reference>(reserved_control_key_names). If you do re-define one of
these control characters, you cannot access the function originally associated
with it during the current Console Monitor Interface session.
<TABLE>(Reserved Control Key Names\reserved_control_key_names)
<TABLE_SETUP>(4\12\12\12)
<TABLE_ROW>(CTRL_A_KEY\CTRL_E_KEY\CTRL_J_KEY\CTRL_U_KEY)
<TABLE_ROW>(CTRL_B_KEY\CTRL_F_KEY\CTRL_Q_KEY\CTRL_V_KEY)
<TABLE_ROW>(CTRL_D_KEY\CTRL_H_KEY\CTRL_S_KEY\CTRL_X_KEY)
<ENDTABLE>
<P>
Use the key names specified in <reference>(function_keypad_key_names) to define
editing, keypad, or function keys.
<TABLE>(Function and Keypad Key Names\function_keypad_key_names)
<TABLE_SETUP>(6\6\6\6\6\6)
<TABLE_ROW>(PF1\PF2\PF3\PF4\KP0\KP1)
<TABLE_ROW>(KP2\KP3\KP4\KP5\KP6\KP7)
<TABLE_ROW>(KP8\KP9\PERIOD\COMMA\MINUS\ENTER)
<TABLE_ROW>(UP\DOWN\LEFT\RIGHT\E1\E2)
<TABLE_ROW>(E3\E4\E5\E6\HELP\DO)
<TABLE_ROW>(F6\F7\F8\F9\F10\F11)
<TABLE_ROW>(F12\F13\F14\F15\F16\F17)
<TABLE_ROW>(F18\F19\F20\\\)
<ENDTABLE>
<P>
The keys in <reference>(function_keypad_key_names) are located on the editing
and application keypads as follows:

<TABLE>(Make This Table Formal\formal_sym)
<TABLE_SETUP>(2\17)
<TABLE_ROW>(<KEYPAD_SECTION>
            <KEYPAD>(Editing Keypad Keys\display)
            <KEYPAD_ROW>(E1\E2\E3\NONE)
            <KEYPAD_ROW>(E4\E5\E6\NONE)
            <KEYPAD_ROW>(NONE\UP\NONE\NONE)
            <KEYPAD_ROW>(LEFT\DOWN\RIGHT\NONE)
            <ENDKEYPAD>
            <ENDKEYPAD_SECTION>\

            <KEYPAD_SECTION>
            <KEYPAD>(Application Keypad Keys\display)
            <KEYPAD_ROW>(PF1\PF2\PF3\PF4)
            <KEYPAD_ROW>(KP7\KP8\KP9\MINUS)
            <KEYPAD_ROW>(KP4\KP5\KP6\COMMA)
            <KEYPAD_ROW>(KP1\KP2\KP3\ )
            <KEYPAD_ENDROW>(KP0\PERIOD\ENTER)
            <ENDKEYPAD>
            <ENDKEYPAD_SECTION>)
<ENDTABLE>


<PARAMITEM>(string)
<PARAMDEF>
is a sequence of keystrokes, typically a command and its parameters. Although
quotation marks are not required as string delimiters, you must include them if
you wish to retain extra spaces and lowercase letters.
<ENDPARAMDEFLIST>

<QUALDEFLIST>
<QUALITEM>(/KEY)
<QUALDEF>
is required with the DEFINE command to assign a command or command string to a
key.
<QUALITEM>(/SHIFT_KEY\/NOSHIFT_KEY (D))
<QUALDEF>
indicates if the key, when executed, is to be preceded by the <emphasis>(shift)
key that is defined by the SET SHIFT_KEY command. /SHIFT_KEY enables you to
assign two command strings to one key: one is used when you press the key by
itself, and the other is used when you press the key after the defined
<emphasis>(shift) key. You define the <emphasis>(shift) key with the SET
SHIFT_KEY command.
<P>
The default is /NOSHIFT_KEY.
<QUALITEM>(/TERMINATE\/NOTERMINATE (D))
<QUALDEF>
indicates if a carriage-return character is to be included as part of the string
you assign to a key. Thus, you can execute the command simply by pressing the
defined key. If you specify /NOTERMINATE, the carriage-return character is not
included as part of the string. Pressing the defined key causes the Console
Monitor Interface to insert the associated string at the current location on the
command line. To complete and execute the command, you must then press
<key>(Return).
<P>
The default is /NOTERMINATE.
<ENDQUALDEFLIST>

<DESCRIPTION>
You can save time by assigning a frequently used command or string to a key. You
can then issue the command by pressing one key, instead of typing the full
command name.
<P>
Quotation marks are not required as string delimiters. For example, either the
string <emphasis>(SELECT ALPHA\bold) or the string <emphasis>(<quote>(SELECT
ALPHA)\bold) prints as <emphasis>(SELECT ALPHA\bold) on your terminal. You must
use quotation marks if you want to retain spaces and lowercase letters. For
example, <emphasis>(select alpha\bold) prints as <emphasis>(SELECT ALPHA\bold)
and <emphasis>(<quote>(select alpha)\bold) prints as <emphasis>(select
alpha\bold). Extra spaces in an unquoted string are compressed into a single
space.
<P>
For a quotation mark to be the first printed character in the string, you must
enclose the string in a second set of quotation marks. For example, 
<emphasis>(<quote>()SELECT ALPHA<quote>()\bold) prints as 
<emphasis>(<quote>(SELECT ALPHA)\bold).
<P>
You can re-define keys that were defined previously. The Console Monitor
Interface informs you of the overridden definition with a message similar to
either one of the following:
<DISPLAY>
%VCS-I-MONS_USERKEYWAS, KP9 definition was "SHOW MONITOR"
%VCS-I-MONS_VCSKEYWAS, KP0 function was "Next screen"
<ENDDISPLAY>
<P>
The %VCS-I-MONS_USERKEYWAS message indicates that a user-defined key was
re-defined. It displays the previously defined command string that was bound to
the key. The %VCS-I-MONS_VCSKEYWAS message indicates that a VCS pre-defined key
was re-defined. It displays the original VCS function that was bound to the key.
<P>
The key definitions remain in effect for your current session only, unless you
preserve the key definitions with the SAVE <X>(SAVE command) command. Once you
SAVE the key definitions, you can reactivate them by specifying the VCS
MONITOR/SECTION command. 
<P>
Use the UNDEFINE/KEY command to remove a key definition. The undefined state of
a key also remain in effect for your current session only. That is, to
permanently have a key undefined, you also need to SAVE that state. Otherwise,
the next time you invoke the Console Monitor Interface, the old definition
remains same.
<P>
Use the SHOW KEYS command to display the current key definitions.
<ENDDESCRIPTION>

<EXAMPLE_SEQUENCE>
<EXI><S>(Command: )<U>(DEFINE/KEY KP1 CONNECT <key>(Return))
<S>(Command: )<U>(<key>(KP1))
<S>(Command: CONNECT)
<EXTEXT>
This example shows how to define key KP1 so that, when you press <key>(KP1), the
text CONNECT prints on the command line.
<ENDEXAMPLE_SEQUENCE>


<ENDCOMMAND_SECTION>

    You are running VAX DOCUMENT T1.2 with an old (incompatible) version of
    the online bookbuilding tools. To build online books using T1.2, you
    must install the saveset referenced in Note 64.4.
    
    Mary