UL/DB2 and SQL statements - Revision history

Admin: Admin moved page SQL statements in a User Language procedure to UL/DB2 and SQL statements without leaving a redirect

2015-11-25T21:03:45Z

← Older revision	Revision as of 21:03, 25 November 2015
(No difference)

2015-11-25T20:40:03Z

← Older revision		Revision as of 20:40, 25 November 2015
Line 695:		Line 695:
	<p>		<p>
	You can use the Model 204 <var>[[USE PRINTER / PUNCH command\|USE PRINTER]]</var> command to direct the output.</p>		You can use the Model 204 <var>[[USE PRINTER / PUNCH command\|USE PRINTER]]</var> command to direct the output.</p>

			==See also==
			{{Template:UL/DB2 topic list}}

	[[Category: UL/DB2]]		[[Category: UL/DB2]]

2015-07-29T21:16:32Z

Invalid statement

← Older revision		Revision as of 21:16, 29 July 2015
Line 694:		Line 694:
	<p class="note"><b>Note:</b> In $SPIFY, a dash (-) in the output indicates that the column has the NULL indicator set.</p>		<p class="note"><b>Note:</b> In $SPIFY, a dash (-) in the output indicates that the column has the NULL indicator set.</p>
	<p>		<p>
	You can use the Model 204 <var>[[USE PRINTER/PUNCH command\|USE PRINTER]]</var> command to direct the output.</p>		You can use the Model 204 <var>[[USE PRINTER / PUNCH command\|USE PRINTER]]</var> command to direct the output.</p>

	[[Category: UL/DB2]]		[[Category: UL/DB2]]

2015-07-29T21:14:27Z

Invalid statement

← Older revision		Revision as of 21:14, 29 July 2015
Line 694:		Line 694:
	<p class="note"><b>Note:</b> In $SPIFY, a dash (-) in the output indicates that the column has the NULL indicator set.</p>		<p class="note"><b>Note:</b> In $SPIFY, a dash (-) in the output indicates that the column has the NULL indicator set.</p>
	<p>		<p>
	You can use the Model 204 <var>[[USE PRINTER command\|USE PRINTER]]</var> command to direct the output.</p>		You can use the Model 204 <var>[[USE PRINTER/PUNCH command\|USE PRINTER]]</var> command to direct the output.</p>

	[[Category: UL/DB2]]		[[Category: UL/DB2]]

2015-07-29T21:09:07Z

Example

← Older revision		Revision as of 21:09, 29 July 2015
Line 247:		Line 247:
	END REPEAT</p>		END REPEAT</p>
	<p>		<p>
	A $STATUS of 100 indicates that the FETCH found no rows or no more rows. After each FETCH, test for a $STATUS of 100 and move out of the loop when you encounter it. See [[~~Interpreting~~ codes and messages]] for more information on $STATUS and error processing.</p>		A $STATUS of 100 indicates that the FETCH found no rows or no more rows. After each FETCH, test for a $STATUS of 100 and move out of the loop when you encounter it. See [[UL/DB2 error codes and messages]] for more information on $STATUS and error processing.</p>
	<p>		<p>
	Also, test for $STATUS NE 0 and $STATUS NE 100 for a real error condition (an exceptional case).</p>		Also, test for $STATUS NE 0 and $STATUS NE 100 for a real error condition (an exceptional case).</p>

2015-07-29T21:08:33Z

Checking $STATUS

← Older revision		Revision as of 21:08, 29 July 2015
Line 84:		Line 84:
	===Checking $STATUS===		===Checking $STATUS===
	<p>		<p>
	Check $STATUS after each EXEC DB2... END EXEC block to make sure that the processing completed correctly. See [[~~Interpreting~~ codes and messages#$STATUS and $STATUSD\|$STATUS and $STATUSD]] for more information on checking $STATUS in a User Language procedure.</p>		Check $STATUS after each EXEC DB2... END EXEC block to make sure that the processing completed correctly. See [[UL/DB2 error codes and messages#$STATUS and $STATUSD\|$STATUS and $STATUSD]] for more information on checking $STATUS in a User Language procedure.</p>

	==Connecting a User Language procedure to DB2==		==Connecting a User Language procedure to DB2==

2015-07-29T21:07:54Z

Errors connecting to DB2

← Older revision		Revision as of 21:07, 29 July 2015
Line 111:		Line 111:
	====Errors connecting to DB2====		====Errors connecting to DB2====
	<p>		<p>
	If the CONNECT TO statement within a User Language procedure fails, Model 204 displays an error message. See [[~~Interpreting~~ codes and messages#Errors involving Call Attach Facility calls\|Errors involving Call Attach Facility calls]] for more information.</p>		If the CONNECT TO statement within a User Language procedure fails, Model 204 displays an error message. See [[UL/DB2 error codes and messages#Errors involving Call Attach Facility calls\|Errors involving Call Attach Facility calls]] for more information.</p>

	===DISCONNECT FROM statement===		===DISCONNECT FROM statement===

2015-07-28T20:35:16Z

Example

← Older revision		Revision as of 20:35, 28 July 2015
Line 605:		Line 605:
	<p>INDICATOR is an optional keyword; if a %variable is followed directly by a %variable with no intervening comma, it is assumed to be an indicator variable.</p>		<p>INDICATOR is an optional keyword; if a %variable is followed directly by a %variable with no intervening comma, it is assumed to be an indicator variable.</p>

	====Example====		=====Example=====
	<p class="syntax">EXEC DB2		<p class="syntax">EXEC DB2
	FETCH <span class="term">cursor_name</span>		FETCH <span class="term">cursor_name</span>

2015-07-28T20:34:57Z

Syntax

← Older revision		Revision as of 20:34, 28 July 2015
Line 593:		Line 593:
	You can specify the INDICATOR type on FETCH commands.</p>		You can specify the INDICATOR type on FETCH commands.</p>

	====Syntax====		=====Syntax=====
	<p class="syntax">EXEC DB2		<p class="syntax">EXEC DB2
	FETCH <span class="term">cursor_name</span>		FETCH <span class="term">cursor_name</span>

2015-07-28T20:33:56Z

Example

← Older revision		Revision as of 20:33, 28 July 2015
Line 568:		Line 568:
	When DB2 returns a string to a User Language %variable, that string contains the number of blanks necessary to make the value equal to the defined maximum length of the %variable.</p>		When DB2 returns a string to a User Language %variable, that string contains the number of blanks necessary to make the value equal to the defined maximum length of the %variable.</p>

	====Example====		=====Example=====
	<p>		<p>
	In the following code, if the string being fetched by CUR1 into %BAR is three characters ("Joe"), that value is padded with enough blanks to make it 20 characters long ("Joe           "):</p>		In the following code, if the string being fetched by CUR1 into %BAR is three characters ("Joe"), that value is padded with enough blanks to make it 20 characters long ("Joe           "):</p>