IBM S544-5285-01 manual That, Placing TLEs in named, 179, Lines

Appendix A. Helpful Hints

When using ACIF, the following topics may prove to be helpful to you:

Ÿ	Working	with	control	statements that contain numbered lines	(OS/390	or
	VM, VSE	environments		only)
Ÿ	Understanding how ACIF processes fonts
Ÿ	Placing TLEs in named groups
Ÿ	Working with file transfer and AIX (AIX environment only)
Ÿ	Understanding how ANSI and machine carriage controls are used
Ÿ	Understanding		common	methods of transferring files to AIX	from	othe

– Physical media such as tape

– PC file transfer program

– FTP

Ÿ Invoke Medium Map (IMM) structured field

ŸIndexing considerations

ŸConcatenating the resource file and the document.

Working with control statements

that

contain

numbered

lines

(If

you

work

in

the AIX

environment,

you may

skip

this

section,

as

about control statements pertains only to the OS/390 or MVS, VM, VSE

environments.)

You

sometimes

can

receive

unexpected

results

when

data

set

names

ar

and the control statements have line numbers

in

columns 73-80, because A

reads all 80 columns of the control statements

for

processing

purposes.

attempts

to use

the

line

number as

a

data

set

name,

and issues

MSGA

and MSGAPK417I with a numeric value.) To

resolve

this

problem,

remove

an

numbers from the control statements and

rerun

the

job,

or

use a

comm

(“/*”) before

each

line number.

Placing TLEs in named

groups

To

avoid

having

your job terminated by ACIF, IBM recommends

that

you

page-level

TLEs

inside

named groups,

using one named group per page.

You

should

be

aware that ifINDEXOBJyou

request=ALLfor

a

job

that

has

an

input data set containing composed

(AFPDS) pages, page-level TLEs (TLE re

after

the

AEG)

and

no

named

groups

(BNG/ENG), your job may end

with

MSGAPK410S or MSGAPK408S. The reason for

this action is that no named

groups are present, and the

page-level

TLE

records

must

be

collected

until

the

end

of the

input

document or

file.

MO:DCA

index

structures

extent (size)

of the object being indexed. Indexed objects are

group

(or

end

document-EDT). If no

named groups

are

present,

ACIF

will

to

build

the

index

in

memory. If

the

input

file

is

large

enough, t

enough

memory,

and ACIF will terminate. The ACIF memory

manager

currently

limits the number (but not the size) of memory blocks that can be

therefore,

increasing

REGION

size

may

not

alleviate

the

problem.

 Copyright IBM Corp. 1993, 1999 179