Running the BUILDX Utility

You can execute the BUILDX utility program using a RUN command in a CANDE or MARC session, or in a WFL job.

The BUILDX utility requires a valid NXSERVICES credentials file to securely access the external system. For details on creating a credentials file, refer to the topic, “MAKECREDENTIALS Utility.”

Syntax

        ┌◄────────────────────────────────────┐
── #$ ──┴─<SET or RESET>───<build options>────┴────────────────────────┤

<build options>

── AUTOMAP ──────┬─────┬──────────────────────────────────┬─────┬─────────┤
                 └─ ' ─┤                                  ├─ ' ─┘
                       ├──<drive>: ──<mapping>────────────┤
                       ├──<drive>: ───────────────────────┤
                       └──<mapping> ──────────────────────┘

── OVERRIDE ───────────────────────────────────────────────────────────────┤

── CACHEOK ────────────────────────────────────────────────────────────────┤

Explanation

<drive>

Specifies a drive letter. The drive that you specify is mapped to a share that you specify of the MCP running on the platform. If you specify a drive letter, it must be followed by a colon (:).

<mapping>

Specifies a share. The share that you specify must be in the form \\<server>\<share>, where <server> can be a computer name, domain name, or IP address.

#$RESET AUTOMAP

Automap does not run and the DOCKERCODE TASKSTRING is null.

AUTOMAP is RESET by default.

#$SET AUTOMAP

The DOCKERCODE TASKSTRING is set to the following default EVLAN mapping:

M: \\192.168.16.5\_HOMEXL_

#$SET AUTOMAP <mapping>

No drive value is used during the AUTOMAP process. When the AUTOMAP option is set, the BUILDX compiler automatically generates the AUTOMAP.PS1 file in the build directory. You can file equate the SCRIPT file to create the file with any valid title. If the file already exists in the build directory, it is not overwritten unless OVERRIDE is set.

OVERRIDE

The OVERRIDE option is reset by default. You can set the OVERRIDE option to remove an existing AUTOMAP.PS1 script in the build directory. If you set the OVERRIDE option, you must also specify COPY AUTOMAP.PS1 . in the Dockerfile. For more information on the specifying COPY AUTOMAP.PS1 ., see “Setting or Resetting AUTOMAP” in the ClearPath MCP Software ClearPath Extension Kit for MCP Getting Started and Best Practices Guide.

CACHEOK

The CACHEOK option controls the Docker Build option --no-cache. If the no-cache option is set, cache is not used when the image is built. CACHEOK is reset by default. If CACHEOK is set, the BUILDX compiler issues the following warning:

Docker build cache enabled. Files changed in the 
MCP environment may be ignored.

Examples

#$SET AUTOMAP 'K: \\192.168.16.5\_HOME_'

#$RESET AUTOMAP CACHEOK

#$SET AUTOMAP RESET  CACHEOK

Compiling with the BUILDX Compiler

You can also use the BUILDX utility as a compiler by including it in COMPILE statements a CANDE or MARC session, or in a WFL job.

Security Rescrictions

You must have the PLATFORMACCESS granulated privilege or PU privilege if security administrator status is not enabled (??SECAD-) on the system. If security administrator status is enabled on the system (??SECAD+), you must have the PLATFORMACCESS granulated privilege or SECADMIN privilege to use the RUNX utility.

Credentials

You must have a valid NXSERVICES credentials file to securely access the external system using the BUILDX utility. For information on creating a credentials file, refer to MAKECREDENTIALS Utility.