HP 3000 Manuals HP 3000 Manuals
Creating the File
An MPE file to be input to the Batch Configurator is always an 80byte,
fixed length record, USASCII file. If you create the file using one of
Hewlett-Packard's text editors, keep the file unnumbered.
The file is made up of two kinds of records: passive and active.
Passive Record Format
Passive records are included in the file to improve its clarity and to
end it. A passive record is defined by any of the following:
* Blank Line. Use blank lines to make the file easier to read. The
Batch Configurator ignores blank lines.
* $ (Dollar sign). Type $ at the first character position of the
line to indicate the Batch Configurator that the following
characters are your comments.
* **(Two asterisks). Place these in columns 1 and 2 of the final
line of the file to indicate its end. The Batch Configurator
ignores any data following these characters.
Active Record Format
The active records of a batch configuration file perform actions on
elements of the database: adding, modifying or deleting.
The active records of a file, must be in a certain format, so that a
given operation completes. The file always begins with an operation code
and is followed by parameters, and perhaps other records. The operation
code is either the first two or four characters of the transaction,
depending on the type of transaction, and defines the operation.
Operations can be continued over further records by ending the first
record with an ampersand character (&). Please note that other
continuation characters are sometimes used, for example, a hyphen (-),
however it is recommended that you only use the & character.
The operation code is followed by one or more parameter fields. These
fields must follow in a defined order and are of a certain field length.
The information entered into these parameter fields is required for the
completion of the operation. Some of the fields must contain
information, whilst others do not, before a given operation can complete.
The operation code field and parameter fields are of fixed lengths and
always follow each other directly.
There are no blanks that separate the operation code field and parameter
fields from one another. The operation code field will either be two or
four characters long, (depending on the type of operation to be
completed), and will contain either two or four numeric characters that
uniquely identify that operation. Any parameter field is of fixed
length, and may contain characters and blanks.
If the number of characters used in a parameter is less than the full
parameter length add blanks to complete the parameter field.
Operation codes must be added to the file in the order which they are to
be applied to the database during batch configuration. Therefore, the
operation to add a new location must always appear in the file before any
operations to add new users for that location.
An Example File
The example file shown here is one created by the Administrator of the
Pharaoh Company's New York computer to add parts of the company's
European network to the local configuration. (This scenario is used in
all the examples throughout this chapter.) It illustrates the format of
a batch configuration file and of some of the operations. The operations
in the file add a computer, mailnode, and users for a facility in
Liverpool, England, and an FSC gateway and users for an IBM PROFS system
at Liverpool.
All the records beginning with $ are comments. The file is terminated
with the characters **. To take the last operation as an example: 41 is
the operation code, O'Neill, Pat / HPIBMA/00 is the username and
mailnode, & is the continuation code, and (PONEILL.RDPROFS) is the
foreign address. The continuation code ends the first record and allows
the foreign address to be provided on another record.
________________________________________________________________
| |
| |
| $UPDATE NEW YORK WITH LIVERPOOL CONFIGURATION DATA |
| |
| $ADD A COUNTRY |
| 11UK United Kingdom |
| |
| $ADD LOCATIONS |
| 21UK MANF2 Liverpool Manufacturing |
| 21UK HPIBMA R&D PROFS system |
| |
| $ADD A SUBLOCATION |
| 31MANF2 PCProduction Control 1 |
| |
| $ADD A HIERARCHIC LOCATION |
| 71HPIBMA1 |
| |
| $ADD COMPUTER/GATEWAY |
| 51LVRPOOL 0 |
| 51HPIBMA 4 |
| |
| $ADD ROUTES |
| 61LVRPOOL MANF2 PC |
| 61HPIBMA HPIBMA 3 |
| |
| $ADD USERS |
| 41David Webb / MANF2/PC |
| 41James Pemberton / MANF2/PCBuilding B, Factory Foreman |
| 410'Neill, Pat / HPIBMA/00(PONEILL.RDPROFS) |
| |
| |
| ** |
| |
________________________________________________________________
Example Batch Configuration file