2.Invoke the preprocessor on the clien t and use the alias name for the DBEn vironment. In the following example, the P ascal preprocessor is used.

:run psqlpas.pub.sys;info= "AliasName"

A module is created and stored in the system catalog of the DBEn vironment on the server. The modi￿ed source code ￿le and the four include ￿les created b y the preprocessor remain on the client. For more information on preprocessors, refer to the speci￿c ALLBASE/SQL application programming guide for the language y ou are using.

3.Compile and link the modi￿ed source ￿le with the necessary libraries on the clien t as shown in the following example:

:pasxllk sqlout,someprog

where:

sqlout is the modi￿ed source code ￿le someprog is the executable output ￿le

The executable program resides on the clien t. The program someprog is now ready to run from the client to access the DBEn vironment on the server.

Running an Application Program

Run the program by typing:

:run someprog

Authorizations

If an application program uses a CONNECT command to start a DBE session, the o wner of the module must have CONNECT authority and R UN or module OWNER authority to run the program. The run time CONNECT and R UN authorities are based on the user's serv er login. Additionally , the module owner must have permission to access all objects acted upon by the program. This usually means one or more of the table or view authorities m ust be granted to the module o wner. There may be other authorities needed as w ell.

The module owner is de￿ned at preprocess time b y the -o option of the preprocess command or, by default, the clien t's login. Refer to \Clien t and Server Login Names" under \Cross-System Connectivity" in the \Getting Started" c hapter.

Using ALLBASE/SQL Through ALLBASE/NET 3-3