DE3319211A1 - ONLINE DOCUMENTATION PROCEDURE AND SETUP - Google Patents

Description

Online documentation process and facility

Computer systems often include an online documentation means by which different types of investment information _n users in response to Dokumentatiosn- or "help" commands are made available. For example, a user can issue a documentation command HELP TERM = BILLING_IDENTIFIER (help on the expression "calculation identification"),

_{1 (} - whereupon the system gives the user at his or her connection documentation or information regarding the meaning of the expression "calculation identifier" used in the system. The user can, for example, also issue a documentation command HELP COMMAND = CALL (help in Connection with the command "Call"), whereupon the system provides information on how the command "Call" is to be used. Another possibility is a documentation command HELP ERROR = E_NOT_FOUND (help in connection with the command "E-NQT_FOUND"), whereupon

2g information or documentation regarding the system of the error, the abbreviation of which is E_NOT_FOUND is.

In the past, documentation of this type was completely defined within the system, i.e. by the designers of the system. In connection with the present system, however, the users a computer system that offers online documentation, offered the possibility for a special documentation command user-specific documentation too Define by making changes to the system documentation for this command, i.e. the documentation which in the other case would be provided by the system. (The term "user" used here

refers not only to an individual but also to a community of people, for example those people who are under a particular invoice number Have access to the system.,)

It is of course necessary that the system documentation remains untouched, so that it is available to other users either in its original form or in the can be made available in a modified form by the other users. In preferred embodiments this is achieved by using one or more plant documentation storage sections (Files) and also one or more user documentation storage sections for each User provided itferden the user-specific Take advantage of documentation options will ο contain the system memory sections in detail the system documentation. The user memory sections contain documentation provided by the user in connection with commands on how these texts are to be used in order to change the system documentation. In other words, the user memory sections contain information about how the user-specific Differentiate between documentation and system documentation for one or more documentation commands. When a certain Documentation command is issued by the user, the system accesses the system documentation memory sections and, if necessary, to the user documentation memory sections and provides the respective user-specific documentation.

The invention is described below with reference to the drawings. Show it:

1 shows the block diagram of a processing / communication system, in which the invention is used;

2 shows the block diagram of a multiple computer node in the system according to Figure 1;

FIG. 3 shows a program package which is executed in the nodes according to FIG. 2 and a

Online documentation facility

contains the basic idea of the invention; 4 parts of system and user database storage areas within the node of Figure 2;

Fig. 5 shows the format of the plant documentation records in the plant storage area ;

Figure 6 shows the format of the user documentation records in user memory

area;

Figures 7 through 9 are flow charts of the on-line documentation facility ;

Fig. 10 Plant, User and Exit Record Lists, through the online

Documentation facility can be generated during command execution. The following table I shows the system documentation that the user of the computer system according to Fig. 1 in response to the documentation command HELP COMMAND = CALL (help in connection with the "Call" command) is given.

Table I.
** CALL ** (calling)

* USAGE * (usage).

PACKAGE - SPHP (SPHP program package)

call (nsa =) / nsa /

(mode = / mode /) (operating mode = / operating mode /)

* EXPLANATION * (explanation)

The command CALL causes the program so named to be executed.

* ARGUMENTS * (arguments)

NSA:

The program installed on the given NSA will be executed.

MODE: (operating mode :)

The operating mode of the data connection (terminal) is changed to the specified value before the program is performed. The operating mode can be one of the operating modes common, transparent or class-specific. 5

According to the present invention, the users of the system are given the option of user-specific Documentation for a documentation command by specifying changes to be made to the system documentation , i.e. for the documentation, which in the other case by the system responding to the respective documentation command would be provided. As an example, Table II shows a modification of the system documentation according to Table I after modification by a user for the purpose of providing user-specific documentation for the command CALL.

Table II

** CALL ** (calling)
* USAGE * (use)

Calling or calling up <network standard address> (operating mode = <usual or class-specific>) ■ * EXPLANATION * (explanation) Programs are identified by a 10-digit network standard address (NSA, from Network Standard Address). The command CALL causes the designated program to be executed. * ■ ARGUMENTS * (arguments)
NSA:

The one at the given standard network address (NSA) installed program will be executed. MODE: (operating mode :)

The operating mode of the data connection is changed to the specified value before the program runs. the Operating mode can be common, transparent or class-specific. The "transparent" operating mode becomes not currently operating and should not be used.

EXAMPLE * (example)

Call up 0451271234, operating mode = class-specific. This program calls the standard subscriber control program (Standard Customer Control Program) and brings the respective data connection into the "Class-specific" operating mode.

Note that the user section has been replaced with a sentence at the beginning of the "Explanation" section added that "Arguments" has been added at the end of the section and that in addition an "Example" section appears.

Fig. 1 shows an installation in which the present invention is used. The plant represents an integrated Data processing / messaging service for a large number of participants ready and contains a number of nodes 10, which are arranged in the area or on the property of the supplier for the service are. The core of each node consists of one or more digital computers according to the following Explanation. A large number of data connections 10a and dependent computers or guest computers are connected to the nodes

10 connected via suitable data lines. Most of the data connections and guest computers belong to the participants and is located in their area. However, some data connections and guest computers belong to the landlord and are used, for example, to organize the system. The nodes 10 communicate with one another via a packet switching network 15 in connection. The nodes are connected to the network via appropriate connecting lines

11 connected the data at 56 kB / s using a Protocol that corresponds to the CCITT standard X.25. Different nodes can be assigned to certain functions, for example charging, for service provision, maintenance, etc.

Message delivery provision gives the subscriber a number of options. That includes the time-divided execution of participant and

Landlord application programs operating within the node are stored, the storage of subscriber data in databases in the nodes, the delivery of by the Participants program-wise callable building blocks, the an editing, a command interpretation, a form possibility and the like, and also the possibility of distributed processing in different Processes executed by nodes can connect to processes on a time-critical basis, which are executed in other nodes and a store and relay message operation.

FIG. 2 shows the block diagram of an individual node TO .. which contains the node shown as an example two node processors 20 and a database processor

26. Each of these processors is exemplified by a VAX 11/780 computer from Digital Equipment Corporation (DEC), the runs with a VMS operating system supplied by DEC. The node also includes a backup processor 28 of the type VAX 11/780, which can replace the database processor or one of the node processors. Other knots 10 (Fig. 1) may have fewer or more than two node processors, depending on those anticipated Processing requirements. The communication link between the processors takes place via a collective line 25, which shows a PCL bus (parallel communication link from Parallel Communication Links).

Mass storage devices, i. E.

Disk _{units 21 S} and each database processor 26 are assigned mass storage units 27. The mass storage units 27 have duplicate outputs and inputs, so that access by the backup processor 28 is possible. General-purpose input-output devices 29 (I / O), for example display devices, are assigned to each of the four processors.

Each node processor is assigned at least one upstream processor 22, which provides an interface between

see the node processor on the one hand and assigned data connections Figure 10a and guest computers 10b, on the other hand, illustrate. The ballast processors 22 are illustrative IBM Series / 1 computers running the RPS operating system supplied by IBM. Any upstream processor communicates with its corresponding node processor using an X.25 protocol. from Programs supplied by DEC which control a DEC microprocessor 23 perform the DTE task of the stage 2 (the link level) of the protocol. Another, Microprocessor 24 associated with each node processor performs a similar function for the X.25 communications links via line 11.

The function of the node processor 20 is to execute programs for the subscriber and the Landlord. To this end, the mass storage units 21 associated with each processor are used first Line used, if not exclusively, for the processing currently in progress in this processor.

Practically all data, programs and other storage parts, both those belonging to the participant, as well as those belonging to the landlord are in a database in the mass storage devices 27 filed. These have the task of managing the database and granting access to the node processors. The structure of a typical user program package provided by the landlord as a news application s package (MAP from Message Application Package) is shown in FIG. This program package provides the user with operating options, such as text editing, the ability to Generate and send messages, as well as a variety of database options.

The program package MAP has a main program 31, which is linked to a number of operating programs that are called by the main program as sub-programs will. These operating programs include an editor 32, which provides the text processing options.

represents a set / fetch station parameter handler 33, which gives the user the opportunity to fetch numerous parameters assigned to his data connection and set, a command parser 34, which receives a command from the subscriber, the command word (for example "Call" or "Help") identifies it in the internal Form converts and packs the arguments into a form that is appropriate for the operating program to which the command is to be passed, a menu program 35, which gives the user various menu options and - depending from the individual or multiple selection of the user - provides further menus or a certain function in the name of the user executes, as well as an online documentation option 36, which reveals the basic ideas of the invention bodies.

Further, provided by the landlord, the user-contributed Progranmpakete _s which are not shown in the drawing, for example, include a standard subscriber tax package (SCCP standard Customer Control package), which gives the participants the opportunity to functions such as the operation and shutdown of Execute programs and stations, as well as a standard parameter processing package (SPHP from _Standard Parameter Handling Package), which enables a function similar to that of the operating program 33 for fetching and setting station parameters. Each of these program packages is linked to a corresponding group of operating programs, to which an implementation of the online documentation device 36 belongs in each case.

The memory areas in the database are of two types, namely a system memory area and one User storage area. As shown in FIG. 4, the plant storage area 40 includes, for example, one Number of system documentation storage sections (files)

400. Five memory sections are specifically shown. These are command documentation memory sections 401, 402, 403, a look-up storage section 404 and a Error documentation storage section 405. The storage

Sections 401, 402 and 403 consist of records, which each contain system documentation with reference to a specific command, which is referred to as MAP, SCCP or SPHP is. The look-up storage section 404 consists of records each defining a particular, included in the annex used expression. The error storage section 405 consists of records, each Contain information about a specific error or warning condition that has been detected by the system and the user is notified when one of the program packages is executed.

A separate memory area is created for each user within the database. Fig. 4 shows the user memory area 45 which is assigned to a particular user. According to the invention has the user storage area 45 user documentation storage areas or files 450, the records of which are accompanied by documentation texts supplied by the user of commands, contain how these texts are to be used in order to create the system documentation for one or more documentation commands to change. In other words, the user documentation files contain information indicating how the user-specific documentation and the Plant documentation that includes one or more documentation commands is assigned, distinguish. The corresponding memory sections (files) within the user memory area have been created using editor 32, for example.

In the example at hand, the

³ ^ users decided to keep documentation information for

a) commands used in the MAP program and

b) to deliver errors.

There are two user memory sections for this purpose (Files), namely the MAP command documentation storage section 451 and the error documentation storage section 452, created in user storage area. The names of these memory areas are for explanation identical to the corresponding system documentation

Storage areas, i.e. the storage areas 401 and 405. Accordingly, if the documentation program means 36 the name of the respective system documentation memory section to be opened - as explained below B, it also has the name of the respective user documentation memory section to be opened (if one is available).

Each of the program packages contains a corresponding data structure, which is called "Environment" referred to as. The environment for each package contains the storage section names for the plant documentation storage sections, which are assigned to this particular program package. In detail, the package MAP (shown in Fig. 3) associated environment 310 contain error, lookup, and command memory section names, for example Error documentation (Error.doc), printout documentation (Term.doc) and MAPrDokumentation (MAP.doc), which contain the names of the memory sections 405, 404 and 401, respectively represent. For example, when the documentation facility 36 retrieves the command documentation associated with the MAP wants, it speaks to environment 310 to determine the name of the system documentation memory section, to be accessed. The environments assigned to the packages SCCP and SPHP each contain the same Error and look-up memory section names like the MAP environment, as uniform groups of error abbreviations and uniform terminology can be used throughout the facility. The commands that are in each program package used change. Accordingly, the SCCP and SPHP environments each contain corresponding ones Command documentation memory section names, for example SCCP documentation (SCCP.doc) and SPHP documentation (SPHP.doc), which contains the names of the memory sections 402 and 402 respectively. 403 are.

Any record in the facility and user documentation storage sections praises one as an index "Key", the value of which is the command, expression, or error mnemonic. on which the

Recording relates. Accordingly, a record in a facility or user storage section containing the Contains documentation for, for example, a particular command, retrieved by having that command as a the index key is specified during the database read operation.

The format for a plant documentation record, i.e. a record in one of the plant documentation storage sections 400, is shown in Figure 5. The recording begins with a field delimitation - as an example the characters ## - followed by an optional main recording mark (flag) and a assigned end delimitation, at least a first section header and a section text for each section header, where all parts are separated by ## delimitations.

The value of the main record token can be the character C, which stands for "Continuation" and indicates that the in question Documentation associated with the index key is too long to be recorded and is therefore included in additional records continues. (Each such additional record has an index key that can be identified by adding a Number is formed for the key under which the first record is indexed, e.g. calH, call2 (Call1, Call2) etc.)

Alternatively, the main recording mark be the letter M, which stands for "menu". This flag indicates that the record in question is not a contains real documentation, but instead the name of a menu, and that when such a recording is encountered by the documentation device 36, this call the menu program device 35 and that menu should indicate that is to be presented to the user. This type of recording is used, for example, when The system provides documentation for a family of command words, for example "List memory sections" (list_file), "List Beifehle" (list_command), "List tables of contents" (list directories) etc.,

and anticipate that users will enter the incomplete documentation command "HELP LIST". In this case, the command documentation storage section contains a record indexed with the key "list" with an M as the main record tag and includes the name of a menu that asks the user what type of listing befehls a documentation desired xtfird.

The section heads in the facility documentation record according to Figo 5 are character strings, for example the heads USAGE (use) and EXPLANATION (explanation) in Table I. The section texts are character strings that comprise the texts associated with each section header follow.

(Another type of record used in the plant documentation storage sections, which does not conform to the format of Fig. 5, is simply composed of an index key with no initial delimitation. The documentation device 36 speaks when such a record is encountered by directly accessing that record This facility enables the system to automatically correct certain anticipated errors made by the user. For example, a record containing the entry "run_j>rogram" could be entered under the code "Lauf "(run), which is not a valid command. Accordingly, if the user who desires documentation regarding the command" program run "erroneously issues the documentation command" help "relating to the command" run "(HELP COMMAND = RUN), so the documentation facility first wins the record that is indexed under the key "Lauf". When ordering that this record simply contains the entry "Program run", it immediately proceeds to the acquisition of the record which is indexed under "Program run", which automatically corrects the user's error.) ^F

The format for a user documentation record, i.e., a record in one of the user documentation storage sections 450, is shown in FIG. 6. The record has an initial demarcation, a or two optional major record marks, at least a first section header and, after each section header, an optional section marker and section text with all parts separated by boundaries.

The main record flag field can be the Contains the letter C, which means continuation as before. It can also contain either an R or an N. The R stands for Replace and the N for New. These flag values can be used interchangeably each of which represents a command indicating that the total size of that user documentation record is to be used instead of the entirety of the corresponding system documentation record.

The section headers and section texts in the user documentation records are the same in the plant documentation records and need therefore not to be further explained.

The section marker can have one of the four values A, B, R or N. A and B stand for "after" (after) and "before" and represent commands indicating that the section text is in the user record either after or before the section text of the headed section of the corresponding Plant documentation record is to be added. R and N are, in turn, interchangeable commands used for "Replace" and "New" stand. Each of them indicates that the section text in question is the section text Replace the section with the corresponding header in the corresponding plant documentation record target. If the section flag is omitted, the section is treated as if the value of the Section marker A would be. If the section header of the user documentation record is not the same

like the section header in any plant documentation drawing is, the value of the section flag becomes irrelevant, as will be seen.

Before proceeding to the flowchart according to FIGS. 7 through 9, it is useful to determine the format of the documentation commands to be explained in more detail. As stated earlier, the user can issue commands such as HELP COMMAND = CALL (help regarding the "Call" command), HELP TERM = BILLING_IDENTIFIER (help in connection with the expression "calculation identifier") and HELP ERROR = E_NOT_ FOUND (Help in connection with error E not found). In response to this, the system delivers the full documentation available for the command, expression, or error in question, and modified (if applicable) by the user. As an optional option, the user can use the word "COMMAND =" (command) omit in a request for command documentation, for example, specify "HELP CALL" (help in connection with the call). Another option is to that the user indicates that only a specific section or sections of the documentation are presented should be, for example "HELP CALL SECTION = USAGE SECTIOn = EXAMPLE "(help in connection with call, section usage, section example). There is another option gives the user the option of retrieving documentation from the command documentation storage section associated with a program package which is not the currently used program package, provided that the user knows the name of this section of memory.

For example, a user using the MAP program package can use the command "HELP CALL FILE = SCCP.doc SECTION = ARGUMENTS "(help in connection with calls, memory section SCCP, documentation section arguments) and thereby obtain documentation regarding the arguments for the "Call" command, which is included in the program package SCCP is used.

7 to 9 contain a flow chart of the online documentation device 36 which - as indicated above

- is called as a subroutine and is also referred to below as "the subroutine". Fig. 7 shows in detail the record recovery part of the Subroutine. It begins at step 701 by examining the arguments supplied by the command parser 34 have been to determine what documentation is being requested will. If, according to step 703, the user has given an incorrect documentation command, for example "HELP ERROR" (help in connection with errors), then the documentation facility calls the menu facility 35 according to step 704. The menu facility tries to determine by evaluating the user's responses what documentation the user requested. When this is determined, the menu facility forms a documentation request instead of the user and gives them to the documentation facility.

It is assumed for the explanation that the user is using the program package MAP and a documentation command requesting documentation for the invoke command. According to step 706 now determined whether the last documentation request by this user was for the same command as the Documentation requested now, i.e. the command "Call". (This documentation is still available in the Output Record List 1050, discussed below If this is the case, the control goes directly to the marking / printing part of the subroutine (Fig. 9).

In the other case, the documentation device now determines the name of the relevant in accordance with step 709 Command documentation memory sections, in this example MAP.doc. According to 711 the subroutine then speaks provide a table for the names of open documentation storage sections to determine if there is a section or sections of memory with the Names MAP.doc are already open. If this is not the case, an attempt is made according to 714, one Memory section of this name in both the system and

also open in user storage space.

At this point it can be assumed that a system memory area of the name in question is open, since a plant memory section is always present. Possibly however, a user storage section for the type of documentation requested does not yet exist. Accordingly, at step 717, it is determined whether there is an open user memory section with the name MAP.doc is present. If this is not the case, the subroutine proceeds directly to step 732 in which the recording or (in the case of continuations). Records are retrieved that the documentation for contain the command in question.

On the other hand, if a user memory section named MAP.doc is open, then take place according to step 721 an attempt to retrieve from this section a user record or records that contain the Document the "Call" command. According to step 724, if there is no such record, what means that the user has not provided documentation for the "invoke" command, that's how it works Simply continue the subroutine to step 732. On the other hand, if there is a user record, it will Main record flag field (Fig. 6) with regard to checked for the presence of "R" or "N". This would mean the user documentation for the command "Call" is intended to replace the system documentation as a whole. In this case step 732 is omitted, since the system record that the documentation for the Command "invoke" is not required. On the other hand, if the user record does not have such a replacement record drawing is, the system record must also be retrieved, and it will be - as before the Step 732 performed.

At this point, control goes to the record processing section the documentation facility as indicated by step 734. This part of the subroutine, which is shown in Fig. 8 begins with

Step 801 where the previously retrieved plant documentation record - if available - is checked and dismantled. This includes making entries in a so-called system record list 1010 shown in FIG. The plant record list is a preferred arrangement of data structures, namely system blocks 1020, each of which is made to receive the following information from or memory with respect to a corresponding section of the facility record includes: the section header attached to the Stele 1021 is stored; a pointer to the position of the section text, which is at the point 102 2 is stored; a count for the number of characters in the text that is stored at location 1023.

Referring again to FIG. 8, the subroutine now proceeds to step 803 where the previously retrieved user documentation record - if one is available - checked in a similar manner and broken down into a user record list 1030 which is also shown in FIG. This list consists of user blocks 1040. Each user block shows, in addition to storage locations for a section header, a text reference and a character count, which are stored at locations 1041, 1042 and 1043, respectively, a storage location 1045 for the one described above Section Flag Value (A, B, R, or N).

The facility and user record lists are used to generate what is known as an output record list 1050 is used, as will be described shortly.

This list is composed of an arrangement of output blocks 1060, each of which has a storage location for the following information: a section header, a reference to a first text, a character count for the first text, a reference to a second text, a character count for the second Text and a pressure mark. This information is given under 1061 to 1066.

In particular, the subroutine populates the output record list 1050 by executing a Loop as indicated at step 808 in FIG. Each time the loop is run through, there is a subsequent block of the system blocks 1020 checked and determined in step 811 whether a matching section header in a the user blocks 1040 is present. If not, the subroutine continues to step 814, in which the section header from position 1021 in the system block to position 1061 of the next available output block 1060 is copied. In addition, the text information and the character count from positions 1022 and 1023 of the system block in positions 1062 and 1063 of the output block as the first text information or first character count copied. The second text information in the output block, which is saved at position 1064 is deleted, creating an Oh chain. The subroutine then runs through the loop for processing the next system block.

On the other hand, if there is a section header in one of the user blocks 1040, the one with the section header matches in the system block currently under consideration, then the subroutine copies this header according to step 816 into position 1061 of the next available output block and then sets the text information in step 819 (and corresponding character counts) in the output block corresponding to the value in the user block at location 1045 stored section marker. If in particular the value of the section marker "A" (for "after"), the first and second text information, which are stored in the output block at positions 1062 and 1064, the value of the text information given that at points 1022 and 1024 of the plants or User blocks are stored, and accordingly for the character counts. If the section marker "B" (for "before"), the output block text notes and character counts are given the same values, but assigned in the opposite order. if

the section mark is "R" (for "replace") or "N" C for "new"), the system documentation for the special section to be completely replaced by the user documentation. In this case, get the first Text information and the character count in the output block the values of the user block text indication and the corresponding counter value, and the second output block -Text notice is made a null chain. As indicated in step 821, the user block in question becomes now marked as if it has been "used", for example by adding its section header to a NuIl chain is made.

After all plant blocks 1020 have been processed in this way, the loop is exited, and the subroutine continues to step 824. There the user record list 1030 is searched for unmarked user blocks scanned, i.e. blocks whose section headers are not null strings. The information from each such user block is copied into a corresponding output block in the same way as the information has been copied to an output block in a system block that does not have a matching user block is as described in connection with step 814. From the foregoing it can be seen that the value of the section mark is irrelevant in this case.

According to step 826, the subroutine now continues to its section marking / printing part, which is shown in FIG. 9 is shown. If the documentation command states that only certain portions are to be reproduced according to a determination in step 901, see above as indicated by step 903, the print flag is set in the respective output block. In the other case As step 904 indicates, the print flags are set in all output blocks.

The documentation is now ready for "printing", i.e. for reproduction by the user. First becomes the record button that is used to retrieve the record has been used in capital letters

with double stars as the main heading according to step 908 printed (e.g. ** CALL ** in Tables I and II). Then each block in the output list 1050 is sequential viewed over a loop that starts at 911, within the loop each output block comes first checked according to step 913 whether it has been marked for printing. If not, the exam goes to the next one Block over. However, if the block has been marked for printing, the subroutine goes through steps 915, 916 and 919, each of which has the section header printed in capital letters, then the first, in the output block specified text and finally - if available, the second text is printed.

After all output blocks have been considered, the subroutine returns to its call point.

Claims (4)

Claims Online documentation procedure for use in a computer system, characterized by the process steps: Provision of system documentation for individual users of the system in response to a special documentation command issued by the user, the system documentation being assigned to the respective documentation command,
and providing for at least one other user of the system, in response to the issuance of the particular documentation command by the other user, user-specific documentation that has been previously defined by the other user. 2. Device for carrying out the online * 15 documentation method according to claim 1, characterized by a first device (36, 40; 1010, 1050) for providing system documentation for individual users of the system in response to a special documentation command issued by the user, wherein the system documentation to the respective documentation command is assigned, and a second device (36, 40, 45, 1030, 1050) for providing for at least one other user of the system in response to the issue of the special document Sonnenberger Straße 43 6200 Wiesbaden Telephone (06121) 562943/561998 Telex 4186237 Telegrams Potentconsult tion command by the other user of a user-specific Documentation previously defined by the other user. 3. Device according to claim 2, characterized in that the first and second means share a common means (40) for storing the System documentation that is assigned to the special documentation command and for storing system documentation the other documentation commands ^ O is assigned, which is issued by the users of the system can be, and that the second device also has a device (45) for storing one or more user documentation texts, at least the special documentation IQ command are assigned, and for storing a command which is assigned to each user documentation text and indicates how this user documentation text is to be used to modify the stored system documentation assigned to the particular command, and a device (36, 1030, 1050, 1010) to generate the user-specific documentation according to the aforementioned command. 4. Apparatus according to claim 2, characterized in that the first and second means a common device (40) for storing the system documentation assigned to the particular documentation command and has, for storing the system documentation, assigned to other documentation commands which can be output by the users of the system, that the system documentation assigned to each documentation command is made up of one or more sections of the system documentation text, that the second device further includes a device (45) for storing one or more, at least the particular Documentation command for assigned user documentation texts and for storing each user documentation text has assigned command, the indicates whether this user documentation text is to be added to a corresponding system documentation text, a should replace the corresponding system documentation text or as a separate section in the user-specific Documentation is to be used and that the second facility (36, 1010, 1050, 1030) continues a device for generating the user-specific Contains documentation corresponding to the aforementioned command.