As400 Call Cl Program From Sql How To Control Cookies

The amount of positions between the single quotes (including the F) must be an even amount.

For instance, if your parameter was defined as 2,0 and you wanted to pass the value of 99, the hex value will look like X099F 99 for the 2,0 parameter value and an extra 0 to make the amount of positions between the quotes an even amount.

As400 Call Cl Program From Sql How To Control Cookies

To find out more, including how to control cookies, see here.

I wont bore you with the details but, what I wanted to do was create a temporary file, populate it with orders for a (user specified) date and then copy this file into a library that has been made available to an external ftp application.

British father of three, now living in Belgium and making a living from building interfaces.

Since schema names are limited to the traditional 10-character library name, you might see something like this: call MYLIB001.GetAvailableInventory.

SQL does things well that are difficult or nearly impossible in RPG and vice versa.

The trick is to develop programming strategies that take advantage of both.

IBM recognized this and created the potent embedded RPG tooling, which allows you to easily take advantage of SQL from within RPG programs.

This article is going to focus on the related technique of calling RPG from within SQL.

SQL defines two mechanisms for extending the language: stored procedures and user-defined functions (UDFs).

Stored procedures were originally designed to execute external code, usually written in C.

DB2 on the IBM i extends that capability to execute code written in any language, including RPG.

UDFs, on the other hand, are encapsulated pieces of SQL logic that can be used by other SQL statements.

You invoke the stored procedure typically to update a variable, which you can then use in another discrete statement.

You cannot, for example, use the result of a stored procedure in a WHERE clause of another SELECT statement.

Instead, you invoke the stored procedure, store the result somewhere, and then execute the SELECT statement.

Thus, stored procedures are limited to programmatic SQL environments, such as embedded SQL, or within other SQL functions.

It can be used just as easily in an ad hoc query as in a complex SELECT statement.

In many ways, this parallels the difference between a program call and a procedure call.

The example code is trivial; it determines the price based on the first character of the item number.

Youd obviously have far-more-involved business logic in a production application, but this is adequate for the purposes of this article.

I can do this in iSeries Navigator, in STRSQL, or even with the command RUNSQLSTM.

There are slight syntax differences, especially if you use iSeries Navigator, which defaults to dot notation for qualifying objects, rather than the slash were accustomed to on the IBM i.

That difference aside, I recommend using iSeries Navigator because you can test a stored procedure there, which is something you cant do in STRSQL.

Also, in this case, I created a procedure whose name is different from the name of the program it calls.

In other environments, I have named the procedure the same as the program.

This is one of those shop standards decisions youll have to make.

If you dont keep them the same, you can use longer, more descriptive names for the procedures, at which point Id probably switch to mixed case.

The only fly in that ointment is that if you need to qualify the stored procedure, youll need to use the schema name.