Assuming you are using RTC 3.0.1, we also write the list of deployed files to a deltaDeployed.xml file that is stored on the deployment machine. There is an ant property which the location of this file is set to, but that is during the runtime of deployment, so it is not a property you can pass to your REXX script through the Post Deploy Command. You would instead need to modify the ant script (zosdeploy.xml) to call your REXX script.

In the zosdeploy.xml script you will want to add in the postDeploy target the same lines from the execPostDeployCommand target except change the arg line. For example if my REXX script was called POSTDEP then my arg line would be:

POSTDEP ${team.deploy.common.deployPackage.dir}/deltaDeployed.xml

All of our manifest files in RTC 3.0.1 are based off one schema which you can find at BST_INSTALL_DIRECTORY/buildsystem/buildtoolkit/scripts/enterprise/manifest.xsd

You can find the zosdeploy.xml file at BST_INSTALL_DIRECTORY/buildsystem/buildtoolkit/scripts/zos/

Does anyone know how to pass the list of files being deployed to a deploy post command process? Once the deployment ends this information is written to the deployment summary tab of the deployment build results, but I can't figure out how to pass them to a rexx program I execute from the deploy post command line. I need the list of members so that I can do some post deployment processing such as performing a bind of a DB2 program. I am creating the package by specifying a work item so the list of members can not be hard coded. It must be generated dynamically based upon what was built using members changed by the work item.