Running IBM App Connect Enterprise commands on IBM z/OS Container Extensions (zCX) by using IBM z/OS console commands
Run IBM® App Connect Enterprise commands on IBM z/OS® Container Extensions (zCX) by using IBM z/OS console commands.
Before you begin
- Set the necessary environment variables. For more information, see Environment variables in STDENV and BIPENVS.
- For more information about access options, see Configuring access to Integration Servers running in IBM z/OS Container Extensions (zCX).
- Copy the started task into the procedures library, as described in Copying the started task to the procedures library.
About this task
mqsiAssemblyInstall
, mqsicommandconsole
,
mqsicredentials
, and mqsivault
are not supported on IBM
z/OS Container Extensions (zCX). Some commands, for
example mqsideploy
, require one or more input files to first be made available on
the docker container that runs the integration server. If the files are not available on the
integration server docker container, you must use the BIPXPUT
sample JCL to
transfer them.
Some commands produce output. You can copy or move files from the integration server docker container by using the BIPXGET sample JCL.
BINARY
mode. IBM
z/OS Container Extensions (zCX) run in
ASCII mode. You can convert a file from ASCII to
EBCDIC in UNIX System Services by using iconv
. For example, if
you want to convert the ASCII file props.txt to
EBCDIC, run the following
command:iconv -f ISO8859-1 -t IBM-1047 props.txt > props.ebcdic.txt
Procedure
Results
The output of the command is written to ACECMDS in the job log.
What to do next
When you finish running commands, you can stop the integration server by using IBM z/OS console commands. For more information, see Stopping an integration server on IBM z/OS Container Extensions (zCX) by using IBM z/OS console commands.