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] |
package |
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.
- package
- Indicates that you want to rebuild the COBOL application. Specifying
package runs a series of MSBuild commands and Powershell scripts to recreate the CICS application.
- x64
- Indicates that you want to run the CICS application in a 64-bit environment.
- x86
- Indicates that you want to run the CICS application in a 32-bit environment.
- 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 --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 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.