SirLib change control - Revision history

JAL: mention RKWeb equivalents

2017-06-21T23:26:25Z

mention RKWeb equivalents

← Older revision		Revision as of 23:26, 21 June 2017
Line 1:		Line 1:
	==SirLib main menu==		==SirLib main menu==
	<var class="product">SirLib</var> functions are accessed through its main menu (the <b>Configuration and Change Control System</b> screen) in the SIRLIB subsystem. This screen is displayed by selecting item 2 from the [[RKTools#Integrating RKTools with other subsystems\|RKTools System Main Menu screen]]. In RKWeb, this screen is accessed by selecting <code>Build > Configure</code>.		<var class="product">SirLib</var> functions are accessed through its main menu (the <b>Configuration and Change Control System</b> screen) in the SIRLIB subsystem. This screen is displayed by selecting item 2 from the [[RKTools#Integrating RKTools with other subsystems\|RKTools System Main Menu screen]].

			In [[RKWeb]], this screen is accessed by selecting <code>Build > Configure</code>, and [[Janus Web Legacy Support]] provides a facsimile of the TN3270 screen.

	<p class="caption" style="width:450px">SirLib main menu</p>		<p class="caption" style="width:450px">SirLib main menu</p>

JAL: mention RKWeb equivalents

2017-06-21T19:32:12Z

mention RKWeb equivalents

← Older revision		Revision as of 19:32, 21 June 2017
Line 1:		Line 1:
	==SirLib main menu==		==SirLib main menu==
	<var class="product">SirLib</var> functions are accessed through its main menu (the <b>Configuration and Change Control System</b> screen) in the SIRLIB subsystem. This screen is displayed by selecting item 2 from the [[RKTools#Integrating RKTools with other subsystems\|RKTools System Main Menu screen]].		<var class="product">SirLib</var> functions are accessed through its main menu (the <b>Configuration and Change Control System</b> screen) in the SIRLIB subsystem. This screen is displayed by selecting item 2 from the [[RKTools#Integrating RKTools with other subsystems\|RKTools System Main Menu screen]]. In RKWeb, this screen is accessed by selecting <code>Build > Configure</code>.

	<p class="caption" style="width:450px">SirLib main menu</p>		<p class="caption" style="width:450px">SirLib main menu</p>
Line 135:		Line 135:

	===Applying Fixes/Changes===		===Applying Fixes/Changes===
	~~The programmer uses~~ the <b>SirLib File ReConfiguration</b> screen to apply changes to a file. Pressing Enter while on the screen applies all active updates in the FixFile to the Base version of target procedures in the target file. This option may be protected by the System Administrator, so that only approved users may reconfigure a file.		You use the <b>SirLib File ReConfiguration</b> screen to apply changes to a file. Pressing Enter while on the screen applies all active updates in the FixFile to the Base version of target procedures in the target file. This option may be protected by the System Administrator, so that only approved users may reconfigure a file.

	If a procedure is locked when <var class="product">SirLib</var> attempts to apply changes to it, the reconfiguration fails, and a message is displayed identifying the procedure that could not be updated by <var class="product">SirLib</var>. This could happen if a user is editing the procedure, or if the procedure is locked by an active application subsystem. The reconfiguration should be done over again.		If a procedure is locked when <var class="product">SirLib</var> attempts to apply changes to it, the reconfiguration fails, and a message is displayed identifying the procedure that could not be updated by <var class="product">SirLib</var>. This could happen if a user is editing the procedure, or if the procedure is locked by an active application subsystem. The reconfiguration should be done over again.

JAL: add screenshot image for file reconfiguration

2017-06-05T22:32:44Z

add screenshot image for file reconfiguration

← Older revision		Revision as of 22:32, 5 June 2017
Line 127:		Line 127:
	Applying updates is always done one <i>file</i> at a time.		Applying updates is always done one <i>file</i> at a time.
	The process is called <var class="term">ReConfiguring</var> a file.		The process is called <var class="term">ReConfiguring</var> a file.
	~~The file and FixFile are selected on the SirLib~~
	~~main menu at the time Option 2 is selected.~~
	~~The <b>SirLib File ReConfiguration</b> screen is then displayed, with the following text:~~

	~~<p class="code" style="font-size:95%"><nowiki>------------------- * * * SIRLIB File ReConfiguration * * * ----------------</nowiki>~~		You invoke a reconfiguration by specifying the target file and the fix file on the SirLib main menu, then selecting Option 2, <b>Apply changes (Reconfigure a file)</b>.
	<b>~~Name of procedure~~ file ~~to be fixed ==>~~</b> ~~SIRMON~~		This produces a screen like the following (which results from target file M204PROC and fix file M204FIX):
	~~<b>File for CONTROL~~ and ~~change decks ==></b> SIRLIBP~~

	~~This function applies managed updates (change decks) to a Model 204~~		<p class="caption" style="width:450px">SirLib file reconfiguration</p>
	~~procedure file. The control and change decks must be in same procedure~~		<p class="figure">[[File:SlibReconfigure.png\|450px]]</p>
	~~file (SIRLIBP is the system default, but the user may change it.)~~

	~~The procedure CONTROL.pfile controls file reconfiguration, where 'pfile'~~
	~~is the name of the file to which changes are being applied. CONTROL~~
	~~procedures are maintained via the CHANGES screen in SIRLIB, and contain~~
	~~8-char change identifiers, followed by an optional asterix and comment.~~
	~~Change identifiers beginning with '*' are not applied.~~

	~~Each uncommented change identifier must match one or more procedures~~
	~~named pfile.fixname.procname, residing in the same file, where pfile~~
	~~is the file targeted for reconfiguration, fixname is the logical change~~
	~~identifier and procname is the procedure to which the change(s) applies.~~

	<b>~~Press ENTER to reconfigure the selected~~ file.</~~b><nowiki~~>
	~~----------------------------------------------------------------------------~~
	~~PF3/ Exit~~ <~~/nowiki~~></p>

	===Applying Fixes/Changes===		===Applying Fixes/Changes===

JAL: add image for Cutover

2017-06-05T20:44:21Z

add image for Cutover

@@ Line 319: / Line 319: @@
 <p class="note"><b>Note:</b> Managed files are added to the <var class="product">SirLib</var> system using the <b>SIRLIB Administration</b> screen. To remove a file from the <var class="product">SirLib</var> system, press the F10 key, and <var class="product">SirLib</var> removes all security, history, procedure locks, administration, and user privileges for the file. If the file has already been added to the <code>SIRLIB</code> subsystem, use [[System requirements for Application Subsystems#Overview of the SUBSYSMGMT interface|SUBSYSMGMT]] to remove it. </p>
-<div id="cutover"></div>
+==<b id="cutover"></b>Release cutover==
 One way to use <var class="product">SirLib</var> is to keep update procedures forever, allowing
 unlimited flexibility to reconfigure a system to a previous state.
@@ Line 370: / Line 366: @@
 Cutover is initiated from the <var class="product">SirLib</var> main menu using option 5. The file to be cutover is specified on the main menu along with the FixFile from which the changes are to be applied and deleted, as shown in the following representation.
 <p>If the <b>FixFile</b> field is left blank, the default FixFile from the File record is used.</p>
-       Apply Changes             ==> Y
+<p class="caption" style="width:450px">SIRLIB Cutover</p>
-       Delete Base Procedures    ==> Y                  ________ _____
+<p class="figure">[[File:SlibCutover.png|450px]]</p>
 A scrollable panel at the bottom of the Cutover screen lets you
 view the changes that are to be applied. If the projects shown are not the ones you want applied and deleted, the process should not be continued until the appropriate FixFile is located.

ELowell: /* The SirLib main menu */

2017-05-08T22:49:04Z

The SirLib main menu

← Older revision		Revision as of 22:49, 8 May 2017
Line 1:		Line 1:
	==~~The~~ SirLib main menu==		==SirLib main menu==
	<var class="product">SirLib</var> functions are accessed through its main menu (the <b>Configuration and Change Control System</b> screen) in the SIRLIB subsystem. This screen is displayed by selecting item 2 from the [[RKTools#Integrating RKTools with other subsystems\|RKTools System Main Menu screen]].		<var class="product">SirLib</var> functions are accessed through its main menu (the <b>Configuration and Change Control System</b> screen) in the SIRLIB subsystem. This screen is displayed by selecting item 2 from the [[RKTools#Integrating RKTools with other subsystems\|RKTools System Main Menu screen]].

JAL: typo

2017-05-08T16:27:04Z

typo

← Older revision		Revision as of 16:27, 8 May 2017
Line 155:		Line 155:

	===Applying Fixes/Changes===		===Applying Fixes/Changes===
	The programmer uses the <b>SirLib File ~~Reconfiguration~~</b> screen to apply changes to a file. Pressing Enter while on the screen applies all active updates in the FixFile to the Base version of target procedures in the target file. This option may be protected by the System Administrator, so that only		The programmer uses the <b>SirLib File ReConfiguration</b> screen to apply changes to a file. Pressing Enter while on the screen applies all active updates in the FixFile to the Base version of target procedures in the target file. This option may be protected by the System Administrator, so that only approved users may reconfigure a file.
	approved users may reconfigure a file.

	If a procedure is locked when <var class="product">SirLib</var> attempts to apply changes to it, the reconfiguration fails, and a message is displayed identifying the procedure that could not be updated by <var class="product">SirLib</var>. This could happen if a user is editing the procedure, or if the procedure is locked by an active application subsystem. The reconfiguration should be done over again.		If a procedure is locked when <var class="product">SirLib</var> attempts to apply changes to it, the reconfiguration fails, and a message is displayed identifying the procedure that could not be updated by <var class="product">SirLib</var>. This could happen if a user is editing the procedure, or if the procedure is locked by an active application subsystem. The reconfiguration should be done over again.
Line 371:		Line 370:
	Cutover is initiated from the <var class="product">SirLib</var> main menu using option 5. The file to be cutover is specified on the main menu along with the FixFile from which the changes are to be applied and deleted, as shown in the following representation.		Cutover is initiated from the <var class="product">SirLib</var> main menu using option 5. The file to be cutover is specified on the main menu along with the FixFile from which the changes are to be applied and deleted, as shown in the following representation.
	<p>If the <b>FixFile</b> field is left blank, the default FixFile from the File record is used.</p>		<p>If the <b>FixFile</b> field is left blank, the default FixFile from the File record is used.</p>
			<br>
	<p class="code" style="font-size:95%"><nowiki>----------------------</nowiki> <b>* * * SIRLIB File Cutover * * *</b> ----------------------		<p class="code" style="font-size:95%"><nowiki>----------------------</nowiki> <b>* * * SIRLIB File Cutover * * *</b> ----------------------
	==>		==>
Line 395:		Line 394:
	1/Help 3/Quit		1/Help 3/Quit
	7/Up 8/Down 9/Repeat 12/Commit</p>		7/Up 8/Down 9/Repeat 12/Commit</p>
			<br>
	A scrollable panel at the bottom of the Cutover screen lets you		A scrollable panel at the bottom of the Cutover screen lets you
	view the changes that are to be applied. If the projects shown are not the ones you want applied and deleted, the process should not be continued until the appropriate FixFile is located.		view the changes that are to be applied. If the projects shown are not the ones you want applied and deleted, the process should not be continued until the appropriate FixFile is located.

ELowell: /* Configuring files (applying updates) */

2017-05-05T20:34:41Z

Configuring files (applying updates)

← Older revision		Revision as of 20:34, 5 May 2017
Line 154:		Line 154:
	PF3/ Exit </nowiki></p>		PF3/ Exit </nowiki></p>

	~~<p><b>~~Applying Fixes/Changes~~</b></p>~~		===Applying Fixes/Changes===
	The programmer uses the <b>SirLib File Reconfiguration</b> screen to apply changes to a file. Pressing Enter while on the screen applies all active updates in the FixFile to the Base version of target procedures in the target file. This option may be protected by the System Administrator, so that only		The programmer uses the <b>SirLib File Reconfiguration</b> screen to apply changes to a file. Pressing Enter while on the screen applies all active updates in the FixFile to the Base version of target procedures in the target file. This option may be protected by the System Administrator, so that only
	approved users may reconfigure a file.		approved users may reconfigure a file.

ELowell: /* Release cutover */

2017-05-05T20:32:28Z

Release cutover

@@ Line 369: / Line 369: @@
 </ul>
-Cutover is initiated from the <var class="product">SirLib</var> main menu using option 5. The file to be cutover is specified on the main menu along with the FixFile from which the changes are to be applied and deleted. If the <b>FixFile</b> field is left blank, the default FixFile from the File record is used.
+Cutover is initiated from the <var class="product">SirLib</var> main menu using option 5. The file to be cutover is specified on the main menu along with the FixFile from which the changes are to be applied and deleted, as shown in the following representation.
-<p class="caption" style="width:450px">SIRLIB File Cutover</p>
+<p class="code" style="font-size:95%"><nowiki>----------------------</nowiki> <b>* * * SIRLIB File Cutover  * * *</b> ----------------------
-<p class="figure">[[File:.png|450px]]</p>
+==>
 A scrollable panel at the bottom of the Cutover screen lets you

ELowell: /* Configuring files (applying updates) */

2017-05-05T20:11:25Z

Configuring files (applying updates)

← Older revision		Revision as of 20:11, 5 May 2017
Line 126:		Line 126:
	==Configuring files (applying updates)==		==Configuring files (applying updates)==
	Applying updates is always done one <i>file</i> at a time.		Applying updates is always done one <i>file</i> at a time.
	The process is called <b>~~reConfiguring~~</b> a file.		The process is called <var class="term">ReConfiguring</var> a file.
	The file and FixFile are selected on the SirLib		The file and FixFile are selected on the SirLib
	main menu at the time Option 2 is selected.		main menu at the time Option 2 is selected.
	The <b>SirLib File ~~Reconfiguration~~</b> screen is then displayed:		The <b>SirLib File ReConfiguration</b> screen is then displayed, with the following text:

	<p class="~~caption~~" style="~~width~~:~~450px~~">~~SirLib~~ File ~~Reconfiguration~~</p>		<p class="code" style="font-size:95%"><nowiki>------------------- * * * SIRLIB File ReConfiguration * * * ----------------</nowiki>
	<~~p class~~=~~"figure"~~>~~[[File:.png\|450px]]~~</p>		<b>Name of procedure file to be fixed ==></b> SIRMON
	<b>~~SCREEN ID~~=~~LIBR07.Applying Fixes/Changes~~</b>		<b>File for CONTROL and change decks ==></b> SIRLIBP

	The ~~above~~ screen ~~shows how~~ the programmer ~~applies~~ changes to a file.		This function applies managed updates (change decks) to a Model 204
	Pressing Enter while on ~~this~~ screen applies all active updates in the		procedure file. The control and change decks must be in same procedure
	FixFile to the Base version of target procedures in the target file.		file (SIRLIBP is the system default, but the user may change it.)
	This option may be protected by the System Administrator, so that only
			The procedure CONTROL.pfile controls file reconfiguration, where 'pfile'
			is the name of the file to which changes are being applied. CONTROL
			procedures are maintained via the CHANGES screen in SIRLIB, and contain
			8-char change identifiers, followed by an optional asterix and comment.
			Change identifiers beginning with '*' are not applied.

			Each uncommented change identifier must match one or more procedures
			named pfile.fixname.procname, residing in the same file, where pfile
			is the file targeted for reconfiguration, fixname is the logical change
			identifier and procname is the procedure to which the change(s) applies.

			<b>Press ENTER to reconfigure the selected file.</b><nowiki>
			----------------------------------------------------------------------------
			PF3/ Exit </nowiki></p>

			<p><b>Applying Fixes/Changes</b></p>
			The programmer uses the <b>SirLib File Reconfiguration</b> screen to apply changes to a file. Pressing Enter while on the screen applies all active updates in the FixFile to the Base version of target procedures in the target file. This option may be protected by the System Administrator, so that only
	approved users may reconfigure a file.		approved users may reconfigure a file.

JAL: add info re field Help

2016-02-09T22:27:24Z

add info re field Help

← Older revision		Revision as of 22:27, 9 February 2016
Line 13:		Line 13:
	<var class="product">SirLib</var>'s default FixFile is always <code>SIRLIBP</code>.		<var class="product">SirLib</var>'s default FixFile is always <code>SIRLIBP</code>.

	Main menu options are described briefly in the following table and in depth in the sections that follow on this page.		Main menu options are described briefly in the following table and in depth in the sections that follow on this page. In addition to these options, you can also use this or any of the SirPro screen's [[RKTools#Fast-pathing\|fast path]] commands and online Help (F1 function key). Pressing F1 while the cursor is located on a screen field invokes the Help text for that field; otherwise, the Help text is positioned at the start of the Help for the screen.

	<table class="thJustBold">		<table class="thJustBold">
Line 301:		Line 301:
	</table>		</table>

	Managed files are added to the <var class="product">SirLib</var> system using the <b>SIRLIB Administration</b> screen. To remove a file from the <var class="product">SirLib</var> system, press ~~PF10~~, and <var class="product">SirLib</var> removes all security, history, procedure locks, administration, and user privileges for the file. If the file has already been added to the <~~var class="product"~~>SIRLIB</~~var~~> subsystem, use SUBSYSMGMT to remove it.		<p class="note"><b>Note:</b> Managed files are added to the <var class="product">SirLib</var> system using the <b>SIRLIB Administration</b> screen. To remove a file from the <var class="product">SirLib</var> system, press the F10 key, and <var class="product">SirLib</var> removes all security, history, procedure locks, administration, and user privileges for the file. If the file has already been added to the <code>SIRLIB</code> subsystem, use [[System requirements for Application Subsystems#Overview of the SUBSYSMGMT interface\|SUBSYSMGMT]] to remove it. </p>

	<div id="cutover"></div>		<div id="cutover"></div>