node_linkN
Purpose:
-
Get variables from a remote node.
Enter:
-
node_linkN [filename] [node=XX/tc=NNN] [name=task_name] [host=hostname] [direction=push/pull] [extender] &
Where:
-
filename
Optional. Specify a filename that contains the desired list of local and remote CyFlex variables.
node/tc
Optional. Specify the node number or test cell number to replace node number in the first block of the specification file.
name
Optional. Specify the name to register this task with the OS. The default is “node_link”.
host
Optional. Specify the IP address or hostname of the remote computer. Use this option when the transfer is to or from a non-qnx node and when the @HOSTNAME option is used in the spec file.
direction
Optional. Specify ‘push’ or ‘pull’ to indicate the direction of data movement. The default is to ‘pull’ data from the remote node.
extender
Optional. Specify the name extender to identify the small_smN version on the remote node.
Example:
-
node_linkN specs/em_specs.316 extender=N50 &
The above starts “node_linkN” on the local node accessing the CyFlex variable specified in the file em_specs.316. The node number for the first block of specifications will be overwritten with ’58’. The task name of “node_linkN” will be registered with the OS.node_linkN node_link.setting direction=push host=ctcnode9 &
The above starts “node_linkN” on the local node and moves data to ctcnode9.
Notes:
-
This program is normally spawned via the go script. Multiple copies may be spawned if links to different nodes using separate spec files is desired.
The following is an example spec file linking to a node via its ip address or hostname.
# keyword ip_address transfer_interval @HOSTNAME 192.168.1.100 1[s]
# fetched_variable(remote node) target variable (this node) my_token cell_2_token