SirPro change management tools and functions - Revision history

JAL: mention RKWeb equivalents

2017-06-22T00:45:17Z

mention RKWeb equivalents

← Older revision		Revision as of 00:45, 22 June 2017
Line 1:		Line 1:
	==Overview==		==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.		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		The output from a managed-update command that produces update
	procedures contains a single-line comment describing the creator,		procedures contains a single-line comment describing the creator,
	date, time, and source file for the change.		date, time, and source file for the change. </p>
	<p>		<p>
	The managed-update commands are entered as prefix commands on the procedure list screen (see [[SirPro procedure-list operations]]).		The managed-update commands are entered as prefix commands on the procedure list screen (see [[SirPro procedure-list operations]]).

JAL: minor formatting

2016-04-28T22:08:28Z

minor formatting

← Older revision		Revision as of 22:08, 28 April 2016
Line 30:		Line 30:
	<td><b>ReSequence</b>.		<td><b>ReSequence</b>.
	<p>Creates a special update procedure to reorder the internal sequence numbers of a procedure.</p></td></tr>		<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>		</table>

Line 37:		Line 46:
	For details on the use of <var class="product">SirLib</var>, including the special commands for managed updates, see [[SirLib]].		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		Only the special Procedure List screen
	prefix commands (<code>Q</code>, <code>X</code>, <code>K</code>, <code>N</code>, and <code>Z</code>) for creating and manipulating managed updates are explained here.		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>, and <code>Z</code> prefix commands are used to generate "working" base and sequenced copies of procedures and to generate updates from those copies.		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		Type one of these managed update commands to the left of the selected procedure, and press the Enter key.
	the Enter key.
	<var class="product">SirPro</var> then presents one of the managed update screens to get		<var class="product">SirPro</var> then presents one of the managed update screens to get
	further details on the managed update.		further details on the managed update.

JAL: replace command content with a template

2015-10-28T22:53:50Z

replace command content with a template

Show changes

JAL: mixed case for XCOMPARE

2015-10-28T16:18:17Z

mixed case for XCOMPARE

Show changes

JAL: mixed case for XCOMPARE

2015-10-28T16:09:19Z

mixed case for XCOMPARE

Show changes

JAL: add graphics

2015-09-11T19:34:59Z

add graphics

Show changes

JAL: add heading

2015-07-28T20:40:20Z

add heading

← Older revision		Revision as of 20:40, 28 July 2015
Line 1:		Line 1:
	<!-~~-Page automatically generated by CMSTOWIK EXEC~~ and ~~will be~~		==Overview==
	automatically replaced -- any manual edits will be lost.		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.
	~~You've been warned. .. (Page built by JAL at~~ the ~~SIRIUS VM;~~ file~~: FUNPGNEW SYSUT2) -->~~
	~~<!-~~- ~~Page name:~~ SirPro change management ~~tools and functions--~~>

	~~Managed update commands are available if the change~~		The output from a managed-update command that produces update
	~~management system, <var class="product">[[SirLib]]</var>, is active in the Online.~~		procedures contains a single-line comment describing the creator,
	~~Managed update commands allow the manipulation and promotion of update procedures,~~		date, time, and source file for the change.
	~~"deltas," instead of entire procedures or entire procedure files.~~
	The output from ~~all~~ managed update ~~commands~~ that ~~produce~~ update
	procedures ~~always contain~~ 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		The managed-update commands are entered as prefix commands on the Procedure List screen
	(see [[SirPro procedure-list operations]]).		(see [[SirPro procedure-list operations]]).
	These prefix commands are:</p>		These prefix commands are:</p>
Line 19:		Line 13:
	<tr><th>X</th>		<tr><th>X</th>
	<td><b>Xcompare</b>.		<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>		<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>		<tr><th>Q</th>
Line 26:		Line 20:

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

	<tr><th>K</th>		<tr><th>K</th>
Line 42:		Line 38:
	For details on the use of <var class="product">SirLib</var>, including the special commands for managed updates, see the <var class="book">[[Media:LibrNew.pdf\|SirLib User's Guide]]</var>.		For details on the use of <var class="product">SirLib</var>, including the special commands for managed updates, see the <var class="book">[[Media:LibrNew.pdf\|SirLib User's Guide]]</var>.
	Only the special Procedure List screen		Only the special Procedure List screen
	prefix commands (Q, X, K, N, and Z) for creating and manipulating		prefix commands (<code>Q</code>, <code>X</code>, <code>K</code>, <code>N</code>, and <code>Z</code>) for creating and manipulating managed updates are explained here.
	managed updates are explained here.

	The <code>Q</code>, <code>X</code>, <code>N</code>, <code>K</code>, and <code>Z</code> prefix commands are used to generate "working" base and sequenced copies of procedures and to generate updates from those copies.		The <code>Q</code>, <code>X</code>, <code>N</code>, <code>K</code>, and <code>Z</code> prefix commands are used to generate "working" base and sequenced copies of procedures and to generate updates from those copies.
Line 261:		Line 256:

	<tr><th>Enter editor for update?</th>		<tr><th>Enter editor for update?</th>
	<td>Entering <code>Y</code> at this prompt places the generating user into an edit session on the new update procedure. The update procedure will have already been stored before the edit session is invoked, so <b>QUIT</b> (~~PF3~~) may be used to exit the edit session without losing the update procedure.</td></tr>		<td>Entering <code>Y</code> at this prompt places the generating user into an edit session on the new update procedure. The update procedure will have already been stored before the edit session is invoked, so <b>QUIT</b> (F3) may be used to exit the edit session without losing the update procedure.</td></tr>

	<tr><th>Synchronization count</th>		<tr><th>Synchronization count</th>

JAL: screen name format

2015-07-24T21:00:38Z

screen name format

← Older revision		Revision as of 21:00, 24 July 2015
Line 351:		Line 351:
	In case this rare event occurs, a manager can generate a resequence procedure.		In case this rare event occurs, a manager can generate a resequence procedure.
	By placing a <code>Z</code> in front of the procedure name on the Procedure List screen,		By placing a <code>Z</code> in front of the procedure name on the Procedure List screen,
	the ~~<b>~~ReSequence procedure~~</b>~~ screen is produced:		the "ReSequence procedure" screen is produced:

	<p class="caption" style="margin-right:15em">Z: Resequencing a managed procedure</p>		<p class="caption" style="margin-right:15em">Z: Resequencing a managed procedure</p>

	The ~~<b>~~ReSequence procedure~~</b>~~ screen has the following input fields:		The "ReSequence procedure" screen has the following input fields:
	<table class="thJustBold">		<table class="thJustBold">
	<tr><th>Resequence procedure</th>		<tr><th>Resequence procedure</th>

JAL: /* K (Klobber): Managed-update procedure deletion */ screen name format

2015-07-24T20:56:11Z

K (Klobber): Managed-update procedure deletion: screen name format

← Older revision		Revision as of 20:56, 24 July 2015
Line 333:		Line 333:

	The <code>K</code> prefix command presents the		The <code>K</code> prefix command presents the
	~~<b>~~Klobber procedure~~</b>~~ screen, which has the same input fields as the ~~<b>~~Create New proc~~</b>~~ screen described in [[#newp\|New: Create a new procedure via update deck]].		"Klobber procedure" screen, which has the same input fields as the "Create New proc" screen described in [[#newp\|New: Create a new procedure via update deck]].

	<p class="caption" style="margin-right:15em">"K" (klobber) Generating a logical procedure deletion</p>		<p class="caption" style="margin-right:15em">"K" (klobber) Generating a logical procedure deletion</p>

	<div id="reseqnc"></div>		<div id="reseqnc"></div>

	==ReSequence: Refreshing internal sequence numbers==		==ReSequence: Refreshing internal sequence numbers==
	<!--Caution: <div> above-->		<!--Caution: <div> above-->

JAL: /* SirPro change management overview */ tweak caption position

2015-07-21T20:24:06Z

SirPro change management overview: tweak caption position

← Older revision		Revision as of 20:24, 21 July 2015
Line 404:		Line 404:

	<p class="figure">[[File:SirLibChange.png\|444px]]</p>		<p class="figure">[[File:SirLibChange.png\|444px]]</p>
	<p class="caption" style="margin-right:~~15em~~">How a change progresses through SirLib</p>		<p class="caption" style="margin-right:26em">How a change progresses through SirLib</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.		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.