Interstage Shunsaku Data Manager Operator's Guide - Microsoft(R) Windows(R) 2000/ Microsoft(R) Windows Server(TM) 2003 - - UNIX -
Contents Index PreviousNext

Appendix E Conflict Relationships> E.1 Conflict Relationships between Applications and Commands

E.1.1 Leading Command/Following Application

The following table shows the API classifications for the leading command/following application scenario.

APIs not listed below do not conflict, and so do not need to be considered.

[Table E-1 API Classifications for the Leading Command/Following Application]

Classification

Java API

.NET API

C API

Class

Method

Class

Method

Establishing

connections

ShunConnection

ShunConnection()

ShunService

Connect()

ShunConnect

Switching the target Shunsaku File

ShunConnection

setShunsakuFileName()

ShunService

ChangeShunsakuFile()

ShunSetConnectAttr

Starting updates/

transactions

ShunPreparedStatement

executeInsert()

ShunService

Insert()

ShunInsert

ShunPreparedRecordID

deleteByRecordID()

ShunService

Delete()

ShunDeleteRecId

ShunPreparedRecordID

updateByRecordID()

ShunService

Update()

ShunUpdateRecId

ShunPreparedKey

deleteByKey()

ShunService

DeleteByKey()

ShunDeleteKey

ShunPreparedKey

updateByKey()

ShunService

UpdateByKey()

ShunUpdateKey

Finishing

transactions

ShunConnection

commit()

ShunService

Commit()

ShunCommit

ShunConnection

rollback()

ShunService

Rollback()

ShunRollback

Looking

up data

ShunPreparedStatement

executeSearch()

ShunService

GetHitCount()

ShunGetHitCount

ShunPreparedStatement

executeSearch()

ShunService

Search()

ShunSearch

ShunPreparedRecordID

searchByRecordID()

ShunService

SearchByRecordID()

ShunSearchRecId

ShunPreparedKey

searchByKey()

ShunService

SearchByKey()

ShunSearchKey

Conflict behavior for the leading command/following application scenario is as follows:

[Table E-2 Conflict Behavior for the Leading Command/Following Application]

Leading command

Following application

Conflict conditions and behavior when conflict occurs

(explanations start with either a or ax)

(e.g. : if there is a sort expression)

(e.g. x: the API will produce an error)

Establishing connections

Switching the target Shunsaku File

Starting

updates/

transactions

Finishing

transactions

Looking

up data

shunsysstart

x

-

-

-

-

x: The API will produce an error

shunsysstop

x

-

-

-

-

x: The API will produce an error

shunsyscfgedit
(except for dynamic

changes to the Shunsaku File)

shunsyscfgedit
(dynamic changes to the Shunsaku File)

:
When a director is deleted from a File or a File is deleted from a Domain, all existing connections to the director/File will be closed and new connections will be rejected.

shunsysstate

shuncstate

shuncterm


shuncservice

-

-

-

-

-

shundstate

shundclear

x

-

x: The API will produce an error.

shundimport

: The API will produce an error if the records being deleted by the shundimport command conflict with the records being updated or deleted by the API.

shundexport

x

-

x: The API will produce an error.

shundresend

x

-

x: The API will produce an error.

shundcds

x

-

x: The API will produce an error.


shundservice

-

-

-

-

-

x: The API will produce an error.

shundbackup
(Start declaration)

-

: The API will produce an error if there is no specification for the OperationLogFolder parameter.

shundbackup
(End declaration)

-

: The API will produce an error if there is no specification for the OperationLogFolder parameter.

shundrecover
(Start declaration)

x

-

x

x: The API will produce an error.

shundrecover
(End declaration)

x

-

x

x: The API will produce an error.

shunostate


shunoservice

-

-

-

-

-

: The API will produce an error if there is a sort expression

shunsstate


shunsservice

-

-

-

-

-

x: The API will produce an error.

shunprtmsg


Contents Index PreviousNext

All Rights Reserved, Copyright (C) FUJITSU LIMITED 2006