This topic tells how to defer use of a build plan that you create. The need arises (for example) if, at generation time, a network failure prevents you from preparing code on a remote system. If you want to defer use of a build plan even in the absence of an unexpected need, generate your output with the build descriptor option prep set to no.
build.bat myProgramBuildPlan.xml
where myProgramBuildPlan is
the build-plan name.For details on preparing multiple COBOL programs at once, see “EGLPREP batch command utility.”
set INSTALL_PATH=InstallDirectory
set SHARED_INSTALL_PATH=SharedInstallDirectory
set JDK_PATH=jdk\jre\bin
set PLUGIN_PATH=plugins
set EGLBatchGen_JAR=com.ibm.etools.egl.batchgeneration_version\runtime\eglbatchgen.jar
set LOGGING_JAR=com.ibm.etools.logging.util_version\runtime\logutil.jar
set CCUBLDC_DIR=com.ibm.etools.egl.distributedbuild_version\executables\Win
set path=%INSTALL_PATH%\%JDK_PATH%;%SHARED_INSTALL_PATH%\%PLUGIN_PATH%\%CCUBLDC_DIR%
set classpath=%SHARED_INSTALL_PATH%\%PLUGIN_PATH%\%EGLBatchGen_JAR%;
%SHARED_INSTALL_PATH%\%PLUGIN_PATH%\%LOGGING_JAR%
cd %INSTALL_PATH%\%JDK_PATH%
java com.ibm.etools.egl.distributedbuild.BuildPlanLauncher %1
If you installed and kept a previous version of the EGL developer product before installing the product that you are using now, the shared installation directory of interest may be the directory that was used in the earlier install.
ccubldc -h destHost@destPort -b x -au destUserId -ap destPassword -V
In this case, destHost, destPort, destUserID and destPassword have the same meaning as described for the corresponding build descriptor options.
The ccubldc command causes a build failure message because of the attempt to run a nonexistent script named x. However, the command has the side effect of starting the CCU Security Manager with the password that you specify in the command.
java com.ibm.etools.egl.distributedbuild.security.CCUconfig
The Distributed Build Security Configuration dialog is displayed.