serverattach
Purpose
Describes the code service state for an RT PC system.
Description
The code service attribute file describes the code
service state for a particular system. It is a standard
attribute file in directory /etc/codeserve. The
serverattach attribute file primarily controls:
o active service client processes
o state conditions and transitions for any system.
The file contains a stanza for every possible server for
this node. If this node has no servers, the standalone
stanza takes effect. The file usually processes seri-
ally, from the first stanza to the last. In the fol-
lowing order, the stanzas describe the primary server,
alternate servers, the standalone parameter, and the
default stanza.
The command chngstate controls the attribute file proc-
essing. The chngstate parameters permit the following
process control over the attribute file:
o If there are no parameters, each stanza processes
serially, beginning with the primary stanza, until a
server attaches or the system becomes a standalone
system.
o The command may specify a starting stanza, as a
parameter. The system ignores previous stanzas, but
processes normally the stanzas that follow the
starting stanza.
o Exclude a stanza from the process. The process must
be repeated for each stanza to be excluded.
o The system may override incorrect values of the fol-
lowing passed parameters. The new value of an over-
ridden parameter applies to all stanzas.
- mode
- time
- interval
Each stanza describes the target state for this partic-
ular node as either active or standalone. If the stanza
specifies active, it also indicates the relationship
between a client node and its server.
The servername may be either a nickname or a node ID.
The first stanza identifies the primary server. Subse-
quent stanzas identify alternate servers followed by the
default stanza. The last stanza is the standalone stanza
and should not include a servername entry.
The valid keywords and values are:
mode Indicates how the client should attempt to
achieve compatibility with a server oper-
ating in the active code service state.
Possible values are:
auto System will interact with the cli-
ent's user as little as possible.
manual System will not upgrade a licensed
program or another program without
interacting with the user.
If a user on a client operating in
the active code service state wants
to prevent automatic upgrades of
licensed programs or programs, the
value should be set to manual. The
default stanza forces a mode of
manual if mode is not specified.
state The code service state in which a system
runs when attached to a particular server.
Possible values are active and standalone.
time The value of time is the maximum number of
seconds that a client will attempt to attach
to a server in either active or
historyvalidation modes.
Note: The historyvalidation mode is a tem-
porary process where the client ensures that
it is fully compatible with the programs
installed on the server. If the client
cannot attach to the server within the spec-
ified time, the client attempts to execute
the instructions in the next stanza, if
present. If the user specifies a time of
less than 60 seconds, then the system forces
a value of 60 seconds.
interval Equals the delay time, in seconds, between
efforts to attach to the server in either
active mode or historyvalidation mode. If
interval is not specified, the default
stanza sets an interval time of 10 seconds.
Example
* Primary server stanza
servera:
mode = auto
state = active
time = 60
interval = 15
* Backup server stanza
serverb:
mode = manual
state = active
time = 90
interval = 10
* Default system stanza
default:
state = standalone
standalone:
state = standalone
mode = manual
time = 60
interval = 10
File
/etc/codeserve/serverattach
Related Information
In this book: "attributes."
The chngstate command in AIX Operating System Commands
Reference.
Managing the AIX Operating System.