https://m204wiki.rocketsoftware.com/api.php?action=feedcontributions&feedformat=atom&user=Mmarshallm204wiki - User contributions [en]2026-05-05T07:16:22ZUser contributionsMediaWiki 1.43.1https://m204wiki.rocketsoftware.com/index.php?title=Release_notes_for_SirScan_V7.5&diff=78328Release notes for SirScan V7.52015-07-21T01:39:47Z<p>Mmarshall: </p>
<hr />
<div>This document lists the changes that have been made for <var class="product">SirScan</var> version S7.5. It requires <var class="product">Model 204</var> release 7.5 or higher.<br />
<br />
== Scan Select Screen (SCANSEL) ==<br />
<br />
=== Field changes ===<br />
<br />
==== Layout changes====<br />
Prompts '==>' replaced by ':' <br />
<br />
==== Functionality changes====<br />
<br />
* The <b>Start time (HH:MM:SS)</b> field will now accept periods(.) as seperators (which means that the valid formats for this field are HH:MM:SS, HH.MM.SS or HHMMSS)<br />
<br />
* The <b>Max I/O's.:</b> and <b>Max records:</b> fields have been changed to recognize, reset and report the situation where the values entered are greater than the maximum allowable. The maximum allowable values, for the <b>Max I/O's.:</b> and <b>Max records:</b> fields, can be viewed and/or set using the SirAdmin apsy (within the <b>SirScan SCLASS settings</b> option). If the <b>Max I/O's.:</b> and/or <b>Max records:</b> values, entered on the SCANSEL screen, exceed those recorded in SirAdmin, then the values will be automatically reset to the maximum allowable and an informational message will be displayed on the 'message line' (2nd bottom line of the screen).<br />
<br />
==== New field Bookmarks ====<br />
<br />
Bookmarks are a new feature. When turned on (value "Y"), a bookmark line will<br />
be created in the display on the SCANLIST page for each successive scan request. <br />
Note that bookmarks are only active if the Interval (Minutes) field is left blank.<br />
The line looks like:<br />
<br />
<p class="code">______________________________________________________ BookMark 4: 19:59:37.23 - 19:59:58.90<br />
</p><br />
<br />
It shows the bookmark number and the time range for that scan. The bookmarks <br />
are sequentially numbered and the message line at the bottom of the screen shows<br />
the lasted bookmark id, for example:<br />
<br />
<p class="code">--------------------------------------------------------------------- -- Latest Bookmark: 4<br />
</p><br />
<br />
Bookmarks are saved for the session. Hence if SirScan is exited and re-entered<br />
during the same session, the previous bookmarks are retained and can be<br />
re-displayed. The new bookmark id's will follow on from the last one previously<br />
created. This provides an alternative to noting down the time of a scan in<br />
cases where the information needs to be re-displayed. Also it is possible to<br />
change the Display and Format Entry Types on this screen and re-display the<br />
journal lines for a previous bookmark period.<br />
<br />
See xxx for more details.<br />
<br />
==Scan List Screen (SCANLIST)==<br />
<br />
=== Field changes ===<br />
==== New Command .[BookmarkId] ====<br />
A command in format .[BookmarkId] will navigate direct to that bookmark, e.g. <br />
<br />
<p class="code">.22</p><br />
<br />
A command with the BookmarkID will navigate to the latest bookmark.<br />
<br />
=== Screen display changes ===<br />
<br />
==== Bookmark Lines ====<br />
<br />
As notes in xxx if the Bookmark setting is turn on "Y", and additional line<br />
is displayed separating each bookmark scan period. The current (active) bookmark<br />
is shown in green whilst old bookmarks are shown in red.<br />
<br />
=== Function Keys ===<br />
<br />
==== PF5/PF6 - Previous/Next Bookmark (or refresh) ==== <br />
If the Interval (Minutes) field in the SCANSEL screen is left blank, then PF5 will<br />
navigate to the previous bookmark and PF6 to the next bookmark, or create a new one <br />
if already on the last bookmark. Hence the sequence is:<br />
<br />
old bookmarks <=> latest bookmark <=> refresh page (i.e. the next bookmark). <br />
<br />
The scan listing for the old bookmarks is “frozen”, e.g. pressing enter or “bottom”<br />
will not add to the listing and only the scan lines for that bookmark are shown.<br />
<br />
However the latest bookmark listing can be added to with fresh scans. Bookmarks on this page listing are shown in green. If you return to the latest bookmark, only the lines for that bookmark are shown – any others previously on the listing become old bookmarks that you can use PF5 to display. Note that pressing PF5 from the latest bookmark page will take you to the bookmark one less than the latest bookmark, even if the display has a number of earlier bookmarks that have accumulated on the page.<br />
<br />
Note that PF6 can be used to refresh the listing page so it is ready for new journal lines (if already on the latest bookmark). This is equivalent to pressing PF3, keying Start Time -0 and then Enter.<br />
<br />
==== PF7/PF8 - line scrolling ====<br />
The scrolling has been enhanced to scroll based on the position of the<br />
cursor when the cursor is in the listing area. If PF8 is pressed then the page scrolls<br />
so the line under the cursor becomes the top line. If PF7 is pressed the the line under<br />
the cursor becomes the bottom line. The cursor is reset to the Command field so <br />
subsequent scrolling will be for full pages.</div>Mmarshallhttps://m204wiki.rocketsoftware.com/index.php?title=Release_notes_for_SirScan_V7.5&diff=78327Release notes for SirScan V7.52015-07-21T01:34:54Z<p>Mmarshall: </p>
<hr />
<div>This document lists the changes that have been made for <var class="product">SirScan</var> version S7.5. It requires <var class="product">Model 204</var> release 7.5 or higher.<br />
<br />
== Scan Select Screen (SCANSEL) ==<br />
<br />
=== Field changes ===<br />
<br />
==== Layout changes====<br />
Prompts '==>' replaced by ':' <br />
<br />
==== Functionality changes====<br />
<br />
* The <b>Start time (HH:MM:SS)</b> field will now accept periods(.) as seperators.<br />
<br />
* The <b>Max I/O's.:</b> and <b>Max records:</b> fields have been changed to recognize, reset and report the situation where the values entered are greater than the maximum allowable. The maximum allowable values, for the <b>Max I/O's.:</b> and <b>Max records:</b> fields, can be viewed and/or set using the SirAdmin apsy (from the <b>SirScan SCLASS settings</b> option). If the <b>Max I/O's.:</b> and <b>Max records:</b> values, entered on the SirScan screen, exceed those recorded in SirAdmin, then the values will be automatically reset to the maximum allowable and an informational message will be displayed on the 'message line' (2nd bottom line of the screen).<br />
<br />
==== New field Bookmarks ====<br />
<br />
Bookmarks are a new feature. When turned on (value "Y"), a bookmark line will<br />
be created in the display on the SCANLIST page for each successive scan request. <br />
Note that bookmarks are only active if the Interval (Minutes) field is left blank.<br />
The line looks like:<br />
<br />
<p class="code">______________________________________________________ BookMark 4: 19:59:37.23 - 19:59:58.90<br />
</p><br />
<br />
It shows the bookmark number and the time range for that scan. The bookmarks <br />
are sequentially numbered and the message line at the bottom of the screen shows<br />
the lasted bookmark id, for example:<br />
<br />
<p class="code">--------------------------------------------------------------------- -- Latest Bookmark: 4<br />
</p><br />
<br />
Bookmarks are saved for the session. Hence if SirScan is exited and re-entered<br />
during the same session, the previous bookmarks are retained and can be<br />
re-displayed. The new bookmark id's will follow on from the last one previously<br />
created. This provides an alternative to noting down the time of a scan in<br />
cases where the information needs to be re-displayed. Also it is possible to<br />
change the Display and Format Entry Types on this screen and re-display the<br />
journal lines for a previous bookmark period.<br />
<br />
See xxx for more details.<br />
<br />
==Scan List Screen (SCANLIST)==<br />
<br />
=== Field changes ===<br />
==== New Command .[BookmarkId] ====<br />
A command in format .[BookmarkId] will navigate direct to that bookmark, e.g. <br />
<br />
<p class="code">.22</p><br />
<br />
A command with the BookmarkID will navigate to the latest bookmark.<br />
<br />
=== Screen display changes ===<br />
<br />
==== Bookmark Lines ====<br />
<br />
As notes in xxx if the Bookmark setting is turn on "Y", and additional line<br />
is displayed separating each bookmark scan period. The current (active) bookmark<br />
is shown in green whilst old bookmarks are shown in red.<br />
<br />
=== Function Keys ===<br />
<br />
==== PF5/PF6 - Previous/Next Bookmark (or refresh) ==== <br />
If the Interval (Minutes) field in the SCANSEL screen is left blank, then PF5 will<br />
navigate to the previous bookmark and PF6 to the next bookmark, or create a new one <br />
if already on the last bookmark. Hence the sequence is:<br />
<br />
old bookmarks <=> latest bookmark <=> refresh page (i.e. the next bookmark). <br />
<br />
The scan listing for the old bookmarks is “frozen”, e.g. pressing enter or “bottom”<br />
will not add to the listing and only the scan lines for that bookmark are shown.<br />
<br />
However the latest bookmark listing can be added to with fresh scans. Bookmarks on this page listing are shown in green. If you return to the latest bookmark, only the lines for that bookmark are shown – any others previously on the listing become old bookmarks that you can use PF5 to display. Note that pressing PF5 from the latest bookmark page will take you to the bookmark one less than the latest bookmark, even if the display has a number of earlier bookmarks that have accumulated on the page.<br />
<br />
Note that PF6 can be used to refresh the listing page so it is ready for new journal lines (if already on the latest bookmark). This is equivalent to pressing PF3, keying Start Time -0 and then Enter.<br />
<br />
==== PF7/PF8 - line scrolling ====<br />
The scrolling has been enhanced to scroll based on the position of the<br />
cursor when the cursor is in the listing area. If PF8 is pressed then the page scrolls<br />
so the line under the cursor becomes the top line. If PF7 is pressed the the line under<br />
the cursor becomes the bottom line. The cursor is reset to the Command field so <br />
subsequent scrolling will be for full pages.</div>Mmarshallhttps://m204wiki.rocketsoftware.com/index.php?title=Release_notes_for_SirScan_V7.5&diff=78326Release notes for SirScan V7.52015-07-21T01:32:43Z<p>Mmarshall: </p>
<hr />
<div>This document lists the changes that have been made for <var class="product">SirScan</var> version S7.5. It requires <var class="product">Model 204</var> release 7.5 or higher.<br />
<br />
== Scan Select Screen (SCANSEL) ==<br />
<br />
=== Field changes ===<br />
<br />
==== Layout changes====<br />
Prompts '==>' replaced by ':' <br />
<br />
==== Functionality changes====<br />
<br />
* The <b>Start time (HH:MM:SS)</b> field will now accept periods(.) as seperators.<br />
<br />
* The <b>Max I/O's.:</b> and <b>Max records:</b> fields have been changed to recognize, reset and report the situation where the values entered are greater than the maximum allowable. The maximum allowable values, for the <b>Max I/O's.:</b> and <b>Max records:</b> fields, can be viewed and/or set using the SirAdmin apsy, <b>SirScan SCLASS settings</b> option. If the <b>Max I/O's.:</b> and <b>Max records:</b> values, entered on the SirScan screen, exceed those recorded in SirAdmin, then the values will be automatically reset to the maximum allowable and an informational message will be displayed on the 'message line' (2nd bottom line of the screen).<br />
<br />
==== New field Bookmarks ====<br />
<br />
Bookmarks are a new feature. When turned on (value "Y"), a bookmark line will<br />
be created in the display on the SCANLIST page for each successive scan request. <br />
Note that bookmarks are only active if the Interval (Minutes) field is left blank.<br />
The line looks like:<br />
<br />
<p class="code">______________________________________________________ BookMark 4: 19:59:37.23 - 19:59:58.90<br />
</p><br />
<br />
It shows the bookmark number and the time range for that scan. The bookmarks <br />
are sequentially numbered and the message line at the bottom of the screen shows<br />
the lasted bookmark id, for example:<br />
<br />
<p class="code">--------------------------------------------------------------------- -- Latest Bookmark: 4<br />
</p><br />
<br />
Bookmarks are saved for the session. Hence if SirScan is exited and re-entered<br />
during the same session, the previous bookmarks are retained and can be<br />
re-displayed. The new bookmark id's will follow on from the last one previously<br />
created. This provides an alternative to noting down the time of a scan in<br />
cases where the information needs to be re-displayed. Also it is possible to<br />
change the Display and Format Entry Types on this screen and re-display the<br />
journal lines for a previous bookmark period.<br />
<br />
See xxx for more details.<br />
<br />
==Scan List Screen (SCANLIST)==<br />
<br />
=== Field changes ===<br />
==== New Command .[BookmarkId] ====<br />
A command in format .[BookmarkId] will navigate direct to that bookmark, e.g. <br />
<br />
<p class="code">.22</p><br />
<br />
A command with the BookmarkID will navigate to the latest bookmark.<br />
<br />
=== Screen display changes ===<br />
<br />
==== Bookmark Lines ====<br />
<br />
As notes in xxx if the Bookmark setting is turn on "Y", and additional line<br />
is displayed separating each bookmark scan period. The current (active) bookmark<br />
is shown in green whilst old bookmarks are shown in red.<br />
<br />
=== Function Keys ===<br />
<br />
==== PF5/PF6 - Previous/Next Bookmark (or refresh) ==== <br />
If the Interval (Minutes) field in the SCANSEL screen is left blank, then PF5 will<br />
navigate to the previous bookmark and PF6 to the next bookmark, or create a new one <br />
if already on the last bookmark. Hence the sequence is:<br />
<br />
old bookmarks <=> latest bookmark <=> refresh page (i.e. the next bookmark). <br />
<br />
The scan listing for the old bookmarks is “frozen”, e.g. pressing enter or “bottom”<br />
will not add to the listing and only the scan lines for that bookmark are shown.<br />
<br />
However the latest bookmark listing can be added to with fresh scans. Bookmarks on this page listing are shown in green. If you return to the latest bookmark, only the lines for that bookmark are shown – any others previously on the listing become old bookmarks that you can use PF5 to display. Note that pressing PF5 from the latest bookmark page will take you to the bookmark one less than the latest bookmark, even if the display has a number of earlier bookmarks that have accumulated on the page.<br />
<br />
Note that PF6 can be used to refresh the listing page so it is ready for new journal lines (if already on the latest bookmark). This is equivalent to pressing PF3, keying Start Time -0 and then Enter.<br />
<br />
==== PF7/PF8 - line scrolling ====<br />
The scrolling has been enhanced to scroll based on the position of the<br />
cursor when the cursor is in the listing area. If PF8 is pressed then the page scrolls<br />
so the line under the cursor becomes the top line. If PF7 is pressed the the line under<br />
the cursor becomes the bottom line. The cursor is reset to the Command field so <br />
subsequent scrolling will be for full pages.</div>Mmarshallhttps://m204wiki.rocketsoftware.com/index.php?title=Release_notes_for_SirScan_V7.5&diff=78325Release notes for SirScan V7.52015-07-21T01:32:12Z<p>Mmarshall: </p>
<hr />
<div>This document lists the changes that have been made for <var class="product">SirScan</var> version S7.5. It requires <var class="product">Model 204</var> release 7.5 or higher.<br />
<br />
== Scan Select Screen (SCANSEL) ==<br />
<br />
=== Field changes ===<br />
<br />
==== Layout changes====<br />
Prompts '==>' replaced by ':' <br />
<br />
==== Functionality changes====<br />
<br />
* The <b>Start time (HH:MM:SS)</b> field will now accept periods(.) as seperators.<br />
<br />
* The <b>Max I/O's.:</b> and <b>Max records:</b> fields have been changed to recognize, reset and report the situation, when the values entered are greater than the maximum allowable. The maximum allowable values, for the <b>Max I/O's.:</b> and <b>Max records:</b> fields, can be viewed and/or set using the SirAdmin apsy, <b>SirScan SCLASS settings</b> option. If the <b>Max I/O's.:</b> and <b>Max records:</b> values, entered on the SirScan screen, exceed those recorded in SirAdmin, then the values will be automatically reset to the maximum allowable and an informational message will be displayed on the 'message line' (2nd bottom line of the screen).<br />
<br />
==== New field Bookmarks ====<br />
<br />
Bookmarks are a new feature. When turned on (value "Y"), a bookmark line will<br />
be created in the display on the SCANLIST page for each successive scan request. <br />
Note that bookmarks are only active if the Interval (Minutes) field is left blank.<br />
The line looks like:<br />
<br />
<p class="code">______________________________________________________ BookMark 4: 19:59:37.23 - 19:59:58.90<br />
</p><br />
<br />
It shows the bookmark number and the time range for that scan. The bookmarks <br />
are sequentially numbered and the message line at the bottom of the screen shows<br />
the lasted bookmark id, for example:<br />
<br />
<p class="code">--------------------------------------------------------------------- -- Latest Bookmark: 4<br />
</p><br />
<br />
Bookmarks are saved for the session. Hence if SirScan is exited and re-entered<br />
during the same session, the previous bookmarks are retained and can be<br />
re-displayed. The new bookmark id's will follow on from the last one previously<br />
created. This provides an alternative to noting down the time of a scan in<br />
cases where the information needs to be re-displayed. Also it is possible to<br />
change the Display and Format Entry Types on this screen and re-display the<br />
journal lines for a previous bookmark period.<br />
<br />
See xxx for more details.<br />
<br />
==Scan List Screen (SCANLIST)==<br />
<br />
=== Field changes ===<br />
==== New Command .[BookmarkId] ====<br />
A command in format .[BookmarkId] will navigate direct to that bookmark, e.g. <br />
<br />
<p class="code">.22</p><br />
<br />
A command with the BookmarkID will navigate to the latest bookmark.<br />
<br />
=== Screen display changes ===<br />
<br />
==== Bookmark Lines ====<br />
<br />
As notes in xxx if the Bookmark setting is turn on "Y", and additional line<br />
is displayed separating each bookmark scan period. The current (active) bookmark<br />
is shown in green whilst old bookmarks are shown in red.<br />
<br />
=== Function Keys ===<br />
<br />
==== PF5/PF6 - Previous/Next Bookmark (or refresh) ==== <br />
If the Interval (Minutes) field in the SCANSEL screen is left blank, then PF5 will<br />
navigate to the previous bookmark and PF6 to the next bookmark, or create a new one <br />
if already on the last bookmark. Hence the sequence is:<br />
<br />
old bookmarks <=> latest bookmark <=> refresh page (i.e. the next bookmark). <br />
<br />
The scan listing for the old bookmarks is “frozen”, e.g. pressing enter or “bottom”<br />
will not add to the listing and only the scan lines for that bookmark are shown.<br />
<br />
However the latest bookmark listing can be added to with fresh scans. Bookmarks on this page listing are shown in green. If you return to the latest bookmark, only the lines for that bookmark are shown – any others previously on the listing become old bookmarks that you can use PF5 to display. Note that pressing PF5 from the latest bookmark page will take you to the bookmark one less than the latest bookmark, even if the display has a number of earlier bookmarks that have accumulated on the page.<br />
<br />
Note that PF6 can be used to refresh the listing page so it is ready for new journal lines (if already on the latest bookmark). This is equivalent to pressing PF3, keying Start Time -0 and then Enter.<br />
<br />
==== PF7/PF8 - line scrolling ====<br />
The scrolling has been enhanced to scroll based on the position of the<br />
cursor when the cursor is in the listing area. If PF8 is pressed then the page scrolls<br />
so the line under the cursor becomes the top line. If PF7 is pressed the the line under<br />
the cursor becomes the bottom line. The cursor is reset to the Command field so <br />
subsequent scrolling will be for full pages.</div>Mmarshallhttps://m204wiki.rocketsoftware.com/index.php?title=Release_notes_for_SirScan_V7.5&diff=78324Release notes for SirScan V7.52015-07-21T01:31:21Z<p>Mmarshall: </p>
<hr />
<div>This document lists the changes that have been made for <var class="product">SirScan</var> version S7.5. It requires <var class="product">Model 204</var> release 7.5 or higher.<br />
<br />
== Scan Select Screen (SCANSEL) ==<br />
<br />
=== Field changes ===<br />
<br />
==== Layout changes====<br />
Prompts '==>' replaced by ':' <br />
<br />
==== Functionality changes====<br />
<br />
* The <b>Start time (HH:MM:SS)</b> field will now accept periods(.) as seperators.<br />
<br />
* The <b>Max I/O's.:</b> and <b>Max records:</b> fields have been changed to recognize, reset and report the situation, when the values entered are greater than the maximum allowable.<br />
The maximum allowable values, for the <b>Max I/O's.:</b> and <b>Max records:</b> fields, can be viewed and/or set using the SirAdmin apsy, <b>SirScan SCLASS settings</b> option.<br />
<br />
If the <b>Max I/O's.:</b> and <b>Max records:</b> values, entered on the SirScan screen, exceed those recorded in SirAdmin, then the values will be automatically reset to the maximum allowable and an informational message will be displayed on the 'message line' (2nd bottom line of the screen).<br />
<br />
==== New field Bookmarks ====<br />
<br />
Bookmarks are a new feature. When turned on (value "Y"), a bookmark line will<br />
be created in the display on the SCANLIST page for each successive scan request. <br />
Note that bookmarks are only active if the Interval (Minutes) field is left blank.<br />
The line looks like:<br />
<br />
<p class="code">______________________________________________________ BookMark 4: 19:59:37.23 - 19:59:58.90<br />
</p><br />
<br />
It shows the bookmark number and the time range for that scan. The bookmarks <br />
are sequentially numbered and the message line at the bottom of the screen shows<br />
the lasted bookmark id, for example:<br />
<br />
<p class="code">--------------------------------------------------------------------- -- Latest Bookmark: 4<br />
</p><br />
<br />
Bookmarks are saved for the session. Hence if SirScan is exited and re-entered<br />
during the same session, the previous bookmarks are retained and can be<br />
re-displayed. The new bookmark id's will follow on from the last one previously<br />
created. This provides an alternative to noting down the time of a scan in<br />
cases where the information needs to be re-displayed. Also it is possible to<br />
change the Display and Format Entry Types on this screen and re-display the<br />
journal lines for a previous bookmark period.<br />
<br />
See xxx for more details.<br />
<br />
==Scan List Screen (SCANLIST)==<br />
<br />
=== Field changes ===<br />
==== New Command .[BookmarkId] ====<br />
A command in format .[BookmarkId] will navigate direct to that bookmark, e.g. <br />
<br />
<p class="code">.22</p><br />
<br />
A command with the BookmarkID will navigate to the latest bookmark.<br />
<br />
=== Screen display changes ===<br />
<br />
==== Bookmark Lines ====<br />
<br />
As notes in xxx if the Bookmark setting is turn on "Y", and additional line<br />
is displayed separating each bookmark scan period. The current (active) bookmark<br />
is shown in green whilst old bookmarks are shown in red.<br />
<br />
=== Function Keys ===<br />
<br />
==== PF5/PF6 - Previous/Next Bookmark (or refresh) ==== <br />
If the Interval (Minutes) field in the SCANSEL screen is left blank, then PF5 will<br />
navigate to the previous bookmark and PF6 to the next bookmark, or create a new one <br />
if already on the last bookmark. Hence the sequence is:<br />
<br />
old bookmarks <=> latest bookmark <=> refresh page (i.e. the next bookmark). <br />
<br />
The scan listing for the old bookmarks is “frozen”, e.g. pressing enter or “bottom”<br />
will not add to the listing and only the scan lines for that bookmark are shown.<br />
<br />
However the latest bookmark listing can be added to with fresh scans. Bookmarks on this page listing are shown in green. If you return to the latest bookmark, only the lines for that bookmark are shown – any others previously on the listing become old bookmarks that you can use PF5 to display. Note that pressing PF5 from the latest bookmark page will take you to the bookmark one less than the latest bookmark, even if the display has a number of earlier bookmarks that have accumulated on the page.<br />
<br />
Note that PF6 can be used to refresh the listing page so it is ready for new journal lines (if already on the latest bookmark). This is equivalent to pressing PF3, keying Start Time -0 and then Enter.<br />
<br />
==== PF7/PF8 - line scrolling ====<br />
The scrolling has been enhanced to scroll based on the position of the<br />
cursor when the cursor is in the listing area. If PF8 is pressed then the page scrolls<br />
so the line under the cursor becomes the top line. If PF7 is pressed the the line under<br />
the cursor becomes the bottom line. The cursor is reset to the Command field so <br />
subsequent scrolling will be for full pages.</div>Mmarshallhttps://m204wiki.rocketsoftware.com/index.php?title=Release_notes_for_SirScan_V7.5&diff=78323Release notes for SirScan V7.52015-07-21T01:29:42Z<p>Mmarshall: /* Functionality changes */</p>
<hr />
<div>This document lists the changes that have been made for <var class="product">SirScan</var> version S7.5. It requires <var class="product">Model 204</var> release 7.5 or higher.<br />
<br />
== Scan Select Screen (SCANSEL) ==<br />
<br />
=== Field changes ===<br />
<br />
==== Layout changes====<br />
Prompts '==>' replaced by ':' <br />
<br />
==== Functionality changes====<br />
<br />
The <b>Start time (HH:MM:SS)</b> field will now accept periods(.) as seperators.<br />
<br />
The <b>Max I/O's.:</b> and <b>Max records:</b> fields have been changed to recognize, reset and report the situation, when the values entered are greater than the maximum allowable.<br />
The maximum allowable values, for the <b>Max I/O's.:</b> and <b>Max records:</b> fields, can be viewed and/or set using the SirAdmin apsy, <b>SirScan SCLASS settings</b> option.<br />
<br />
If the <b>Max I/O's.:</b> and <b>Max records:</b> values, entered on the SirScan screen, exceed those recorded in SirAdmin, then the values will be automatically reset to the maximum allowable and an informational message will be displayed on the 'message line' (2nd bottom line of the screen).<br />
<br />
==== New field Bookmarks ====<br />
<br />
Bookmarks are a new feature. When turned on (value "Y"), a bookmark line will<br />
be created in the display on the SCANLIST page for each successive scan request. <br />
Note that bookmarks are only active if the Interval (Minutes) field is left blank.<br />
The line looks like:<br />
<br />
<p class="code">______________________________________________________ BookMark 4: 19:59:37.23 - 19:59:58.90<br />
</p><br />
<br />
It shows the bookmark number and the time range for that scan. The bookmarks <br />
are sequentially numbered and the message line at the bottom of the screen shows<br />
the lasted bookmark id, for example:<br />
<br />
<p class="code">--------------------------------------------------------------------- -- Latest Bookmark: 4<br />
</p><br />
<br />
Bookmarks are saved for the session. Hence if SirScan is exited and re-entered<br />
during the same session, the previous bookmarks are retained and can be<br />
re-displayed. The new bookmark id's will follow on from the last one previously<br />
created. This provides an alternative to noting down the time of a scan in<br />
cases where the information needs to be re-displayed. Also it is possible to<br />
change the Display and Format Entry Types on this screen and re-display the<br />
journal lines for a previous bookmark period.<br />
<br />
See xxx for more details.<br />
<br />
==Scan List Screen (SCANLIST)==<br />
<br />
=== Field changes ===<br />
==== New Command .[BookmarkId] ====<br />
A command in format .[BookmarkId] will navigate direct to that bookmark, e.g. <br />
<br />
<p class="code">.22</p><br />
<br />
A command with the BookmarkID will navigate to the latest bookmark.<br />
<br />
=== Screen display changes ===<br />
<br />
==== Bookmark Lines ====<br />
<br />
As notes in xxx if the Bookmark setting is turn on "Y", and additional line<br />
is displayed separating each bookmark scan period. The current (active) bookmark<br />
is shown in green whilst old bookmarks are shown in red.<br />
<br />
=== Function Keys ===<br />
<br />
==== PF5/PF6 - Previous/Next Bookmark (or refresh) ==== <br />
If the Interval (Minutes) field in the SCANSEL screen is left blank, then PF5 will<br />
navigate to the previous bookmark and PF6 to the next bookmark, or create a new one <br />
if already on the last bookmark. Hence the sequence is:<br />
<br />
old bookmarks <=> latest bookmark <=> refresh page (i.e. the next bookmark). <br />
<br />
The scan listing for the old bookmarks is “frozen”, e.g. pressing enter or “bottom”<br />
will not add to the listing and only the scan lines for that bookmark are shown.<br />
<br />
However the latest bookmark listing can be added to with fresh scans. Bookmarks on this page listing are shown in green. If you return to the latest bookmark, only the lines for that bookmark are shown – any others previously on the listing become old bookmarks that you can use PF5 to display. Note that pressing PF5 from the latest bookmark page will take you to the bookmark one less than the latest bookmark, even if the display has a number of earlier bookmarks that have accumulated on the page.<br />
<br />
Note that PF6 can be used to refresh the listing page so it is ready for new journal lines (if already on the latest bookmark). This is equivalent to pressing PF3, keying Start Time -0 and then Enter.<br />
<br />
==== PF7/PF8 - line scrolling ====<br />
The scrolling has been enhanced to scroll based on the position of the<br />
cursor when the cursor is in the listing area. If PF8 is pressed then the page scrolls<br />
so the line under the cursor becomes the top line. If PF7 is pressed the the line under<br />
the cursor becomes the bottom line. The cursor is reset to the Command field so <br />
subsequent scrolling will be for full pages.</div>Mmarshallhttps://m204wiki.rocketsoftware.com/index.php?title=Release_notes_for_SirScan_V7.5&diff=78322Release notes for SirScan V7.52015-07-21T01:08:54Z<p>Mmarshall: </p>
<hr />
<div>This document lists the changes that have been made for <var class="product">SirScan</var> version S7.5. It requires <var class="product">Model 204</var> release 7.5 or higher.<br />
<br />
== Scan Select Screen (SCANSEL) ==<br />
<br />
=== Field changes ===<br />
<br />
==== Layout changes====<br />
Prompts '==>' replaced by ':' <br />
<br />
==== Functionality changes====<br />
<br />
The <b>Start time</b> field will now accept periods(.) and semicolons(:) as seperators. <br />
<br />
==== New field Bookmarks ====<br />
<br />
Bookmarks are a new feature. When turned on (value "Y"), a bookmark line will<br />
be created in the display on the SCANLIST page for each successive scan request. <br />
Note that bookmarks are only active if the Interval (Minutes) field is left blank.<br />
The line looks like:<br />
<br />
<p class="code">______________________________________________________ BookMark 4: 19:59:37.23 - 19:59:58.90<br />
</p><br />
<br />
It shows the bookmark number and the time range for that scan. The bookmarks <br />
are sequentially numbered and the message line at the bottom of the screen shows<br />
the lasted bookmark id, for example:<br />
<br />
<p class="code">--------------------------------------------------------------------- -- Latest Bookmark: 4<br />
</p><br />
<br />
Bookmarks are saved for the session. Hence if SirScan is exited and re-entered<br />
during the same session, the previous bookmarks are retained and can be<br />
re-displayed. The new bookmark id's will follow on from the last one previously<br />
created. This provides an alternative to noting down the time of a scan in<br />
cases where the information needs to be re-displayed. Also it is possible to<br />
change the Display and Format Entry Types on this screen and re-display the<br />
journal lines for a previous bookmark period.<br />
<br />
See xxx for more details.<br />
<br />
==Scan List Screen (SCANLIST)==<br />
<br />
=== Field changes ===<br />
==== New Command .[BookmarkId] ====<br />
A command in format .[BookmarkId] will navigate direct to that bookmark, e.g. <br />
<br />
<p class="code">.22</p><br />
<br />
A command with the BookmarkID will navigate to the latest bookmark.<br />
<br />
=== Screen display changes ===<br />
<br />
==== Bookmark Lines ====<br />
<br />
As notes in xxx if the Bookmark setting is turn on "Y", and additional line<br />
is displayed separating each bookmark scan period. The current (active) bookmark<br />
is shown in green whilst old bookmarks are shown in red.<br />
<br />
=== Function Keys ===<br />
<br />
==== PF5/PF6 - Previous/Next Bookmark (or refresh) ==== <br />
If the Interval (Minutes) field in the SCANSEL screen is left blank, then PF5 will<br />
navigate to the previous bookmark and PF6 to the next bookmark, or create a new one <br />
if already on the last bookmark. Hence the sequence is:<br />
<br />
old bookmarks <=> latest bookmark <=> refresh page (i.e. the next bookmark). <br />
<br />
The scan listing for the old bookmarks is “frozen”, e.g. pressing enter or “bottom”<br />
will not add to the listing and only the scan lines for that bookmark are shown.<br />
<br />
However the latest bookmark listing can be added to with fresh scans. Bookmarks on this page listing are shown in green. If you return to the latest bookmark, only the lines for that bookmark are shown – any others previously on the listing become old bookmarks that you can use PF5 to display. Note that pressing PF5 from the latest bookmark page will take you to the bookmark one less than the latest bookmark, even if the display has a number of earlier bookmarks that have accumulated on the page.<br />
<br />
Note that PF6 can be used to refresh the listing page so it is ready for new journal lines (if already on the latest bookmark). This is equivalent to pressing PF3, keying Start Time -0 and then Enter.<br />
<br />
==== PF7/PF8 - line scrolling ====<br />
The scrolling has been enhanced to scroll based on the position of the<br />
cursor when the cursor is in the listing area. If PF8 is pressed then the page scrolls<br />
so the line under the cursor becomes the top line. If PF7 is pressed the the line under<br />
the cursor becomes the bottom line. The cursor is reset to the Command field so <br />
subsequent scrolling will be for full pages.</div>Mmarshallhttps://m204wiki.rocketsoftware.com/index.php?title=Release_notes_for_SirScan_V7.5&diff=78321Release notes for SirScan V7.52015-07-21T01:04:12Z<p>Mmarshall: </p>
<hr />
<div>This document lists the changes that have been made for <var class="product">SirScan</var> version S7.5. It requires <var class="product">Model 204</var> release 7.5 or higher.<br />
<br />
== Scan Select Screen (SCANSEL) ==<br />
<br />
=== Field changes ===<br />
<br />
==== Layout changes====<br />
Prompts '==>' replaced by ':' <br />
<br />
==== Functionality changes====<br />
<br />
===== Start time =====<br />
<br />
==== New field Bookmarks ====<br />
<br />
Bookmarks are a new feature. When turned on (value "Y"), a bookmark line will<br />
be created in the display on the SCANLIST page for each successive scan request. <br />
Note that bookmarks are only active if the Interval (Minutes) field is left blank.<br />
The line looks like:<br />
<br />
<p class="code">______________________________________________________ BookMark 4: 19:59:37.23 - 19:59:58.90<br />
</p><br />
<br />
It shows the bookmark number and the time range for that scan. The bookmarks <br />
are sequentially numbered and the message line at the bottom of the screen shows<br />
the lasted bookmark id, for example:<br />
<br />
<p class="code">--------------------------------------------------------------------- -- Latest Bookmark: 4<br />
</p><br />
<br />
Bookmarks are saved for the session. Hence if SirScan is exited and re-entered<br />
during the same session, the previous bookmarks are retained and can be<br />
re-displayed. The new bookmark id's will follow on from the last one previously<br />
created. This provides an alternative to noting down the time of a scan in<br />
cases where the information needs to be re-displayed. Also it is possible to<br />
change the Display and Format Entry Types on this screen and re-display the<br />
journal lines for a previous bookmark period.<br />
<br />
See xxx for more details.<br />
<br />
==Scan List Screen (SCANLIST)==<br />
<br />
=== Field changes ===<br />
==== New Command .[BookmarkId] ====<br />
A command in format .[BookmarkId] will navigate direct to that bookmark, e.g. <br />
<br />
<p class="code">.22</p><br />
<br />
A command with the BookmarkID will navigate to the latest bookmark.<br />
<br />
=== Screen display changes ===<br />
<br />
==== Bookmark Lines ====<br />
<br />
As notes in xxx if the Bookmark setting is turn on "Y", and additional line<br />
is displayed separating each bookmark scan period. The current (active) bookmark<br />
is shown in green whilst old bookmarks are shown in red.<br />
<br />
=== Function Keys ===<br />
<br />
==== PF5/PF6 - Previous/Next Bookmark (or refresh) ==== <br />
If the Interval (Minutes) field in the SCANSEL screen is left blank, then PF5 will<br />
navigate to the previous bookmark and PF6 to the next bookmark, or create a new one <br />
if already on the last bookmark. Hence the sequence is:<br />
<br />
old bookmarks <=> latest bookmark <=> refresh page (i.e. the next bookmark). <br />
<br />
The scan listing for the old bookmarks is “frozen”, e.g. pressing enter or “bottom”<br />
will not add to the listing and only the scan lines for that bookmark are shown.<br />
<br />
However the latest bookmark listing can be added to with fresh scans. Bookmarks on this page listing are shown in green. If you return to the latest bookmark, only the lines for that bookmark are shown – any others previously on the listing become old bookmarks that you can use PF5 to display. Note that pressing PF5 from the latest bookmark page will take you to the bookmark one less than the latest bookmark, even if the display has a number of earlier bookmarks that have accumulated on the page.<br />
<br />
Note that PF6 can be used to refresh the listing page so it is ready for new journal lines (if already on the latest bookmark). This is equivalent to pressing PF3, keying Start Time -0 and then Enter.<br />
<br />
==== PF7/PF8 - line scrolling ====<br />
The scrolling has been enhanced to scroll based on the position of the<br />
cursor when the cursor is in the listing area. If PF8 is pressed then the page scrolls<br />
so the line under the cursor becomes the top line. If PF7 is pressed the the line under<br />
the cursor becomes the bottom line. The cursor is reset to the Command field so <br />
subsequent scrolling will be for full pages.</div>Mmarshallhttps://m204wiki.rocketsoftware.com/index.php?title=SoulEdit&diff=78214SoulEdit2015-07-13T02:02:22Z<p>Mmarshall: Changed the SCMD forward slash (eg., "SCMD/") to a backSlash (eg., "SCMD\")</p>
<hr />
<div>'''SoulEdit''' is a code editor, written in SOUL, specifically designed for SOUL application development. '''SoulEdit''' features extended editing capability - like split/join, bookmarks, display filtering and syntax-specific colors - as well as facilities that make running, debugging and testing SOUL code more seamless and intuitive.<br />
<br />
'''SoulEdit''' runs as an application subsystem, so it needs an apsy definition for it to operate along with a minimum 640K server size - 750K would be safer as that provides room for future enhancements and the addition of user-written macros. See the ULSPF Installation Guide for more information on setting up the environment for SoulEdit. '''SoulEdit''' is built into <var class="product">SirPro</var>, which is part of the [[ULSPF | UL/SPF]] family of products from '''Rocket Software''', and it can also be run as a standalone editor by setting up a separate APSY - at '''Rocket''' we run it as an apsy called SE so it's executable from the command line. Details for setting up your own '''SoulEdit''' apsy are also in the installation guide.<br />
<br />
==Overview==<br />
<br />
<var class="product">SirPro</var> is a menu-driven application subsystem that provides tools for programmers, database administrators and application managers inside the Model 204 environment. <var class="product">SirPro</var>'s primary feature set is centered on the manipulation of <var class="product">Model 204</var> procedures contained in Model 204 files. To access '''SoulEdit''' from <var class="product">SirPro</var>, use the 'E' prefix command from the list of procedure. If '''SoulEdit''' is defined as a standalone apsy (for example, 'SE') simply type the apsy name with a procedure: '''SE MYPROCEDURE''' where MYPROCEDURE is a procedure in the current file.<br />
<br />
One of the most useful features of '''SoulEdit''' is the ability to run a program via the GO command and immediately view the output in a scrollable [[Stringlist class | stringList]]. If errors occurred while running a series of AUDIT commands is available to display the audit trail output of the procedure you've just run.<br />
<br />
[[File:SoulEdit_Overview.png|border|650px]]<br />
<br />
''SoulEdit - main editing screen. The top line shows the name of the SOUL procedure, the file where the procedure lives, and a warning if the file is in read-only mode. At the right are shown the line numbers with the current top-of-the-screen line number. Note the color-coding of lines in the sample - colors are user-settable via the COLORS command.''<br />
<br />
==Command Line options== <br />
<br />
T[ n]|TOP[ n]|M+PF7 - go to the Top of the editor content... optional n (linenum) as top of page <br />
B|BOTTOM|M+PF8 - go to the Bottom of the editor content <br />
C <lineNumber> - center the line specified by lineNumber... lineNumber is absolute... not relative <br />
+|-<numericValue> - position content relative to the numeric value <br />
[-]F|Find <value> - find previous/next value from cursor position (PF5 repeats last find) <br />
[-]/<value> - find previous/next value from cursor position (PF5 repeats last find) <br />
R|REPLACE/<replaceThis>/<withThis>[[/n] ALL] - replace... n = replacements per line for replace... the character immediately following the R or REPLACE is used as a delimiter between tokens(cannot be alphanumeric) <br />
A|ALL <value> - hide all lines that do not match <value>... command without <value> performs a SHOW ALL instead<br />
HIDE <value> - hide all lines that match <value> <br />
SHOW|HIDE COMMENTS - show or hide all comment lines <br />
UNHIDE <value> - unhide all lines that match <value> <br />
CLEAR HIDDEN|RESET HIDDEN - clear all hidden lines (unhide) <br />
SHOW ALL|SHOW HIDDEN - clear all hidden lines (unhide)<br />
GO - Run the program and capture the output into a scrollable stringList. <br />
[IN <fileName> ]GET <procName> - obtain the named proc and insert into editor... can use line command targeting <br />
SAVE[ <procName>] - save current editor content (optional save into a different named proc including temp procs) <br />
END - perform SAVE and exit the editor <br />
QUIT - exit the editor without saving or giving a modification warning <br />
ALIGN <value> - requires BB line command range (has issues when crossing 'block' statements) <br />
SORT [A|D|ASC|DESC|ASCENDING|DESCENDING] - requires BB line command range <br />
CLEAR - clear all line commands <br />
RESET PROC|RELOAD|RELOAD PROC - discards any changes by reloading the current procedure from file <br />
REFRESH PAGE - ignore any changes upon this page since last enter <br />
NUM|NUMS|NUMBERS [ON|OFF] - show line numbers in prefix field (toggle) <br />
= - Repeat last command (same as PF9) <br />
command stack (pf6) - cycles thru the command stack <br />
SET COMMAND STACK n - defaults to 10... but user may want to increase/decrease. <br />
split/join lines (pf2) - cursor sensitive... if no data from cursor a join is performed else split is performed <br />
FLIP HIDDEN - flip the hidden state of lines... hidden->shown && shown->hidden <br />
FF|BB+FORMAT - FORMAT [width] [INDENT n] - format range (indents and alignment)... not fully completed... but mostly functional <br />
UNDO FORMAT - reinstates the last FORMAT to its state before the format (does not check if code has changed) <br />
SET FORMAT <type> - force the formatting type used by FORMAT/FF .. Valid types: M204, XSL <br />
RUN (saves & runs code in a daemon) - output from the execution is scrollable (lost daemons are trapped and reported) <br />
RUN TERM (saves & runs code on current thread) <br />
RUN [TERM] [<procName> [FILE <filename> [PASS <password]]] <br />
SHOW [ [RUN|OUTPUT]|RUN OUTPUT] - shows the output from the last executed code or commands line VAR/SHOW [SEQ] CHANGES <br />
SHOW CHANGES - compares current content against proc on file and is displayed in a scrollable form <br />
SHOW SEQ CHANGES - do compare against SEQ version in same procfile <br />
SCALE (toggles on/off) - |...+....1....+....2....+....3...etc <br />
PFKEYS (toggles on/off) - show valid pfkeys upon the last line of the page <br />
NEW PROC[EDURE] - clear current code (essentially a quit)... and start with a blank proc <br />
Formatting for XSL - change formatting where proc name ends with .xsl <br />
HELP (pf1) - displays help text <br />
VAR|VARS|VARIABLES - show variable usage(counts) within scope <br />
SETUP|PROFILE - set user editor preferences <br />
COLORS - set user editor color preferences <br />
bookmarks .<value> - bookmarks...example. .foo as a line command bookmarks it... command .foo focuses the bookmark<br />
CLEAR BOOKMARKS - clear all bookmarks <br />
XCOMPARE|XC [EXACT|DEBLANK|COMPRESS] - XCompares current content against proc on file and is displayed in a scrollable form <br />
XCOMPARE SEQ|XCS [EXACT|DEBLANK|COMPRESS] - do XCompare against SEQ version in same procfile (only works for SirLib users) <br />
LAYOUT|MAP - list all class/subroutines/functions... can use pf4 to focus entry from listing<br />
INCLUDES command - show heirarchy of all includes referenced within the current procedure <br />
PROTECT/UNPROTECT - force the displayed content to be protected/unprotected <br />
BB¦BLOCK WHERE - Used to add BB markers to the current 'where' scope <br />
AUDIT [minutes¦timestamp¦LAST[RUN]] - This command shows the journal lines for the user... defaults to the last minute unless an <br />
optional time is supplied <br />
SET FILE <fileName> - sets the filename for saving procedures... also clears the procedure name <br />
SNAP¦SNAPSHOT - Takes a copy of the code in the current editing session and saves it as snapshot <br />
XCB [previous snapshot offset] - Compare the current code against the last snapshot taken <br />
<br />
Used in conjunction with the pf12 key on the run output when compilation/runtime errors occur, the following commands can be used to navigate <br />
thru the errors in the currently loaded procedure:- <br />
<br />
NE¦NEXT ERROR - Navigate to the next error <br />
PE¦PREVIOUS ERROR - Navigate to the previous error <br />
CE¦CURRENT ERROR - Navigate to the current error <br />
CLE¦CLEAR ERRORS - Clear the error bookmarks <br />
<br />
==Line Prefix Commands==<br />
<br />
===Block Prefixes - with repeating ignored=== <br />
<br />
CC = Block Copy (requires targeting prefix) <br />
MM = Block Move (requires targeting prefix) <br />
DD = Block Delete <br />
HH = Block Hide <br />
** = Block Comment (set/clear - first line is used to determine state switch... if first char is * then comments are removed)<br />
BB = Block Boundaries.. used with editor commands: SORT, ALIGN, FORMAT. Optional for R, REPLACE <br />
FF = Format specified block - sets indenting to the number of spaces specified in the user profile.<br />
<br />
===Block Prefixes - with repeating honored===<br />
<br />
(so, for instance, ""3 replicates the block 3 times)<br />
RR "" = Block Replicate <br />
<< (( = Block Shift Left (with protections to prevent loss of leading text) <br />
>> )) = Block Shift Right (with protections to prevent loss of trailing text) <br />
<br />
===Targeting Prefixes===<br />
<br />
A = Target After Line <br />
F = Target Following Line <br />
B = Target Before Line <br />
P = Target Previous Line <br />
<br />
===Singular Prefixes - with repeating ignored===<br />
<br />
C = copy (requires targeting prefix) <br />
M = Move (requires targeting prefix) <br />
E = Expand line to 255 bytes (toggles on/off) <br />
/ = center this line <br />
- = folding of blocks... hide lines from marked line to closing/opening block... example: if -> end if... etc <br />
X = Expand/collapse INCLUDE inline... only usable on INCLUDE lines... the expanded INCLUDE lines are protected <br />
<br />
===Singular Prefixes - with repeating honored===<br />
<br />
H = Hide <br />
S + = Show <br />
D = Delete <br />
R " = Replicate <br />
* = Comment (set/clear - if first char is * then comments are removed) <br />
< ( = Shift Line Left (with protections to prevent loss of leading text) <br />
> ) = Shift Line Right (with protections to prevent loss of trailing text) <br />
<br />
==PF Keys==<br />
PF1 = Help<br />
PF2 = Split the current line at the cursor, or join the current line with the next line if cursor is at end-of-line. <br />
PF3 = Quit the editor without saving<br />
PF4 = <br />
PF5 = <br />
PF6 = Cycle through the command stack. The command stack size defaults to 10 but can be reset via SET<br />
PF7 = Scroll up / use with M to scroll to top<br />
PF8 = Scroll down / use with M to scroll to bottom<br />
PF9 = Repeat previous command<br />
= shift+PF10 performs an ALL for the text under the cursor <br />
PF11 = creates/appends the value under the cursor to a traceText upon the following line<br />
PF12 = saves current procedure and opens the INCLUDEd text under the cursor. If the cursor is not on an INCLUDE line, no action is taken.<br />
<br />
==User Written Extensions (SCMDs)==<br />
<br />
'''SoulEdit''' has a facility that allows anyone to add command-line extensions to the editor.<br />
<br />
Starting with an example, "INFO" is a user-written command extension provided by Rocket Software. It provides information about any Model 204 system function in XML format via the [[LoadSystemMethodInfo (XmlDoc subroutine)|LoadSystemMethodInfo]] method call. If you type ''info currenttimestring'' into the command line of SoulEdit, like this:<br />
<br />
[[File:SOUL_UserCommands1.png|border|650px]]<br />
<br />
''User-defined commands are entered on the command line.''<br />
<br />
You'll see the output of the [[LoadSystemMethodInfo (XmlDoc subroutine)|LoadSystemMethodInfo]] call displayed in a scrollable screen, like this:<br />
<br />
[[File:SOUL_UserCommands2.png|border|650px]]<br />
<br />
''The output of commands appears in a scrollable screen. PF3 takes the user back to their in-progress editing session.''<br />
<br />
The editor extensions are created via '''SCMD''' procedures stored in a user-designated file. You can see how ''INFO'' works by looking at procedure SCMD\INFO in SIRIUS.<br />
<br />
To create your own commands, specify a procfile file where they will live, via the ''PROFILE'' command and ''Custom Macros File''. '''SoulEdit''' will scan this file for procedures prefixed with ''SCMD\'' and will load them into memory at the beginning of the editing session. Copy ''SCMD\INFO'' into your Macros file with a new name and customize the ''run'' method to your liking.<br />
<br />
==Timed Backups==<br />
<br />
'''SoulEdit''' will take timed backups of the procedures you're editing - this feature can be turned on, on a user-by-user basis via the ''PROFILE'' command. Backups are take by default to the same file in which a procedure is being edited. Optionally a separate backup file can be specified, also via ''PROFILE''.<br />
<br />
==Auditing==<br />
After running a procedure via the ''GO'' command from inside the editor, the user can then see the journal output of the run by typing ''AUDIT'' on the command line of the output display. ''AUDIT'' options are:<br />
<br />
<br />
==See also==<br />
<br />
[[SirPro]]<br />
<br />
[[SirLib]]<br />
<br />
[[Category:Sirius Software products]]</div>Mmarshallhttps://m204wiki.rocketsoftware.com/index.php?title=ObjectId_(Object_function)&diff=77709ObjectId (Object function)2015-05-25T07:49:40Z<p>Mmarshall: </p>
<hr />
<div>{{Template:Object:ObjectId subtitle}}<br />
<br />
This function returns a unique numeric id for an object.<br />
==Syntax==<br />
{{Template:Object:ObjectId syntax}}<br />
===Syntax terms===<br />
<table class="syntaxTable"><br />
<tr><th>%number</th><td>Is the online-wide unique id of the object.</td></tr><br />
<tr><th>object</th><br />
<td>Object object for which id is to be returned. Of course, since all classes extend the <var>Object</var> class, <var>object</var> can be of any class.</td></tr><br />
</table><br />
==Usage notes==<br />
<ul><br />
<li>As noted above, the object ids are unique in an Online. However, they are not unique between Onlines nor between runs of an Online.</li><br />
<li>The object ids are assigned in numeric order starting at 1. So the first object instantiated in an Online run has object id 1, the second has object id 2, and so on. Since the object ids are online-wide, there is no guarantee that an object instantiated right after another object in the same request will have an object id one greater than the previous one's. This is because other objects for other threads (users) might instantiate an object between the two instantiations in the request.</li><br />
<li>The id is a characteristic of the object, not the object variable. As such, the same value is returned for a given object, regardless of what variable is used to obtain the id and regardless of the class of the variable used to invoke the <var>Objectid</var> method (base class or extension class).</li><br />
<li><var>XmlNode</var> objects return the id of the containing <var>XmlDoc</var> object.</li><br />
</ul><br />
==Examples==<br />
The <var>ObjectId</var> function can be useful in creating temporary object-specific references to other objects. For example, suppose you have <var>Widget</var> and <var>Box</var> objects in an application. The <var>Widget</var> objects do not contain references to <var>Box</var> objects because boxes don't have much to do with widgets. However, in our specific application, we are tracking widgets in boxes so it would be very useful to be able to get a <var>Box</var> object from a <var>Widget</var> object. To accomplish this, we first declare a [[FloatNamedArraylist_class|FloatNamedArraylist]] of <var>Box</var> objects:<p class="code">%widgetBox is floatNamedArraylist of object box<br />
</p><br />
The idea is that the collection "names" will be the <var>Widget</var> object ids. Now, whenever a widget is put into a box or determined to be in a box, we assign that <var>Box</var> object variable to the FloatNamedArraylist item with the <var>Widget</var>'s object id:<p class="code">%widgetBox(%widget:objectId) = %box<br />
</p><br />
If a <var>Widget</var> is moved to a different <var>Box</var> its <var>WidgetBox</var> item must be set to point to the new <var>Box</var>. With this in place, it becomes very easy to access the correct <var>Box</var> object, given a <var>Widget</var> object:<p class="code">%box = %widgetBox(%widget:objectId)<br />
</p><br />
<br />
==See also==<br />
{{Template:Object:ObjectId footer}}</div>Mmarshallhttps://m204wiki.rocketsoftware.com/index.php?title=FNVMASK_parameter&diff=77624FNVMASK parameter2015-05-21T10:50:26Z<p>Mmarshall: </p>
<hr />
<div>{{Template:FNVMASK parameter subtitle}}<br />
==Summary==<br />
<dl><br />
<dt>Default value<br />
<dd>X'00'<br />
<dt>Parameter type<br />
<dd>System<br />
<dt>Where set<br />
<dd>User 0 CCAIN parameters<br />
<dt>Related products<br />
<dd>[http://sirius-software.com/maint/download/perfr.pdf Sirius Performance Enhancements V3]<br />
<dt>Introduced<br />
<dd>Before <var class="product">Sirius Mods</var> 6.7<br />
</dl><br />
<br />
==Description==<br />
This is a single-byte bitmask parameter.<br />
If set to a non-zero value, <var>FNVMASK</var> indicates the bytes in<br />
filenames that are not required to match those in the filenames on the physical<br />
file pages.<br />
Bytes in filenames corresponding to the ON bits in <var>FNVMASK</var> do not have to<br />
match the comparable bytes in the physical filenames.<br />
<br />
For example, if <var>FNVMASK</var> is set to X'10', the fourth byte of a filename<br />
does not have to match the physical filename.<br />
That is, you might be able to open a file with physical name FOOBAR as<br />
FOODAR, or FOOLAR, or FOOTAR.<br />
If <var>FNVMASK</var> were set to X'34', bytes 3, 4, and 6 wouldn't need to match, so<br />
FOOBAR could be opened as FOOLAP, or FOCKAZ, or FOLDAR, or FOXBAG to name just a few.<br />
<br />
<var>FNVMASK</var> facilitates sharing of data between Onlines, making it possible<br />
for two files with the same physical name to be opened in the same Online<br />
by opening them under two different names that differ only in the bytes<br />
indicated by <var>FNVMASK</var>.<br />
This can be especially useful in moving procedures from one file to a<br />
like-named file to be used in a different Online.<br />
<br />
<p class="note">'''Note:''' <var>FNVMASK</var> in no way alters the file-enqueuing behavior<br />
of <var class="product">Model 204</var> &mdash; no file opened for update by one Online can be opened<br />
by another, regardless of the name under which it is opened. </p><br />
<br />
Use of <var>FNVMASK</var> does not weaken page trailer validation, as page trailer<br />
validation at disk reads will validate the name against all bytes of<br />
the physical file name, regardless of <var>FNVMASK</var>.<br />
<br />
[[Category:System parameters]]<br />
[[Category:Parameters]]</div>Mmarshallhttps://m204wiki.rocketsoftware.com/index.php?title=FNVMASK_parameter&diff=77623FNVMASK parameter2015-05-21T10:36:10Z<p>Mmarshall: </p>
<hr />
<div>{{Template:FNVMASK parameter subtitle}}<br />
==Summary==<br />
<dl><br />
<dt>Default value<br />
<dd>X'00'<br />
<dt>Parameter type<br />
<dd>System<br />
<dt>Where set<br />
<dd>User 0 CCAIN parameters<br />
<dt>Related products<br />
<dd>[http://sirius-software.com/maint/download/perfr.pdf Sirius Performance Enhancements V3]<br />
<dt>Introduced<br />
<dd>Before <var class="product">Sirius Mods</var> 6.7<br />
</dl><br />
<br />
==Description==<br />
This is a single-byte bitmask parameter.<br />
If set to a non-zero value, <var>FNVMASK</var> indicates the bytes in<br />
filenames that are not required to match those in the filenames on the physical<br />
file pages.<br />
Bytes in filenames corresponding to the ON bits in <var>FNVMASK</var> do not have to<br />
match the comparable bytes in the physical filenames.<br />
<br />
For example, if <var>FNVMASK</var> is set to X'10', the fourth byte of a filename<br />
does not have to match the physical filename.<br />
That is, you might be able to open a file with physical name FOOBAR as<br />
FOODAR, or FOOLAR, or FOOTAR.<br />
If <var>FNVMASK</var> were set to X'34', bytes 3, 4, and 6 wouldn't need to match, so<br />
FOOBAR could be opened as FOOLER, or FOCKER, or FOLDER, to name just a few.<br />
<br />
<var>FNVMASK</var> facilitates sharing of data between Onlines, making it possible<br />
for two files with the same physical name to be opened in the same Online<br />
by opening them under two different names that differ only in the bytes<br />
indicated by <var>FNVMASK</var>.<br />
This can be especially useful in moving procedures from one file to a<br />
like-named file to be used in a different Online.<br />
<br />
<p class="note">'''Note:''' <var>FNVMASK</var> in no way alters the file-enqueuing behavior<br />
of <var class="product">Model 204</var> &mdash; no file opened for update by one Online can be opened<br />
by another, regardless of the name under which it is opened. </p><br />
<br />
Use of <var>FNVMASK</var> does not weaken page trailer validation, as page trailer<br />
validation at disk reads will validate the name against all bytes of<br />
the physical file name, regardless of <var>FNVMASK</var>.<br />
<br />
[[Category:System parameters]]<br />
[[Category:Parameters]]</div>Mmarshall