×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Visit the IBM i InfoCenter, in the "Search:" enter the two tokens:
transaction scoped
The Lack Space (*LCKSPC) object is an implementation object for
X/OPEN CAE or XA specification.
_XA transaction support for commitment control_
http://publib.boulder.ibm.com/infocenter/iseries/v5r4/topic/rzakj/rzakjxatransaction.htm
"DB2 Universal Database™ (UDB) for iSeries™ can participate in X/Open
global transactions. ..."
Effectively the *LCKSPC is used for commitment control [xa_commit(),
xa_rollback()] whereby allocations across different jobs can be tracked;
i.e. multiple jobs participating in the same unit of work.
_Scope for a commitment definition_
http://publib.boulder.ibm.com/infocenter/iseries/v5r4/topic/rzakj/rzakjscope.htm
" ...
Commitment definitions with transaction-scoped locks
* Transaction-scoped commitment definition
Commitment definitions with job-scoped locks can be used only by
programs that run in the job that started the commitment definitions. In
comparison, more than one job can use commitment definitions with
transaction-scoped locks.
...
"
Typically the OS would create the Lock Space object to deal with
[start\enable] requests to use XA; distributed processing. The database
has the capability to establish that via some 'client' requests; JDBC,
ODBC, SQLCLI
I believe the Lock Space is created for the request to "Open an XA
Resource Manager" with the xa_open() API.
xa_open()--Open an XA Resource Manager (Transaction Scoped Locks)
http://publib.boulder.ibm.com/infocenter/iseries/v5r4/topic/apis/dxatlopn.htm
" Syntax
#include <xa.h>
int xa_switch.xa_open_entry(char *xa_info,
int rmid, long flags);
Default Public Authority: *USE
Service Program: QTNXADTP
Threadsafe: Yes
A transaction manager calls xa_open() to open the XA resource manager
and to prepare it for use in the XA distributed transaction environment.
This function must be called before any other resource manager (xa_)
calls are made.
...
"
When an object or record is identified as being allocated to a Lock
Space, the Lock Space Identifier would be returned, which is then used
as input to another API specific to the Lock Space. For example, the
Retrieve Job Locks (QWCRJBLK) API:
http://publib.boulder.ibm.com/infocenter/iseries/v5r4/topic/apis/qwcrjblk.htm
midrange.com
