DDM Files

Figure 156 on page 312 is an example showing conditional commitment control.

*..

1 ...

+...

2 ...

+...

3 ...

+...

4

...+...

5 ...

+...

6 ...

+...

7 ...

+...

*

FFilename++IPEASFRlen+LKlen+AIDevice+.Keywords+++++++++++++++++++++++

 

 

FMASTER

UF

E

K

 

DISK

 

COMMIT(COMITFLAG)

 

 

 

 

FTRANS

UF

E

K

 

DISK

 

COMMIT(COMITFLAG)

 

 

 

 

*.. 1 ...+... 2 ...+... 3 ...+... 4 ...+... 5 ...+... 6 ...+... 7 ...+... *

CL0N01Factor1+++++++Opcode(E)+Factor2+++++++Result++++++++Len++D+HiLoEq.￿...

*If COMITFLAG = '1' the files are opened under commitment con￿trol,

*otherwise they are not.

C

*ENTRY

PLIST

 

C

 

PARM

COMITFLAG

C

 

:

 

C

 

:

 

 

*

 

 

*Use the COMMIT operation to complete a group of operation￿s if

*they were successful or rollback the changes if they were￿ not

*successful. You only issue the COMIT or ROLBK if the files

*were opened for commitment control (ie. COMITFLAG = '1')

*

 

 

 

C

UPDATE

MAST_REC

90

C

UPDATE

TRAN_REC

91

C

IF

COMITFLAG = '1'

 

C

IF

*IN90 OR *IN91

 

C

ROLBK

 

 

C

ELSE

 

 

C

COMMIT

 

 

C

ENDIF

 

 

C

ENDIF

 

 

C*

 

 

 

 

 

 

Figure

156. Example of Using Conditional Commitment Control

 

Commitment Control in

the

 

Program

Cycle

 

 

 

 

 

 

 

 

 

 

 

 

 

Commitment

control is

intended

for

full

procedural

files,

where

the input

is

under

your

control.

Do not use commitment control with primary

and

se

files,

where

input

and

output is

under the

control of

the RPG

program

following

are some of the reasons for this

recommendation:

 

 

 

¹

You

cannot

issue

a

COMMIT

operation

for

the

last

total output

in

you

¹

It

is

difficult

to

program

within

the

cycle

for

recovery

from

a

 

tion.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

¹

Level

indicators

are

not

reset

by

the

ROLBK

operation.

 

 

 

¹After a ROLBK operation, processing matching records may produce a sequence error.

DDM Files

ILE

RPG

programs

access

files

on remote

systemsdistributed throughdata man-

 

 

 

agement

 

(DDM).

DDM

allows

application

programs

on one

system

to

use

files

stored

on a remote system as database files. No

special

statements a

ILE

RPG

programs

to

support DDM

files.

 

 

 

 

 

 

A DDM

file

is

created by

a user or program on a

local (source)

syste

(with object

type

*FILE)

identifies

a

file

that

is kept

on

a remote

312 ILE RPG for AS/400 Programmer's Guide

Page 335 Page 337
Page 336
Image 336
IBM AS/400 manual Cycle, DDM Files
Page 335 Page 337

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.
Top Page Image Contents