Send Data To Security Unit {CACO-2}

This option will send the user’s access information, as created in {CACO-1}, to the Security Control Unit.

Data is sent to the control unit with one of three status codes. These status codes cannot be seen by the screen user, but can be used for query purposes by any user that can do SQL queries:

When a new record for a user is created in {CACO-1}, the status of the user would be N (normal). When this record is sent to the control unit, a new record will be created on the control unit.
When the user's data has been changed on an existing record in {CACO-1}, the status of that user will be changed to U (update). When this record is sent to the control unit, the existing record will be updated on the control unit.
When a user’s data is deleted from {CACO-1}, the status of that user will be changed to D (deleted). ). When this record is sent to the control unit, the existing record will be deleted from the control unit. If this was successful, the user’s data will be deleted from the access control tables in the ITS system.
Once data has been sent to the control unit, and, processed successfully, the status of the user is updated to a P (processed) on the ITS system.

When this option is run, all users with the statuses, N, U and D are sent to the GCS and will then be updated to the status P.

The users can also run {CACM-4} to send an individual user’s access data to the GCS.

User Selection	Prompt Text ^{* an item between square brackets [ ] is the default answer}	Type & Length	Comments

Sort Order	Per	Comments

System Select
	No special system selection.

Example: When sending the data, a message will display:

Connected to server gcs1 on port 43692 socket 5 on Wed Mar 3 18:59:46 1999
All done on Wed Mar 3 18:59:49 1999

No record for S9500717 on table CAGCRD
No record for S9673435 on table CAGCRD
No record for S9673559 on table CAGCRD
No record for S9675187 on table CAGCRD

Any errors, which occurred when the data was sent, will come back in a report format. The report will list user types and numbers, and the error that was experienced.
These user numbers must be followed up on, because no access will be created for them on the control unit.

Processing Rules
	No special processing rules.

List of fields in xml/xsl object (delete if not applicable):

See Also:

Procedures:

None

History of Changes

Date	System Version	By Whom	Job	Description
29-May-2008	v01.0.0.0	Charlene van der Schyff	t145487	New manual format.
15-Aug-2008	v01.0.0.0	Charlene van der Schyff	t151624	Edit Language obtained from proof read language; Juliet Gillies