SirScan: Difference between revisions

Latest revision as of 22:13, 6 June 2017

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 SIRSCAN subsystem ADMIN SCLASSes to browse journal entries for any set of users. The data is displayed in a TN3270 full-screen or web browser interface (RKWeb) with powerful searching commands and filtering options.

SirScan lets you view either:

The journal for the current Online
The journal for another Online allocated to the current Online as a sequential file.

SirScan is part of the RKTools family of products. As with all RKTools products, SirScan formerly required the installation of the Sirius Mods, with a version equal to or higher than the SirScan version. As of Model 204 V7.5, however, the functions and facilities necessary to run RKTools are built into the Model 204 kernel.

SirScan topics

The SirScan documentation consists of the pages listed below. This list is also available as a "See also" link from each of the pages.

For information about product changes and Model 204 feature support per SirScan version, see the release notes.

For information about product error messages, see MSIR. messages.

@@ Line 1: / Line 1: @@
-'''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''' is a high performance utility that allows users in a <var class="product">[[Model 204]]</var> Online to browse the contents of its [[Tracking system activity (CCAJRNL, CCAAUDIT, CCAJLOG)#Overview of the journal data sets|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.
+<var class="product">SirScan</var> permits ordinary users to view journal entries generated by their own online session, and it allows users in
+[[Application_Subsystem_development#User_class|SIRSCAN subsystem ADMIN SCLASSes]] to browse journal entries for any set of users. The data is displayed in a TN3270 full-screen or web browser interface (RKWeb) 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, <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.
+<var class="product">SirScan</var> lets you view either:
+<ul>
+<li>The journal for the current Online</li>
+<li>The journal for another Online allocated to the current Online as a sequential file. </li>
+</ul>
-==Overview==
+<var class="product">SirScan</var> is part of the <var class="product">[[RKTools]]</var> family of products. As with all <var class="product">RKTools</var> products, <var class="product">SirScan</var> formerly required the installation of the <var class="product">Sirius Mods</var>, with a version equal to or higher than the <var class="product">SirScan</var> version. As of Model&nbsp;204 V7.5, however, the functions and facilities necessary to run RKTools are built into the Model&nbsp;204 kernel.
-The installation of the <var class="product">Sirius Mods</var> is required and sufficient to install and run the
+==SirScan topics==
-SIRSCAN subsystem. However, out of the wrapper, SIRSCAN has some limitations in
+The <var class="product">SirScan</var> documentation consists of the pages listed below.
-selecting and formatting journal entries. These are caused by the fact that journal
+This list is also available as a "See also" link from each of the pages.
-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 <var class="product">SirScan</var> 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 <var class="product">Sirius Mods</var> version 6.0, selection criteria based on userid would only
+For information about product changes and Model&nbsp;204 feature
-work for currently logged on threads, and then only for journal entries from the current
+support per <var class="product">SirScan</var> version, see
-session. This is because, for logged in users, <var class="product">SirScan</var> can determine user number and
+the [[M204wiki main page#rktools_notes|release notes]].
-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 information about product error messages, see [[List of Model 204 messages#msir|MSIR. messages]].
-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 <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
-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 <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
-to why.
-In <var class="product">Sirius Mods</var> 6.0 and later, <var class="product">SirScan</var> makes more of an effort to use whatever
+{{Template: SirScan topic list}}
-information is available in the journal to associate journal records with userids or other
-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
-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, <var class="product">SirScan</var> can use the MSIR.0114 message, which indicates a Janus port
+==See also==
-and client IP address for any Janus server request, to associate a thread number with an
+<ul>
-IP address and port name. Unfortunately, while this approach makes it possible to use
+<li>[[SoulEdit |SoulEdit (The SOUL Editor)]] </li>
-non-thread-number and non-thread-type based selection criteria for sessions that are no
+<li>[[Terminal MODEL 6 support]] </li>
-longer active, it also makes <var class="product">SirScan</var>'s behavior even more anomalous and confusing,
+</ul>
-because whether or not a journal record is selected might depend on whether or not
-<var class="product">SirScan</var> happened to see an identifying message in the journal for that thread.
-===Historical journals===
-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==
+[[Category:RKTools]]
-All Sirius <var class="product">UL/SPF</var> documentation is a available for download in PDF format at http://sirius-software.com/maint/manlist
+[[Category:SirScan]]

SirScan: Difference between revisions

Latest revision as of 22:13, 6 June 2017

SirScan topics

See also

Navigation menu