Deciding whether and what to customize

Consider whether the IBM-supplied values for the runtime options provided with Language Environment suits the needs of your site. These values control such features as:

The national language in which messages appear
How a debug tool is invoked
When condition handling is invoked
How storage is allocated to the heap and stack
How much storage is allocated
The format of the program invocation character parameter
Creation of a storage and runtime options report
Shared storage allocations

Start of change If you do not want to customize Language Environment now, you can put it into production using the IBM-supplied defaults. Or, you can use the instructions in this information to customize Language Environment later, if you choose. For many of the runtime options, application programmers can override the defaults in their code. End of change

Application programmers at your site will be the primary users of Language Environment. Ask them what defaults they prefer for runtime options and user exits, which affect their work directly. Doing so ensures that the modifications you make will best support the application programs being developed at your site.

You need to make decisions about customizing:

Runtime library access method (see Choosing your Language Environment runtime library access)
Runtime options (see Customizing Language Environment runtime options)
Assembler user exits (see Customizing user exits)
Cataloged procedures (see Customizing the cataloged procedures)

You also need to decide:

Whether to install some routines in the link pack area (see Placing Language Environment modules in link pack and LIBPACK)
Whether to make Language Environment available under CICS® (see Using Language Environment under CICS)
Whether to customize any programming language-specific features (see Automatic storage tuning behavior)