Defining blob objects  Defining database interface objects

Chapter 3: Using MSG-IDE

Defining distributed function objects

A Distributed Function Object contains the definition of a Distributed Function Call (DFC command) that the AIM makes to another application within the Impact environment. In the DFC command, you define arguments for the information going out to the Impact server and the receiving application and for the information returning from it. The order of the arguments in this window must exactly match the order of the arguments in the Impact receiving DFC function. As you build the arguments, they appear in the idempotent statement displayed in the viewing area at the bottom of the window. When you delete an argument from the Argument List, it is also removed from this statement. Enlarge the bottom of the window to view the entire statement if it exceeds a few lines.

StepsDefining a distributed function object

  1. In the Distributed Function Declaration window, click in the Distributed Function field and type the distributed function call (DFC) command.

    If you accessed the Distributed Function declaration box through the Define window, this field is disabled and displays the last entry to the Name drop-down box in the Define window.

    After you build a DFC command, if you select Accept, focus returns to this drop-down box, and you can enter the name of another DFC command.

  2. Choose one of the following:

  3. Select the Function Wrapper check box to generate a function that issues the DFC command, checks the return value from the function, and displays an error message if it detects a problem.

    The function name is identical to the DFC command name, but is prepended with an underscore. The Argument Name field becomes a drop-down list from which you can select predefined data objects as arguments.

  4. Click in the Argument Name field and type the user-assigned name for this argument in the Name field.

    This name does not need to match the name of the argument used in the destination AIM.

  5. Select one or more of the following Attributes:

    Attribute

    Description

    In

    The sending AIM fills this argument with a value before issuing the DFC command.

    Out

    The receiving application fills this argument. The destination AIM fills this argument upon receiving the DFC command and before the argument set returns to the sending AIM.

    Flavor

    Impact uses the flavor in the idempotent statement to choose a specific function from its tables to service the DFC command. Only one argument per DFC command can have a Flavor attribute.

    Each argument must have one or more of the attributes check boxes selected.

  6. Select the Array check box and use the associated field to define an array.

  7. Select the Pointer check box if this DFC argument is a pointer.

  8. In the Argument List box, which displays a list of the arguments built for this DFC command, do any of the following:

  9. Click Add Arg when you complete your definition of an argument to add it to the arguments list.

    You can use a maximum of 100 arguments per DFC command.

Viewing Area

The viewing area is at the bottom of the Distributed Function Declaration dialog box. It displays the DFC command in its current state.

NoteSee the e-Biz Impact ODL Guide for more information on SFM and DFC interfaces.

StepsUsing the Viewing Area

  1. Click Accept to add the distributed function object to the current file and remain in the Distributed Function Declaration box to build another object.

    If you build the object from the Define dialog box and click Accept in the Define dialog box, you return to that dialog box.

  2. Click OK to add the distributed function object to the current file and return to the Browse dialog box.





Copyright © 2005. Sybase Inc. All rights reserved. Defining database interface objects

View this book as PDF