CT Center Documentation > Reference Manual Menu
While the Interactive IO program is operating, CT Center and Cubs are carrying on a robust, real-time conversation transferring data and messages back and forth. The IO Log Query provides an audit trail to this on-going conversation. This screen will typically be used by CCI personnel as a troubleshooting tool.
|
||
|
IAT Dialer Interactive IO Log
Page 3 of 25 |
|
Day/Time Logon Dir MsgType
Ref#
Message
|
||
2 14:16:36 CCI
CTD Reject
193146888 1885223 |
||
2 14:16:36 CCI
DTC Qualify
193146888 1885223 |
||
2 14:16:35 CCI
DTC Update
193146888 1885223; NO_ANSWER |
||
2 14:16:25 CCI
CTD Submit
193146888 1940480
|
||
2 14:16:25 CCI
DTC ReqByList 193146888 CF35
|
||
2 14:16:25 CCI
DTC Update
193146888 1947693; NO_ANSWER |
||
2 14:16:24 CCI
CTD Accept
193146888 1947693
|
||
2 14:16:24 CCI
DTC Qualify
193146888 1947693 |
||
2 14:16:21 CCI
CTD Submit
193146888 1941562 |
||
2 14:16:21 CCI
DTC ReqByList 193146888 CF35 |
||
2 14:16:21 CCI
DTC Update
192487432 1945202; ANS_MACH_LMTC |
||
2 14:16:21 CCI
CTD Reject
193146888 1939346 |
||
2 14:16:21 CCI
DTC Qualify
193146888 1939346 |
||
2 14:16:21 CCI
DTC Update
193146888 1939346; NO_ANSWER |
||
2 14:16:20 CCI
CTD Reject
193146888 1473734 |
||
2 14:16:20 CCI
DTC Qualify
193146888 1473734 |
||
2 14:16:20 CCI
CTD Submit
192487432 1818920 |
||
2 14:16:20 CCI
DTC ReqByList 192487432 CF34 |
||
2 14:16:20 CCI
DTC Update
193146888 1813457; TRANSFER_TO_OPERATOR |
||
2 14:16:15 CCI
CTD Reject
192487432 1445779 |
||
|
||
(B)ack, (F)irst, (N)ext, (L)ast, (S)earch, (R)efresh, e(X)it: |
||
|
Day/Time: Typically, the interactive conversation is so active that in the rolling 500 line window of activity, only a few minutes have elapsed. For that reason, the date doesn’t change unless crossing the midnight hour. That’s why we don’t bother taking up space with the month or year. Only the day of the month is shown.
Logon: If there are multiple logons using the CT Center dialer, they all feed into the same IO Log. Therefore we show the logon for each transaction line.
Dir: There are 2 possible directions for the flow of data, Dialer-To-Cubs (DTC) or Cubs-To-Dialer (CTD).
MsgType: There are many types of messages which pass between the Cubs interface and the dialer. Their names, as displayed here, are descriptive.
Ref#: The reference number originates on the dialer side of the conversation and is attached to requests and updates. Responses from Cubs include the same reference number as the original request which allows the dialer to sort out responses when multiple requests are pending. The dialer is programmed to re-use a reference number after the previous request/response for that reference number has gone round trip.
Message: The format of the message field varies, depending upon the message type. In many cases it includes the Cubs debtor account number. For some other message types, it may include a list name.
B: Back a page. Used if this is not the first page.
F: Move to the first page.
N: Next page. Used if this is not the last page.
L: Move to the last page.
S: Entering “S” causes another prompt to display, “Enter search text”. Enter any text that you want to locate in any of the data columns. The program will search for the first occurrence of that text starting with the next page. The next time that you enter “S”, your previous search text will be the default value, so you can simply key {Enter} to look for the next page that has that same text.
The search feature is very helpful if, for example, you want to focus on transactions only about a specific campaign. You would enter the campaign name as the search text and be able to skip pages which don’t contain any records for that campaign.
R: During the time that you’ve been looking at the IO Log, it has been moving. Use the “R” option to load the more current accumulation of data.
X: Exit from the IO Log query screen, returning to the menu.
Copyright 2012, Cubs Consulting, Inc.