You can use deployment spaces for testing or production to maintain a strict separation from the development environment. Users in a space can open and update connections, parameters, partitioning, and other project settings, but cannot view or modify flows.

To maintain a strict separation from the development environment, use a project for all development, debugging, and design. As you complete flows, propagate them to a deployment space that you can create and configure with a vault, credentials, and collaborators. For more information about spaces, see Deployment spaces.

Running jobs in a space

Once you have completed a flow, you can export it as a .zip file and import it into a deployment space by using the dsjob command line. Importing an ISX file into a space is not recommended. Before running an imported flow, open the flow's connections and update the credentials to match the new environment. Review parameter sets and adjust parameter values to the correct values for the space. You can run jobs, configure a schedule to run jobs, and optionally configure notifications in a space. You can also use the dsjob command line to invoke jobs in a space.

Troubleshooting

If your credentials and parameters are correct but a job fails to run correctly, you can export the flow as a zip file and import it back into a project to be viewed and modified before importing it back into the space. Using the cpdctl dsjob migrate command, set the conflict-resolution flag to determine what happens when a new version of an existing flow is imported into a space. See DataStage command-line tools for more information.