Application Subsystem development - Revision history

Ekern: /* Commit exits */

2022-04-25T22:16:32Z

Commit exits

← Older revision		Revision as of 22:16, 25 April 2022
Line 892:		Line 892:
	If the automatic COMMIT option is selected, <var class="product">Model 204</var> automatically issues a COMMIT statement for any outstanding updates whenever a subsystem procedure terminates and transfers control using the communication global variable. If the COMMIT option is not selected, the application must issue the COMMIT statement to commit any pending updates. </p>		If the automatic COMMIT option is selected, <var class="product">Model 204</var> automatically issues a COMMIT statement for any outstanding updates whenever a subsystem procedure terminates and transfers control using the communication global variable. If the COMMIT option is not selected, the application must issue the COMMIT statement to commit any pending updates. </p>
	===Commit exits===		===Commit exits===
			<p class="note"><b>Note:</b> This feature is available as of Model 204 release 7.8. It is licensed and purchased separately from Model 204.</p>
	A commit exit enables you to set up SOUL code to run at commit time, as in: "on commit run <var class="term">xxx</var>".		A commit exit enables you to set up SOUL code to run at commit time, as in: "on commit run <var class="term">xxx</var>".

Ekern: /* Commit exits */

2022-04-22T17:07:10Z

Commit exits

← Older revision		Revision as of 17:07, 22 April 2022
Line 892:		Line 892:
	If the automatic COMMIT option is selected, <var class="product">Model 204</var> automatically issues a COMMIT statement for any outstanding updates whenever a subsystem procedure terminates and transfers control using the communication global variable. If the COMMIT option is not selected, the application must issue the COMMIT statement to commit any pending updates. </p>		If the automatic COMMIT option is selected, <var class="product">Model 204</var> automatically issues a COMMIT statement for any outstanding updates whenever a subsystem procedure terminates and transfers control using the communication global variable. If the COMMIT option is not selected, the application must issue the COMMIT statement to commit any pending updates. </p>
	===Commit exits===		===Commit exits===
	~~<p class="note"><b>Note:</b> This feature is available as of Model 204 release 7.8. It is licensed and purchased separately from Model 204.</p>~~
	A commit exit enables you to set up SOUL code to run at commit time, as in: "on commit run <var class="term">xxx</var>".		A commit exit enables you to set up SOUL code to run at commit time, as in: "on commit run <var class="term">xxx</var>".

ELowell: /* Commit exits */

2019-12-31T22:14:22Z

Commit exits

← Older revision		Revision as of 22:14, 31 December 2019
Line 892:		Line 892:
	If the automatic COMMIT option is selected, <var class="product">Model 204</var> automatically issues a COMMIT statement for any outstanding updates whenever a subsystem procedure terminates and transfers control using the communication global variable. If the COMMIT option is not selected, the application must issue the COMMIT statement to commit any pending updates. </p>		If the automatic COMMIT option is selected, <var class="product">Model 204</var> automatically issues a COMMIT statement for any outstanding updates whenever a subsystem procedure terminates and transfers control using the communication global variable. If the COMMIT option is not selected, the application must issue the COMMIT statement to commit any pending updates. </p>
	===Commit exits===		===Commit exits===
	<p class="note"><b>Note:</b> This feature is available as of Model 204 release 7.8.</p>		<p class="note"><b>Note:</b> This feature is available as of Model 204 release 7.8. It is licensed and purchased separately from Model 204.</p>
	A commit exit enables you to set up SOUL code to run at commit time, as in: "on commit run <var class="term">xxx</var>".		A commit exit enables you to set up SOUL code to run at commit time, as in: "on commit run <var class="term">xxx</var>".

ELowell: /* Automatic COMMIT */

2019-12-31T22:09:26Z

Automatic COMMIT

Show changes

JAL: /* Advantages of subsystems */ add nowrap

2018-08-21T23:11:41Z

Advantages of subsystems: add nowrap

← Older revision		Revision as of 23:11, 21 August 2018
Line 15:		Line 15:

	<tr>		<tr>
	<td>Minimal end-user intervention </td>		<td nowrap>Minimal end-user intervention </td>
	<td>Require minimal knowledge of <var class="product">Model 204</var>. The end user need not know what files and procedures exist for the application. The subsystem is invoked simply by entering the subsystem name as a <var class="product">Model 204</var> command.</td>		<td>Require minimal knowledge of <var class="product">Model 204</var>. The end user need not know what files and procedures exist for the application. The subsystem is invoked simply by entering the subsystem name as a <var class="product">Model 204</var> command.</td>
	</tr>		</tr>
Line 44:		Line 44:
	</tr>		</tr>
	</table>		</table>

	===Subsystem definition===		===Subsystem definition===
	<p>		<p>

JAL: minor formatting

2018-08-08T01:36:04Z

minor formatting

← Older revision		Revision as of 01:36, 8 August 2018
Line 7:		Line 7:
	===Advantages of subsystems===		===Advantages of subsystems===
	<p>		<p>
	The following table summarizes the advantages of subsystems over other ~~User Language~~ procedure applications: </p>		The following table summarizes the advantages of subsystems over other [[SOUL]] procedure applications: </p>
	<table>		<table>
	<tr class="head">		<tr class="head">
Line 26:		Line 26:
	<tr>		<tr>
	<td nowrap>Performance improvements </td>		<td nowrap>Performance improvements </td>
	<td>Improve performance by saving and reloading compiled ~~User Language~~ requests, called precompiled procedures. Depending upon how often precompiled procedures are included, 20-90% of the operating costs of a <var class="product">Model 204</var> application can be saved.</td>		<td>Improve performance by saving and reloading compiled SOUL requests, called precompiled procedures. Depending upon how often precompiled procedures are included, 20-90% of the operating costs of a <var class="product">Model 204</var> application can be saved.</td>
	</tr>		</tr>

Line 36:		Line 36:
	<tr>		<tr>
	<td>Security facilities </td>		<td>Security facilities </td>
	<td>~~Either allow~~ or restrict access to the subsystem. </td>		<td>Allow or restrict access to the subsystem. </td>
	</tr>		</tr>

Line 175:		Line 175:
	<ol>		<ol>
	<li>Set the communication global variable to the value XFER.</li>		<li>Set the communication global variable to the value XFER.</li>
	<li>Set the global variable XFER to the name of the subsystem to which control is being passed. </li>		<li>Set the global variable XFER to the name of the subsystem to which control is being passed. </li>
	</ol>		</ol>
	<p>		<p>
	When the current procedure finishes executing, <var class="product">Model 204</var> disconnects the user from the old subsystem, transfers control to the new subsystem, and invokes the login procedure for the new subsystem. </p>		When the current procedure finishes executing, <var class="product">Model 204</var> disconnects the user from the old subsystem, transfers control to the new subsystem, and invokes the login procedure for the new subsystem. </p>

	====Design considerations====		====Design considerations====
Line 655:		Line 655:
	END IF		END IF
	END REPEAT		END REPEAT
	CHK.GTAB: IF $SETG('NEXT',%NEXT)THEN		CHK.GTAB: IF $SETG('NEXT',%NEXT) THEN
	AUDIT 'GLOBAL TABLE FULL - "NEXT"'		AUDIT 'GLOBAL TABLE FULL - "NEXT"'
	END IF		END IF
Line 915:		Line 915:
	<li>Mandatory members		<li>Mandatory members
	<p>		<p>
	Mandatory files or groups are automatically opened by <var class="product">Model 204</var> when a user logs into a subsystem and automatically closed when the user leaves the subsystem. Subsystem requests can assume that all mandatory files are open and that they are physically consistent. The user's file privileges are those defined in the subsystem definition for the current user's SCLASS. The opening of a mandatory member cannot be prevented by the subsystem administrator with the STOP FILE command when the subsystem is active. A mandatory member cannot be accessed by another copy of <var class="product">Model 204</var> until the entire subsystem is stopped.</p>		Mandatory files or groups are automatically opened by <var class="product">Model 204</var> when a user logs into a subsystem and automatically closed when the user leaves the subsystem. Subsystem requests can assume that all mandatory files are open and that they are physically consistent. The user's file privileges are those defined in the subsystem definition for the current user's SCLASS. The opening of a mandatory member cannot be prevented by the subsystem administrator with the <var>STOP FILE</var> command when the subsystem is active. A mandatory member cannot be accessed by another copy of <var class="product">Model 204</var> until the entire subsystem is stopped.</p>
	<p>		<p>
	If a subsystem procedure issues an OPEN or CLOSE command for a mandatory member, the command is ignored by <var class="product">Model 204</var> and the user's current privileges are not changed.</p>		If a subsystem procedure issues an <var>OPEN</var> or <var>CLOSE</var> command for a mandatory member, the command is ignored by <var class="product">Model 204</var> and the user's current privileges are not changed.</p></li>
	</li>

	<li>Optional members		<li>Optional members
	<p>		<p>
	Optional files or groups provide the ability for a file or group to be stopped by a subsystem administrator (using the STOP FILE command) without stopping the entire subsystem. If a member is defined as optional, it is not automatically opened during the subsystem login. It must be opened by the application by using an OPEN/OPENC statement or command. The file privileges assigned are those specified in the subsystem definition for the current user's SCLASS. The member is closed (for that user only) when the user leaves the subsystem if a CLOSE command has not been issued.</p>		Optional files or groups provide the ability for a file or group to be stopped by a subsystem administrator (using the <var>STOP FILE</var> command) without stopping the entire subsystem. If a member is defined as optional, it is not automatically opened during the subsystem login. It must be opened by the application by using an OPEN/OPENC statement or command. The file privileges assigned are those specified in the subsystem definition for the current user's SCLASS. The member is closed (for that user only) when the user leaves the subsystem if a <var>CLOSE</var> command has not been issued.</p>
	<p>		<p>
	When an optional member is not in use, it can be processed by another copy of <var class="product">Model 204</var>. </p>		When an optional member is not in use, it can be processed by another copy of <var class="product">Model 204</var>. </p></li>
	</li>
	</ul>		</ul>
	<p>		<p>
	Requests that reference mandatory or optional members can be precompiled. Files not contained in the subsystem definition can be opened and referenced within a subsystem application, but the requests that reference those files cannot be precompiled.</p>		Requests that reference mandatory or optional members can be precompiled. Files not contained in the subsystem definition can be opened and referenced within a subsystem application, but the requests that reference those files cannot be precompiled. </p>

	====Automatic vs. manual members====		====Automatic vs. manual members====
Line 944:		Line 942:
	====Permanent vs. temporary groups in subsystem definitions====		====Permanent vs. temporary groups in subsystem definitions====
	<p>		<p>
	The GROUP parameter of the subsystem definition applies ~~ONLY~~ to permanent groups. Temporary group names cannot be used. To include temporary group members in a subsystem definition, and thus to enable their use in precompiled code, the members of the temporary group should be individually specified in the subsystem definition.</p>		The GROUP parameter of the subsystem definition applies <strong>only</strong> to permanent groups. Temporary group names cannot be used. To include temporary group members in a subsystem definition, and thus to enable their use in precompiled code, the members of the temporary group should be individually specified in the subsystem definition.</p>

	====Summary of file definition options====		====Summary of file definition options====

JAL: /* Error code values */ link repair

2017-09-05T19:51:36Z

Error code values: link repair

← Older revision		Revision as of 19:51, 5 September 2017
Line 237:		Line 237:
	===Error code values===		===Error code values===
	<p>		<p>
	~~[[#Error code values\|~~Error global variable values and reasons]] lists the error global variable values and their corresponding causes. Correct the cause of the error and/or change your error procedure as discussed in [[#Error procedures\|Error procedures]]. </p>		The "Error global variable values and reasons" table lists the error global variable values and their corresponding causes. Correct the cause of the error, and/or change your error procedure as discussed in [[#Error procedures\|Error procedures]]. </p>
	<table>		<table>
	<caption>Error global variable values and reasons</caption>		<caption>Error global variable values and reasons</caption>
Line 351:		Line 351:
	</tr>		</tr>
	</table>		</table>

	===Error procedures===		===Error procedures===
	<p>		<p>

JAL: /* Summary of file definition options */ adjust table formatting

2017-06-27T21:00:20Z

Summary of file definition options: adjust table formatting

← Older revision		Revision as of 21:00, 27 June 2017
Line 954:		Line 954:
	<th>Subsystem definition <br>option</th>		<th>Subsystem definition <br>option</th>
	<th>Automatic		<th>Automatic
	open and close?</th>		open <br>and close?</th>
	<th>		<th>
	Pre-compiled code?</th>		Pre-compiled <br>code?</th>
	<th>Start/stop file <br>command allowed?</th>		<th>Start/stop file <br>command allowed?</th>
	<th>File privileges <br>assigned</th>		<th>File privileges <br>assigned</th>

JAL: /* Subsystem definition */ link repair

2017-05-16T21:53:23Z

Subsystem definition: link repair

← Older revision		Revision as of 21:53, 16 May 2017
Line 49:		Line 49:
	The characteristics and components of a subsystem are defined to <var class="product">Model 204</var> by the system manager during a process called subsystem definition. The defined options and components are stored in the system file CCASYS. Once a subsystem has been defined, all Dictionary users can display the options and components through Dictionary. For more information about:</p>		The characteristics and components of a subsystem are defined to <var class="product">Model 204</var> by the system manager during a process called subsystem definition. The defined options and components are stored in the system file CCASYS. Once a subsystem has been defined, all Dictionary users can display the options and components through Dictionary. For more information about:</p>
	<ul>		<ul>
	<li>Displaying a subsystem definition, see [[System requirements for Application Subsystems]]. </li>		<li>Displaying a subsystem definition, see [[System requirements for Application Subsystems#Overview of the Subsystem Management facility\|Overview of the Subsystem Management facility]]. </li>

	<li>Defining subsystems that refer to remote files and scattered groups, see [[PQO: Scattered APSY subsystems#Client and service subsystems\|PQO client and service subsystems]].		<li>Defining subsystems that refer to remote files and scattered groups, see [[PQO: Scattered APSY subsystems#Client and service subsystems\|PQO client and service subsystems]].

JAL: /* Cross-Reference facility */ add link

2017-04-26T20:20:40Z

Cross-Reference facility: add link

← Older revision		Revision as of 20:20, 26 April 2017
Line 1,424:		Line 1,424:
	The Cross-Reference facility also includes Preview and Browse functions, which inform the user about the procedures selected for processing.</p>		The Cross-Reference facility also includes Preview and Browse functions, which inform the user about the procedures selected for processing.</p>
	<p>		<p>
	For a complete description of the Cross-Reference facility, refer to the ~~<var class="book">Rocket Model ~~204 Dictionary ~~and Data Administration Guide<~~/~~var>~~.</p>		For a complete description of the Cross-Reference facility, refer to the [[:Category:Dictionary/204#Dictionary/204 topics\|Dictionary/204 topics]].</p>

	[[Category:SOUL]]		[[Category:SOUL]]