This page provides information about the analysis error : Invalid Job generation for Application "<Application name>".
This error comes during the synchronization phase.
Release | Yes/No |
|---|---|
| 8.3.x |  |
| 8.2.x |  |
| 8.1.x | |
| 8.0.x | |
| 7.3.x | |
| 7.2.x | |
| 7.0.x | |
RDBMS | Yes/No |
|---|---|
| Oracle Server | |
| Microsoft SQL Server | |
| CSS3 | |
| CSS2 | |
| CSS1 | |
- Using DMT package Zos source and deliver
- In CMS accept the delivery and run analysis
- Error raised during the synchronization phase
- CAST Support Tool (CST) - alias Sherlock
- Screenshot describing the error.
Open the CAST-MS log file.
- Search for the error message: Invalid Job Generation
- Most of the time the error message is due to the fact that:
- The Deployment folder is not accessible by CAST-MS. Make the Deployment folder accessible.
- If the Deployment folder is accessible, the Manifest File that was used to defined the Analysis Units is not in the deployment folder. Retrieve the Manifest file by setting as current version again.
Check if the extracted Zos Source format is not correct
This error may occur if the extracted ZOs Source format is not correct. Action plan is to verify the source format.
The extracted source could have wrong extracted size of columns .
The files used do not respect the specification as described in the recommended documentation.
The solution is to correct extraction as defined in above link.
Check if the DMT configuration has been modified after the delivered version is set as current version
The error could be encountered in scenarios where the configuration of the DMT has been changed after the version has been set as current version from Cast-MS.
For example, the customer had the initial Zos extraction done with the DB2 files with standard names as DB2.MANIFEST but after the set as current version have renamed the files to CAST.DB2X.DB2.MANIFEST.
Post this they have packaged and delivered again but the changes have not been updated in the Delivery since they have not checked the Force Extraction option to force the changes to be updated in the Delivery.
The synchronize services fails to synchronize due to inconsistency in the delivery folder.
The solution is to open DMT and package and deliver the version with force extraction option set to true.
Note: If you choose to do any sort of configuration changes after you have packaged and delivered your version, one should always use the Force extraction option.
Webcall - 29551
Ticket # 4003
