BCACT: Activate processor

You use a BCACT command on a processor to activate the processor itself along with any processors which can be accessed via this processor.

BCACT on a processor

PROCESSOR = <processor-name 1 .. 8>
,ACT = ONLY , ... / LOCAL, ... / NODE, ... / ALL, ...
	ONLY, ...
		|		,CONFIGURATION = UPDATE / PRIMARY / NO
		|		,LINK-DOWN = KEEP-CONNECTION / DISCONNECT
	LOCAL, ...
		|		,CONFIGURATION = UPDATE / PRIMARY / NO
		|		,LINK-DOWN = KEEP-CONNECTION / DISCONNECT
	NODE, ...
		|		,CONFIGURATION = UPDATE / PRIMARY / NO
		|		,LINK-DOWN = KEEP-CONNECTION / DISCONNECT
	ALL, ...
		|		,CONFIGURATION = UPDATE / PRIMARY / NO
		|		,LINK-DOWN = KEEP-CONNECTION / DISCONNECT

PROCESSOR=<processor-name 1..8>
Name of the processor to be activated

ACT=...
Specifies the group of objects to be activated in addition to the processor.

ACT=ONLY / LOCAL / NODE
The operation is only performed for the processor.

ACT=ALL
The operation is performed for the processor and all objects which can be accessed from it.

CONFIGURATION=...
The operand specifies whether or not the network configuration for the processor must be modified using the routing protocol function. Specification is only possible for processors to which routes with the L3 profile IP, IPv6 or INTF exist.

CONFIGURATION=UPDATE
Route modifications resulting from routing protocol functions lead to modifications to the BCAM routing tables and remain effective for this BCAM session.

CONFIGURATION=PRIMARY
Route modifications resulting from routing protocol functions are to be canceled. The original configuration information is used again.

CONFIGURATION=NO
Route modifications resulting from routing protocol functions are not permitted.

LINK-DOWN=...
The operand specifies whether or not the transport connections assigned to the route are shut down in the event of a route failure.

LINK-DOWN=KEEP-CONNECTION
In the event of a route failure, transport connections assigned to this route are not shut down.

LINK-DOWN=DISCONNECT
In the event of a route failure, all transport connections assigned to this route are shut down.

Command logging

For reasons of compatibility, positive acknowledgments are supplied in news BCA0763, and negative acknowledgments in news BCA0762, followed by the message NBR0740. In addition, for positive acknowledgments, the messages BCA08DB and BCA0622 may also appear.
A description of the error messages that may be issued during command processing is provided in the table below.

Command return codes

(SC2)      SC1	Maincode	Meaning
0        0	CMD0001	Command successfully processed
2        0	BCA0623	Activation aborted
2        0	BCA08D7	Computer already active
0        1	BCA0768	Syntax error in command
0       64	BCA07A0	Computer does not exist
0       64	BCA0834	Line to computer is not active
0       64	BCA0856	Computer is not in operation
0       64	BCA08D8	Computer was not activated
0       64	BCA08E5	Computer is unknown
0      128	BCA0760	BCACT returned, BCACT is already running
0      128	BCA0814	BCAM is being terminated abnormally
0      128	BCA0816	BCAM is terminating
0      130	BCA0766	BCAM is not active