Status-Control(...) Negative-Acknowledge-1
The Status-Control(...) Negative-Acknowledge-1 message flows from the node to the application and from the application to the node. It is used with a PLU connection.
struct Status-Control(...) Negative-Acknowledge-1 {
PTRBFHDR nxtqptr;
PTRBFELT hdreptr;
CHAR numelts;
CHAR msgtype;
CHAR srcl;
CHAR srcp;
INTEGER srci;
CHAR destl;
CHAR destp;
INTEGER desti;
CHAR sfhdr;stctlhdr;ctlstat;
CHAR sfhdr;stctlhdr;ctlqual;
CHAR sfhdr;stctlthdr;ctltype
CHAR sfhdr;stctlhdr;ctlack;
CHAR sfhdr;stctlhdr;ctlflag1;
CHAR sfhdr;stctlhdr;ctlflag2;
INTEGER sfhdr;stctlhdr;ctlnumb1;
INTEGER sfhdr;stctlhdr;ctlnumb2;
INTEGER sfhdr;stctlhdr;ctlmsgk;
};
LUA only (see Remarks):
Element
struct Status-Control(...) Negative-Acknowledge-1 {
PTRBFELT hdreptr->elteptr;
INTEGER hdreptr->startd;
INTEGER hdreptr->endd;
CHAR hdreptr->trpad;
CHAR[268] hdreptr->dataru;
};
Members
-
nxtqptr
-
Pointer to next buffer header.
-
hdreptr
-
Pointer to buffer element (NIL if not using LUA).
-
numelts
-
Number of buffer elements (0x00 if not using LUA).
-
msgtype
-
Message type STATFMI (0x21).
-
srcl
-
Source locality.
-
srcp
-
Source partner.
-
srci
-
Source index.
-
destl
-
Destination locality.
-
destp
-
Destination partner.
-
desti
-
Destination index.
-
sfhdr.stctlhdr.ctlstat
-
Status type STCNTRL (0x02).
-
sfhdr.stctlhdr.ctlqual
-
Control qualifier ACKNEG1 (0x03).
-
sfhdr.stctlhdr.ctltype
-
Control type.
-
sfhdr.stctlhdr.ctlack
-
Reserved.
-
sfhdr.stctlhdr.ctlflag1
-
Application flag 1.
-
sfhdr.stctlhdr.ctlflag2
-
Application flag 2.
-
sfhdr.stctlhdr.ctlnumb1
-
Sense code 1.
-
sfhdr.stctlhdr.ctlnumb2
-
Sense code 2.
-
sfhdr.stctlhdr.ctlmsgk
-
Message key.
LUA only (see Remarks):
Element
-
hdreptr–>elteptr
-
Pointer to buffer element (NIL).
-
hdreptr–>startd
-
Start of data in this buffer element
13 or
10 for second and subsequent segments of outbound segmented RUs
-
hdreptr–>endd
-
End of data in this buffer element.
-
hdreptr–>trpad
-
Reserved.
-
hdreptr–>dataru
-
Data RU.
Remarks
-
If the application is using the LUA variant of the FMI (see FMI Concepts), the TH, RH, and RU are included in the data element, and the startd field points to the TH. The ctlflag1 and ctlflag2 bytes are not defined and should not be used; the appropriate values from the data should be used instead.
-
If the application is not using the LUA variant of the FMI, the message consists of a buffer header only; there is no buffer element.
-
See the table in Status-Control Message for a summary of Status-Control control type codes.
-
For messages from the application to the local node, the message key field must match the message key in the corresponding Status-Control request.