Release notes for SirPro V7.5: Difference between revisions

From m204wiki
Jump to navigation Jump to search
m (add pointers to PL feature)
 
(26 intermediate revisions by 4 users not shown)
Line 1: Line 1:
This document lists the changes that have been made for <var class="product">SirPro</var> version S7.5. It requires <var class="product">Model 204</var> release 7.5 or higher.
This document lists the changes that have been made for <var class="product">SirPro</var> version 7.5. <var class="product">SirPro</var> 7.5 requires <var class="product">Model&nbsp;204</var> V7.5 or higher.


==Procedure Search screen (SEARCH)==
<var class="product">SirPro</var> is a member of the <var class="product">[[RKTools]]</var> product family; see also the [[Release notes for RKTools V7.5|release notes for RKTools version 7.5]].
 
The previous version of <var class="product">SirPro</var> was 707, available in March, 2010.
 
==Procedure Search screen (ProcSearch/PS)==
Option 1, Procedure List, from the [[SirPro#SirPro main menu|SirPro main menu]] brings you to this screen.


===Field changes===
===Field changes===
The searching capabilities have been enhanced to provide better impact analysis. The following fields has been changed or added.
The searching capabilities are enhanced to provide better impact analysis. The following fields are changed or added.
====Enhanced Procedure name search====
 
Enter a procedure name or search mask.  If a procedure 
====Search Strings====
name is entered and any matching procedures are found, 
The maximum length has been increased to 66 for each of the five search string fields.
a procedure list is presented.                         
                                                       
Wildcard strings are valid in this field, using "*" as 
a substitution character for any number of characters in
the procedure name.  For example: *XYZ will find all   
procedure names ending in the string XYZ, and XYZ* will
find all procedure names beginning with XYZ.           
                                                       
A space indicates "AND", so entering "PU END" would   
return only those procedures whose names contain both 
the character sets "PU" and "ND", so, PUNP-END or     
PUMPKIN.SPENDER.                                       
                                                       
The "or" bar indicates "OR", so "PU|ND" would find any 
procedures containing the strings "PU" or "ND".  This 
might include "PUMP", "COLORPURPLE" and "NINTENDO".   
                                                       
Wildcards can be used in conjuntion with the AND/OR   
selections, so "PUPR*|SCPR*|MOPR*" would find all     
procedures starting with any of the above strings. 
                                                   
The routine currently has a bias in favor of "OR"   
selections, so a selection like "PUPR*|SCPR AND"   
won't work.  It will return all procedures beginning
with PUPR, then will attempt to add to the list     
any procedure with the characters "SCPR AND", which 
will find nothing, because of the embedded space.   
So do not combine AND and OR selections.


====Search strings====
The maximum length has bene increased to nn.
====# of context lines====
====# of context lines====
Numeric indicator (0 through 9) of number of lines of code  
This numeric indicator (0 through 9) specifies the number of lines of code to display before and after the line containing the search string.  
to display before and after the line containing the  
 
search string.                                                      
====# occurrences to display====
====# occurrences to find====
This number (from 1 to 999) specifies how many occurrences of a search string within a procedure to display.
The number (from 1 to 999) that specifies the number of occurrences within a procedure that will
 
be displayed.
====Hide SEQs/BASEs====
====Hide SEQa/BASEs====
SirPro users who are also SirLib users can display or hide SEQ. and BASE. procedures, which are used in code management functions but are not intended to be edited directly.  
SirLib users will see a prompt and entry area that allows     
 
the display or hiding of SEQ. and BASE. procedures, which    
are used in code management functions but are not intended    
to be edited directly. Enter "Y" to prevent this procedures 
from being displayed, and "N" to display them.               
====Ignore Comment Lines====
====Ignore Comment Lines====
If set to Y it will ignore any Soul formatted comment lines. If set to N all found lines will be included.
You can ignore any SOUL-formatted comment lines or include all found lines.


===New Function Keys===
===New function keys===
====PF5 - Toggle between case sensitive/insensitive====
====PF5 - Toggle between case sensitive/insensitive====
In Case Sensitive mode, a search for "html" would only find the      
In case-sensitive mode, a search for "html" finds only the lowercase version of that string. In case-insensitive mode, the same search finds procedures containing either "html" or "HTML".
lower-case version of that string. In Case-Insensitive mode
                                           
the same search would find procedures containing either      
"html" or "HTML".                                            
====PF6 - Create Proc====
====PF6 - Create Proc====
Enter the [[SoulEdit]] editor within a skeleton procedure-creation template.
===Other features===
===Other features===
====Longer proc names====
 
====Logical And/Or for Procedure Name search====     
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. 
 
These are added in version 7.5:
<ul>
<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. <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 selections.
<p>
<code>PUPR*|SCPR*|MOPR*</code> finds all     
procedures starting with any of these strings. </p></li>
</ul>
 
For further details, see [[SirPro_procedure-list selection#procname|Procedure Name]].
 
====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.
 
====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)==
[[SirPro procedure-list operations#Overview|This screen]] displays a list of the procedures that satisfy the specifications made on the Procedure Search screen described above.


==Procedure List screen (PL)==
===Field changes===
===Field changes===
====Command Line====
Most of the functions able to be performed on the Search screen may now be done as commands in the Command Line field. In addition commands can be strung together using the semicolon as a delimiter. For example to switch to a new field and display those procedures that have HELP in their name can be done as:
FL SIRIUS;A HELP


If a command is in error it will now leave the command on the screen so it can be amended.
====Command line====
Most of the functions you can perform on the Procedure Search screen may now be done as commands in the command line field. In addition, You can string commands together using a semicolon as a delimiter.
 
For example, to switch to a new file, SIRIUS, and display those procedures that have "HELP" in their name, specify:
<p class="code">FL SIRIUS;A HELP</p>
 
An erroneous command remains on the screen so it can be amended.


Most commands have a full name and an abbreviation.
Most commands have a full name and an abbreviation.


<table class="thJustBold">
<table class="thJustBold">
<caption>Procedure List commands</caption>
<tr class="head"><th>Command</th><th>Description</th></tr>
<tr class="head"><th>Command</th><th>Description</th></tr>


<tr><th>PROCS&nbsp;|&nbsp;A&nbsp;[xxxx]</th>
<tr><th>{PROCS&nbsp;|&nbsp;A}&nbsp;[<i>xxxx</i>]</th>
<td>
<td>Changes the procedure name filter to '<i>xxxx</i>'. Wildcarding is assumed and fully supported, so for instance, the command <code>PROCS CADDIE</code> finds all procedures with the string "CADDIE" in its name.  
Changes the procedure name filter to 'xxxx'. Wildcarding
<p>
is assumed and fully supported, so for instance, the
If you use specific wildcard characters, the search is done for the
command 'PROCS CADDIE' will find all procedures with
specified pattern, so <code>PROCS I.*</code> restricts the display
the string 'CADDIE' in its name. If specific wildcard
to procedures beginning with "I". </p>
characters are used, the search is done for the
<p>
specified pattern, so 'PROCS I.*' restricts the display
If the filter name <var class="term">xxxx</var> is omitted, all procedures are displayed. </p>
to procedures beginning with 'I.'
If the filter name 'xxxx' is omitted then all procedures
are displayed.
</td></tr>
</td></tr>


<tr><th>AND xxxx</th>
<tr><th>AND <i>xxxx</i></th>
<td>
<td>Changes the procedure name filter by combining <var class="term">xxxx</var> with the existing value with And logic, applying the "distributive law" if necessary. For instance, if the current value of the procedure name filter is <code>A|B</code>, an <code>AND C</code> command changes it to <code>A C|B C</code> by applying the distributive law:
Changes the procedure name filter by combining 'xxx' with  
<p class="code">(A|B) C -> A C|B C </p>
the existing value with AND logic, applying 'distributive
Hence this filters the current display listing to show only those that also meet the new criteria.  
law' if necessary. For instance, if the current value of the  
procedure name filter is 'A|B', an 'AND C' command will
change it to 'A C|B C' by applying 'distributive law':
  (A|B) C -> A C|B C.
Hence this filters the current display listing to show
only those that also meet the new criteria.
</td></tr>
</td></tr>


<tr><th>+AND xxxx</th>
<tr><th>+AND <i>xxxx</i></th>
<td>
<td>Changes the procedure name filter by combining <var class="term">xxxx</var> with the existing value with And logic, but <b>without</b> applying the "distributive law." It just simply appends <var class="term">xxxx</var> to the existing procedure name filter. For instance, if the current value of the procedure name filter is <code>A|B</code>, an <code>AND C</code> command changes it to <code>A|B C</code>.   
Changes the procedure name filter by combining 'xxx' with  
the existing value with AND logic, but WITHOUT applying  
'distributive law'. It just simply appends 'xxxx' to the  
existing procedure name filter. For instance, if the current
value of the procedure name filter is 'A|B', an 'AND C'
command will change it to 'A|B C'.   
</td></tr>
</td></tr>
      
      
<tr><th>OR xxxx</th>
<tr><th>OR <i>xxxx</i></th>
<td>
<td>Changes the procedure name filter by combining <var class="term">xxxx</var> with the existing value with Or logic. For instance, if the current value of the procedure name filter is <code>A|B</code>, an <code>OR C</code> command changes it to <code>A|B|C</code>. Hence this adds additional procedures to the display listing.
Changes the procedure name filter by combining 'xxxx' with  
the existing value with OR logic. For instance, if the  
current value of the procedure name filter is 'A|B', an
'OR C' command will change it to 'A|B|C'. Hence this  
adds additional procedures to the display listing.              
</td></tr>
</td></tr>


<tr><th>CREATEPROC | CREATE | CP [xxxx]</th>
<tr><th nowrap>{CREATEPROC | CREATE | CP} [<i>xxxx</i>]</th>
<td>
<td>Creates a new procedure named <code><i>xxxx</i></code> in the current file/group context. If there is no <var class="term">xxxx</var> specified, an unnamed procedure is created.   
Creates a new procedure named 'xxxx' in the current file/group  
context. If there is no 'xxxx' specified, an unnamed    
procedure will be created.   
</td></tr>
</td></tr>


<tr><th>FILE | FL xxx</th>
<tr><th>{FILE | FL} <i>xxx</i></th>
<td>
<td>Changes the file context to <var class="term">xxx</var> using the existing privileges to the file.
Changes the file context using the existing privileges to  
the file.
</td></tr>
</td></tr>


<tr><th>FLP xxx </th>
<tr><th>FLP <i>xxx</i> </th>
<td>
<td>Changes the file context to <var class="term">xxx</var> with a prompt for password.
Changes the file context with prompt for password.
</td></tr>
</td></tr>


<tr><th>GROUP | GP xxx</th>
<tr><th>{GROUP | GP} <i>xxx</i></th>
<td>
<td>Changes the group context to <var class="term">xxx</var> using the existing privileges to the group.   
Changes the group context using the existing privileges to  
the group.   
</td></tr>
</td></tr>
            
            
<tr><th>GPP xxx</th>
<tr><th>GPP <i>xxx</i></th>
<td>
<td>Changes the group context to <var class="term">xxx</var> with a prompt for password.
Changes the group context with prompt for password.
</td></tr>
</td></tr>


<tr><th>PASSWORD | PWD</th>
<tr><th>PASSWORD | PWD</th>
<td>
<td>Reopens the current file or group with a prompt for password. It implies a switch of privileges associated with the password to the current file or group.
Reopens the current file or group with prompt for password.
It implies a switch of privileges associated with the  
password to the current file or group.
</td></tr>
</td></tr>


<tr><th>LASTID | LID [xxx]</th>
<tr><th>{LASTID | LID} [<i>xxx</i>]</th>
<td>
<td>Changes the value of the <b>Last Updater ID</b> field. The valid value for <var class="term">xxx</var> is a string not longer than 10, or is a blank.               
Changes the value of 'Last Updater ID'.    
The valid value for 'xxx' is a string not longer than 10, or    
blank.               
</td></tr>
</td></tr>


<tr><th>HAS | HA | H [xxx]</th>
<tr><th>{HAS | HA | H} [<i>xxx</i>]</th>
<td>
<td>Changes the selection to procedures containing the specified string <var class="term">xxx</var>. <code>HAS $GETG</code> restricts procedures to those containing <code>$GETG</code>. <var>HAS</var> does not support wildcards, so a search for <code>locate*</code> looks for the string "locate*".  
Changes the selection to procedures containing the specified
<p>
string 'xxx'. 'HAS $GETG' restricts procedures to those
If the string <var class="term">xxx</var> is omitted, the search string is cleared. </p></td></tr>
containing $GETG. HAS does not support wildcards, so a
search for 'locate*' will look for the string 'locate*'.
If the string 'xxx' is omitted the search string is cleared.
</td></tr>


<tr><th>DISPLAY&nbsp;|&nbsp; CODE | SHOW | CL [n]</th>
<tr><th>{DISPLAY&nbsp;|&nbsp;CODE | SHOW | CL} [<i>n</i>]</th>
<td>
<td>With these commands you can alter the number of lines of code to be displayed, beginning with the first of any found search string. If no search string was specified on the previous screen, this command has no effect.  
With these commands you can alter the number of lines of
<p>
code to be displayed beginning with the first of any found
Valid values for <var class="term">n</var> are 0 through 9. If there is no <var class="term">n</var> specified, it gives a default value of 0 to the <b># of context lines</b> field. </p>
search string. Obviously, if no search string was
specified on the previous screen, this command has no
effect. Valid values for 'n' are 0 through 9. If there
is no 'n' specified,it will give a default value of 0 to
the '# of context lines'
</td></tr>
</td></tr>


<tr><th>OCC [nnn]</th>
<tr><th>OCC [<i>nnn</i>]</th>
<td>
<td>Changes the value of the <b># of occurrences to find</b> field. The valid value for the optional <var class="term">nnn</var> is a number between 1 and 999 or it is <var>ALL</var>. If there is no <var class="term">nnn</var> specified, it gives a default value of 1 to the <b># of occurrences to find</b> field.
Changes the value of '# of occurrences to find'. The valid
value for the optional 'nnn' is either a number between 1
and 999 or 'ALL'. If there is no 'nnn' specified, it will
give a default value of 1 to the '# of occurrences to find'.
</td></tr>
</td></tr>


<tr><th>IC [x]</th>
<tr><th>IC [<i>x</i>]</th>
<td>
<td>Changes the value of the <b>Ignore Comment lines</b> field. The valid values for the optional <var class="term">x</var> are <code>Y</code> and <code>N</code>. If there is no <var class="term">x</var> specified, it gives a default value of <code>Y</code> to <b>Ignore Comment lines</b>.
Changes the value of 'Ignore Comment lines'. The valid value   
for the optional 'x' is 'Y' or 'N'. If there is no 'x'
specified, it will give a default value of 'Y' to the
'Ignore Comment lines'.
</td></tr>
</td></tr>
        
        
<tr><th>HS [x]</th>
<tr><th>HS [<i>x</i>]</th>
<td>
<td>Changes the value of the <b>Hide SEQs/BASEs</b> field. The valid value for the optional <var class="term">x</var> is <code>Y</code> or <code>N</code>. If there is no <var class="term">x</var> specified, it gives a default value of <code>Y</code> to <b>Hide SEQs/BASEs</b>.  
Changes the value of 'Hide SEQs/BASEs'. The valid value for  
the optional 'x' is 'Y' or 'N'. If there is no 'x'
specified, it will give a default value of 'Y' to the
'Hide SEQs/BASEs'.  
</td></tr>
</td></tr>
</table>
</table>


====Selection field====
====Sel (selection) field====
The following procedure selection option has been added:
The following procedure-selection prefix commands are added:
 
  E  (Edit):  Invokes the [[soulEdit|SoulEditor]].


The following new selection options a part of the
<ul>
Sirius Configuration and Change Control System (SirLib).  If SirLib is
<li><b>E (Edit)</b>
not installed then these commands are not valid.  Further information
<p>
on managed updates and the Configuration Management system is in the
Invokes [[SoulEdit]], the SOUL editor.
SirLib User's Guide.
</p>


<table class="thJustBold">
<li><b>U (Undo)</b>
<tr class="head"><th>Command</th><th>Description</th></tr>
<p>
 
This <i>[[SirLib]]-required</i> command performs the same operation as <var>Q</var>, resulting in the creation of a "working"
<tr><th>U (Undo)</th>
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
<td>
May only be executed against a change deck.  This command
performes the same operation as a Q, resulting in a "working"
procedure and a sequenced copy of that procedure being created
in the user's selected development procfile. However, the U
command specifically includes the change deck against which it is
executed in the code for the working procedure, but NOT 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 U command is executed.
deck. </p>
 
<p>
Typically, the U command is used to recreate the state of development
For further details, see [[SirPro change management tools and functions#undoCmd|U (Undo)]]. </p></li>
when the programmer has accidentally deleted the procedures she
was working on, either manually, or via the "Clean-up" switch on
the Xcompare screen.
 
The U command is a special-use feature, and there are a number
of ways in which it will fail to work -- most notably, if the
selected change deck is somewhere in the middle of a series of
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>
<li><b>Y (Refresh)</b>
<td>
<p>
This change-control prefix command provides a special check-out
This <i>[[SirLib]]-required</i> command lets you "refresh" your 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 you checked out the working copy from
the source procedure file. "Y" is applied against the working
the source procedure file. </p>
procedure, a screen is presented, and the result is a new
<p>
working procedure with all updates applied AND the user's current
For further details, see [[SirPro change management tools and functions#refresh|Y (Refresh)]]. </p>
changes still in place, and a sequenced copy that has all updates
</li>
applied, but the user's current changes not in place.
</ul>
 
In other words, the "Y" command is very much like a "Q" 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==
(Adrian to complete)
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>
<p>
For further details, see [[RKTools#PL command|PL command]]. </p>


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

Latest revision as of 19:19, 4 May 2016

This document lists the changes that have been made for SirPro version 7.5. SirPro 7.5 requires Model 204 V7.5 or higher.

SirPro is a member of the RKTools product family; see also the release notes for RKTools version 7.5.

The previous version of SirPro was 707, available in March, 2010.

Procedure Search screen (ProcSearch/PS)

Option 1, Procedure List, from the SirPro main menu brings you to this screen.

Field changes

The searching capabilities are enhanced to provide better impact analysis. The following fields are changed or added.

Search Strings

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

# of context lines

This numeric indicator (0 through 9) specifies the number of lines of code to display before and after the line containing the search string.

# occurrences to display

This number (from 1 to 999) specifies how many occurrences of a search string within a procedure to display.

Hide SEQs/BASEs

SirPro users who are also SirLib users can display or hide SEQ. and BASE. procedures, which are used in code management functions but are not intended to be edited directly.

Ignore Comment Lines

You can ignore any SOUL-formatted comment lines or include all found lines.

New function keys

PF5 - Toggle between case sensitive/insensitive

In case-sensitive mode, a search for "html" finds only the lowercase version of that string. In case-insensitive mode, the same search finds procedures containing either "html" or "HTML".

PF6 - Create Proc

Enter the SoulEdit editor within a skeleton procedure-creation template.

Other features

Logical And/Or for Procedure Name search

As in previous SirPro versions, an asterisk (*) wildcard is valid in the Procedure Name field as a substitution character for any number of characters in the procedure name.

These are added in version 7.5:

  • A space indicates a logical And operation.

    Entering PU ND returns only those procedures whose names contain both the character sets "PU" and "ND", for example, PUND- or PUMPKIN.SPENDER.

  • A vertical bar (|) indicates a logical Or operation.

    PU|ND finds procedures containing the strings "PU" or "ND", for example, PUMP, COLORPURPLE, and NINTENDO.

  • Wildcards can be used in conjunction with the And/Or selections.

    PUPR*|SCPR*|MOPR* finds all procedures starting with any of these strings.

For further details, see Procedure Name.

Field error tagging

In case of an error in field specification, for example an invalid Context field, the field is tagged red and an error message is displayed above the PF keys.

Better subsystem transfer

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

Similarly, SCAN n.n takes you to SirScan screens, FILE n.n to SirFile screens, and PRO n.n to SirPro screens.

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)

This screen displays a list of the procedures that satisfy the specifications made on the Procedure Search screen described above.

Field changes

Command line

Most of the functions you can perform on the Procedure Search screen may now be done as commands in the command line field. In addition, You can string commands together using a semicolon as a delimiter.

For example, to switch to a new file, SIRIUS, and display those procedures that have "HELP" in their name, specify:

FL SIRIUS;A HELP

An erroneous command remains on the screen so it can be amended.

Most commands have a full name and an abbreviation.

Procedure List commands
CommandDescription
{PROCS | A} [xxxx] Changes the procedure name filter to 'xxxx'. Wildcarding is assumed and fully supported, so for instance, the command PROCS CADDIE finds all procedures with the string "CADDIE" in its name.

If you use specific wildcard characters, the search is done for the specified pattern, so PROCS I.* restricts the display to procedures beginning with "I".

If the filter name xxxx is omitted, all procedures are displayed.

AND xxxx Changes the procedure name filter by combining xxxx with the existing value with And logic, applying the "distributive law" if necessary. For instance, if the current value of the procedure name filter is A|B, an AND C command changes it to A C|B C by applying the distributive law:

(A|B) C -> A C|B C

Hence this filters the current display listing to show only those that also meet the new criteria.

+AND xxxx Changes the procedure name filter by combining xxxx with the existing value with And logic, but without applying the "distributive law." It just simply appends xxxx to the existing procedure name filter. For instance, if the current value of the procedure name filter is A|B, an AND C command changes it to A|B C.
OR xxxx Changes the procedure name filter by combining xxxx with the existing value with Or logic. For instance, if the current value of the procedure name filter is A|B, an OR C command changes it to A|B|C. Hence this adds additional procedures to the display listing.
{CREATEPROC | CREATE | CP} [xxxx] Creates a new procedure named xxxx in the current file/group context. If there is no xxxx specified, an unnamed procedure is created.
{FILE | FL} xxx Changes the file context to xxx using the existing privileges to the file.
FLP xxx Changes the file context to xxx with a prompt for password.
{GROUP | GP} xxx Changes the group context to xxx using the existing privileges to the group.
GPP xxx Changes the group context to xxx with a prompt for password.
PASSWORD | PWD Reopens the current file or group with a prompt for password. It implies a switch of privileges associated with the password to the current file or group.
{LASTID | LID} [xxx] Changes the value of the Last Updater ID field. The valid value for xxx is a string not longer than 10, or is a blank.
{HAS | HA | H} [xxx] Changes the selection to procedures containing the specified string xxx. HAS $GETG restricts procedures to those containing $GETG. HAS does not support wildcards, so a search for locate* looks for the string "locate*".

If the string xxx is omitted, the search string is cleared.

{DISPLAY | CODE | SHOW | CL} [n] With these commands you can alter the number of lines of code to be displayed, beginning with the first of any found search string. If no search string was specified on the previous screen, this command has no effect.

Valid values for n are 0 through 9. If there is no n specified, it gives a default value of 0 to the # of context lines field.

OCC [nnn] Changes the value of the # of occurrences to find field. The valid value for the optional nnn is a number between 1 and 999 or it is ALL. If there is no nnn specified, it gives a default value of 1 to the # of occurrences to find field.
IC [x] Changes the value of the Ignore Comment lines field. The valid values for the optional x are Y and N. If there is no x specified, it gives a default value of Y to Ignore Comment lines.
HS [x] Changes the value of the Hide SEQs/BASEs field. The valid value for the optional x is Y or N. If there is no x specified, it gives a default value of Y to Hide SEQs/BASEs.

Sel (selection) field

The following procedure-selection prefix commands are added:

  • E (Edit)

    Invokes SoulEdit, the SOUL editor.

  • U (Undo)

    This SirLib-required command performs the same operation as Q, resulting in the creation of a "working" procedure and a sequenced copy of that procedure. However, the U 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 not in the code from the sequenced copy. In other words, it recreates the state of the development procedures that created the change deck.

    For further details, see U (Undo).

  • Y (Refresh)

    This SirLib-required command lets you "refresh" your local working copy of a procedure with changes that have been checked in by other programmers since you checked out the working copy from the source procedure file.

    For further details, see Y (Refresh).

New PL subsystem

The new PL subsystem and fast-path command allows direct entry to the Procedure List screen in SirPro. The command format is:

PL [procedurePattern] [FILE filename | GROUP groupname]

For further details, see PL command.

Enhanced Help

(in progress)

Retrieved from "https://m204wiki.rocketsoftware.com/index.php?title=Release_notes_for_SirPro_V7.5&oldid=84037"