Submitting remote build requests using rccbuild

This topic describes rccbuild command options and processing.

Before you begin

References to server are to the mainframe system (z/OS®) and the references to client are to the distributed system where you are initiating the rccbuild command.

For information on migrating to newer versions of the Remote Build server, see Using previous versions of the Remote Build server

Note for z/OS server requests: During a client-to-server transfer, text files are converted to EBCDIC. When server files are transferred to the client, text files are converted to ASCII. Binary files are not converted in either direction. The rccbuild processor cannot handle files that contain both text and binary data. If you have text files with embedded binary data, transfer them to the appropriate data sets before issuing the rccbuild command.

About this task

The server creates a build job when you run the client program rccbuild. The client then waits for completion of the build while the server runs the build script. The server returns the results of the build to the client along with a return code of 0 (success) or 1 (failure).

If both the rccbuild –o option and the appropriate server and build script BCL options are used, build results are sent to the remote workstation's file system. These results include return codes, messages, and any files that are returned to the client.

Procedure

For instructions on formatting and submitting rccbuild requests, select from the following topics: