The Linux sample files are supplied in the
sample/containerization/linux directory by default, and are comprised of the following:
- bld.sh
- Script file to create images that can be run in a container.
- bld_linux_x64.env
- Version and other settings used by
bld.sh.
- Dockerfile_linux_x64
- Text file that contains all the commands to create the base image.
- Dockerfile_linux_x64_app
- Text file that contains all the commands to create the application image from the base image.
- run_app_container.sh
- Script file to run the application image in a foreground container.
- run_base_container.sh
- Script file to run the base image in a foreground container.
- run_container_AcuRCL.sh
- Script file to run the application image in a detached container with AcuRCL started.
- run_container_AcuToWeb.sh
- Script file to run the application image in a detached container with AcuToWeb and AcuRCL started.
- aculic_pmk59
- A directory to hold your extend license files for the products to be run in the container. pmk59 indicates the licenses are
for Linux 64-bit shared products.
- AppContainerDirectory
- A directory containing the sample COBOL programs, configuration files, and script files needed by the application container
for running the sample COBOL programs.
- SharedContainerDirectory
- This directory allows for persistent data after a container has been stopped. It is a single shared directory between the
host and the container where your container applications can create or make changes to files and data that you want to remain
after a container has been stopped. The sample COBOL programs will use this directory for files that get created when they
are run by using the runtime
-e error output file option and the runtime configuration variable FILE-PREFIX for data files.
Note: COBOL programs that call the ACUCOBOL-GT I$IO library routine do not use FILE-PREFIX. To access I$IO files in the
SharedContainerDirectory hard code the full path into your COBOL program. For example,
home/user/SharedContainerDirectory/ftestdat.