Form - Revision history

Laura: /* Syntax */

2014-05-05T14:30:57Z

Syntax

← Older revision		Revision as of 14:30, 5 May 2014
Line 39:		Line 39:

	FORM {{POS\|X} {<integer>\|<[[numeric variable]]>}\|		FORM {{POS\|X} {<integer>\|<[[numeric variable]]>}\|
	{<integer>\|<[[numeric variable]]>}* {"<string>"\|PIC(<pic spec>)}\|{<internal form spec><field length>[.<fraction length>]\|<numeric form spec>< field length>[.<fraction length>]}\|<string form spec>[ <field length>]\|<floating point form spec>}[,...]		{<integer>\|<[[numeric variable]]>}* {"<[[string]]>"\|[[PIC]](<pic spec>)}\|{<[[internal form spec]]><field length>[.<fraction length>]\|<[[numeric form spec]]>< field length>[.<fraction length>]}\|<[[string form spec]]>[ <field length>]\|<[[floating point form spec]]>}[,...]

	[[file:form1.png\|850px]]		[[file:form1.png\|850px]]

Laura: /* Syntax */

2014-04-29T16:45:36Z

Syntax

← Older revision		Revision as of 16:45, 29 April 2014
Line 38:		Line 38:
	(FORM for internal and external files)		(FORM for internal and external files)

	FORM {{POS\|X} {<integer>\|<numeric variable>}\|		FORM {{POS\|X} {<integer>\|<[[numeric variable]]>}\|
	{<integer>\|<numeric variable>}* {"<string>"\|PIC(<pic spec>)}\|{<internal form spec><field length>[.<fraction length>]\|<numeric form spec>< field length>[.<fraction length>]}\|<string form spec>[ <field length>]\|<floating point form spec>}[,...]		{<integer>\|<[[numeric variable]]>}* {"<string>"\|PIC(<pic spec>)}\|{<internal form spec><field length>[.<fraction length>]\|<numeric form spec>< field length>[.<fraction length>]}\|<string form spec>[ <field length>]\|<floating point form spec>}[,...]

	[[file:form1.png\|850px]]		[[file:form1.png\|850px]]

Laura: /* Syntax */

2014-04-28T16:03:42Z

Syntax

← Older revision		Revision as of 16:03, 28 April 2014
Line 38:		Line 38:
	(FORM for internal and external files)		(FORM for internal and external files)

	FORM {POS\|X <integer>\|<numeric variable>,}\|		FORM {{POS\|X} {<integer>\|<numeric variable>}\|
	{<integer>\|<numeric variable>* "<string>"\|PIC(<pic spec>)\|<internal form spec><field length>[.<fraction length>]\|<numeric form spec>< field length>[.<fraction length>]\|<string form spec>[ <field length>]\|<floating point form spec>,}		{<integer>\|<numeric variable>}* {"<string>"\|PIC(<pic spec>)}\|{<internal form spec><field length>[.<fraction length>]\|<numeric form spec>< field length>[.<fraction length>]}\|<string form spec>[ <field length>]\|<floating point form spec>}[,...]

	[[file:form1.png\|850px]]		[[file:form1.png\|850px]]

Laura: /* Syntax */

2014-04-24T18:22:57Z

Syntax

← Older revision		Revision as of 18:22, 24 April 2014
Line 84:		Line 84:
	===Syntax===		===Syntax===
	(FORM for display files)		(FORM for display files)

			FORM {POS\|X\|SKIP <integer>\|<numeric variable>,}\|
			{<integer>\|<numeric variable>* "<string>"\|PIC(<pic spec>)\|<internal form spec><field length>[.<fraction length>]\|<numeric form spec>< field length>[.<fraction length>]\|<string form spec>[ <field length>]\|<floating point form spec>,}

	[[File:Form2.png\|850px]]		[[File:Form2.png\|850px]]

Laura: /* Syntax */

2014-04-24T18:19:44Z

Syntax

← Older revision		Revision as of 18:19, 24 April 2014
Line 38:		Line 38:
	(FORM for internal and external files)		(FORM for internal and external files)

	FORM {POS\|X <integer>\|<numeric variable>,}		FORM {POS\|X <integer>\|<numeric variable>,}\|
	{<integer>\|<numeric variable>* "<string>"\|PIC(<pic spec>)\|<internal form spec><field length>[.<fraction length>]\|<numeric form spec>< field length>[.<fraction length>]\|<string form spec>[ <field length>]\|<floating point form spec>,}		{<integer>\|<numeric variable>* "<string>"\|PIC(<pic spec>)\|<internal form spec><field length>[.<fraction length>]\|<numeric form spec>< field length>[.<fraction length>]\|<string form spec>[ <field length>]\|<floating point form spec>,}

Laura: /* Syntax */

2014-04-24T16:35:12Z

Syntax

← Older revision		Revision as of 16:35, 24 April 2014
Line 39:		Line 39:

	FORM {POS\|X <integer>\|<numeric variable>,}		FORM {POS\|X <integer>\|<numeric variable>,}
	{<integer>\|<numeric variable>* "<string>"\|PIC(<pic spec>)\|<internal form spec><field length>[.<fraction length>]\|<numeric form spec><field length>[.<fraction length>],}		{<integer>\|<numeric variable>* "<string>"\|PIC(<pic spec>)\|<internal form spec><field length>[.<fraction length>]\|<numeric form spec>< field length>[.<fraction length>]\|<string form spec>[ <field length>]\|<floating point form spec>,}
	{<string form spec> [<field length>],}
	{<floating point form spec>,}

	[[file:form1.png\|850px]]		[[file:form1.png\|850px]]

Laura: /* Syntax */

2014-04-24T16:31:38Z

Syntax

← Older revision		Revision as of 16:31, 24 April 2014
Line 36:		Line 36:
	===Syntax===		===Syntax===

	(FORM for internal and external files)<br>		(FORM for internal and external files)

			FORM {POS\|X <integer>\|<numeric variable>,}
			{<integer>\|<numeric variable>* "<string>"\|PIC(<pic spec>)\|<internal form spec><field length>[.<fraction length>]\|<numeric form spec><field length>[.<fraction length>],}
			{<string form spec> [<field length>],}
			{<floating point form spec>,}

	[[file:form1.png\|850px]]		[[file:form1.png\|850px]]

Laura: /* Parameters */

2014-04-18T01:30:53Z

Parameters

← Older revision		Revision as of 01:30, 18 April 2014
Line 60:		Line 60:
	A general definition for the next set of parameters in FORM's syntax is that they allow you to describe the type and length of the information to be printed.		A general definition for the next set of parameters in FORM's syntax is that they allow you to describe the type and length of the information to be printed.

	One exception to this is the "~~character~~ string" parameter: this specification (also referred to as a "literal") is the information to be printed. When a "~~character~~ string" is specified for output, Business Rules or prints the literal. When used for input, the "character string" functions the same as X for the length of the literal. The character string must be enclosed within quotation marks.		One exception to this is the "string" parameter, which can be any set of characters: this specification (also referred to as a "literal") is the information to be printed. When a "string" is specified for output, Business Rules or prints the literal. When used for input, the "character string" functions the same as X for the length of the literal. The character string must be enclosed within quotation marks.

	The "[[PIC]](pic-spec)" parameter allows you to specify a picture of the information to be printed. To use this parameter, you must specify the keyword PIC and then, in parenthesis, identify the desired picture of the information to be printed. Each character within the parenthesis is either an insertion character (to be printed as is) or a digit identifier (to be replaced with a digit when printed). See [[File I/O]] for more information about the PIC specification.		The "[[PIC]](pic-spec)" parameter allows you to specify a picture of the information to be printed. To use this parameter, you must specify the keyword PIC and then, in parenthesis, identify the desired picture of the information to be printed. Each character within the parenthesis is either an insertion character (to be printed as is) or a digit identifier (to be replaced with a digit when printed). See [[File I/O]] for more information about the PIC specification.

Laura: /* Comments and Examples */

2013-08-07T14:51:37Z

Comments and Examples

← Older revision		Revision as of 14:51, 7 August 2013
Line 24:		Line 24:
	00020 FORM "TYPE A", C 10		00020 FORM "TYPE A", C 10
	00030 READ #1,USING 20: A$		00030 READ #1,USING 20: A$

			Form statements may follow the line label reference:

			00500 print #255, using nameform2: A$(1),E$,RF$,"",d1$
			00510 nameform2: form pos 16,c 30,x 9,c 6,x 16,c 7,x 24,c 2,x 16,c 8, skip 3

			Or may be included within quotations in the first statement:

			00600 print #255, using "form pos 18,c 5,skip 1": "SAL.","O.T.","ADD'L","HOL.","Vac.","Sick"

	===Syntax===		===Syntax===

Laura: /* Technical Considerations */

2013-01-21T21:35:58Z

Technical Considerations

← Older revision		Revision as of 21:35, 21 January 2013
Line 75:		Line 75:

	===Technical Considerations===		===Technical Considerations===
	:1.) SKIP 0 causes the printer to do a carriage return, but not a line feed. This is used for overstrike capability and bold printing. For example:		:1.) SKIP 0 causes the printer to do a carriage return, but not a line feed (returns the pointer to the beginning of the current line). This was used for overstrike capability and bold printing on dot matrix printers. For example:

	00010 PRINT USING 20: "BOLD","BOLD"		00010 PRINT USING 20: "BOLD","BOLD"
Line 86:		Line 86:
	00020 FORM POS 5,C 4,POS 5,C 4		00020 FORM POS 5,C 4,POS 5,C 4

	:2.) ~~SKIP~~ 0 prevents line output and saves the current line position for the next PRINT statement. For example:		For details on printing in bold or other styles on modern printers, see [[attributes]].

			:2.) POS 0 prevents line output and saves the current line position for the next PRINT statement. For example:

	00010 PRINT USING 20: "ALL ON THE SAME"		00010 PRINT USING 20: "ALL ON THE SAME"
Line 93:		Line 95:
	00040 FORM C 4		00040 FORM C 4

	;outputs:		outputs:
	ALL ON THE SAME LINE		ALL ON THE SAME LINE

Line 102:		Line 104:
	00020 FORM N 3		00020 FORM N 3

	;outputs:		outputs:
	1 2 3		1 2 3

Line 121:		Line 123:
	:8.) Non-integer values are rounded when a variable is used as a repetition factor, field length or fraction length.		:8.) Non-integer values are rounded when a variable is used as a repetition factor, field length or fraction length.
	:9.) The G format specification is useful when a data item could be a string or a number; it allows the system to read in either string or numeric data without returning an error.		:9.) The G format specification is useful when a data item could be a string or a number; it allows the system to read in either string or numeric data without returning an error.
	:10.) ARRAY elements are formatted in row order (see the READ statement for more information).		:10.) ARRAY elements are formatted in row order (see the [[READ]] statement for more information).
	:11.) FORM statements are non-executable and may be placed anywhere in the program.		:11.) FORM statements are non-executable and may be placed anywhere in the program.
	:12.) A FORM statement must be the only statement on a line or an error [[0726]] ~~result~~.		:12.) A FORM statement must be the only statement on a line or an error [[0726]] results.
	:13.) If a negative number is being output with a PIC specification, there must be a sign specifier in the PIC.		:13.) If a negative number is being output with a PIC specification, there must be a sign specifier in the PIC.
	:14.) Using a PIC specification for output with a string variable is the same as C (PIC width).		:14.) Using a PIC specification for output with a string variable is the same as C (PIC width).
Line 137:		Line 139:
	When days() or DH is used to store a date, normal sorting and indexing becomes Y2K compliant. The days() function, and the date formats enable BASEYEAR processing		When days() or DH is used to store a date, normal sorting and indexing becomes Y2K compliant. The days() function, and the date formats enable BASEYEAR processing
	when the values are stored in binary fields. These can subsequently be indexed as character fields so long as they were stored in high-to-low order.		when the values are stored in binary fields. These can subsequently be indexed as character fields so long as they were stored in high-to-low order.


	===See Also===		===See Also===

← Older revision		Revision as of 14:30, 5 May 2014
Line 39:		Line 39:

	FORM {{POS\|X} {<integer>\|<[[numeric variable]]>}\|		FORM {{POS\|X} {<integer>\|<[[numeric variable]]>}\|
	{<integer>\|<[[numeric variable]]>}* {"<string>"\|PIC(<pic spec>)}\|{<internal form spec><field length>[.<fraction length>]\|<numeric form spec>< field length>[.<fraction length>]}\|<string form spec>[ <field length>]\|<floating point form spec>}[,...]		{<integer>\|<[[numeric variable]]>}* {"<[[string]]>"\|[[PIC]](<pic spec>)}\|{<[[internal form spec]]><field length>[.<fraction length>]\|<[[numeric form spec]]>< field length>[.<fraction length>]}\|<[[string form spec]]>[ <field length>]\|<[[floating point form spec]]>}[,...]

	[[file:form1.png\|850px]]		[[file:form1.png\|850px]]