The configuration file, or INI file, is a series of keywords and values
that are processed when you start your packaged image. Using an INI
file allows you to have generic parameters in your code and specify the actual
parameter value inside the INI file, allowing you to change the parameter
without repackaging the image. For example, using an INI file would be
helpful if one resource is accessed when the application is running in a test
environment and another resource is accessed when the application is running
in a production environment. Without the INI file, you would have to
repackage the image each time you call a different resource.
The data for the INI can be uploaded from a workstation or entered on
OS/390. When entering or changing an INI file on OS/390, the left and
right square brackets must maintain their hex values of x'AD' and
x'BD' respectively.
On OS/390, the default when starting a packaged image is no configuration
file. If you want to use configuration options, specify the
-INI: command line argument in the CLA option when building
the load module from the Smalltalk image. This argument specifies the
location of the INI file to use. If the -INI: command
line argument is not present then no INI file is read. For CICS, the
INI file must be imbedded into a load module which is then located in the CICS
FDHRPL concatenation.
that an INI file be used when starting an image or executable by using the
.
To use an INI file that is in a load module when you are running a packaged
image, do the following:
To find out the contents of the configuration data in a load module,
you need to copy and execute the JCL in member ABTXIPRT located in
the data set hlq.V4R5M0.SABTJLIB. Modify the
parameters for MODNAME and LOADLIB to specify the load
module containing the configuration data. The configuration data is
written to DD SYSPRINT.Specifying a configuration file on CICS
Using a configuration file in a load module
Printing INI information contained in a load module