Version: v3.6 (Non supportée)

Fax Driver

Appendix

"user name" <Tab> "access code" If the name (followed or not by first name) and the associated code are valid, the poke command is accepted. If a call was pending for the operator in question, it is automatically acknowledged.

The USER topic also includes for each operator:

 a <USER> item that contains the record of the user designated by <USER>, operator's name followed or not by his first name (or an abbreviation of the first name). See the record description below.

a <USER>.ONDUTY item allowing the on-duty status of the user to be read and write: 0 = user off-duty 1 = user on-duty

 a <USER>.CALLSTATUS item for reading of the call cycle status of the user: 0 = on call cycle for the user 1 = call in progress 2 = call suspended 3 = call succeeded (wait for call acknowledgment) 4 = call failed 5 = call acknowledged 6 = call not acknowledged (failed)  a <USER>.SCHEDULE.N item that contains the on call schedule of the operator designated by <USER> for the N'th week starting from the current week (N = 0 to 51). By default N is set to 0 (schedule for the current week).  a <USER>.MESSAGE.N item that contains the N'th message (by default N=0) in the mailbox of operator designated by <USER>.  a <USER>.REPORT item that contains the report transmitted by operator designated by <USER>. The user record item contains a line of 17 fields separated by tabulation characters (TAB) and ended by a carriage return (CR):

Field 1 User ID code (numerical identification number) Field 2 User name Field 3 User first name Field 4 Access level (0, 1 or 2) Field 5 1st call number Field 6 Driver code for 1st call number Field 7 Validation of 1st call number (0/1) Field 8 2nd call number Field 9 Driver code for 2nd call number Field 10 Validation of 2nd call number (0/1) Field 11 3rd call number Field 12 Driver code for 3rd call number Field 13 Validation of 3rd call number (0/1) Field 14 Index of active number (0 = none, 1, 2 or 3) Field 15 Index of relief number (0 = none, 1, 2 or 3) Field 16 0 = operator off-duty, 1 = operator on-duty

Field 17 Name of substitute operator (when field 16 = 0)

In writing (poke), the whole file is t ransmitted, but only fields 5 to 17 are taken into account. The schedule item is represented for reading by a line of 7 identical fields separated by tabulations and ended by a carriage return (CR). Each field contains the on call schedule for one day of the week, the 1st field representing the schedule for Monday. Each field of the schedule has the following format: "DD-MM:XXXXXX", with: JJ = day of month (01 to 31) MM = month (01 to 12) XXXXXX = 6 hexadecimal digits representing the daily schedule in the form of a bit field, a bit being set if the operator is on call, the 1 st bit (MSB) corresponding to 0h. Example: 03FFF8 corresponds to the daily schedule:

0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23

- - - - X X X X X X X X X X X X X X - - - This item cannot be written (poke denied). The message item is shown for reading by a line of 4 fields separated by tabulations and ended by a carriage return (CR): Field 1 Index of the message (starting from 1) Field 2 Date/time of deposit of message (format "DD-MM HH:MM:SS") Field 3 Name / first name of user who sent the message Field 4 Message content In writing, only the value "0" is allowed, which provokes the deletion of all the messages sent to the operator.

The GROUP topic contains, in addition to the DDE protocol items, some items concerning on-call groups.

 TOPICITEMLIST List of items supported under the GROUP topic  CONVCOUNT Current number of DDE conversations established with the GROUP topic  ADVISECOUNT Current number of advise transactions with items of the GROUP topic

 GROUPCOUNT Number of defined on-call groups

Appendix

 GROUPLIST List of on call groups

The GROUP topic also includes for each group:

 a <GROUP>.STATUS item that indicates the on-call status of the group designated by <GROUP>: 0 = there is no on-call team defined at the current time, 1 = the current on -call team is defined in reduced duty (only called for important alarms), 2 = the current on-call team is defined in normal duty (called for all alarms), 3 = no valid user in the current on-call team. This item is read only.  a <GROUP>.TEAM item that returns the name of the current team to call for the group designated by <GROUP>. This item is read only.  a <GROUP>.DEROGTEAM read/write item that designates the team selected to be called when the group designated by <GROUP> is in derogation state.  a <GROUP>.DEROGATION read/write item that specifies the current derogation status of the group designated by <GROUP>: 0 = group in normal on-call state (teams called according to the defined schedule), 1 = group in derogation state. The called team is the one that is preset as derogation team. If there is not a preset team, calls concerning the group are locked.  a <GROUP>.CALLSTATUS item that indicates the current status of the call cycle for the group designated by <GROUP>: 0 = no current call cycle for the group, 1 = call cycle in progress, 2 = call transmitted (wait for call acknowledgment), 3 = group unwarned (call failed), 4 = warned group (calls acknowledged). This item is read only.  a <GROUP>.CALLSTATUS item that indicates the team changeover status of the group designated by <GROUP>: 0 = programmed schedule or forced team, 1 = team changeover done (before the scheduled time), 2 = waiting for team changeover (after the scheduled time or on -call ended in the "team changeover mandatory" mode), 3 = timeout for team changeover expired, 4 = on-call ended (before the scheduled time, except in the "team changeover mandatory" mode). This item is read only.

The DATASERVER topic contains, in addition to the DDE protocol items, some items concerning the data servers.