Running the CICS Container Demonstration

For users of Enterprise Developer for Eclipse:

The CICS container demonstration includes a batch file (bld.bat) to make the process of running the demonstration as easy as possible. This topic lists and describes the parameters that you can specify when running bld.bat.

The command to execute the batch file to run the CICS container demonstration is as follows:

bld.bat { {dn|x64|x86} [debug]  |
         rmi }

where the parameters are:

debug: Indicates that you want to debug the CICS application rather than simply execute it. Specifying debug causes Dockerfile.debug to be run rather than Dockerfile.
dn: Indicates that you want to run the CICS application in a .NET environment. Specifying dn causes Dockerfile.dn to be run rather than Dockerfile.
x64: Indicates that you want to run the CICS application in a 64-bit environment. Specifying x64 causes Dockerfile.x64 to be run rather than Dockerfile.
x86: Indicates that you want to run the CICS application in a 32-bit environment. Specifying x86 causes Dockerfile.x86 to be run rather than Dockerfile.
rmi: Indicates that you want to remove any previously-created CICS container demonstration images. Specifying rmi results in the execution of a number of docker rmi --forceor podman rmi --force commands to remove any CICS container demonstration images.

Note: When you run the image created by the CICS container demonstration, to be able to manage the container's enterprise servers using Micro Focus Directory Server (MFDS) and Enterprise Server Monitor and Control (ESMAC) from a machine other than the host machine you must specify some additional parameters on the docker runor podman run command. The additional parameters are as follows:

```
-p 16001:86/udp -p16001:86/tcp -p 9000-9010:9000-9010
```
To map the container port (86) to a port on the host machine (16001).
```
-e MFDS_EXTERNAL_ADDR=host-computer-name
```
To specify the name of the host machine that MFDS will use to navigate to ESMAC.

For users of Enterprise Developer UNIX Components:

The CICS container demonstration includes a shell script (bld.sh) to make the process of running the demonstration as easy as possible. This topic lists and describes the parameters that you can specify when running bld.sh.

The command to execute the shell script to run the CICS container demonstration is as follows:

./bld.sh IacceptEULA  
         [dryrun]
         [esadmgid=admin-gid]
         [esadminuser=admin-id]
         [esadmuid=admin-uid]
         [login|nologin] 
         [logingid=login-gid]
         [loginid=login-id]
         [logingname=login-gname]
         [loginname=login-name]
         [nojava | (java | oraclejava) [javaversion=java-version]]
         [notools]
         [package]
         [rmi]
         [settings]
         [verbose]

where the parameters are:

IacceptEULA

Indicates that you accept the Micro Focus End User License Agreement (EULA). If you do not specify IacceptEULA, no image is created.

dryrun

Indicates that you do not want bld.sh to run any Docker or podman commands. Use dryrun with the verbose parameter to display the Docker or podman commands without running them.

esadminuser=admin-id

Specifies the ID to be used for the Enterprise Server admin user.

esadmgid=admin-gid

Specifies the group ID to use for the Enterprise Server admin user.

esadmuid=admin-uid

Specifies the user ID to use for the Enterprise Server admin user.

java

Indicates that you want the image to include Java support provided by the AdoptOpenJDK OpenJDK. Use the javaversion parameter to specify the version of Java that you want support for.

javaversion=java-version

When specified with the java or oraclejava parameters, specifies the version of Java that you want support for. java-version can be 8, 9, or 10.

login

Indicates that you want to create a login image. Using this option results in image that you can use to log in to (using any details specified by the logingid, loginid, logingname and loginname parameters). Once logged in to this image you can execute shell or Enterprise Developer commands.

This option is useful if you are not adding any application files to a base image but want to be able to use Enterprise Developer commands from it.

When you specify login the tag of the image created is suffixed with "_login".

logingid=login-gid

Specifies the group ID to use for the user specified by the loginid parameter.

loginid=login-id

Specifies the user ID to use for the login image.

logingname=login-gname

Specifies the group name to use for the user specified by the loginid parameter.

loginname=login-name

Specifies the user name to use for the user specified by the loginid parameter.

nojava

Indicates that you do not want Java to be installed in the base image. You might want to use this parameter if your system already includes a number of different versions of Java and you don't want to introduce another version unnecessarily.

nologin

Indicates that you do not want to create a login image. You would typically want to use this option when creating an image that contains an application rather than just a base image for Enterprise Developer. This is the default.

notools

Indicates that you do not want the image to contain the IP tools (such as ping and netcat) that are included in the image by default. Use this option if you do not need the tools and want to minimize the size of the image.

oraclejava

Indicates that you want the image to include Java support provided by the Oracle JDK. Use the javaversion parameter to specify the version of Java that you want support for.

package

Indicates that you want to rebuild the COBOL application in this image.

rmi

Indicates that you want to remove any previously-created CICS container demonstration images. Specifying rmi results in the execution of a number of docker rmi --forceor podman rmi --force commands to remove any CICS container demonstration images.

settings

Causes the settings that will be used for various properties of the image to be displayed on-screen. Properties that are displayed include the names of the installable file and the license file for Enterprise Developer, the details to be used for the Enterprise Server admin user, and the details to be used for the login image. Specifying settings does not cause an image to be created.

verbose

Causes Docker or podman commands to be displayed on-screen as they are executed.