Release notes for SirPro V7.5 - Revision history

JAL: add pointers to PL feature

2016-05-04T19:19:55Z

add pointers to PL feature

← Older revision		Revision as of 19:19, 4 May 2016
Line 165:		Line 165:

	<ul>		<ul>
	<li>E (Edit)		<li><b>E (Edit)</b>
	<p>		<p>
	Invokes [[SoulEdit]], the SOUL editor.		Invokes [[SoulEdit]], the SOUL editor.
	</p>		</p>

	<li>U (Undo)		<li><b>U (Undo)</b>
	<p>		<p>
	This ~~command requires~~ [[SirLib]]~~, the~~		This <i>[[SirLib]]-required</i> command performs the same operation as <var>Q</var>, resulting in the creation of a "working"
	~~managed update and configuration management system. If SirLib is~~		procedure and a sequenced copy of that procedure. However, the <var>U</var> command may only be executed against a change deck. It includes the change deck against which it is executed in the code for the working procedure but <b>not</b> in the code from the sequenced copy. In other words, it recreates
	~~not installed, these commands are not valid. </p>~~
	~~<p>~~
	~~The <var>U~~</~~var~~> command performs the same operation as <var>Q</var>, resulting in a "working"
	procedure and a sequenced copy of that procedure ~~being created~~
	~~in the user's selected development procedure file~~. However, the <var>U</var> command ~~May~~ only be executed against a change deck. It ~~specifically~~ includes the change deck against which it is executed in the code for the working procedure, but <b>not</b> in the code from the sequenced copy. In other words, it recreates
	the state of the development procedures that created the change		the state of the development procedures that created the change
	deck ~~against which the <var>U</var> command is executed~~. </p>		deck. </p>
	<p>		<p>
	For further details, see [[SirPro change management tools and functions#undoCmd\|U (Undo)]]. </p></li>		For further details, see [[SirPro change management tools and functions#undoCmd\|U (Undo)]]. </p></li>

	<li>Y		<li><b>Y (Refresh)</b>
	<p>		<p>
	This ~~command requires~~ [[SirLib]]~~, the~~		This <i>[[SirLib]]-required</i> command lets you "refresh" your local working copy
	~~managed update and configuration management system. If SirLib is~~
	~~not installed, these commands are not valid.~~ </p>
	~~<p>~~
	~~This change-control prefix~~ command ~~provides a special check-out~~
	~~ability in which the user can~~ "refresh" ~~their~~ local working copy
	of a procedure with changes that have been checked in by other		of a procedure with changes that have been checked in by other
	programmers since the working copy ~~was originally taken~~ from		programmers since you checked out the working copy from
	the source procedure file. </p>		the source procedure file. </p>
	<p>		<p>
Line 201:		Line 191:

	==New PL subsystem==		==New PL subsystem==
	The new <var>PL</var> command allows direct entry to the [[SirPro procedure-list operations#Overview\|Procedure List screen]] in SirPro. The format is:		The new <var>PL</var> subsystem and fast-path command allows direct entry to the [[SirPro procedure-list operations#Overview\|Procedure List screen]] in SirPro. The command format is:
	<p class="syntax">PL [<span class="term">procedurePattern</span>] [FILE <span class="term">filename</span> \| GROUP <span class="term">groupname</span>]		<p class="syntax">PL [<span class="term">procedurePattern</span>] [FILE <span class="term">filename</span> \| GROUP <span class="term">groupname</span>]
	</p>		</p>
	~~If <var>FILE</var> or <var>GROUP</var> is not supplied, the current open context is used. The context is obtained using <code>$view('APDFCNTX')</code> (see [[APDFCNTX parameter]]).~~

	~~<blockquote class="note">~~
	~~<p><b>Note:</b> If a procedure name search is required for the words "FILE" or "GROUP", it must be entered as: </p>~~
	~~<p class="code">PL file FILE <i>filename</i></p>~~
	<p>		<p>
	~~where:~~ </p>		For further details, see [[RKTools#PL command\|PL command]]. </p>
	~~<ul>~~
	~~<li><code>file</code> indicates procedures whose name contains the word "file".</li>~~

	~~<li><code>FILE</code> is required because the context is not automatically added if searching for the words "FILE" or "GROUP". </li>~~
	~~</ul>~~
	~~</blockquote~~>

	==Enhanced Help==		==Enhanced Help==
	(in progress)		(in progress)

JAL: add pointers to features

2016-05-03T14:45:32Z

add pointers to features

← Older revision		Revision as of 14:45, 3 May 2016
Line 162:		Line 162:

	====Sel (selection) field====		====Sel (selection) field====
	The following procedure selection ~~option is~~ added:		The following procedure-selection prefix commands are added:

	<dl>		<ul>
	<dt>E (Edit)		<li>E (Edit)
	<dd>Invokes [[SoulEdit]], the SOUL editor.		<p>
	</dl>		Invokes [[SoulEdit]], the SOUL editor.
	~~The following new selection options are part of~~ [[SirLib]], the		</p>

			<li>U (Undo)
			<p>
			This command requires [[SirLib]], the
	managed update and configuration management system. If SirLib is		managed update and configuration management system. If SirLib is
	not installed, these commands are not valid.		not installed, these commands are not valid. </p>
			<p>
	~~<table class="thJustBold">~~		The <var>U</var> command performs the same operation as <var>Q</var>, resulting in a "working"
	~~<caption>Options that require SirLib~~</~~caption~~>
	<~~tr class="head"><th>Command</th><th>Description</th></tr~~>

	~~<tr>~~<th>
	U ~~(Undo)~~
	</th>
	~~<td>~~
	~~May only be executed against a change deck. This~~ command
	performs the same operation as <var>Q</var>, resulting in a "working"
	procedure and a sequenced copy of that procedure being created		procedure and a sequenced copy of that procedure being created
	in the user's selected development procedure file. However, the <var>U</var> command specifically includes the change deck against which it is executed in the code for the working procedure, but <b>not</b> in the code from the sequenced copy. In other words, it recreates		in the user's selected development procedure file. However, the <var>U</var> command May only be executed against a change deck. It specifically includes the change deck against which it is executed in the code for the working procedure, but <b>not</b> in the code from the sequenced copy. In other words, it recreates
	the state of the development procedures that created the change		the state of the development procedures that created the change
	deck against which the <var>U</var> command is executed.		deck against which the <var>U</var> command is executed. </p>
			<p>
			For further details, see [[SirPro change management tools and functions#undoCmd\|U (Undo)]]. </p></li>

	~~Typically, the~~ <~~var~~>U<~~/var~~> ~~command is used to recreate the state of development when the programmer has accidentally deleted the procedures she was working on, either manually, or via the "Clean-up" switch on~~		<li>Y
	~~the Xcompare screen.~~		<p>
			This command requires [[SirLib]], the
	~~The <var>U</var>~~ command ~~is a special-use feature~~, ~~and there are a number~~		managed update and configuration management system. If SirLib is
	~~of ways in which it will fail to work — most notably, if~~ the		not installed, these commands are not valid. </p>
	~~selected change deck is somewhere in the middle of a series of~~		<p>
	~~changes~~ and~~, by excluding it from procedure creation, some code~~
	~~dependency~~ is ~~missing. However, for its primary function —~~
	~~recovering from a mistake that was made very recently~~, ~~typically~~
	~~as the most recent change to a procedure — it should always work~~.
	~~</td></tr>~~

	~~<tr><th>~~
	Y
	</th>
	<td>
	This change-control prefix command provides a special check-out		This change-control prefix command provides a special check-out
	ability in which the user can "refresh" their local working copy		ability in which the user can "refresh" their local working copy
	of a procedure with changes that have been checked in by other		of a procedure with changes that have been checked in by other
	programmers since the working copy was originally taken from		programmers since the working copy was originally taken from
	the source procedure file.		the source procedure file. </p>
			<p>
	~~<var>Y~~</~~var~~> ~~is applied against the working~~		For further details, see [[SirPro change management tools and functions#refresh\|Y (Refresh)]]. </p>
	~~procedure, a screen is presented, and the result is both of these:~~		</li>
	<ul>
	~~<li>A new working procedure with all updates applied <b>~~and</~~b> the user's current changes still in place </li~~>

	~~<li>A sequenced copy that has all updates applied, but the user's current changes not in place~~ </li>
	</ul>		</ul>

	In other words, the <var>Y</var> command is very much like a <var>Q</var> command, but it is done while changes are in progress, and it slips into place other changes that have occurred since the original
	~~procedure check-out.~~
	~~</td></tr>~~
	~~</table>~~

	==New PL subsystem==		==New PL subsystem==

JAL: /* New PL subsystem */ minor formatting

2016-05-03T13:41:58Z

New PL subsystem: minor formatting

← Older revision		Revision as of 13:41, 3 May 2016
Line 224:		Line 224:
	==New PL subsystem==		==New PL subsystem==
	The new <var>PL</var> command allows direct entry to the [[SirPro procedure-list operations#Overview\|Procedure List screen]] in SirPro. The format is:		The new <var>PL</var> command allows direct entry to the [[SirPro procedure-list operations#Overview\|Procedure List screen]] in SirPro. The format is:
	<p class="syntax">PL [<span class="term">procedurePattern</span>] [FILE <span class="term">~~fileName~~</span> \| GROUP <span class="term">~~groupName~~</span>]		<p class="syntax">PL [<span class="term">procedurePattern</span>] [FILE <span class="term">filename</span> \| GROUP <span class="term">groupname</span>]
	</p>		</p>
	If <var>FILE</var> or <var>GROUP</var> is not supplied, the current open context is used. The context is obtained using <code>$view('APDFCNTX')</code> (see [[APDFCNTX parameter]]).		If <var>FILE</var> or <var>GROUP</var> is not supplied, the current open context is used. The context is obtained using <code>$view('APDFCNTX')</code> (see [[APDFCNTX parameter]]).

	<blockquote class="note">		<blockquote class="note">
	<p><b>Note:</b> If a procedure name search is required for the words "FILE" or "GROUP," it must be entered as: </p>		<p><b>Note:</b> If a procedure name search is required for the words "FILE" or "GROUP", it must be entered as: </p>
	<p class="code">PL file FILE <i>filename</i></p>		<p class="code">PL file FILE <i>filename</i></p>
	<p>		<p>
	where: </p>		where: </p>
	<ul>		<ul>
	<li><code>file</code> indicates procedures whose name contains the word "file."</li>		<li><code>file</code> indicates procedures whose name contains the word "file".</li>

	<li><code>FILE</code> is required because the context is not automatically added if searching for the words "FILE" or "GROUP." </li>		<li><code>FILE</code> is required because the context is not automatically added if searching for the words "FILE" or "GROUP". </li>
	</ul>		</ul>
	</blockquote>		</blockquote>

JAL: /* Logical And/Or for Procedure Name search */ shrink and point to feature

2016-04-28T17:50:32Z

Logical And/Or for Procedure Name search: shrink and point to feature

← Older revision		Revision as of 17:50, 28 April 2016
Line 35:		Line 35:
	===Other features===		===Other features===

	====Logical And/Or for Procedure Name search====		====Logical And/Or for Procedure Name search====
	~~If a procedure name is entered and any matching procedures are found,~~		As in previous SirPro versions, an asterisk (<tt>*</tt>) wildcard is valid in the <b>Procedure Name</b> field as a substitution character for any number of characters in the procedure name.
	~~a procedure list is presented.~~

	As in previous SirPro versions, ~~wildcard strings are valid in this field, using~~ an asterisk (<tt></tt>) as a substitution character for any number of characters in the procedure name. ~~For example: <code>XYZ</code> finds all procedure names ending in the string "XYZ", and <code>XYZ*</code> finds all procedure names beginning with "XYZ".~~

	~~New~~ in version 7.5:		These are added in version 7.5:
	<ul>		<ul>
	<li>A space indicates a logical And operation. Entering <code>PU ND</code> returns only those procedures whose names contain both the character sets "PU" and "ND", for example, <code>PUND-</code> or <code>PUMPKIN.SPENDER</code>. </li>		<li>A space indicates a logical And operation.
			<p>
			Entering <code>PU ND</code> returns only those procedures whose names contain both the character sets "PU" and "ND", for example, <code>PUND-</code> or <code>PUMPKIN.SPENDER</code>. </p></li>

	<li>A vertical bar (<tt>\|</tt>) indicates a logical Or operation. <code>PU\|ND</code> finds procedures containing the strings "PU" or "ND", for example, <code>PUMP</code>, <code>COLORPURPLE</code>, and <code>NINTENDO</code>. </li>		<li>A vertical bar (<tt>\|</tt>) indicates a logical Or operation. <p>
			<code>PU\|ND</code> finds procedures containing the strings "PU" or "ND", for example, <code>PUMP</code>, <code>COLORPURPLE</code>, and <code>NINTENDO</code>. </p></li>

	<li>Wildcards can be used in conjunction with the And/Or		<li>Wildcards can be used in conjunction with the And/Or selections.
	selections. <code>PUPR\|SCPR\|MOPR*</code> finds all		<p>
	procedures starting with any of these strings. </li>		<code>PUPR\|SCPR\|MOPR*</code> finds all
			procedures starting with any of these strings. </p></li>
	</ul>		</ul>

	~~<blockquote class="note">~~		For further details, see [[SirPro_procedure-list selection#procname\|Procedure Name]].
	~~<p><b>Note:</b> You must use caution when combining And and Or selections~~, ~~because the routine currently has a bias in favor of Or selections.~~
	Specifying <code>PUPR*\|~~SCPR AND</code> for example, does not work. It returns all procedures beginning~~
	~~with "PUPR", then attempts to add to the list~~
	~~any procedure with the characters "SCPR AND", which~~
	~~finds nothing because of the embedded space~~. ~~</p>~~
	~~</blockquote >~~

	====Field error tagging====		====Field error tagging====

JAL: /* Logical And/Or for Procedure Name search */ typos

2016-04-27T22:50:12Z

Logical And/Or for Procedure Name search: typos

← Older revision		Revision as of 22:50, 27 April 2016
Line 43:		Line 43:
	New in version 7.5:		New in version 7.5:
	<ul>		<ul>
	<li>A space indicates a logical And operation. Entering <code>PU ~~END~~</code> returns only those procedures whose names contain both the character sets "PU" and "ND", for example, <code>~~PUNP~~-</code> or <code>PUMPKIN.SPENDER</code>. </li>		<li>A space indicates a logical And operation. Entering <code>PU ND</code> returns only those procedures whose names contain both the character sets "PU" and "ND", for example, <code>PUND-</code> or <code>PUMPKIN.SPENDER</code>. </li>

	<li>A vertical bar (<tt>\|</tt>) indicates a logical Or operation. <code>PU\|ND</code> finds procedures containing the strings "PU" or "ND", for example, <code>PUMP</code>, <code>COLORPURPLE</code>, and <code>NINTENDO</code>. </li>		<li>A vertical bar (<tt>\|</tt>) indicates a logical Or operation. <code>PU\|ND</code> finds procedures containing the strings "PU" or "ND", for example, <code>PUMP</code>, <code>COLORPURPLE</code>, and <code>NINTENDO</code>. </li>
Line 49:		Line 49:
	<li>Wildcards can be used in conjunction with the And/Or		<li>Wildcards can be used in conjunction with the And/Or
	selections. <code>PUPR\|SCPR\|MOPR*</code> finds all		selections. <code>PUPR\|SCPR\|MOPR*</code> finds all
	procedures starting with any of ~~the above~~ strings. </li>		procedures starting with any of these strings. </li>
	</ul>		</ul>

Line 58:		Line 58:
	any procedure with the characters "SCPR AND", which		any procedure with the characters "SCPR AND", which
	finds nothing because of the embedded space. </p>		finds nothing because of the embedded space. </p>
	</blockquote >		</blockquote >

	====Field error tagging====		====Field error tagging====

JAL: /* Other features */ remove Longer procedure names -- may be in 7.7

2016-04-27T22:06:53Z

Other features: remove Longer procedure names -- may be in 7.7

← Older revision		Revision as of 22:06, 27 April 2016
Line 62:		Line 62:
	====Field error tagging====		====Field error tagging====
	In case of an error in field specification, for example an invalid <b>Context</b> field, the field is tagged red and an error message is displayed above the PF keys.		In case of an error in field specification, for example an invalid <b>Context</b> field, the field is tagged red and an error message is displayed above the PF keys.

	~~====Longer procedure names====~~
	~~Still TBD.~~

	====Better subsystem transfer====		====Better subsystem transfer====

JAL: /* Other features */ add content to empty headers

2016-04-27T21:39:27Z

Other features: add content to empty headers

← Older revision		Revision as of 21:39, 27 April 2016
Line 64:		Line 64:

	====Longer procedure names====		====Longer procedure names====
			Still TBD.

	====Better subsystem transfer====		====Better subsystem transfer====
			Users can now move from any screen in SirPro, for example, to a screen in SirMon by specifying <code>MON 3.2</code>, for example, in the command line. The <code>3</code> refers to option 3 from the SirMon main menu, which opens the <b>USER Monitor Options</b> screen. The <code>2</code> refers to option 2 on the <b>USER Monitor Options</b> screen, which invokes the display of system users and measures of their level of activity.

			Similarly, <code>SCAN <i>n.n</i></code> takes you to SirScan screens, <code>FILE <i>n.n</i></code> to SirFile screens, and <code>PRO <i>n.n</i></code> to SirPro screens.

	====Save profile for each change====		====Save profile for each change====
			Most changes you make to SirPro screens are saved, including entries like last item searched for and any procedure selection restrictions, and they are restored if you exit and then return to SirPro.

	==Procedure List screen (ProcList/PL)==		==Procedure List screen (ProcList/PL)==

JAL: /* Search Strings */ replace question marks with correct length

2016-04-27T20:35:54Z

Search Strings: replace question marks with correct length

← Older revision		Revision as of 20:35, 27 April 2016
Line 12:		Line 12:

	====Search Strings====		====Search Strings====
	The maximum length has been increased to ??.		The maximum length has been increased to 66 for each of the five search string fields.

	====# of context lines====		====# of context lines====

JAL: minor cleanup

2016-01-07T00:15:39Z

minor cleanup

← Older revision		Revision as of 00:15, 7 January 2016
Line 232:		Line 232:

	<blockquote class="note">		<blockquote class="note">
	<p><b>Note:</b> If a procedure search is required for the words "FILE" or "GROUP," it must be entered as: </p>		<p><b>Note:</b> If a procedure name search is required for the words "FILE" or "GROUP," it must be entered as: </p>
	<p class="code">PL file FILE <i>filename</i></p>		<p class="code">PL file FILE <i>filename</i></p>
	<p>		<p>

JAL: minor cleanup

2016-01-06T23:48:29Z

minor cleanup

← Older revision		Revision as of 23:48, 6 January 2016
Line 237:		Line 237:
	where: </p>		where: </p>
	<ul>		<ul>
	<li><code>file</code> indicates procedures ~~containing~~ the word "file."</li>		<li><code>file</code> indicates procedures whose name contains the word "file."</li>

	<li><code>FILE</code> is required because the context is not automatically added if searching for the words "FILE" or "GROUP." </li>		<li><code>FILE</code> is required because the context is not automatically added if searching for the words "FILE" or "GROUP." </li>
	</ul>		</ul>