Using Commitment Control

Using Commitment Control

This section describes how to use commitment control to process file a group. With commitment control, you ensure one of two outcomes for operations:

¹ all of the file operations are successful (a commit operation)

¹ none of the file operations has any effect (a rollback operation

In this way, you process a group of operations as a unit.

To use commitment control, you do the following:

¹On the AS/400:

1.Prepare for using commitment control:. Use the CL commands CRTJRN (Create Journal), CRTJRNRCV (Create Journal Receiver) and STRJRNP (Start Journal Physical File).

2.Notify the AS/400 when to start and end commitment control: Use commands STRCMTCTL (Start Commitment Control) and ENDCMTCTL

(End Commitment Control). See CLtheReference (Abridged)for informa- tion on these commands.

¹In the RPG program:

1. Specify

commitment

control

(COMMIT) on the file-description specifi

of the

files you

want

under commitment control.

2.Use the COMMIT (commit) operation code to apply a group of c files under commitment control, or use the ROLBK (Roll Back) oper code to eliminate the pending group of changes to files under control. For information on how the rollback function is performed system, refer Backupto theand Recoverymanual.

Note: Commitment control applies only to database files.

Starting and Ending Commitment

Control

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

The

CL command

STRCMTCTL

notifies

the

system

that

you

want

to

start

commi

ment

control.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

The

LCKLVL(Lock

Level)

parameter

allows

you

to

select

the

level

at

whic

are

locked

under

commitment

control. See

“Commitment

Control

Locks”

on

 

page 308

and

theCL

Programming

manual

for

further

 

details

on lock

levels.

You can make commitment control conditional, in

the

sense

that

the

dec

whether

to

process

a file under commitment control is made at run ti

information, see “Specifying Conditional Commitment

 

Control”

on

page 311.

When

you

complete

a

group

of changes with

a

COMMIT

operation, you c

a label to identify the end of the group. In the event of an ab

identification

label

is written to a file, message queue, or data

know

which

group

of

changes is the last group to be completed succe

specify

this

file,

message

 

queue,

or

data

area

on

the

STRCMTCTL

comma

Before you call any program that processes files specified for com issue the STRCMTCTL command. If you call a program that opens a file

Chapter 16. Accessing Database 307Files

Page 331
Image 331
IBM AS/400 manual Using Commitment Control, Starting and Ending Commitment

AS/400 specifications

The IBM AS/400, now known as the IBM iSeries, is a midrange computer system that has been a cornerstone of enterprise computing since its introduction in 1988. Designed to provide a robust platform for business applications, the AS/400 is celebrated for its reliability, scalability, and integrated database capabilities.

One of the key features of the AS/400 is its Integrated Operating Environment, which blends hardware and software resources seamlessly. This integration allows businesses to execute diverse workloads, ranging from traditional applications to modern web-based services, all on a single platform. The operating system, OS/400 (now IBM i), offers a rich set of APIs and tools for developers, simplifying application development and management.

Another standout characteristic of the AS/400 is its built-in database, DB2 for i. This powerful relational database management system allows for efficient data handling and provides advanced features such as support for SQL, XML, and JSON, making it easier for businesses to manage their data and integrate it with other systems. The database's tight integration with the operating system enables high performance and security.

In terms of scalability, the AS/400 can accommodate small businesses as well as large enterprises, with the ability to support hundreds of users simultaneously. Its architecture allows for easy upgrades in hardware, meaning that organizations can scale their systems without replacing the entire infrastructure.

Security is another critical attribute of the AS/400. With a sophisticated security model, it offers built-in user authentication, access control, encryption, and auditing capabilities to protect data and applications from unauthorized access.

The AS/400 also supports multiple programming languages, including RPG, COBOL, Java, and PHP, giving organizations the flexibility to choose the development tools that best fit their needs. This diversity helps maintain legacy applications while also developing new ones that leverage modern technologies.

Moreover, the platform supports both traditional green-screen interfaces and modern graphical user interfaces, allowing organizations to transition smoothly into contemporary user experience paradigms.

Overall, the IBM AS/400 stands out as a resilient, flexible, and secure computing platform that enables organizations to effectively manage their business operations, streamline processes, and adapt to changing market demands. Its unique combination of integrated features and capabilities ensures that it remains relevant in today's fast-paced technology landscape.