FMT vs PIC - Revision history

Gordon.dye: /* FMT Syntax */

2023-03-31T19:09:17Z

FMT Syntax

← Older revision		Revision as of 19:09, 31 March 2023
Line 22:		Line 22:
	\|width="10%"\|'''P or p'''\|\|Protected. Business Rules will not allow the cursor to rest on or change any data that is displayed in this position		\|width="10%"\|'''P or p'''\|\|Protected. Business Rules will not allow the cursor to rest on or change any data that is displayed in this position
	\|-valign="top"		\|-valign="top"
	\|width="10%"\|'''R'''\|\|Right flush this part from current position to the end of this part or ~~next~~ #, ~~whichever comes first; allow format and force case~~ according to the next character identifier within this part (if R is the only ~~one~~ used, error [[0805]] will result).		\|width="10%"\|'''R'''\|\|Mimic the next character specification. Right flush this part from current position to the end of this part (preceding next R or #), process according to the next character identifier within this part (if R is the only character type used, error [[0805]] will result).
	\|-valign="top"		\|-valign="top"
	\|width="10%"\|'''X'''\|\|Allow any character and force to uppercase if its alphabetic.		\|width="10%"\|'''X'''\|\|Allow any character and force to uppercase if its alphabetic.
Line 32:		Line 32:
	\|width="10%"\|'''y'''\|\|Allow only Y, y, N, or n, and force it to lowercase.		\|width="10%"\|'''y'''\|\|Allow only Y, y, N, or n, and force it to lowercase.
	\|-valign="top"		\|-valign="top"
	\|width="10%"\|'''#'''\|\|Right flush and zero fill from current position to end of this part or next R, ~~whichever comes first; allow format and force case~~ according to the next character identifier within this part (if # is the only one used, error [[0805]] will result).		\|width="10%"\|'''#'''\|\|Mimic the next character specification. Right flush and zero fill from current position to end of this part (preceding next R or #), process according to the next character identifier within this part (if # is the only one used, error [[0805]] will result).
	\|-valign="top"		\|-valign="top"
	\|}		\|}

Laura: /* FMT Syntax */

2013-02-21T03:04:46Z

FMT Syntax

← Older revision		Revision as of 03:04, 21 February 2013
Line 40:		Line 40:

	Insertion characters are inserted for the operator's benefit. They will not be in the data. Note that "P" can be used to protect characters that you want to appear in the data.		Insertion characters are inserted for the operator's benefit. They will not be in the data. Note that "P" can be used to protect characters that you want to appear in the data.

			<noinclude>
			[[Category:Format Specifications]]
			</noinclude>

Laura: /* FMT Syntax */

2013-02-21T03:02:38Z

FMT Syntax

← Older revision		Revision as of 03:02, 21 February 2013
Line 12:		Line 12:
	{\|		{\|
	\|-valign="top"		\|-valign="top"
	\|width="10%"\|'''P or p'''\|\|Protected. Business Rules will not allow the cursor to rest on or change any data that is displayed in this position.		\|width="10%"\|'''9'''\|\|Allow any number from 0 to 9.
			\|-valign="top"
			\|width="10%"\|'''a'''\|\|Allow any character from A to Z or a to z, and leave case as entered.
			\|-valign="top"
			\|width="10%"\|'''G'''\|\|Allow any character from A to Z, a to z, or 0 to 9, and force it to upppercase if its alphabetic.
			\|-valign="top"
			\|width="10%"\|'''g'''\|\|Allow any character from A to Z, a to z, or 0 to 9, and force it to lowercase if its alphabetic.
			\|-valign="top"
			\|width="10%"\|'''P or p'''\|\|Protected. Business Rules will not allow the cursor to rest on or change any data that is displayed in this position
			\|-valign="top"
			\|width="10%"\|'''R'''\|\|Right flush this part from current position to the end of this part or next #, whichever comes first; allow format and force case according to the next character identifier within this part (if R is the only one used, error [[0805]] will result).
			\|-valign="top"
			\|width="10%"\|'''X'''\|\|Allow any character and force to uppercase if its alphabetic.
			\|-valign="top"
			\|width="10%"\|'''x'''\|\|Allow any character and force to lowercase if its alphabetic.
			\|-valign="top"
			\|width="10%"\|'''Y'''\|\|Allow only Y, y, N, or n, and force it to uppercase.
			\|-valign="top"
			\|width="10%"\|'''y'''\|\|Allow only Y, y, N, or n, and force it to lowercase.
			\|-valign="top"
			\|width="10%"\|'''#'''\|\|Right flush and zero fill from current position to end of this part or next R, whichever comes first; allow format and force case according to the next character identifier within this part (if # is the only one used, error [[0805]] will result).
	\|-valign="top"		\|-valign="top"
	\|}		\|}
	<br>		<br>
	~~[[Image:FmtChart2.jpg]]<br>~~
	Insertion characters are displayed exactly as they appear in the FMT specification. Business Rules treats any keyboard character that is not a character identifier (listed above) as an insertion character.		Insertion characters are displayed exactly as they appear in the FMT specification. Business Rules treats any keyboard character that is not a character identifier (listed above) as an insertion character.

	Insertion characters are inserted for the operator's benefit. They will not be in the data. Note that "P" can be used to protect characters that you want to appear in the data.		Insertion characters are inserted for the operator's benefit. They will not be in the data. Note that "P" can be used to protect characters that you want to appear in the data.

Laura at 02:50, 21 February 2013

2013-02-21T02:50:17Z

← Older revision		Revision as of 02:50, 21 February 2013
Line 1:		Line 1:
	With some exceptions, [[FMT]] is best suited to handling strings, whereas [[PIC]] is generally used with numeric data only.		With some exceptions, [[FMT]] is best suited to handling strings, whereas [[PIC]] is generally used with numeric data only. See the chart below comparing the two:

	[[Image:FmtChart.jpg\|750px]]		[[Image:FmtChart.jpg\|750px]]

			===FMT Syntax===
	[[Image:Fmt.png\|500px]]<br>		[[Image:Fmt.png\|500px]]<br>

Laura at 02:49, 21 February 2013

2013-02-21T02:49:10Z

← Older revision		Revision as of 02:49, 21 February 2013
Line 1:		Line 1:
	With some exceptions, [[FMT]] is best suited to handling strings, whereas [[PIC]] is generally used with numeric data only.		With some exceptions, [[FMT]] is best suited to handling strings, whereas [[PIC]] is generally used with numeric data only.

	[[Image:FmtChart.jpg]]		[[Image:FmtChart.jpg\|750px]]

	[[Image:Fmt.png\|500px]]<br>		[[Image:Fmt.png\|500px]]<br>

Laura at 02:30, 21 February 2013

2013-02-21T02:30:44Z

← Older revision		Revision as of 02:30, 21 February 2013
Line 3:		Line 3:
	[[Image:FmtChart.jpg]]		[[Image:FmtChart.jpg]]

	[[Image:Fmt.png\|~~400px~~]]<br>		[[Image:Fmt.png\|500px]]<br>

	The FMT spec can be used in the same places that PIC is allowed in INPUT FIELDS, RINPUT FIELDS and PRINT FIELDS statements. The FMT keyword must be followed by up to 40 character identifiers and/or insertion characters.		The FMT spec can be used in the same places that PIC is allowed in INPUT FIELDS, RINPUT FIELDS and PRINT FIELDS statements. The FMT keyword must be followed by up to 40 character identifiers and/or insertion characters.

Laura at 02:30, 21 February 2013

2013-02-21T02:30:26Z

← Older revision		Revision as of 02:30, 21 February 2013
Line 3:		Line 3:
	[[Image:FmtChart.jpg]]		[[Image:FmtChart.jpg]]

	[[Image:Fmt.png]]<br>		[[Image:Fmt.png\|400px]]<br>

	The FMT spec can be used in the same places that PIC is allowed in INPUT FIELDS, RINPUT FIELDS and PRINT FIELDS statements. The FMT keyword must be followed by up to 40 character identifiers and/or insertion characters.		The FMT spec can be used in the same places that PIC is allowed in INPUT FIELDS, RINPUT FIELDS and PRINT FIELDS statements. The FMT keyword must be followed by up to 40 character identifiers and/or insertion characters.

Laura at 02:29, 21 February 2013

2013-02-21T02:29:34Z

← Older revision		Revision as of 02:29, 21 February 2013
Line 15:		Line 15:
	\|}		\|}
	<br>		<br>
	[[Image:~~Help0171~~.jpg]]<br>		[[Image:FmtChart2.jpg]]<br>
	Insertion characters are displayed exactly as they appear in the FMT specification. Business Rules treats any keyboard character that is not a character identifier (listed above) as an insertion character.		Insertion characters are displayed exactly as they appear in the FMT specification. Business Rules treats any keyboard character that is not a character identifier (listed above) as an insertion character.

	Insertion characters are inserted for the operator's benefit. They will not be in the data. Note that "P" can be used to protect characters that you want to appear in the data.		Insertion characters are inserted for the operator's benefit. They will not be in the data. Note that "P" can be used to protect characters that you want to appear in the data.

Laura at 02:29, 21 February 2013

2013-02-21T02:29:15Z

← Older revision		Revision as of 02:29, 21 February 2013
Line 1:		Line 1:
	With some exceptions, [[FMT]] is best suited to handling strings, whereas [[PIC]] is generally used with numeric data only.		With some exceptions, [[FMT]] is best suited to handling strings, whereas [[PIC]] is generally used with numeric data only.

	[[Image:~~Help0169~~.jpg]]		[[Image:FmtChart.jpg]]

			[[Image:Fmt.png]]<br>

	~~[[Image:Help0170.jpg]]<br>~~
	The FMT spec can be used in the same places that PIC is allowed in INPUT FIELDS, RINPUT FIELDS and PRINT FIELDS statements. The FMT keyword must be followed by up to 40 character identifiers and/or insertion characters.		The FMT spec can be used in the same places that PIC is allowed in INPUT FIELDS, RINPUT FIELDS and PRINT FIELDS statements. The FMT keyword must be followed by up to 40 character identifiers and/or insertion characters.

Laura: Created page with "With some exceptions, FMT is best suited to handling strings, whereas PIC is generally used with numeric data only. Image:Help0169.jpg Image:Help0170.jpg
..."

2013-02-20T23:42:04Z

Created page with "With some exceptions, FMT is best suited to handling strings, whereas PIC is generally used with numeric data only. Image:Help0169.jpg Image:Help0170.jpg<br>..."

New page

With some exceptions, [[FMT]] is best suited to handling strings, whereas [[PIC]] is generally used with numeric data only.

[[Image:Help0169.jpg]]

[[Image:Help0170.jpg]]<br>
The FMT spec can be used in the same places that PIC is allowed in INPUT FIELDS, RINPUT FIELDS and PRINT FIELDS statements. The FMT keyword must be followed by up to 40 character identifiers and/or insertion characters.

Character identifiers tell the system which characters are allowed in the current position, and they identify the way in which the data part should be formatted for input. (Business Rules considers any section of a FMT spec, which is separated from other sections by one or more insertion characters to be a data part.) The following character identifiers are currently available:

{|
|-valign="top"
|width="10%"|'''P or p'''||Protected. Business Rules will not allow the cursor to rest on or change any data that is displayed in this position.
|-valign="top"
|}
<br>
[[Image:Help0171.jpg]]<br>
Insertion characters are displayed exactly as they appear in the FMT specification. Business Rules treats any keyboard character that is not a character identifier (listed above) as an insertion character.

Insertion characters are inserted for the operator's benefit. They will not be in the data. Note that "P" can be used to protect characters that you want to appear in the data.

FMT vs PIC - Revision history

Gordon.dye: /* FMT Syntax */

Laura: /* FMT Syntax */

Laura: /* FMT Syntax */

Laura at 02:50, 21 February 2013

Laura at 02:49, 21 February 2013

Laura at 02:30, 21 February 2013

Laura at 02:30, 21 February 2013

Laura at 02:29, 21 February 2013

Laura at 02:29, 21 February 2013

Laura: Created page with "With some exceptions, FMT is best suited to handling strings, whereas PIC is generally used with numeric data only. Image:Help0169.jpg Image:Help0170.jpg..."

Laura: Created page with "With some exceptions, FMT is best suited to handling strings, whereas PIC is generally used with numeric data only. Image:Help0169.jpg Image:Help0170.jpg
..."