Managing Dynamically-Allocated Storage

*-----------------------------------------------------------------

 

*

* Heap Storage Misuse

 

*

*-----------------------------------------------------------------

 

*

D Fld1

S

25A

BASED(Ptr1)

D Fld2

S

5A

BASED(Ptr2)

D Ptr1

S

*

 

D Ptr2

S

*

 

....

 

 

 

C

ALLOC

25

Ptr1

C

DEALLOC

 

Ptr1

*-----------------------------------------------------------------

 

*

* After this point, Fld1 should not be accessed since the

* basing pointer ptr1 no longer points to allocated storag￿e.

*-----------------------------------------------------------------

 

*

C

CALL

'SOMEPGM'

 

*-----------------------------------------------------------------

 

*

* During the previous call to 'SOMEPGM', several storage

* allocations may have been done.

 

* In any case, it is extremely dangerous to make the

* following assignment, since 25 bytes of storage will be

* filled with 'a'. It is impossible to know what that storage

* is currently being used for.

 

*-----------------------------------------------------------------

 

*

C

EVAL

Fld1 = *ALL'a'

 

 

 

 

Figure 53.

Heap Storage Misuse

 

 

Similarly, errors can occur in the following cases:

¹A similar error can be made if a pointer is copied before bei deallocated. Great care must be taken when copying pointers to a storage, to ensure that they are not used after the storage i reallocated.

¹If a pointer to heap storage is copied, the copy can be use

reallocate

the

storage.

In

this

case,

the

original

pointer

should

it

is

 

set

to

a

new

value.

 

 

 

 

 

 

 

 

 

 

 

 

 

¹ If a pointer to

heap

storage is passed as a parameter, the c

cate

or reallocate

the

storage. After the call returns, attempts

pointer

could

cause

 

problems.

 

 

 

 

 

 

 

 

 

 

 

 

 

¹ If a pointer to

heap

storage

is set

in the *INZSR, a later RES

could

 

cause

the

pointer

to

get

set

to

storage

that

is

no

longer

¹ Another

type

of

problem

can

be

 

caused

if

a pointer

to

heap

sto

being

 

cleared,

or

set

to

a

new

pointer

 

by

an ALLOC

 

operation,

fo

Once

the

pointer

is

lost,

the

storage it

pointed

to

cannot

be

f

is

unavailable

 

to

be

allocated

since

the

system

does

not

know

tha

is

no

 

longer

addressable.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

The

storage

will

not

 

be

freed

until

the

 

activation

group

ends.

 

Managing Your Own Heap

Using

ILE

Bindable APIs

 

 

 

 

 

 

You can isolate the dynamic storage

used

by

some

programs

and

proc

within

an

activation

group by creating

one

or

more user-created heap

tion on creating

a

user-created ILEheapConceptsrefer.

to

 

 

 

The following example shows you how to

manage

dynamic

storage

for

a

array

with a user-created heap from

an

ILE

RPG procedure.

In

this

Chapter 9. Running a Program119

Page 143
Image 143
IBM AS/400 manual Managing Your Own Heap, Bindable APIs, RPG procedure This, Call Somepgm

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.