| $$CM |
Output |
Calling $$CM^HLUCM(SDT,EDT,NMSP,PROT,SAVE,COND,ERR)
returns a 3 piece string of data. The pieces of data are:
Piece 1 = Number of characters in all messages found by the API call.
Piece 2 = Number of messages found by the API call.
Piece 3 = Total transmission and receipt time for all messages
found by API call.
Calling $$CM^HLUCM returns this 3 piece string of data. In addition, when the
API is called, it creates some ^TMP global data holding additional information
about the messages found. Full information about the global created can be
found in the patch HL*1.6*103 documentation. However, a brief overview of the
data structure is provided below.
The fifth parameter passed into the $$CM^HLUCM API is SAVE. This parameter
specifies the initial subscript to be used in the ^TMP global data. (See the
SAVE variable for more information.) For example, if the save parameter is
passed as "DATA", the ^TMP global data is stored in ^TMP("DATA",$J,...).
The ^TMP global data created by the $$CM^HLUCM call point is subdivided (by
sorting subscripts) into the following sections:
Totals by transmission time, namespace, and protocol.
Totals by namespace, incoming/outgoing, namespace, transmission
time, and protocol.
Totals by namepsace, local/remote, namespace, transmission
time, and protocol.
Totals by protocol, namespace, and time.
To explain the above information more fully, consider the last entry. What
this means is that totals are sorted by protocol, and within protocol the
totals are sorted by namespace, and within namespace the totals are sorted by
transmission time.
Example data, and additional explanation of the global data created by the API
is in patch HL*1.6*103.
|
SDT (parameter 1) |
Input |
The syntax for the $$CM call point is:
$$CM(SDT,EDT,NMSP,PROT,SAVE,COND,ERR)
The first parameter, SDT, is the start time in Fileman format. An example
call is shown below.
W $$CM^HLUCM(3011123.12,3011123.13,"DG","VAFH A08","DATA","BOTH",.ERR)
In this example, SDT has the value of 3011123.12.
|
EDT (parameter 2) |
Input |
The syntax for the $$CM call point is:
$$CM(SDT,EDT,NMSP,PROT,SAVE,COND,ERR)
The second parameter, EDT, is the end time in Fileman format. An example call
is shown below.
W $$CM^HLUCM(3011123.12,3011123.13,"DG","VAFH A08","DATA","BOTH",.ERR)
In this example, EDT has the value of 3011123.13.
|
NMSP (parameter 3) |
Input |
The syntax for the $$CM call point is:
$$CM(SDT,EDT,NMSP,PROT,SAVE,COND,ERR)
The third parameter, NMSP, is the NAMESPACE of the entry(s) to be included.
An example call is shown below.
W $$CM^HLUCM(3011123.12,3011123.13,"DG","VAFH A08","DATA","BOTH",.ERR)
In this example, NMSP has the value of "DG".
See patch HL*1.6*103 documentation for additional details.
|
PROT (parameter 4) |
Input |
The syntax for the $$CM call point is:
$$CM(SDT,EDT,NMSP,PROT,SAVE,COND,ERR)
The fourth parameter, PROT, is the PROTOCOL of the entry(s) to be included.
An example call is shown below.
W $$CM^HLUCM(3011123.12,3011123.13,"DG","VAFH A08","DATA","BOTH",.ERR)
In this example, PROT has the value of "VAFH A08".
See patch HL*1.6*103 documentation for additional details.
|
SAVE (parameter 5) |
Input |
The syntax for the $$CM call point is:
$$CM(SDT,EDT,NMSP,PROT,SAVE,COND,ERR)
The fifth parameter, SAVE, is the initial subscript to use in the ^TMP global
data. An example call is shown below.
W $$CM^HLUCM(3011123.12,3011123.13,"DG","VAFH A08","DATA","BOTH",.ERR)
In this example, SAVE has the value of "DATA". This would cause the Creation
of ^TMP("DATA",$J) data.
|
COND (parameter 6) |
Input |
The syntax for the $$CM call point is:
$$CM(SDT,EDT,NMSP,PROT,SAVE,COND,ERR)
The sixth parameter, COND, defines criteria to be used when searching For
messages. An example call is shown below.
W $$CM^HLUCM(3011123.12,3011123.13,"DG","VAFH A08","DATA","BOTH",.ERR)
In this example, COND has the value of "BOTH". Passing the value of "BOTH"
requires that each message has to have a namespace of "DG" and a protocol of
"VAFH A08." In other words, 'both' the namespace and the protocol values have
to be true before a message is counted.
Instead of "BOTH", the value of "EITHER" can be passed. In the above Example,
if "EITHER" had been passed as the value of COND, then Messages will be
counted if 'either' the namespace is "DG" or the Protocol is "VAFH A08." In
other words, if either criteria is Matched, a message is counted.
See patch HL*1.6*103 documentation for addition information.
|
ERR (parameter 7) |
Output |
The syntax for the $$CM call point is:
$$CM(SDT,EDT,NMSP,PROT,SAVE,COND,ERR)
The sixth parameter, COND, defines criteria to be used when searching For
messages. An example call is shown below.
W $$CM^HLUCM(3011123.12,3011123.13,"DG","VAFH A08","DATA","BOTH",.ERR)
In this example, ERR is passed by reference. No data is present in The ERR
array prior to the call, (and even if it did, the ERR local Array is killed as
one of the initial API actions, in order to ensure That the ERR array is empty
at the start of processing.) If any Problems are encountered by the API, such
as passing in invalid Parameter values, information about the error(s) is
placed in the ERR local array and "passed back" to the calling process.
See patch HL*1.6*103 documentation for addition information.
|