Introduction to User Language - Revision history

Abe: /* Compilation errors */ removed AFAIK-incorrectly-added recent addition of underlining to the example re when the mode is “X'01'”

2024-10-03T14:33:26Z

Compilation errors: removed AFAIK-incorrectly-added recent addition of underlining to the example re when the mode is “X'01'”

← Older revision		Revision as of 14:33, 3 October 2024
Line 318:		Line 318:
	</ul>		</ul>
	<p class="code"><b></b> 1* M204.2775: INVALID EXPRESSION IN INITIAL CLAUSE **********		<p class="code"><b></b> 1* M204.2775: INVALID EXPRESSION IN INITIAL CLAUSE **********
	*** %A IS STRING LEN 10 DP 0 INITIAL(>~~><u~~>C'A1B2'~~</u>~~<<) STATIC *****		*** %A IS STRING LEN 10 DP 0 INITIAL(>>C'A1B2'<<) STATIC *****
	***** (FILE = ULP42, PROCEDURE = V4R2.TEST.42FINIT.ERRORA, LINE=10		***** (FILE = ULP42, PROCEDURE = V4R2.TEST.42FINIT.ERRORA, LINE=10
	***** M204.1042: COMPILATION ERRORS		***** M204.1042: COMPILATION ERRORS

Abe: /* Compilation errors */ underlining

2024-10-03T14:21:58Z

Compilation errors: underlining

← Older revision		Revision as of 14:21, 3 October 2024
Line 318:		Line 318:
	</ul>		</ul>
	<p class="code"><b></b> 1* M204.2775: INVALID EXPRESSION IN INITIAL CLAUSE **********		<p class="code"><b></b> 1* M204.2775: INVALID EXPRESSION IN INITIAL CLAUSE **********
	*** %A IS STRING LEN 10 DP 0 INITIAL(>>C'A1B2'<<) STATIC *****		*** %A IS STRING LEN 10 DP 0 INITIAL(>><u>C'A1B2'</u><<) STATIC *****
	***** (FILE = ULP42, PROCEDURE = V4R2.TEST.42FINIT.ERRORA, LINE=10		***** (FILE = ULP42, PROCEDURE = V4R2.TEST.42FINIT.ERRORA, LINE=10
	***** M204.1042: COMPILATION ERRORS		***** M204.1042: COMPILATION ERRORS
Line 327:		Line 327:
	</ul>		</ul>
	<p class="code"><b></b> 1* M204.2775: INVALID EXPRESSION IN INITIAL CLAUSE **********		<p class="code"><b></b> 1* M204.2775: INVALID EXPRESSION IN INITIAL CLAUSE **********
	*** %A IS STRING LEN 10 DP 0 INITIAL(C'A1B2') STATIC *********		*** %A IS STRING LEN 10 DP 0 INITIAL(<u>C'A1B2'</u>) STATIC *********
	***** (FILE = ULP42, PROCEDURE = V4R2.TEST.42FINIT.ERRORA, LINE=10		***** (FILE = ULP42, PROCEDURE = V4R2.TEST.42FINIT.ERRORA, LINE=10
	***** M204.1042: COMPILATION ERRORS		***** M204.1042: COMPILATION ERRORS

Abe: /* Compilation errors */ em dashes around “one or many”

2024-10-03T14:05:58Z

Compilation errors: em dashes around “one or many”

← Older revision		Revision as of 14:05, 3 October 2024
Line 310:		Line 310:
	<b>Compilation error handling</b>		<b>Compilation error handling</b>
	<p>		<p>
	Sometimes an initial compilation error causes a cascade of subsequent error messages that do not help you analyze the problem. Furthermore, the error messages do not point out just where the problem occurred. The COMPERR parameter lets you determine how many error message--one or many--to display and to highlight the code that resulted in the error.</p>		Sometimes an initial compilation error causes a cascade of subsequent error messages that do not help you analyze the problem. Furthermore, the error messages do not point out just where the problem occurred. The COMPERR parameter lets you determine how many error message — one or many — to display and to highlight the code that resulted in the error.</p>
	<p>		<p>
	You can set COMPERR to X'01', X'02', X'04', or a sum of a combination of your choice. </p>		You can set COMPERR to X'01', X'02', X'04', or a sum of a combination of your choice. </p>
Line 339:		Line 339:
	</li>		</li>
	</ul>		</ul>

	===Counting errors===		===Counting errors===
	<p>		<p>

Abe: /* Remote files and scattered groups */ hyphenation [again — I missed one the first time in this section]

2024-10-03T14:04:28Z

Remote files and scattered groups: hyphenation [again — I missed one the first time in this section]

← Older revision		Revision as of 14:04, 3 October 2024
Line 297:		Line 297:
	===Remote files and scattered groups===		===Remote files and scattered groups===
	<p>		<p>
	Parallel Query Option/204 users can access data stored in files in remote locations, in single-remote-file context, or in scattered group context. A scattered group is a file group which is locally defined, and which includes at least one remote file as a member.</p>		Parallel Query Option/204 users can access data stored in files in remote locations, in single-remote-file context, or in scattered-group context. A scattered group is a file group which is locally defined, and which includes at least one remote file as a member.</p>
	<p>		<p>
	Throughout this manual, all references to remote files, scattered groups, and remote file or scattered-group context, are addressed to Parallel Query Option/204 users. </p>		Throughout this manual, all references to remote files, scattered groups, and remote file or scattered-group context, are addressed to Parallel Query Option/204 users. </p>

Abe: /* Remote files and scattered groups */ hyphenation

2024-10-03T14:03:30Z

Remote files and scattered groups: hyphenation

← Older revision		Revision as of 14:03, 3 October 2024
Line 297:		Line 297:
	===Remote files and scattered groups===		===Remote files and scattered groups===
	<p>		<p>
	Parallel Query Option/204 users can access data stored in files in remote locations, in single remote file context, or in scattered group context. A scattered group is a file group which is locally defined, and which includes at least one remote file as a member.</p>		Parallel Query Option/204 users can access data stored in files in remote locations, in single-remote-file context, or in scattered group context. A scattered group is a file group which is locally defined, and which includes at least one remote file as a member.</p>
	<p>		<p>
	Throughout this manual, all references to remote files, scattered groups, and remote file or scattered group context, are addressed to Parallel Query Option/204 users. </p>		Throughout this manual, all references to remote files, scattered groups, and remote file or scattered-group context, are addressed to Parallel Query Option/204 users. </p>

	==Request compilation and evaluation==		==Request compilation and evaluation==
	<p>		<p>

Abe: /* Composition of a Model 204 file */ “direct access devices” => “direct-access storage devices (DASDs)”

2024-10-03T14:02:38Z

Composition of a Model 204 file: “direct access devices” => “direct-access storage devices (DASDs)”

← Older revision		Revision as of 14:02, 3 October 2024
Line 226:		Line 226:
	===Composition of a Model 204 file===		===Composition of a Model 204 file===
	<p>		<p>
	A file is stored on one or more physical data sets on direct access devices. </p>		A file is stored in one or more physical data sets on direct-access storage devices (DASDs).</p>
	<p>		<p>
	A file is divided into the following logical sections: </p>		A file is divided into the following logical sections: </p>

Abe: /* Stored procedures */ hyphenation

2024-10-03T14:01:17Z

Stored procedures: hyphenation

← Older revision		Revision as of 14:01, 3 October 2024
Line 37:		Line 37:
	Any combination of commands and User Language statements can be saved for later execution. These sequences can be rerun at any time, or edited and rerun at any time, without being reentered. Stored procedures are permanently stored in your database until they are deleted or revised.</p>		Any combination of commands and User Language statements can be saved for later execution. These sequences can be rerun at any time, or edited and rerun at any time, without being reentered. Stored procedures are permanently stored in your database until they are deleted or revised.</p>
	<p>		<p>
	Stored procedures can be included as parts of requests, or they can be run alone either unconditionally or as a result of a specified test. Typical practice is to store commonly used requests, application procedures, screen layouts, or print statements for standard report formats.</p>		Stored procedures can be included as parts of requests, or they can be run alone either unconditionally or as a result of a specified test. Typical practice is to store commonly-used requests, application procedures, screen layouts, or print statements for standard report formats.</p>
	<p>		<p>
	Stored procedures can be made more flexible by using techniques which call for end-user input at runtime by suspending execution and displaying a prompt. The user's input is used by the procedure as the value of a variable which can specify, for example, a record search criterion. </p>		Stored procedures can be made more flexible by using techniques which call for end-user input at runtime by suspending execution and displaying a prompt. The user's input is used by the procedure as the value of a variable which can specify, for example, a record search criterion. </p>

	===Optional User Language/DATABASE 2 Interface===		===Optional User Language/DATABASE 2 Interface===
	<p>		<p>

Abe: /* Fields */ hyphenation

2024-10-03T14:00:42Z

Fields: hyphenation

← Older revision		Revision as of 14:00, 3 October 2024
Line 196:		Line 196:
	</p>		</p>
	<p>		<p>
	Field names can appear more than once within single records. Such multiply occurring fields can be used in expressing retrieval conditions in the same manner as other fields. File maintenance statements are provided for changing or deleting multiply occurring fields. </p>		Field names can appear more than once within single records. Such multiply-occurring fields can be used in expressing retrieval conditions in the same manner as other fields. File maintenance statements are provided for changing or deleting multiply occurring fields. </p>
	<p>		<p>
	Each <var class="product">Model 204</var> field has a set of one or more attributes called the field description. In [[#Request structure\|Request structure]], the field CITY might be a KEY field. Thus, records containing the value CITY = SAN DIEGO can be located through the index (Table C), rather than by directly searching the data records (Table B). CITY might also be an FRV (for-each-value) or ORDERED field, which means that it can be used with FOR EACH VALUE statements (see [[Value loops]]). </p>		Each <var class="product">Model 204</var> field has a set of one or more attributes called the field description. In [[#Request structure\|Request structure]], the field CITY might be a KEY field. Thus, records containing the value CITY = SAN DIEGO can be located through the index (Table C), rather than by directly searching the data records (Table B). CITY might also be an FRV (for-each-value) or ORDERED field, which means that it can be used with FOR EACH VALUE statements (see [[Value loops]]). </p>

	===Records===		===Records===
	<p>		<p>

Abe: /* Report statements */ “multipage reports” instead of “multiple page reports”

2024-10-03T13:59:34Z

Report statements: “multipage reports” instead of “multiple page reports”

← Older revision		Revision as of 13:59, 3 October 2024
Line 135:		Line 135:
	Entire records, the contents of selected fields within records, or computations based on the selected fields can be formatted and displayed. Output can be displayed at the terminal, directed to a data set for intermediate storage, or directed to system spooling facilities (that is, printers).</p>		Entire records, the contents of selected fields within records, or computations based on the selected fields can be formatted and displayed. Output can be displayed at the terminal, directed to a data set for intermediate storage, or directed to system spooling facilities (that is, printers).</p>
	<p>		<p>
	Field values can be positioned anywhere on the terminal display: left-justified, right-justified, truncated between two positions, or positioned at variable tab stops. Field values can be concatenated and edited for output. Quoted strings can be printed for output labels or comments. Page header and trailer lines can be entered or deleted on ~~multiple page~~ reports. Paging is specified by a variable line count parameter; new page and multiple line-skip statements are provided.</p>		Field values can be positioned anywhere on the terminal display: left-justified, right-justified, truncated between two positions, or positioned at variable tab stops. Field values can be concatenated and edited for output. Quoted strings can be printed for output labels or comments. Page header and trailer lines can be entered or deleted on multipage reports. Paging is specified by a variable line count parameter; new page and multiple line-skip statements are provided.</p>
	<p>		<p>
	Output can be formatted using the full-screen feature and displayed for subsequent review and data entry.</p>		Output can be formatted using the full-screen feature and displayed for subsequent review and data entry.</p>

	===Full-screen formatting===		===Full-screen formatting===
	<p>		<p>

Abe: /* Computation */ hyphenation

2024-10-03T13:58:34Z

Computation: hyphenation

← Older revision		Revision as of 13:58, 3 October 2024
Line 123:		Line 123:
	User Language can perform arithmetic and logical operations using constants, field values, special temporary variables, and functional values. You can define any number of temporary variables within the context of a request. Variables can be set in assignment statements or used within expressions, and they can be arrays. The number of significant digits retained by fixed point or string variables can be set. Variable names always start with a percent sign (for example, %YEAR). </p>		User Language can perform arithmetic and logical operations using constants, field values, special temporary variables, and functional values. You can define any number of temporary variables within the context of a request. Variables can be set in assignment statements or used within expressions, and they can be arrays. The number of significant digits retained by fixed point or string variables can be set. Variable names always start with a percent sign (for example, %YEAR). </p>
	<p>		<p>
	A set of built-in functions extends the capabilities of User Language. These functions provide facilities for data editing and validation, character string manipulation, global variables, and current date and time. The FORTRAN set of mathematical functions is also available as an option. Function names always start with a dollar sign (for example, $DATE).</p>		A set of built-in functions extends the capabilities of User Language. These functions provide facilities for data editing and validation, character-string manipulation, global variables, and current date and time. The FORTRAN set of mathematical functions is also available as an option. Function names always start with a dollar sign (for example, $DATE).</p>
	<p>		<p>
	Expressions are formed by combining constants, variables, functions, field names, or other expressions with operators. Parentheses can be used to alter the normal sequence of operations. </p>		Expressions are formed by combining constants, variables, functions, field names, or other expressions with operators. Parentheses can be used to alter the normal sequence of operations. </p>
	<p>		<p>
	Computational results can be used for output purposes, to store derived information in the database, or to control the sequence of operations within a request.</p>		Computational results can be used for output purposes, to store derived information in the database, or to control the sequence of operations within a request.</p>

	===Report statements===		===Report statements===
	<p>		<p>