SirScan: Difference between revisions
m (→Overview) |
m (→Overview) |
||
| Line 3: | Line 3: | ||
SirScan permits ordinary users to view journal entries generated by their own online session, and it allows users in ADMIN SCLASSes to browse journal entries for any set of users. The data is displayed in a full-screen browser with powerful searching commands and filtering options. | SirScan permits ordinary users to view journal entries generated by their own online session, and it allows users in ADMIN SCLASSes to browse journal entries for any set of users. The data is displayed in a full-screen browser with powerful searching commands and filtering options. | ||
SirScan is part of the [[ULSPF | UL/SPF]] family of products from [[Sirius Software]]. As with all UL/SPF products, SirScan requires the installation of the [[Sirius Mods]], with a version equal to or higher than the SirScan version. | SirScan is part of the [[ULSPF | UL/SPF]] family of products from [[Sirius Software]]. As with all UL/SPF products, <var class="product">SirScan</var> requires the installation of the [[Sirius Mods]], with a version equal to or higher than the <var class="product">SirScan</var> version. | ||
==Overview== | ==Overview== | ||
| Line 11: | Line 11: | ||
selecting and formatting journal entries. These are caused by the fact that journal | selecting and formatting journal entries. These are caused by the fact that journal | ||
records contain only a user number and do not contain other potentially useful identifying | records contain only a user number and do not contain other potentially useful identifying | ||
information, such as userid, terminal ID, or IP address. So when SirScan scan | information, such as userid, terminal ID, or IP address. So when <var class="product">SirScan</var> scan | ||
specifications in the SIRSCAN subsystem are based on things like userid, IP address, or | specifications in the SIRSCAN subsystem are based on things like userid, IP address, or | ||
port name, there is often no way to determine whether a single journal entry is | port name, there is often no way to determine whether a single journal entry is | ||
| Line 18: | Line 18: | ||
In fact, before Sirius Mods version 6.0, selection criteria based on userid would only | In fact, before Sirius Mods version 6.0, selection criteria based on userid would only | ||
work for currently logged on threads, and then only for journal entries from the current | work for currently logged on threads, and then only for journal entries from the current | ||
session. This is because, for logged in users, SirScan can determine user number and | session. This is because, for logged in users, <var class="product">SirScan</var> can determine user number and | ||
login time. From these two pieces of information, it can be sure that all journal entries | login time. From these two pieces of information, it can be sure that all journal entries | ||
for the thread associated with a requested userid, and with a date/time stamp after the | for the thread associated with a requested userid, and with a date/time stamp after the | ||
| Line 24: | Line 24: | ||
Outside of being very limiting — it was impossible to select journal info based on userid | Outside of being very limiting — it was impossible to select journal info based on userid | ||
for non-logged in users — SirScan could also produce anomalous behavior in autorefresh | for non-logged in users — <var class="product">SirScan</var> could also produce anomalous behavior in autorefresh | ||
mode (“Auto-refresh mode” on page 20). Because SirScan only collects data | mode (“Auto-refresh mode” on page 20). Because <var class="product">SirScan</var> only collects data | ||
from the previous end of the interval when in auto-refresh mode, if a userid present and | from the previous end of the interval when in auto-refresh mode, if a userid present and | ||
selected in a previous interval logged off before the data is refreshed for the new | selected in a previous interval logged off before the data is refreshed for the new | ||
interval, none of the journal records for that user would appear between the end of the | interval, none of the journal records for that user would appear between the end of the | ||
previous interval and the end of the current. Outside of the annoyance of not seeing the | previous interval and the end of the current. Outside of the annoyance of not seeing the | ||
expected data, this could cause confusion among SirScan end-users, because a user's | expected data, this could cause confusion among <var class="product">SirScan</var> end-users, because a user's | ||
journal entries might seem to suddenly stop without a logoff record or any other hint as | journal entries might seem to suddenly stop without a logoff record or any other hint as | ||
to why. | to why. | ||
In Sirius Mods 6.0 and later, SirScan makes more of an effort to use whatever | In Sirius Mods 6.0 and later, <var class="product">SirScan</var> makes more of an effort to use whatever | ||
information is available in the journal to associate journal records with userids or other | information is available in the journal to associate journal records with userids or other | ||
attributes not actually on the journal records. For example, if SirScan sees a M204.0352 | attributes not actually on the journal records. For example, if <var class="product">SirScan</var> sees a M204.0352 | ||
message for a login, it knows that from that time on all journal records for that thread | message for a login, it knows that from that time on all journal records for that thread | ||
number are associated with the userid on the M204.0352 message, until the end of the | number are associated with the userid on the M204.0352 message, until the end of the | ||
interval or a M204.0352 logout message is reached for that thread. | interval or a M204.0352 logout message is reached for that thread. | ||
In a similar way, SirScan can use the MSIR.0114 message, which indicates a Janus port | In a similar way, <var class="product">SirScan</var> can use the MSIR.0114 message, which indicates a Janus port | ||
and client IP address for any Janus server request, to associate a thread number with an | and client IP address for any Janus server request, to associate a thread number with an | ||
IP address and port name. Unfortunately, while this approach makes it possible to use | IP address and port name. Unfortunately, while this approach makes it possible to use | ||
| Line 50: | Line 50: | ||
===Historical journals=== | ===Historical journals=== | ||
As of SirScan Version 7.7 and Sirius Mods 7.8, SirScan can be used to view either the journal for the current online, or the journal file for another online if it is allocated to the current online as a sequential file. | As of <var class="product">SirScan</var> Version 7.7 and Sirius Mods 7.8, <var class="product">SirScan</var> can be used to view either the journal for the current online, or the journal file for another online if it is allocated to the current online as a sequential file. | ||
==See also== | ==See also== | ||
All Sirius <var class="product">UL/SPF</var> documentation is a available for download in PDF format at http://sirius-software.com/maint/manlist | All Sirius <var class="product">UL/SPF</var> documentation is a available for download in PDF format at http://sirius-software.com/maint/manlist | ||
Revision as of 23:22, 29 October 2012
SirScan is a high performance utility that allows users in a Model 204 online to browse the contents of its journal in real time.
SirScan permits ordinary users to view journal entries generated by their own online session, and it allows users in ADMIN SCLASSes to browse journal entries for any set of users. The data is displayed in a full-screen browser with powerful searching commands and filtering options.
SirScan is part of the UL/SPF family of products from Sirius Software. As with all UL/SPF products, SirScan requires the installation of the Sirius Mods, with a version equal to or higher than the SirScan version.
Overview
The installation of the Sirius Mods is required and sufficient to install and run the SIRSCAN subsystem. However, out of the wrapper, SIRSCAN has some limitations in selecting and formatting journal entries. These are caused by the fact that journal records contain only a user number and do not contain other potentially useful identifying information, such as userid, terminal ID, or IP address. So when SirScan scan specifications in the SIRSCAN subsystem are based on things like userid, IP address, or port name, there is often no way to determine whether a single journal entry is associated with the requested attributes or not.
In fact, before Sirius Mods version 6.0, selection criteria based on userid would only work for currently logged on threads, and then only for journal entries from the current session. This is because, for logged in users, SirScan can determine user number and login time. From these two pieces of information, it can be sure that all journal entries for the thread associated with a requested userid, and with a date/time stamp after the login time of the user, are associated with that user.
Outside of being very limiting — it was impossible to select journal info based on userid for non-logged in users — SirScan could also produce anomalous behavior in autorefresh mode (“Auto-refresh mode” on page 20). Because SirScan only collects data from the previous end of the interval when in auto-refresh mode, if a userid present and selected in a previous interval logged off before the data is refreshed for the new interval, none of the journal records for that user would appear between the end of the previous interval and the end of the current. Outside of the annoyance of not seeing the expected data, this could cause confusion among SirScan end-users, because a user's journal entries might seem to suddenly stop without a logoff record or any other hint as to why.
In Sirius Mods 6.0 and later, SirScan makes more of an effort to use whatever information is available in the journal to associate journal records with userids or other attributes not actually on the journal records. For example, if SirScan sees a M204.0352 message for a login, it knows that from that time on all journal records for that thread number are associated with the userid on the M204.0352 message, until the end of the interval or a M204.0352 logout message is reached for that thread.
In a similar way, SirScan can use the MSIR.0114 message, which indicates a Janus port and client IP address for any Janus server request, to associate a thread number with an IP address and port name. Unfortunately, while this approach makes it possible to use non-thread-number and non-thread-type based selection criteria for sessions that are no longer active, it also makes SirScan's behavior even more anomalous and confusing, because whether or not a journal record is selected might depend on whether or not SirScan happened to see an identifying message in the journal for that thread.
Historical journals
As of SirScan Version 7.7 and Sirius Mods 7.8, SirScan can be used to view either the journal for the current online, or the journal file for another online if it is allocated to the current online as a sequential file.
See also
All Sirius UL/SPF documentation is a available for download in PDF format at http://sirius-software.com/maint/manlist