System requirements for Application Subsystems - Revision history

JDamon: /* Subsystem Administration screen */

2025-06-06T21:15:26Z

Subsystem Administration screen

← Older revision		Revision as of 21:15, 6 June 2025
Line 1,783:		Line 1,783:
	Select Administrative privileges for a <b>User Account</b> by entering <code>A</code>. The four <b>Admin</b> options are explained in the following section, [[#Admin options\|Admin options]].</p>		Select Administrative privileges for a <b>User Account</b> by entering <code>A</code>. The four <b>Admin</b> options are explained in the following section, [[#Admin options\|Admin options]].</p>
	<p>		<p>
	When setting privileges for specific users, remember that access to SUBSYSMGMT must be authorized via the DICTADMIN facility, as it is for every <var class="product">Model 204</var> Dictionary subsystem. ~~The privileges granted here supplement but do~~ not ~~override general access privileges granted through~~ DICTADMIN.</p>		When setting privileges for specific users, remember that access to SUBSYSMGMT must be authorized via the DICTADMIN facility, as it is for every <var class="product">Model 204</var> Dictionary subsystem. However, if the [[APSYSEC parameter]]=1, that authorization is not required for users who are system managers. System managers are automatically authorized to use the SUBSYSMGMT and DICTADMIN facilities.
			</p>

	===Admin options===		===Admin options===

JDamon: /* SUBSYSMGMT privileges screen */

2024-09-27T16:32:06Z

SUBSYSMGMT privileges screen

← Older revision		Revision as of 16:32, 27 September 2024
Line 1,150:		Line 1,150:
	</ul>		</ul>

	==SUBSYSMGMT ~~privileges~~ screen==		==SUBSYSMGMT Command Privileges screen==
	<p>		<p>
	The subsystem management command privileges screen is shown below:</p>		The subsystem management command privileges screen is shown below:</p>

JDamon: /* Parameter descriptions */

2020-06-10T19:46:04Z

Parameter descriptions

← Older revision		Revision as of 19:46, 10 June 2020
Line 1,326:		Line 1,326:
	The original value is restored when the user exits the subsystem.</p></li>		The original value is restored when the user exits the subsystem.</p></li>

	<li><b>Privileges (in HEX):</b> (optional) specifies a user's privileges while in the subsystem. Privileges specified before logging into the subsystem are overridden, regardless of the value of the <b>Log user into M204</b> field. The original value is restored when the user exits the subsystem.		<li><b>Privileges (in HEX)</b> (optional) specifies a user's privileges while in the subsystem. Privileges specified before logging into the subsystem are overridden, regardless of the value of the <b>Log user into M204</b> field. The original value is restored when the user exits the subsystem.
	<p>		<p>
	The privilege option is expressed as a hexadecimal value within the range of X'00' to X'FF', as described in [[Establishing and maintaining security#File security\|File security]]. </p>		The privilege option is expressed as a hexadecimal value within the range of X'00' to X'FF', as described in [[Establishing and maintaining security#File security\|File security]]. </p>
	</li>		</li>

	<li><b>Start Login Privileges (in HEX):</b> specifies user login privileges for use while running the subsystem initialization procedure. If specified, <b>Start Login Privileges</b> overrides both the user's previous privileges and other privilege fields in the subsystem definition.		<li><b>Start Login Privileges (in HEX)</b> specifies user login privileges for use while running the subsystem initialization procedure. If specified, <b>Start Login Privileges in (HEX)</b> overrides both the user's previous privileges and other privilege fields in the subsystem definition.
	<p>		<p>
	In the case of automatic login, the starting user's privileges are reset to those set on the Operational Parameters or Subsystem Classes screens prior to continuing execution within the subsystem. </p>		In the case of automatic login, the starting user's privileges are reset to those set on the Operational Parameters or Subsystem Classes screens prior to continuing execution within the subsystem. </p>

JDamon: Add "(in HEX):" to privileges specification

2020-06-10T19:43:28Z

Add "(in HEX):" to privileges specification

← Older revision		Revision as of 19:43, 10 June 2020
Line 1,326:		Line 1,326:
	The original value is restored when the user exits the subsystem.</p></li>		The original value is restored when the user exits the subsystem.</p></li>

	<li><b>Privileges</b> (optional) specifies a user's privileges while in the subsystem. Privileges specified before logging into the subsystem are overridden, regardless of the value of the <b>Log user into M204</b> field. The original value is restored when the user exits the subsystem.		<li><b>Privileges (in HEX):</b> (optional) specifies a user's privileges while in the subsystem. Privileges specified before logging into the subsystem are overridden, regardless of the value of the <b>Log user into M204</b> field. The original value is restored when the user exits the subsystem.
	<p>		<p>
	The privilege option is expressed as a hexadecimal value within the range of X'00' to X'FF', as described in [[Establishing and maintaining security#File security\|File security]]. </p>		The privilege option is expressed as a hexadecimal value within the range of X'00' to X'FF', as described in [[Establishing and maintaining security#File security\|File security]]. </p>
	</li>		</li>

	<li><b>Start Login Privileges</b> specifies user login privileges for use while running the subsystem initialization procedure. If specified, <b>Start Login Privileges</b> overrides both the user's previous privileges and other privilege fields in the subsystem definition.		<li><b>Start Login Privileges (in HEX):</b> specifies user login privileges for use while running the subsystem initialization procedure. If specified, <b>Start Login Privileges</b> overrides both the user's previous privileges and other privilege fields in the subsystem definition.
	<p>		<p>
	In the case of automatic login, the starting user's privileges are reset to those set on the Operational Parameters or Subsystem Classes screens prior to continuing execution within the subsystem. </p>		In the case of automatic login, the starting user's privileges are reset to those set on the Operational Parameters or Subsystem Classes screens prior to continuing execution within the subsystem. </p>

JAL: Dictionary and SQL server from RKTools main menu

2017-06-23T00:03:30Z

Dictionary and SQL server from RKTools main menu

← Older revision		Revision as of 00:03, 23 June 2017
Line 949:		Line 949:
	==Overview of the SUBSYSMGMT interface==		==Overview of the SUBSYSMGMT interface==
	<p>		<p>
	SUBSYSMGMT is the full-screen interface used to define user-written applications that run under the Application Subsystem facility. In addition to the TN3270 interface described below on this page, SUBSYSMGMT is accessible from the [[RKWeb]] browser GUI ~~introduced in [[~~RKTools]] version 7.7. </p>		SUBSYSMGMT is the full-screen interface used to define user-written applications that run under the Application Subsystem facility. In addition to accessing from command line the TN3270 interface described below on this page, SUBSYSMGMT is accessible both from the [[RKTools#mainmenu\|RKTools main menu]] and from the [[RKWeb#Manage\|RKWeb]] browser GUI as of RKTools version 7.7. </p>
	<p>		<p>
	To issue a command from the SUBSYSMGMT screens, press the assigned PF key or enter the command on the command line (<code>===></code>). Abbreviations for commands are indicated by the uppercase portion of the command listed for PF keys. The following table describes common commands and PF keys for SUBSYSMGMT screens: </p>		To issue a command from the SUBSYSMGMT screens, press the assigned PF key or enter the command on the command line (<code>===></code>). Abbreviations for commands are indicated by the uppercase portion of the command listed for PF keys. The following table describes common commands and PF keys for SUBSYSMGMT screens: </p>

JAL: mention RKWeb equivalents

2017-06-20T00:37:28Z

mention RKWeb equivalents

← Older revision		Revision as of 00:37, 20 June 2017
Line 949:		Line 949:
	==Overview of the SUBSYSMGMT interface==		==Overview of the SUBSYSMGMT interface==
	<p>		<p>
	SUBSYSMGMT is the full-screen interface used to define user-written applications that run under the Application Subsystem facility. </p>		SUBSYSMGMT is the full-screen interface used to define user-written applications that run under the Application Subsystem facility. In addition to the TN3270 interface described below on this page, SUBSYSMGMT is accessible from the [[RKWeb]] browser GUI introduced in [[RKTools]] version 7.7. </p>
	<p>		<p>
	To issue a command from the SUBSYSMGMT screens, press the assigned PF key or enter the command on the command line (<code>===></code>). Abbreviations for commands are indicated by the uppercase portion of the command listed for PF keys. The following table describes common commands and PF keys for SUBSYSMGMT screens: </p>		To issue a command from the SUBSYSMGMT screens, press the assigned PF key or enter the command on the command line (<code>===></code>). Abbreviations for commands are indicated by the uppercase portion of the command listed for PF keys. The following table describes common commands and PF keys for SUBSYSMGMT screens: </p>
Line 1,053:		Line 1,053:

	<tr>		<tr>
	<td>Subsystem Administration</td>		<td nowrap>Subsystem Administration</td>
	<td>Defines user and administrative privileges</td>		<td>Defines user and administrative privileges</td>
	</tr>		</tr>
Line 1,255:		Line 1,255:
	==Operational Parameters screen==		==Operational Parameters screen==
	<p>		<p>
	Selecting F4 from the Activity screen brings up the Operational Parameters screen. Use it to specify the operating parameters of the subsystem. </p>		Selecting F4 from the Activity screen brings up the Operational Parameters screen. Use it to specify the operating parameters of the subsystem. You access the [[RKWeb#Operational\|RKWeb version of this screen]] by selecting <code>Manage > Subsystem Management > Operational</code>. </p>
	<p>		<p>
	On this screen, only system managers can modify <b>Account</b>, <b>Privileges</b>, and <b>Start Login privileges</b> fields.</p>		On this screen, only system managers can modify <b>Account</b>, <b>Privileges</b>, and <b>Start Login privileges</b> fields.</p>
Line 1,368:		Line 1,368:
	==Procedure Specifications screen==		==Procedure Specifications screen==
	<p>		<p>
	Enter specifications for subsystem procedures on the Procedure Specifications screen. </p>		Enter specifications for subsystem procedures on the Procedure Specifications screen. You access the [[RKWeb#Procedure\|RKWeb version of this screen]] by selecting <code>Manage > Subsystem Management > Procedure</code>.</p>

	<p class="caption" style="width:564px">Procedure Specifications screen</p>		<p class="caption" style="width:564px">Procedure Specifications screen</p>
Line 1,437:		Line 1,437:
	==Subsystem File Use screen==		==Subsystem File Use screen==
	<p>		<p>
	The Subsystem File Use screen defines the files, including the procedure file used by the subsystem.</p>		The Subsystem File Use screen defines the files, including the procedure file used by the subsystem. You access the [[RKWeb#Files\|RKWeb version of this screen]] by selecting <code>Manage > Subsystem Management > Files</code>.</p>

	<p class="caption" style="width:537px">Subsystem File Use screen</p>		<p class="caption" style="width:537px">Subsystem File Use screen</p>
Line 1,492:		Line 1,492:
	<li>Pressing Enter validates the screen.</li>		<li>Pressing Enter validates the screen.</li>

	<li>You must issue the <code>TOP</code>, <code>BOTTOM</code>, and <code>MAXIMUM</code>commands on the command line. These commands have no corresponding PF keys.		<li>You must issue the <code>TOP</code>, <code>BOTTOM</code>, and <code>MAXIMUM</code> commands on the command line. These commands have no corresponding PF keys.
	<ul>		<ul>
	<li><code>TOP</code> scrolls to the first file.</li>		<li><code>TOP</code> scrolls to the first file.</li>
Line 1,536:		Line 1,536:
	==Subsystem Classes screen==		==Subsystem Classes screen==
	<p>		<p>
	Define command and file privileges for each class of subsystem users on the Subsystem Classes screen. Each class of user requires a separate screen. User class privileges defined to the subsystem override settings for <var>OPENCTL</var> and file privileges that reside in the password table.</p>		Define command and file privileges for each class of subsystem users on the Subsystem Classes screen. You access the [[RKWeb#System_Classes\|RKWeb version of this screen]] by selecting <code>Manage > Subsystem Management > System Classes</code>. </p>
			<p>
			Each class of user requires a separate screen. User class privileges defined to the subsystem override settings for <var>OPENCTL</var> and file privileges that reside in the password table.</p>
	<p>		<p>
	Only the system manager can update the <b>Logon Privilege</b>, <b>Record Security ID</b>, and <b>Account</b> fields.</p>		Only the system manager can update the <b>Logon Privilege</b>, <b>Record Security ID</b>, and <b>Account</b> fields.</p>
Line 1,635:		Line 1,637:
	==User Definitions screen==		==User Definitions screen==
	<p>		<p>
	List user classes on the User Definitions (USErdef) screen for updating or browsing class definitions. </p>		List user classes on the User Definitions (USErdef) screen for updating or browsing class definitions. You access the [[RKWeb#Operational\|RKWeb version of this screen]] by selecting <code>Manage > Subsystem Management > Operational</code>. </p>

	<p class="caption" style="width:562px">User Definitions screen</p>		<p class="caption" style="width:562px">User Definitions screen</p>
Line 1,669:		Line 1,671:
	==Subsystem Class Users screen==		==Subsystem Class Users screen==
	<p>		<p>
	Define user accounts assigned to a specific class on the Subsystem Class Users screen. A user can belong to only one class within a subsystem. If using more than one subsystem, the user can belong to a different class (different privileges) in each subsystem. </p>		Define user accounts assigned to a specific class on the Subsystem Class Users screen. You access the [[RKWeb#classUsers\|RKWeb version of this screen]] by selecting <code>Manage > Subsystem Management > Users</code>. </p>
			<p>
			A user can belong to only one class within a subsystem. If using more than one subsystem, the user can belong to a different class (different privileges) in each subsystem. </p>

	<p class="caption" style="width:531px">Subsystem Class Users screen</p>		<p class="caption" style="width:531px">Subsystem Class Users screen</p>
Line 1,682:		Line 1,686:
	===Copy SCLASS option===		===Copy SCLASS option===
	<p>		<p>
	The <b>Copy from Sclass</b> options allow you to copy user IDs from an SCLASS already defined in one subsystem to the current SCLASS being defined.</p>		The <b>Copy from Sclass</b> options allow you to copy user IDs from an SCLASS already defined in one subsystem to the current SCLASS being defined. This option is not available in the RKWeb interface.</p>

	====PF keys====		====PF keys====

JAL: add links

2017-05-16T23:30:04Z

add links

← Older revision		Revision as of 23:30, 16 May 2017
Line 2:		Line 2:
	==Overview of CCASYS==		==Overview of CCASYS==
	<p>		<p>
	CCASYS is a system file used in conjunction with Dictionary and the Subsystem Management facility (SUBSYSMGMT). It contains the procedure names, file names, and parameters that create a [[Application Subsystem development\|subsystem]] definition. When a subsystem is executed, <var class="product">Model 204</var> opens and reads the CCASYS file.</p>		CCASYS is a system file used in conjunction with [[:Category:Dictionary/204\|Dictionary/204]] and the [[Subsystem Management facility]] (SUBSYSMGMT). It contains the procedure names, file names, and parameters that create a [[Application Subsystem development\|subsystem]] definition. When a subsystem is executed, <var class="product">Model 204</var> opens and reads the CCASYS file.</p>
	<p>		<p>
	The CCASYS file must be open to use the Subsystem Management facility and to run any user-written subsystem.</p>		The CCASYS file must be open to use the Subsystem Management facility and to run any user-written subsystem.</p>
Line 9:		Line 9:
	<p>		<p>
	This page describes CCASYS and explains how to create and maintain the file.</p>		This page describes CCASYS and explains how to create and maintain the file.</p>
	~~<p>~~
	~~For details about the <var class="product">Model 204</var> Dictionary, refer to the [[:Category:Dictionary/204\|Dictionary/204]] wiki pages. </p>~~

	==Maintaining CCASYS==		==Maintaining CCASYS==
Line 445:		Line 443:
	===Required files===		===Required files===
	<p>		<p>
	Dictionary/204, with the files shown in the table below, must be installed to define a subsystem; see the ~~Rocket <var class="product">Model ~~204~~</var>~~ installation ~~guides~~. Dictionary entries pertaining to subsystems are for reference purposes only. The subsystem is executed by using the data stored in CCASYS.</p>		Dictionary/204, with the files shown in the table below, must be installed to define a subsystem; see the [[Dictionary/204 installation guide]]. Dictionary entries pertaining to subsystems are for reference purposes only. The subsystem is executed by using the data stored in CCASYS.</p>
	<table>		<table>
	<caption>Dictionary/204 files required for subsystem management</caption>		<caption>Dictionary/204 files required for subsystem management</caption>

JAL: add links

2017-05-16T21:40:11Z

add links

← Older revision		Revision as of 21:40, 16 May 2017
Line 10:		Line 10:
	This page describes CCASYS and explains how to create and maintain the file.</p>		This page describes CCASYS and explains how to create and maintain the file.</p>
	<p>		<p>
	For details about the <var class="product">Model 204</var> Dictionary, refer to the ~~<var class="book">~~[[~~Media~~:~~M204 DictionaryGuide V75.pdf~~\|~~Rocket Model 204~~ Dictionary/204 ~~and Data Administration Guide~~]]~~</var>~~. </p>		For details about the <var class="product">Model 204</var> Dictionary, refer to the [[:Category:Dictionary/204\|Dictionary/204]] wiki pages. </p>

	==Maintaining CCASYS==		==Maintaining CCASYS==
Line 25:		Line 25:
	===Reorganizing CCASYS===		===Reorganizing CCASYS===
	<p>		<p>
	For instructions on reorganizing CCASYS and Dictionary files, refer to ~~the~~ Dictionary ~~section of the <var class="product">Model ~~204~~</var> installation guide~~.</p>		For instructions on reorganizing CCASYS and Dictionary files, refer to [[Dictionary/204 operation and file maintenance]].</p>

	==Using CCASYS==		==Using CCASYS==
Line 187:		Line 187:
	The Subsystem Management facility (SUBSYSMGMT) is a full-screen <var class="product">Model 204</var> Dictionary interface. It is used as a tool to define user-written applications that run under the Application Subsystem facility (APSY). </p>		The Subsystem Management facility (SUBSYSMGMT) is a full-screen <var class="product">Model 204</var> Dictionary interface. It is used as a tool to define user-written applications that run under the Application Subsystem facility (APSY). </p>
	<p>		<p>
	Subsystem characteristics and components are defined by means of a series of screens and stored in the CCASYS file. Data in the CCASYS file is used by the application subsystem to control the processing required by the subsystem. <var class="product">Model 204</var> Dictionary entries are maintained for the operational parameters, procedure specifications, and subsystem files. The Subsystem Management facility makes ~~User Language~~ applications easier to use, easier to maintain, and more efficient. </p>		Subsystem characteristics and components are defined by means of a series of screens and stored in the CCASYS file. Data in the CCASYS file is used by the application subsystem to control the processing required by the subsystem. <var class="product">Model 204</var> Dictionary entries are maintained for the operational parameters, procedure specifications, and subsystem files. The Subsystem Management facility makes SOUL applications easier to use, easier to maintain, and more efficient. </p>
	<p>		<p>
	The following sections provide an overview of subsystem processing and explains how to use the SUBSYSMGMT interface to define a subsystem, establish user privileges, and migrate subsystem definitions from one <var class="product">Model 204</var> environment to another.</p>		The following sections provide an overview of subsystem processing and explains how to use the SUBSYSMGMT interface to define a subsystem, establish user privileges, and migrate subsystem definitions from one <var class="product">Model 204</var> environment to another.</p>
Line 193:		Line 193:
	For more information on subsystems, requirements, and options, refer to: </p>		For more information on subsystems, requirements, and options, refer to: </p>
	<ul>		<ul>
	<li>~~The <var class="product">Model ~~204</~~var> installation guides~~, which discuss the installation and preparation of CCASYS, D204SYS, and Dictionary files</li>		<li>[[Dictionary/204 installation guide]] and [[Dictionary/204 operation and file maintenance]], which discuss the installation and preparation of CCASYS, D204SYS, and Dictionary files</li>

	<li>~~The <var class="book">Rocket Model ~~204 ~~DICTIONARY and Data Administration Guide</var>~~, which describes the dictionary entries relating to subsystems</li>		<li>[[Dictionary/204 entity type definitions#SUBSYSTEM\|SUBSYSTEM]], which describes the dictionary entries relating to subsystems</li>

	<li>[[PQO: Overview of Parallel Query Option/204]], which describes a <var class="product">Model 204</var> distributed processing facility</li>		<li>[[PQO: Overview of Parallel Query Option/204]], which describes a <var class="product">Model 204</var> distributed processing facility</li>

JAL: /* Sample screens and PQO */ add link

2017-05-10T21:25:10Z

Sample screens and PQO: add link

← Older revision		Revision as of 21:25, 10 May 2017
Line 1,086:		Line 1,086:
	PQO-specific fields are explained briefly but their use is not described in detail. Not shown here is the Subsystem Trust screen, which is specific to PQO.</p>		PQO-specific fields are explained briefly but their use is not described in detail. Not shown here is the Subsystem Trust screen, which is specific to PQO.</p>
	<p>		<p>
	For full explanations of client and server definitions in PQO applications, see ~~the <var class="book">Rocket Parallel Query Option/204 User's Guide</var>~~.</p>		For full explanations of client and server definitions in PQO applications, see [[PQO: Defining a PQO network]].</p>

	==SUBSYSMGMT Activity screen==		==SUBSYSMGMT Activity screen==

JAL: /* Subsystem Administration screen */ mention ADMIN

2017-05-10T21:14:38Z

Subsystem Administration screen: mention ADMIN

← Older revision		Revision as of 21:14, 10 May 2017
Line 1,771:		Line 1,771:
	==Subsystem Administration screen==		==Subsystem Administration screen==
	<p>		<p>
	The Subsystem Administration screen appears when the system manager selects option 10 on the SUBSYSMGMT primary menu. This option is available only to a system manager. </p>		The Subsystem Administration screen appears when the system manager selects option 10 (ADMIN) on the SUBSYSMGMT primary menu. This option is available only to a system manager. </p>

	<p class="caption" style="width:513px">Subsystem Administration screen</p>		<p class="caption" style="width:513px">Subsystem Administration screen</p>