SirLib update example - Revision history

JAL: mixed case for XCOMPARE

2015-10-28T16:19:45Z

mixed case for XCOMPARE

← Older revision		Revision as of 16:19, 28 October 2015
Line 6:		Line 6:
	Notice that sequenced versions of procedures do not apply to New, Erase,		Notice that sequenced versions of procedures do not apply to New, Erase,
	or Resequence operations.		or Resequence operations.
	Also note that <var>Q</var> is the managed update equivalent of a Copy, just as <var>N</var> is the equivalent of Create, and <var>K</var> 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.		Also note that <var>Q</var> is the managed update equivalent of a Copy, just as <var>N</var> is the equivalent of Create, and <var>K</var> 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:575px">How a change progresses through SirLib</p>		<p class="caption" style="width:575px">How a change progresses through SirLib</p>
Line 16:		Line 16:
	A single line of new code is inserted in <code>TEMP</code> (the line		A single line of new code is inserted in <code>TEMP</code> (the line
	<code>PRINT STATE AND ZIP AT 40</code>).		<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>.		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>.		A project leader defines the project name <code>CHG1</code> in <code>CONTROL.PFILE1</code>.

JAL: mixed case for XCOMPARE

2015-10-28T16:02:08Z

mixed case for XCOMPARE

← Older revision		Revision as of 16:02, 28 October 2015
Line 4:		Line 4:
	<!-- Page name: SirLib update example-->		<!-- Page name: SirLib update example-->

	Notice that sequenced versions of procedures do not apply to New, Erase		Notice that sequenced versions of procedures do not apply to New, Erase,
	or Resequence operations.		or Resequence operations.
	Also note that <var>Q</var> is the managed update equivalent of a Copy, just as <var>N</var> is the		Also note that <var>Q</var> is the managed update equivalent of a Copy, just as <var>N</var> is the equivalent of Create, and <var>K</var> 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.
	equivalent of Create, and <var>K</var> 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:575px">How a change progresses through SirLib</p>		<p class="caption" style="width:575px">How a change progresses through SirLib</p>
Line 21:		Line 16:
	A single line of new code is inserted in <code>TEMP</code> (the line		A single line of new code is inserted in <code>TEMP</code> (the line
	<code>PRINT STATE AND ZIP AT 40</code>).		<code>PRINT STATE AND ZIP AT 40</code>).
	Using <var>~~XCOMPARE~~</var>, the update is generated to file <code>CHANGES</code>, and named		Using <var>Xcompare</var>, the update is generated to file <code>CHANGES</code>, and named <code>PFILE1.CHG1.TEMP</code>.
	<code>PFILE1.CHG1.TEMP</code>.
	A project leader defines the project name <code>CHG1</code> in <code>CONTROL.PFILE1</code>.		A project leader defines the project name <code>CHG1</code> in <code>CONTROL.PFILE1</code>.

JAL: add graphic

2015-10-19T22:10:28Z

add graphic

← Older revision		Revision as of 22:10, 19 October 2015
Line 13:		Line 13:
	Resequencing is of course a special purpose function with no unmanaged corollary.		Resequencing is of course a special purpose function with no unmanaged corollary.

	<p class="~~code~~">~~:FIGCAP.~~How a change progresses through SirLib</p>		<p class="caption" style="width:575px">How a change progresses through SirLib</p>
			<p class="figure">[[File:SlibChangeProgressFig.png\|575px]]</p>

	In the example above, procedure <code>TEMP</code> exists in file <code>PFILE1</code> (upper left).		In the example above, procedure <code>TEMP</code> exists in file <code>PFILE1</code> (upper left).

Admin: 1 revision

2015-10-19T21:37:24Z

1 revision

← Older revision	Revision as of 21:37, 19 October 2015
(No difference)

JAL at 21:11, 16 October 2015

2015-10-16T21:11:14Z

New page

Notice that sequenced versions of procedures do not apply to New, Erase
or Resequence operations.
Also note that <var>Q</var> is the managed update equivalent of a Copy, just as <var>N</var> is the
equivalent of Create, and <var>K</var> 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="code">:FIGCAP.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 <var>Q</var> command to copy <code>TEMP</code> into <code>WORKFILE</code>, getting
both a working and a <var>SEQ</var> 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, described in the [[SirLib change control#Configuring files (applying updates)|Configuring files (applying updates)]] section, 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>.
The final state of <code>PFILE1</code> is shown lower right.

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

[[Category: SirLib]]