Commit 99b590b9 authored by Claes Sjofors's avatar Claes Sjofors

Documentation changes

parent dc129ac9
......@@ -60,6 +60,16 @@ SObject pwrb:Class
!/**
! Specification of a Qcom bus.
! A number in the intervall 1-999.
!
! Qcom is the communication protocoll used by the nethandler and
! message handler to communicate between Proview nodes. The Qcom network
! is divided into busses, where two nodes has to be on the same bus to be
! able to communicate.
!
! Normally you divide the network into one production bus and one simulation
! bus, thus preventing the simulation nodes to interfere with the production
! nodes. In large networks it is also possible to divide the production nodes
! into several busses.
!*/
Object BusNumber $Attribute 2
Body SysBody
......
......@@ -23,14 +23,16 @@ SObject pwrb:Class
! @Version 1.0
! @Group ProjectConfiguration
! @Summary Configures distribution of files.
! The Distribute object configures distribution of files to process and
! operator stations.
! The Distribute object configures distribution of files from the
! development environment to process and operator stations.
!
! The object reside in the project volume beneath a NodeConfig object.
! The specified file(s) will be included in the distribution package and
! The specified files will be included in the distribution package and
! copied to the node configured by the NodeConfig object.
!
! The files are specified in the Components attribute, which is a bitmask.
! The collected files are specified in the Components attribute, which is
! a bitmask.
!
! Description of the bits in Compontents:
!
! @b UserDatabase
......@@ -80,6 +82,12 @@ SObject pwrb:Class
! Other files can be included with an ApplDistribute object.
! The GraphDistribute and SystemDistribute objects are obsolete.
!
! The distribution is performed by the Distributor, which is activated
! from the menu in the configurator. The distributor collects all the
! files that are needed for a process or operator station, into a package
! file. The package is copied to the process and operator station and
! unpacked there.
!
! @b See also
! @classlink NodeConfig pwrb_nodeconfig.html
! @classlink ApplDistribute pwrb_appldistribute.html
......
......@@ -65,7 +65,7 @@ SObject pwrb:Class
EndBody
EndObject
!/**
! Name of the node
! The name of the node, i.e. the network node hostname.
!*/
Object NodeName $Attribute 2
Body SysBody
......@@ -73,7 +73,7 @@ SObject pwrb:Class
EndBody
EndObject
!/**
! Operating system of the node
! Operating system of the node.
!*/
Object OperatingSystem $Attribute 3
Body SysBody
......@@ -86,6 +86,7 @@ SObject pwrb:Class
! Loadfiles, applications and graph-files will be copied to this
! node by the distributor.
! In most cases this is the node itself.
!
! For ELN systems that is booted from a VMS node, the the VMS-node
! is the boot node.
! If the node is a development node which has access to the
......@@ -108,7 +109,9 @@ SObject pwrb:Class
EndBody
EndObject
!/**
! Ip address of the node.
! IP address of the node.
!
! In format a.b.c.d, e.g. 192.168.32.144
!*/
Object Address $Attribute 6
Body SysBody
......
......@@ -22,7 +22,7 @@ SObject pwrs:Class
!/**
! @Version 1.0
! @Group Volumes
! A dynamic volume only exist in runtime, and contains objects that is
! A dynamic volume only exist in runtime, and contains objects that are
! created and deleted in runtime.
!
! A dynamic volume is configured by a CreateVolume object, normally
......
......@@ -59,7 +59,7 @@ SObject pwrs:Class
! the project name. Sometimes, at an upgrade or major revision, it is
! a good idea to make a copy, to keep the current state of the project.
! The copy will have a new projectname, but the system name remains the
! same, and identifies the volumes and node that belongs to the system.
! same, and identifies the volumes and nodes that belongs to the system.
!*/
Object SystemName $Attribute 2
Body SysBody
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment