Defining Externally Described

Files

field

in

positions

49

through 62

and

assign

a match-level value

tions

65

and 66.

 

 

 

 

 

In this

example, the CUSTNO field in both records MSTREC and

WKREC

is

assigned

the

match-level

value

M1.

 

.2/ To assign a field indicator to a field in an externally des specify the record-format name in positions 7 through 16 of identification line. On the field-description line, specify th positions 49 through 62, and specify an indicator in positions 74.

In this

example,

the field BALDUE in the record

WKREC is

te

zero

when

it is

read into the program. If the

field’s

val

cator

98

is

set

on.

 

 

Using Output Specifications

Output specifications are optional for an externally described file. operation codes such as WRITE and UPDATE that use the external rec description to describe the output record without requiring output the externally described file.

You can use output specification to control when the data is to be specify selective fields that are to be written. The valid entries

description

line

for an

externally described

file

are

output indicat

29),

field name (positions 30 -

43), and

blank

after (position 45). Ed

edit

codes

for

fields

written

to an externally described file are

for

the file. Device-dependent

functions

such

as

fetch

overflow (pos

space/skip (positions 40 - 51) are not valid in an RPG program for ex described files. The overflow indicator is not valid for externally

either. For a description of

how

to

specify

editingDDS Referin the-

DDS,

se

ence.

 

 

 

 

 

 

 

If

output specifications are

used

for an externally

described

file

name

is specified in positions

7 -

16

instead

of the

file name.

 

If all the fields in an externally described file are to be plac enter *ALL in positions 30 through 43 of the field-description line. I fied, you cannot specify other field description lines for that re

If you want to place only certain fields in the output record, ent positions 30 through 43. The field names you specify in these posit field names defined in the external record description, unless the on the input specifications. See Figure 135 on page 270.

You

should know about these considerations for using the output spec

an

externally described file:

¹In the output of an update record, only those fields specified specifications and meeting the conditions specified by the output placed in the output record to be rewritten. Fields not specifie

specifications are rewritten using the values that were read. Th offers a good method of control as opposed to the UPDATE operat that updates all fields.

Chapter 14. Defining Files269

Page 293
Image 293
IBM AS/400 manual Using Output Specifications, Ence

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.