View source for SirPro change management tools and functions

==Overview==
Managed-update commands allow the manipulation and promotion of just the updates you make to a procedure, "deltas," instead of preserving and working with a sequence of updated copies of the entire procedure or entire procedure file. Managed-update commands are available in SirPro if the change management system, <var class="product">[[SirLib]]</var>, is active in the Online.
<p class="note"><b>Note:</b>
Managed-update commands are not available in [[RKWeb]]; they require the SirPro TN3270 interface. </p> 
<p>
The output from a managed-update command that produces update
procedures contains a single-line comment describing the creator,
date, time, and source file for the change. </p>
<p>
The managed-update commands are entered as prefix commands on the procedure list screen (see [[SirPro procedure-list operations]]).
These prefix commands are:</p>

<table class="thJustBold">
<tr><th>X</th>
<td><b>XCompare</b>. 
<p>Compares two versions of a procedure and creates a third procedure containing the differences between the two. This output is an "update procedure," the physical unit managed by the change management system.</p></td></tr>

<tr><th>Q</th>
<td><b>Sequence</b>. 
<p>Creates both a working and sequenced version of a procedure that are the later input to <var>XCompare</var>.</p></td></tr>

<tr><th>N</th>
<td><b>New</b>. 
<p>
Creates a "differences" update procedure similar to <var>XCompare</var>, but which is the source for a new procedure.</p></td></tr>

<tr><th>K</th>
<td><b>Erase</b>. 
<p>Creates an update procedure similar to <var>XCompare</var> output, but telling <var class="product">SirLib</var> to perform a logical delete on the procedure.</p></td></tr>

<tr><th>Z</th>
<td><b>ReSequence</b>. 
<p>Creates a special update procedure to reorder the internal sequence numbers of a procedure.</p></td></tr>

<tr><th>U</th> 
<td><b>Undo</b>.
<p>Like <var>Q</var>, but may only be executed against a change deck. It adds the change deck to the code for the working procedure, but <b>not</b> to the code from the sequenced copy. Added in version 7.5.</p></td></tr>

<tr><th>Y</th>
<td><b>Refresh</b>.
<p>Refreshes your local working copy of a procedure with changes that have been checked in by other programmers since the working copy was originally taken from
the source procedure file. Added in version 7.5.</p></td></tr>
</table>

The Procedure List screen is the main working environment for the
programmer in the <var class="product">SirPro</var>/<var class="product">SirLib</var>-controlled environment. This screen, and others like it,
provide access to all procedure activity in <var class="product">Model&nbsp;204</var>.
For details on the use of <var class="product">SirLib</var>, including the special commands for managed updates, see [[SirLib]].
Only the special Procedure List screen
prefix commands (<code>Q</code>, <code>X</code>, <code>K</code>, <code>N</code>, <code>Z</code>, <code>U</code>, and <code>Y</code>) for creating and manipulating managed updates are explained here.

The <code>Q</code>, <code>X</code>, <code>N</code>, <code>K</code>, <code>Z</code>, <code>U</code>, and <code>Y</code> prefix commands are used to generate "working" base and sequenced copies of procedures and to generate updates from those copies.
Type one of these managed update commands to the left of the selected procedure, and press the Enter key.
<var class="product">SirPro</var> then presents one of the managed update screens to get
further details on the managed update.
Those screens are shown in the following detailed sections.

{{Template:SirPro commands}}

==SirPro change management overview==
<!-- Page name: SirPro change management overview-->

Notice that no sequenced copy of a procedure is needed for New, Erase,
or Resequence operations. <var>Q</var> (seQuence) is the managed update equivalent of a Copy, just as <var>N</var> (New) is the equivalent of Create, and <var>K</var> (Klobber, or Erase) is the equivalent of Delete.
<var>XCompare</var> has no direct equivalent in the "unmanaged" command structure, though coupled with later reconfiguration using the output update procedure, it is analogous to moving finished changes to a staging area. Resequencing is of course a special purpose function with no "unmanaged" corollary.

<p class="caption" style="width:444px">How a change progresses through SirLib</p>
<p class="figure">[[File:SirLibChange.png|444px]]</p>

In the example above, procedure <code>TEMP</code> exists in file <code>PFILE1</code> (upper left). The programmer uses the <code>Q</code> command to copy <code>TEMP</code> into <code>WORKFILE</code>, getting both a working and a <code>SEQ</code> version of the procedure. 

A single line of new code is inserted in <code>TEMP</code> (the line
<code>PRINT STATE AND ZIP AT 40</code>).
Using <var>XCompare</var>, the update is generated to file <code>CHANGES</code>, and named <code>PFILE1.CHG1.TEMP</code>.
A project leader defines the project name <code>CHG1</code> in <code>CONTROL.PFILE1</code>.

Finally, <var class="product">SirLib</var>'s ReConfiguration function is used to create a "BASE" version of the procedure, so the update can be backed out if necessary, and the original procedure <code>TEMP</code> is deleted.
The update procedure <code>PFILE1.CHG1.TEMP</code> is applied to <code>BASE.TEMP</code>
to create the new executable procedure <code>TEMP</code>.
<p>
The final state of <code>PFILE1</code> is shown lower right.</p>

==See also==
{{Template:SirPro topic list}}

[[Category: SirPro]]