HP 3000 Manuals HP 3000 Manuals
Operation Record Formats
The required record formats for each operation are listed in the rest of
this chapter. The operations codes are listed in numeric order and are
grouped as follows:
Local system Data Codes 1 to 10
Country Data Codes 11 to 20
Location Data Codes 21 to 30
Sublocation Data Codes 31 to 40
User/Resource Data Codes 41 to 50
Computer/Gateway Data Codes 51 to 60
Route Data Codes 61 to 70
Hierarchical Address Data Codes 71 to 80
Foreign Address Data Codes 81 to 90
HP Schedule Data Codes 91 to 99
All field are mandatory unless stated they are optional.
01 Sequence Record
Use
Use the Sequence Record to apply sequenced Directory updates.
The Batch Configurator applies the Directory updates when the Sequence
record is used and the update is in sequence.
The Batch Configurator does not apply the update and sends an error
message to the sender when the update is not sequenced. An error message
is also sent to General Delivery on the node to which the update was
intended.
Not using the Sequence Record in a file indicates that sequence checks
are not required. Updates are then applied without making any sequence
number checks.
Format
01ComputerSequencenumber
where
01 is the operation code.
Computer is the computer from which the transactions
originated.
Field length of 8-alphanumeric characters.
Sequencenumber is the sequence number of the transactions.
Numeric digits up to 32767. 0 is considered to be
immediately after 32767.
Examples
01DUINH1 1234
01JP00H1 32766
0501 Modify *ADMIN Reporting Characteristics
Use
Use this record to modify the *ADMIN reporting characteristics.
Format
0501ReportflagsAltusernameAltusernode
where
0501 is the operation code.
Reportflags are 12 consecutive, one character ASCII fields. The
first four fields contain the values defined below:
0 no
1 yes
The remaining 8 characters must be blank, and are
reserved for the future use.
The first four, one character fields are:
* First Reportflag reports the successful Directory
updates to the originator of the message. The
default value is 0 (no). The default is
overridden if the originator sets a Reply
acknowledgment on the message that contains the
updates.
* Second Reportflag reports the unsuccessful
Directory updates to originator of message. The
default value is 1 (yes).
* Third Reportflag reports successful Directory
updates to a specified user. The default value is
0 (no), where reports are sent to General Delivery
on the machine on which the updates are being
applied.
* Fourth Reportflag reports unsuccessful Directory
updates to a specified user. The default value is
0 (no).
Altusername is the name of the specified user to whom *ADMIN reports
are to be sent when either of the third or fourth
Reportflags (in columns 7 or 8) are set to 1 (yes). The
user may be a local user or a user on another system.
The field is 36 alphanumeric characters long and may
contain blanks. It follows the Reportflag fields, and
begins in column 16.
Altusernode names the specified user's address. The field is 8
characters long and specifies the location and
sublocation of the user. It begins in column 52. The
"/" (separating character) must never be used to separate
the location and sublocation when you perform this
operation.
Examples
05010101 GEORGE AMI PARIS 03
0502 - Modify Default Routing Computers
Use
Use this record to modify data on the default routing computers.
Format
0502PrimcompSeccompPri1Pri2
where
0502 is the operation code.
Primcomp is the name of the primary default routing computer
Field length of 8-alphanumeric characters.
Seccomp is the name of the secondary default routing computer
Field length of 8-alphanumeric characters.
Pri1 is the value that indicates the route priority of the
primary default routing computer.
Field length of one character with a value of either:
Blank Route all mail over this route.
A Route Deferred mail only.
B Route Deferred and Normal mail only.
Pri2 is the value that indicates the route priority of the
secondary default routing computer.
Field length of one character with a value of either:
Blank Route all mail over this route.
A Route Deferred mail only.
B Route Deferred and Normal mail only.
Examples
0502NEWYORK CHICAGO B
0503 Modify Default Filing Cabinet and Work Area Usage Limits
Use
Use this record to modify the default Filing Cabinet and Work Area usage
limits.
Format
0503FClimitWAlimit
where
0503 is the operation code.
FClimit is the new default value for the Filing Cabinet usage
limit, in sectors.
Field length 9-numeric characters long. This is an
optional entry.
If the field is left blank then the limit will be set
at "unlimited".
WAlimit is the new default value for the Work Area usage
limit, in sectors.
Field length 9-numeric characters long. This is an
optional entry.
If the field is left blank then the limit will be set
at "unlimited".
Examples
0503 100000000
0551 - Add/Modify User Configuration Template
Use
Use this record to add or modify user templates for configuring groups of
users.
NOTE The first template in the file is the default template with the
name DEFAULT, from which the default settings in the User
Definition Screen 2, displayed by the Configurator, are obtained.
Format
0551TemplateFClimitWAlimitAccesscapsSpecialcaps1-32
where
0551 is the operation code.
Template is the name of the new or existing configuration
template.
Field length of 16-alphanumeric characters.
If the template exists already, it will be modified
with the contents of this transaction. Otherwise a
new one will be created.
FClimit is the Filing Cabinet usage limit that applies for
that template.
Field length of 9-numeric characters.
If no values are provided in these fields then the
respective limit will be set to "unlimited".
WAlimit is the Work Area usage limit that apply for that
template.
Field length of 9-numeric characters.
If no values are provided in these fields then the
respective limit will be set to "unlimited".
Accesscaps are the new user access capabilities, which consist of
ten one character fields. Their values can be:
0 No
1 Yes
Blank Default value is set.
The 10 one character fields are listed, in order
below:
Read items Default = 1
Copy to Filing Default = 1
Cabinet
Delete items Default = 1
Create items Default = 1
Copy to Work Area Default = 1
Edit items Default = 1
Mail items Default = 1
Calendar/Diary Default = 1
access
Autofile Default = 0
MPE access Default = 0
Specialcaps1-32 are the new user capability settings. These consist
of 32 one character ASCII fields with the following
values:
0 No
1 Yes
Blank Default value is set.
The first 16 one character fields refer to the special
capabilities given to users. The next 16 one
character fields refer to the first 16 of the User
Definable Capability Groups. The defaults are set
either to those already defined in the existing
template, or if the template is new, to the defaults
listed below:
Everyone Default value=1
SysAdmin Default value=0
LocalAdmin Default value=0
Script Default value=0
PubDl Default value=0
NoticeBrd Default value=0
HelpInstl Default value=0
NetAdmin Default value=0
FormInstl Default value=0
Special Capability No values apply
Fields 10-16
User Definable Default value=0
Capabilities 1-16
Examples
0551TEMPLATEA021 1000000 1000000 1111111110
0552 - Modify User Configuration Template (2)
Use
Use this record to modify an existing user configuration template.
Format
0552TemplateFkeysProfileSpecialcaps33-64
where
0552 is the operation code.
Template is the name of an existing configuration template.
Field length of 16-alphanumeric characters.
Fkeys is the name of the file in MAILCONF.HPOFFICE from
which to extract the user's function keys (default is
SOFTKEYS).
Field length of 8-alphanumeric characters.
Values must begin with an alphabetical character.
Profile is the name of the file in MAILCONF.HPOFFICE which
holds the user's initial profile settings. The
default file is USERCONF in the case where this is a
new user. If an existing user is being modified then
no change is made.
Field length of 8-alphanumeric characters.
Specialcaps33-64 are the user capability settings for the remaining
User Definable Capability Groups (32 to 64). These
consist of 32 one character ASCII fields where the
values are:
0 No
1 Yes
Blank No changes made
Examples
0552TEMPLATEB0139 SOFTKEYSUSERCONF
0553 - Delete User Configuration Template
Use
Use this record to delete a user configuration Template.
Format
0553Template
where
0553 is the operation code.
Template is the name of an existing configuration template.
Field length of 16-alphanumeric characters.
Examples
0553TEMPLATEF675
06 Transactions Application Filter
Use
Use this record to filter transaction applications. This allows certain
transactions that have been mailed to the *ADMIN server on several
machines to be applied only to one specific system.
All the transactions that follow the 06 transaction are selectively
applied to the system where that mailnode is local, until the next 06
transaction, or end of transaction file is reached.
Format
06Node
where
06 is the operation code.
Node is the name of the mailnode on the system where the
following transactions are to be applied:
Field length of 8-alphanumeric characters. It names
the location and sublocation of the system. In this
transaction, the location and sublocation information
must never be separated by the separating "/"
character.
This is optional.
If the Node is left blank, selective application of
transactions cease. This causes the Batch
configurator to attempt to apply all the remaining
transactions to all systems that have been mailed.
Examples
06SALE1
06MANF1
11 Add a Country
Use
Adds a new country to the database.
Format
11CountryCountryname
where
11 is the operation code.
Country is the country code to be added.
Must not already exist in the database.
Field length of 8-alphanumeric characters.
First character value in the field must always be a
letter.
The code will be upshifted and romanized.
Countryname is a description of the country.
Field length of 36-alphanumeric characters. This is
optional.
Examples
11UK United Kingdom
11SWITZ Switzerland
12 Delete a Country
Use
Deletes a country from the database. Any locations that were associated
with the country must have first been deleted.
Format
12Country
where
12 is the operation code.
Country is the country code to be deleted.
Must exist in the database.
Field length of 8-alphanumeric characters.
Field value must start with a letter.
Examples
12SPAIN
12ITALY
13 Modify a Country
Use
Replaces the existing description of a country with that specified, or
removes it if no new description is specified.
Format
13CountryCountryname
where
13 is the operation code.
Country is the country code whose description is to be modified.
Must already exist in the database.
Field length of 8-alphanumeric characters.
Field value starts with a letter.
Countryname is the new description of the country.
Field length of 36-alphanumeric characters. This is
optional.
Examples
13SWITZ
13UK Great Britain
21 Add a Location
Use
Adds a new location to the specified country.
Format
21CountryLocationLocationname
where
21 is the operation code.
Country is the country code with which the location is to be
associated.
Field length of 8-alphanumeric characters.
Field value starts with a letter.
Location is the location code to be added.
Must not already exist in the database.
Up to 6-alphanumeric characters.
Will be upshifted and romanized.
Locationname is a description of the location.
Field length of 28-alphanumeric characters. This is
optional.
Examples
21UK MANF2
21SWITZ SALE2 European Sales Region
22 Delete a Location
Use
Deletes the specified location from the database. Any sublocations that
were associated with the location must first have been deleted.
Format
22Location
where
22 is the operation code.
Location is the location code to be deleted.
Must exist in the database.
No mailnodes must be associated with this location.
Field length of 6-alphanumeric characters.
Examples
22MANF3
22SALE3
23 Modify a Location
Use
Replaces the existing description of a location with that specified, or
removes it if no new description is specified.
Format
23LocationLocationname
where
23 is the operation code.
Location is the location code to be modified
Must exist in the database.
Up to 6-alphanumeric characters.
Locationname is the new description of the location.
Field length of 28-alphanumeric characters. This is
optional.
Examples
23MANF2 Liverpool Manufacturing
23SALE2 Eastern Hemisphere Sales
24 Purge a Location
Use
Purges an existing location, complete with any associated sublocations,
users and routes. If native (non-USASCII) names are configured for any
of the purged users, these will be deleted from the Native Database.
NOTE User Interface Sessions must be completely disabled for this
transaction to work.
CAUTION Use this operation with care. Accidental use can disrupt your
configuration.
Format
24Location
where
24 is the operation code.
Location is the location code to be purged.
Field length of 6-alphanumeric characters.
Examples
24MANF2
24SALE2
31 Add a Sublocation
Use
Adds a sublocation to an existing location and applies controls over the
application of remote directory updates mailed from this sublocation.
Format
31LocationSublocSublocnameLocalUpdateflagSubsetflagDistributeflag
where
31 is the operation code.
Location is the location code of an existing location.
Field length of 6-alphanumeric characters.
Subloc is the sublocation code to be added.
2-alphanumeric characters.
Sublocname is a description of the sublocation.
Field length of 28-characters. This is optional.
Local is a one character field that indicates if the mailnode
is local or remote:
1 specifies a remote mailnode - (on another
computer).
2 specifies a local mailnode - (on this computer).
Updateflag one character, which may be:
Blank No remote updates sent from this mailnode
will be applied to this system's database.
1 Remote Directory updates sent from this
mailnode will be applied to the database.
2 In addition to the above, local system and
Directory updates will be accepted.
3 In addition to the above, local user deletion
updates will be accepted
4 In addition to the above, password updates
will be accepted.
Subsetflag one character, which may be:
1 if future updates relating to users on this
remote mailnode are to be ignored.
Blank if future updates relating to users on this
remote mailnode are to be applied.
Distributeflag 1 character, which may be:
1 if this transaction should be reported to the
BCREPORT file, for later distribution to
other computers.
Blank if this transaction is not required to be
reported to the BCREPORT file, for later
distribution to other computers.
Example
31SALES2 SFsalesForce 1111
32 Delete a Sublocation
Use
Deletes an existing sublocation from the database. Any users or routes
that were associated with the mailnode must first have been deleted.
Also the sublocation must not be the default sublocation for a location.
Format
32LocationSublocation
where
32 is the operation code.
Location is the location code from which the sublocation is to be
deleted.
Field length of 6-alphanumeric characters.
Sublocation is the sublocation code to be deleted.
2-alphanumeric characters.
Examples
32MANF2 AC
32SALE2 01
33 Modify a Sublocation
Use
Replaces the existing description of a sublocation with that specified,
or removes it if no new description is specified.
Format
33LocationSublocSublocnameLocalUpdateflagSubsetflagDistributeflag
where
33 is the operation code.
Location is the existing location code of the sublocation.
Up to 6-alphanumeric characters.
Subloc is the sublocation code whose description is to be
modified.
Field length of 2-alphanumeric characters.
Sublocname is a new description for the sublocation.
Field length of 28-characters any kind.
Local one character, which may be:
1 If this is on a remote system.
2 If it is a local node.
Updateflag one character field where the values can be:
Blank No remote updates sent from this mailnode will
be applied to this system's database.
1 Remote directory updates sent from this
mailnode will be applied to the database.
2 In addition to the above, local system and
directory updates will be accepted.
3 In addition to the above, local user deletion
updates will be accepted.
4 In addition to the above, password updates
will be accepted.
Subsetflag one character, which may be:
1 if future updates relating to users on this
remote mailnode are to be ignored.
Blank if future updates relating to users on this
remote mailnode are to be noted.
Distributeflag 1 character, which may be:
1 if this transaction should be reported to the
BCREPORT file, for later distribution to other
computers.
Blank if this transaction is not required to be
reported to the BCREPORT file, for later
distribution to other computers.
Example
33SALE2 SFSales Force 13 111