When you use the DeployJobs command in the CLI to redeploy a job that was initially manually deployed under a different name, the tool causes the job to be re-created under the default name. That results in two files for the job residing in the deployment directory. The scheduler still uses the initially created job file and not the newly deployed one.

For example, you schedule the job TestAlpha for deployment, but you enter "TestBeta" in the Deployed Job Name field, which creates a new file, TestBeta.sas. You then redeploy TestBeta with this command: 

Here is the output from the command:

The output indicates that the new name is applied. The deployment directory contains files with two different names:

• TestBeta.sas (job that you initially deployed)
• TestAlpha.sas (new file, but with the default job name)

The workaround is to use different folder locations in the command for both the -deploymentdir and the -sourcedir options. That prevents the source code file from being re-created with the default job name.

Click the Hot Fix tab in this note to access the hot fix for this issue.

Operating System and Release Information

A fix for this issue for Data Integration Studio 4.7_M7 is available at:

A fix for this issue for SAS Middle Tier 9.4_M7 is available at:

A fix for this issue for SAS Grid Manager Plug-ins for SAS Management Console 9.4_M7 is available at:

A fix for this issue for SAS Management Console 9.4_M6 is available at:

A fix for this issue for Data Integration Studio 4.904 is available at:

A fix for this issue for SAS Middle Tier 9.4_M6 is available at: