Search results

This IBM® Redpaper™ provides a step-by-step introduction on how to get started with Web services using Data Studio V2.1. Our goal is to explain basic concepts and introduce the functions that can help you take your first steps in the Web services arena with DB2® for z/OS®. We start with describing and setting up the basic software components and showing a step-by-step guide to creating your first Web service. We then show how you can test and deploy Web services and let DB2 operate as a Web service requester (consumer) and a Web service server (provider). Last, we introduce the SOAP UDFs that enable DB2 to act directly as a Web service consumer and we show how stylesheets can easily transform your Web service response into a service message in HTML format.

Archive Actions allow you to execute one or more custom procedures at designated points in Archive or Restore processes. To implement an Archive Action, you select the point in the process at which the custom procedure will be performed and provide an SQL statement to be executed. In many cases, a simple SQL statement is sufficient to accomplish the task. For example, simple inserts, updates or deletes of rows in tables can be accomplished using the Action SQL statement. When the needed task is more comple

When an Optim client connects to an Optim Server and initiates a process such as an archive or restore, the Optim Server daemon creates a new process to run the request. The new process space will run under the authority of the user signed on within it. Access to system resources will be controlled by the ermissions assigned to the user that is signed on in the spawned process space. The “filelogon” option tells the Optim Server daemon how to assign a user to these spawned process spaces when r

Whenever Optim follows a relationship path from one table to another during extract processing, it makes an internal decision on how to best access the table it is about to process. The two methods it may choose to use are “table scan” or “key lookup”. It makes this decision based on a number of factors like the presence of indexes on the columns involved in the relationship path, the number of rows existing in the table, and the number of key values it needs to query the table for.

During extract processing, normal traversal of relationship paths proceed like a waterfall through the data model. All selected relationship paths will be followed from the parent table in the relationship to the child table. Optim provides two selectable options that can be specified individually on each relationship path included in the extract data model. These two options add to the traversal process, they do not prevent the natural waterfall flow through the data model.

A database primary key is an object that defines uniqueness within a table. A primary key is defined to include one or more columns in the table to establish a unique key to identify each individual row. When a primary key includes multiple columns, the primary key value is the concatenation of the values of all of the columns it includes. By definition, there can only be one row within a table that contains a distinct primary key value when the table has a database primary key defined.

A discussion on using multiple database connections (parallel connections) in Option processing. The “Database Connections” setting on the request editor panel for the specific request provides the ability to control this processing. The multiple database connections option is available on archive, extract, and delete processes.

There are a number of factors that affect the overall runtime of a delete process. To understand the effects of these factors, you should first have an understanding of how Optim performs delete processing. First we’ll take a look at Optim delete theory, and build a basic understanding of the processing involved. Next we’ll discuss some tuning tips to help you get the best performance from your delete run.