Distributed Generation Server

The AppMaster Builder Distributed Generation Server feature enables you to generate APS for z/OS code using AppMaster Builder on a local PC or LAN without having to download your APS source members and import them into an AppMaster Builder project. You can generate programs for CICS, IMS, ISPF, and MVS data communication targets, and screens for CICS and IMS data communication targets.

The DGS is designed to receive and send messages to and from your mainframe via a middleware interface. These messages provide information such as file names and locations, output requirements, and other preference settings. DGS generation is achieved using the following process:

1. On the mainframe side, a message to AppMaster Builder is initiated in the JCL that runs an APS generation job by executing the DGS AMBCOMP program. The job pauses at that point, awaiting a return message.
2. On the PC side, the message is received by the DGS, which downloads required APS source members and then generates them according to the details in the message. When generation is complete, the DGS initiates a return message to the mainframe and uploads the appropriate generated files.
3. When the return message is received on the mainframe, depending on the message returned, the APS generation job either continues from the point after the execution of the AMBCOMP program, or stops running.

For detailed information describing the role of the AMBCOMP program and the middleware interface, see AMBCOMP Program and The WebSphere MQ DGS Interface.

To see example JCL that executes AMBCOMP, see JCL Example.