Index - Revision history

Gordon.dye: /* Technical Considerations */

2021-03-04T15:34:11Z

Technical Considerations

← Older revision		Revision as of 15:34, 4 March 2021
Line 73:		Line 73:
	{{:Badkeys}}		{{:Badkeys}}

	==~~Technical~~ Considerations==		==Special Considerations==

	The Index command may be executed in a program as part of the [[EXECUTE]] statement. If a program is active, this method of running the INDEX command does not CLEAR memory.		The Index command may be executed in a program as part of the [[EXECUTE]] statement. If a program is active, this method of running the INDEX command does not CLEAR memory.
Line 100:		Line 100:

	INDEX MASTER.FIL KEY.FIL 1/3 2/2U REPLACE		INDEX MASTER.FIL KEY.FIL 1/3 2/2U REPLACE


	If a key field is a two digit year it should be flagged as such so BR will use [[BaseYear]] when comparing values for sorting purposes. Place the letter Y after either the field position or its length.		If a key field is a two digit year it should be flagged as such so BR will use [[BaseYear]] when comparing values for sorting purposes. Place the letter Y after either the field position or its length.

	INDEX MASTER.FIL KEY.FIL 1/3 2/2Y REPLACE		INDEX MASTER.FIL KEY.FIL 1/3 2/2Y REPLACE

			If a two digit year is stored in binary or packed decimal form, the INDEX command needs to indicate that by following the Y with either P or D as in:

			INDEX MASTER.FIL KEY.FIL 1/3 2/2YB REPLACE



	The INDEX command ~~now~~ defaults to B-tree indexing unless OPTION 5 is used in the BRConfig.sys file to set the universal default to ISAM or the ISAM parameter is used within the syntax of the INDEX command to override the B-tree default on an individual basis. If OPTION 5 is specified in BRConfig.sys, the INDEX command's BTREE parameter can be used to override the ISAM default on an individual basis.		The INDEX command defaults to B-tree indexing unless OPTION 5 is used in the BRConfig.sys file to set the universal default to ISAM or the ISAM parameter is used within the syntax of the INDEX command to override the B-tree default on an individual basis. If OPTION 5 is specified in BRConfig.sys, the INDEX command's BTREE parameter can be used to override the ISAM default on an individual basis.

	;INDEX will completely rebuild the [[B-tree]] index when any of the following three conditions is true:		;INDEX will completely rebuild the [[B-tree]] index when any of the following three conditions is true:

Gordon.dye: /* Technical Considerations */

2021-03-04T15:09:55Z

Technical Considerations

← Older revision		Revision as of 15:09, 4 March 2021
Line 77:		Line 77:
	The Index command may be executed in a program as part of the [[EXECUTE]] statement. If a program is active, this method of running the INDEX command does not CLEAR memory.		The Index command may be executed in a program as part of the [[EXECUTE]] statement. If a program is active, this method of running the INDEX command does not CLEAR memory.

	When the starting key position and key length parameters are both specified as 0, INDEX will now use the key parameters as they exist in the key file. The REPLACE parameter is assumed. ~~Also, the~~ INDEX command may now include a SHR parameter. This allows another workstation to ~~open~~ the master file. For example:		''When the starting key position and key length parameters are both specified as 0, INDEX will now use the key parameters as they exist in the key file.'' The REPLACE parameter is assumed.


			The INDEX command may now include a SHR parameter. This allows another workstation to access the master file while indexing. For example:

	INDEX master.fil index.fil 1 4 REPLACE SHR		INDEX master.fil index.fil 1 4 REPLACE SHR

	'''Note''' that ~~this parameter~~ should be used only for making temporary indexes.		'''Note''' that SHR should be used only for making temporary indexes because master files normally should not be modified when rebuilding indexes. When INDEX is used with the SHR parameter, all records in the master file can be accessed by the INDEX command, even if a record is locked by another user.


	~~Case~~ insensitive key file access ~~is now supported. Placing~~ a U after the key length or key starting position parameters causes the program to keep that key field as uppercase. Whenever a record is written, the key field is converted to uppercase before it is written to the key file (master record is unchanged) and whenever the file is read with KEY=, the parts of the key that need to be converted to uppercase are converted before the key look up.		For ''case insensitive key file access'' place a U after the key length or key starting position parameters. This causes the program to keep that key field as uppercase. Whenever a record is written, the key field is converted to uppercase before it is written to the key file (master record is unchanged) and whenever the file is read with KEY=, the parts of the key that need to be converted to uppercase are converted before the key look up.

	This is useful for looking up names, where the capitalization of the data on file and the key entered by the operator may be inconsistent. This also permits sequential processing of a keyed file in alpha order without regard to the case of the data. '''Note''' that even though BR stores the key as uppercase, the resulting processing occurs as if the case is ignored. In other words, 'A' and 'a' are considered equal.		This is useful for looking up names, where the capitalization of the data on file and the key entered by the operator may be inconsistent. This also permits sequential processing of a keyed file in alpha order without regard to the case of the data. '''Note''' that even though BR stores the key as uppercase, the resulting processing occurs as if the case is ignored. In other words, 'A' and 'a' are considered equal.
Line 97:		Line 101:
	INDEX MASTER.FIL KEY.FIL 1/3 2/2U REPLACE		INDEX MASTER.FIL KEY.FIL 1/3 2/2U REPLACE

	~~When INDEX~~ is ~~used with the SHR parameter, all records in~~ a ~~master file can now~~ be ~~accessed, even if a record is locked in that master file~~. The INDEX command now defaults to B-tree indexing unless OPTION 5 is used in the BRConfig.sys file to set the universal default to ISAM or the ISAM parameter is used within the syntax of the INDEX command to override the B-tree default on an individual basis. If OPTION 5 is specified in BRConfig.sys, the INDEX command's BTREE parameter can be used to override the ISAM default on an individual basis.		If a key field is a two digit year it should be flagged as such so BR will use [[BaseYear]] when comparing values for sorting purposes. Place the letter Y after either the field position or its length.

			INDEX MASTER.FIL KEY.FIL 1/3 2/2Y REPLACE


			The INDEX command now defaults to B-tree indexing unless OPTION 5 is used in the BRConfig.sys file to set the universal default to ISAM or the ISAM parameter is used within the syntax of the INDEX command to override the B-tree default on an individual basis. If OPTION 5 is specified in BRConfig.sys, the INDEX command's BTREE parameter can be used to override the ISAM default on an individual basis.

	;INDEX will completely rebuild the [[B-tree]] index when any of the following three conditions is true:		;INDEX will completely rebuild the [[B-tree]] index when any of the following three conditions is true:
Line 104:		Line 113:
	:3) When INDEX REORG is specified and the key file does not exist.		:3) When INDEX REORG is specified and the key file does not exist.

	The syntax of the INDEX command ~~now~~ allows the BTREE or ISAM parameters, as follows:
			The syntax of the INDEX command allows the BTREE or ISAM parameters, as follows:

	INDEX file.dat,file.idx,1,2,REPLACE,ISAM		INDEX file.dat,file.idx,1,2,REPLACE,ISAM

Gordon.dye: /* BADKEYS */

2021-03-04T14:16:56Z

BADKEYS

← Older revision		Revision as of 14:16, 4 March 2021
Line 70:		Line 70:
	The '''-N''' option suppresses all information that would normally be output (except LISTDUPKEYS information).		The '''-N''' option suppresses all information that would normally be output (except LISTDUPKEYS information).

	===BADKEYS===		==BADKEYS==
	{{:Badkeys}}		{{:Badkeys}}

John at 15:50, 11 November 2019

2019-11-11T15:50:26Z

← Older revision		Revision as of 15:50, 11 November 2019
Line 1:		Line 1:
	The '''Index''' [[command]] creates or recreates an index file. See the [[Index Facility]] for additional information. You may also find it useful to familiarize yourself with the concept of a [~~http://http~~://en.wikipedia.org/wiki/Index_(database) Database Index]		The '''Index''' [[command]] creates or recreates an index file. See the [[Index Facility]] for additional information. You may also find it useful to familiarize yourself with the concept of a [https://en.wikipedia.org/wiki/Index_(database) Database Index]

	For a simple tutorial, see [[Index_and_Sort_facilities_Tutorial\|Index Tutorial]].		For a simple tutorial, see [[Index_and_Sort_facilities_Tutorial\|Index Tutorial]].

Laura: /* Syntax */

2014-05-08T16:56:51Z

Syntax

← Older revision		Revision as of 16:56, 8 May 2014
Line 4:		Line 4:

	==Syntax==		==Syntax==
	INDEX <data file> <index file> <key start position>[/...] <key length>[/...] [-<work path>] [{DUPKEYS\|NATIVE\|REORG\|REPLACE\|LISTDUPKEYS[>[>]<output file>]}][...] [-N]		INDEX <data file> <[[index file]]> <key start position>[/...] <key length>[/...] [-<work path>] [{[[DUPKEYS]]\|NATIVE\|[[REORG]]\|REPLACE\|[[LISTDUPKEYS]][>[>]<output file>]}][...] [-N]

	[[Image:Index.png\|1000px]]		[[Image:Index.png\|1000px]]

Laura: /* Syntax */

2014-05-06T16:42:25Z

Syntax

← Older revision		Revision as of 16:42, 6 May 2014
Line 4:		Line 4:

	==Syntax==		==Syntax==
			INDEX <data file> <index file> <key start position>[/...] <key length>[/...] [-<work path>] [{DUPKEYS\|NATIVE\|REORG\|REPLACE\|LISTDUPKEYS[>[>]<output file>]}][...] [-N]

	[[Image:Index.png\|1000px]]		[[Image:Index.png\|1000px]]

Laura: /* BADKEYS */

2013-07-16T00:59:28Z

BADKEYS

← Older revision		Revision as of 00:59, 16 July 2013
Line 69:		Line 69:

	===BADKEYS===		===BADKEYS===
	{{:~~BADKEYS~~}}		{{:Badkeys}}

	==Technical Considerations==		==Technical Considerations==

Laura at 00:58, 16 July 2013

2013-07-16T00:58:40Z

← Older revision		Revision as of 00:58, 16 July 2013
Line 67:		Line 67:

	The '''-N''' option suppresses all information that would normally be output (except LISTDUPKEYS information).		The '''-N''' option suppresses all information that would normally be output (except LISTDUPKEYS information).

			===BADKEYS===
			{{:BADKEYS}}

	==Technical Considerations==		==Technical Considerations==

Laura at 18:51, 11 July 2013

2013-07-11T18:51:34Z

← Older revision		Revision as of 18:51, 11 July 2013
Line 1:		Line 1:
	The '''Index''' [[command]] creates or recreates an index file. See the [[Index Facility]] for additional information. You may also find it useful to familiarize yourself with the concept of a [http://http://en.wikipedia.org/wiki/Index_(database) Database Index]		The '''Index''' [[command]] creates or recreates an index file. See the [[Index Facility]] for additional information. You may also find it useful to familiarize yourself with the concept of a [http://http://en.wikipedia.org/wiki/Index_(database) Database Index]

	For a simple tutorial, see [[~~How to Make an Index File Tutorial~~\|Index Tutorial]].		For a simple tutorial, see [[Index_and_Sort_facilities_Tutorial\|Index Tutorial]].

	==Syntax==		==Syntax==

Laura at 18:51, 11 July 2013

2013-07-11T18:51:01Z

← Older revision		Revision as of 18:51, 11 July 2013
Line 1:		Line 1:
	The '''Index''' [[command]] creates or recreates an index file. See the [[Index Facility]] for additional information. You may also find it useful to familiarize yourself with the concept of a [http://http://en.wikipedia.org/wiki/Index_(database) Database Index]		The '''Index''' [[command]] creates or recreates an index file. See the [[Index Facility]] for additional information. You may also find it useful to familiarize yourself with the concept of a [http://http://en.wikipedia.org/wiki/Index_(database) Database Index]

			For a simple tutorial, see [[How to Make an Index File Tutorial\|Index Tutorial]].

	==Syntax==		==Syntax==