The SYSGEN configuration utility/More INI Details - Revision history

SteveA: /* Documenting the INI file with comments */

2008-08-21T19:24:51Z

Documenting the INI file with comments

← Older revision		Revision as of 19:24, 21 August 2008
Line 102:		Line 102:

	* Each segment title must end with a semicolon. Any text beyond the semicolon is considered a comment and is ignored by SYSGEN.		* Each segment title must end with a semicolon. Any text beyond the semicolon is considered a comment and is ignored by SYSGEN.
-
-

	For example:		For example:

-		+	[NODE]
-		+	Name = MANAGER; Node name is MANAGER
-	[NODE]	+	Server = N01,FS; Get files and security from N01
-		+
-	Name = MANAGER; Node name is MANAGER	+
-		+
-	Server = N01,FS; Get files and security from N01	+

SteveA: /* Documenting the INI file with comments */

2008-08-21T19:23:43Z

Documenting the INI file with comments

← Older revision		Revision as of 19:23, 21 August 2008
Line 95:		Line 95:

	For example:		For example:
-	~~<nowiki><pre>~~
-	~~***************************************************************~~

-	* COMET.INI *	+	***************************************************************
		+	* COMET.INI *
		+	* Last Date Modified: 04/16/01 # of NODES = 60 *
		+	***************************************************************

-	* Last Date Modified: 04/16/01 # of NODES = 60 *	+	* Each segment title must end with a semicolon. Any text beyond the semicolon is considered a comment and is ignored by SYSGEN.
-		+
-	~~***************************************************************~~	+
-	~~</pre></nowiki>~~	+
-		+
-		+
-	2. Each segment title must end with a semicolon. Any text ~~to the right of~~ the semicolon is considered a comment and is ignored by SYSGEN.	+

SteveA: /* Global -vs- Local */

2008-08-21T19:22:15Z

Global -vs- Local

← Older revision		Revision as of 19:22, 21 August 2008
Line 89:		Line 89:
	</pre>		</pre>

-	~~There are no limitations exist between what can be declared global or local. For some installations, a specific global declaration may make sense whereas for another, it would make no sense.~~	+	==Documenting the INI file with comments==

-		+	It's always a good idea to document your work. There are two ways to include documentation within your Comet INI file, they are:
-		+	* Using the asterisk character (*) in the 1st position of any INI line.
-		+
-		+
-	~~Documenting the INI file with comments~~	+
-		+
-		+
-		+
-	It's always a ~~great~~ idea to document your ~~INI file, if for no other reason but to clarify configuration entries~~. There are two ways to include documentation within your Comet INI file, they are:	+
-		+
-		+
-		+
-	1. Using the asterisk character (*) in the 1st position of any INI line.	+
-		+
-		+
-		+
-	~~For example:~~	+
-		+
-		+

		+	For example:
		+	<nowiki><pre>
	***************************************************************		***************************************************************

Line 118:		Line 103:

	***************************************************************		***************************************************************
-		+	</pre></nowiki>

SteveA: /* Global -vs- Local */

2008-08-21T19:18:03Z

Global -vs- Local

← Older revision		Revision as of 19:18, 21 August 2008
Line 88:		Line 88:
	08 = S ,\\FS1\SYS\COMET\SECURITY; Add directory for this node		08 = S ,\\FS1\SYS\COMET\SECURITY; Add directory for this node
	</pre>		</pre>
-

-	~~Here’s a good strategy to follow when editing the INI file for global and local settings:~~	+	There are no limitations exist between what can be declared global or local. For some installations, a specific global declaration may make sense whereas for another, it would make no sense.
-		+
-		+
-		+
-	~~Complete the segment entries for each of the sections except [NODE]. The segment entries here~~ are ~~the global entries for the enterprise. Entries should be the settings that are most common for all the nodes in the enterprise.~~	+
-	~~Place the [NODE] section(s) after the [INVALID TRANSLATION TABLE] section and before the [END] section. The local entries for each node are specified in this area.~~	+
-		+
-		+
-		+
-	~~In order to satisfy, in the broadest terms, all configuration options that are possible,~~ no limitations exist between what can be declared global or local. For some installations, a specific global declaration may make sense whereas for another, it would make no sense.	+

SteveA: /* Global -vs- Local */

2008-08-21T19:16:03Z

Global -vs- Local

← Older revision		Revision as of 19:16, 21 August 2008
Line 68:		Line 68:
	</pre>		</pre>

-	The local section for the MANAGER node would contain the following:	+	The local section for the MANAGER node would contain the following definition for the eighth directory in the configuration:
	<pre>		<pre>
	[NODE]		[NODE]
Line 79:		Line 79:
	The local section can also take away entries that were made in the global section. For example, suppose that the MANAGER node wants to (1) add the SECURITY directory, and (2) remove the TEMP and QSPOOL directories. The local section would then look like this:		The local section can also take away entries that were made in the global section. For example, suppose that the MANAGER node wants to (1) add the SECURITY directory, and (2) remove the TEMP and QSPOOL directories. The local section would then look like this:

-		+	<pre>
-		+
	[NODE]		[NODE]
-
	Name = MANAGER; Node name is MANAGER		Name = MANAGER; Node name is MANAGER
-
	Server = N01,FS; Get files and security from N01		Server = N01,FS; Get files and security from N01
-
-
-
	[DIRECTORIES]		[DIRECTORIES]
-
	03 = ; Don’t configure this directory on this node		03 = ; Don’t configure this directory on this node
-
	04 = ; Don’t configure this directory on this node		04 = ; Don’t configure this directory on this node
-
	08 = S ,\\FS1\SYS\COMET\SECURITY; Add directory for this node		08 = S ,\\FS1\SYS\COMET\SECURITY; Add directory for this node
-		+	</pre>

SteveA at 19:13, 21 August 2008

2008-08-21T19:13:27Z

← Older revision		Revision as of 19:13, 21 August 2008
Line 50:		Line 50:
	Global statements are default entries for all nodes, and local statements supplement these default entries.		Global statements are default entries for all nodes, and local statements supplement these default entries.

-	Here’s an example. Comet directories would typically be the same for most nodes in a network and these would be defined as global entries in the INI file. However, you could still make local directory entries for a specific node, and these entries would take precedence. Local entries are coded in the [NODE] section for each workstation that requires access to directories that are not defined in the global settings section.	+	Here’s an example. Comet directories would typically be the same for most nodes in a network and these would be defined as global entries in the INI file. However, you could still make local directory entries for a specific node, and these entries would take precedence. Local entries are coded in the [NODE] section for each workstation that requires access to directories that are not defined in the global settings section.
-		+
-		+

	In this example, let assume that the node named MANAGER wants to configure an extra directory named SECURITY.		In this example, let assume that the node named MANAGER wants to configure an extra directory named SECURITY.

-		+	The global section of the INI contains the following directory definitions:
-		+
-	The global section ~~might contain~~ the following directory definitions:	+
-		+
-		+

		+	<pre>
	[DIRECTORIES]		[DIRECTORIES]
-
	00 = S ,\\FS1\SYS\COMET\REL\; REL directory		00 = S ,\\FS1\SYS\COMET\REL\; REL directory
-
	01 = S ,\\FS1\SYS\COMET\SYS\; SYS directory		01 = S ,\\FS1\SYS\COMET\SYS\; SYS directory
-
	02 = S ,\\FS1\SYS\COMET\NET\; NET directory		02 = S ,\\FS1\SYS\COMET\NET\; NET directory
-
	03 = L ,D:\TEMP\; TMP directory		03 = L ,D:\TEMP\; TMP directory
-
	04 = S ,\\FS1\SYS\COMET\SPOOL\; SPL directory		04 = S ,\\FS1\SYS\COMET\SPOOL\; SPL directory
-
	05 = S ,\\FS1\SYS\COMET\UTL\; UTL directory		05 = S ,\\FS1\SYS\COMET\UTL\; UTL directory
-
	06 = S ,\\FS1\SYS\COMET\UTR\; UTR directory		06 = S ,\\FS1\SYS\COMET\UTR\; UTR directory
-
	07 = S ,\\FS1\SYS\COMET\MISC\; MSC directory		07 = S ,\\FS1\SYS\COMET\MISC\; MSC directory
-		+	</pre>
-		+

	The local section for the MANAGER node would contain the following:		The local section for the MANAGER node would contain the following:
-		+	<pre>
-		+
-		+
	[NODE]		[NODE]
-
	Name = MANAGER; Node name is MANAGER		Name = MANAGER; Node name is MANAGER
-
	Server = N01,FS; Get files and security from N01		Server = N01,FS; Get files and security from N01
-
-
-
	[DIRECTORIES]		[DIRECTORIES]
-
	08 = S ,\\FS1\SYS\COMET\SECURITY; Add directory for this node		08 = S ,\\FS1\SYS\COMET\SECURITY; Add directory for this node
-		+	</pre>
-		+

	The local section can also take away entries that were made in the global section. For example, suppose that the MANAGER node wants to (1) add the SECURITY directory, and (2) remove the TEMP and QSPOOL directories. The local section would then look like this:		The local section can also take away entries that were made in the global section. For example, suppose that the MANAGER node wants to (1) add the SECURITY directory, and (2) remove the TEMP and QSPOOL directories. The local section would then look like this:

SteveA at 19:01, 21 August 2008

2008-08-21T19:01:43Z

← Older revision		Revision as of 19:01, 21 August 2008
Line 50:		Line 50:
	Global statements are default entries for all nodes, and local statements supplement these default entries.		Global statements are default entries for all nodes, and local statements supplement these default entries.

-		+	Here’s an example. Comet directories would typically be the same for most nodes in a network and these would be defined as global entries in the INI file. However, you could still make local directory entries for a specific node, and these entries would take precedence. Local entries are coded in the [NODE] section for each workstation that requires access to directories that are not defined in the global settings section.
-		+
-	Here’s an example ~~that demonstrates this point~~. Comet directories ~~may~~ be the same for most nodes in a network~~. Logically,~~ these would be global entries in the INI file. However, you could still make local directory entries for a specific node, and these entries would take ~~pcedence~~. Local entries are ~~made by including a new~~ [NODE] section for each ~~node~~ that requires ~~settings~~ that are ~~different from~~ the global settings.	+

SteveA at 18:59, 21 August 2008

2008-08-21T18:59:01Z

← Older revision		Revision as of 18:59, 21 August 2008
Line 44:		Line 44:
	==Global -vs- Local==		==Global -vs- Local==

-		+	The INI file can contain global and local entries. Global entries apply to the entire enterprise, while local ones apply to a specific node.

-	~~In order to accommodate all possible configuration options, the INI file can contain global and local entries. Global~~ entries ~~apply to the entire enterprise, while local ones apply~~ to a ~~specific node~~. ~~Since the main goal is to develop an INI file specification that would declare Comet configuration~~ information ~~for an entire enterprise~~, ~~the concept of global verses local entries must be further clarified~~.	+	Local entries are unique to a given workstation. Typical examples of this include declarations of local directories, partition/terminal/session information, individual printers, gateways that are used on one node only.

-		+	Global statements are default entries for all nodes, and local statements supplement these default entries.
-		+
-	Global ~~entries refer to those entries that are common to multiple nodes within a networked system. Typical examples of this are:~~	+
-		+
-		+
-		+
-	~~[DIRECTORIES]~~	+
-		+
-	~~[COMET SYSTEM OPTIONS]~~	+
-		+
-	~~[INVALID CHARACTER TRANSLATION]~~	+
-		+
-		+
-		+
-	Local entries refer to those entries that are unique to a given workstation. Typical examples of this include declarations of local directories, partition/terminal/session information, individual printers, gateways that are used on one node only (for example, XAP, ODBC, Winsock, and the fax gateway).	+
-		+
-		+
-		+
-	~~The blend of global and local entries within an INI file is left up to to the system administrator. During the compilation of the INI file, global~~ statements are ~~recorded as~~ default entries for all ~~subsequent~~ nodes, and local statements ~~overriding the~~ default entries.	+

SteveA at 18:55, 21 August 2008

2008-08-21T18:55:35Z

← Older revision		Revision as of 18:55, 21 August 2008
Line 36:		Line 36:
	In this example, the four lines following the major keyword define the partition and terminal range for a particular Comet node.		In this example, the four lines following the major keyword define the partition and terminal range for a particular Comet node.

-	Each segment title line ends with a semicolon (;)~~, which provides one way to add comments to the INI file, as all~~ text following a semicolon is ignored by SYSGEN. (See below for more information about adding comments to an INI file.)	+	Each segment title line ends with a semicolon (;). All text following a semicolon is ignored by SYSGEN and can be used to comment lines. (See below for more information about adding other comments to an INI file.)

-		+	'''Note:''' there is no line continuation allowed in an INI file. Each segment title must fit on its own line.
-		+
-	~~Please note that~~ there is no line continuation allowed in an INI file. Each segment title must fit on its own line.	+
-		+
-		+

	Do not mix segment titles of one section with another. For example, it makes no sense to declare a directory name under the [COMET SYSTEM OPTIONS] groups, since it belongs to the [DIRECTORIES] group.		Do not mix segment titles of one section with another. For example, it makes no sense to declare a directory name under the [COMET SYSTEM OPTIONS] groups, since it belongs to the [DIRECTORIES] group.

-		+	==Global -vs- Local==
-		+
-		+
-		+
-	Global ~~and~~ Local	+

SteveA at 18:52, 21 August 2008

2008-08-21T18:52:36Z

← Older revision		Revision as of 18:52, 21 August 2008
Line 26:		Line 26:
	Here is an example of the [COMET SYSTEM OPTIONS] group:		Here is an example of the [COMET SYSTEM OPTIONS] group:

-	<~~code~~>	+	<pre>
	[COMET SYSTEM OPTIONS]		[COMET SYSTEM OPTIONS]
	First Partition = P00;		First Partition = P00;
Line 32:		Line 32:
	First Terminal = T00;		First Terminal = T00;
	# of Terminals = 3;		# of Terminals = 3;
-	<~~code~~>	+	</pre>

	In this example, the four lines following the major keyword define the partition and terminal range for a particular Comet node.		In this example, the four lines following the major keyword define the partition and terminal range for a particular Comet node.