Version 8 compile issues

Post questions here relative to DataStage Server Edition for such areas as Server job design, DS Basic, Routines, Job Sequences, etc.

Moderators: chulett, rschirm, roy

Post Reply
jdmiceli
Premium Member
Premium Member
Posts: 309
Joined: Wed Feb 22, 2006 10:03 am
Location: Urbandale, IA

Version 8 compile issues

Post by jdmiceli »

We have two supposedly identical environments for Development and Production. We are running DataStage on AIX Unix.

I recently migrated my version 7 project to version 8. It was running fine on version 7 and the initial move to version 8 Development went fine. Performance on v8 has been pitiful thus far and we have had to get some patches from IBM for the InformationServer side of things. Compiling on Dev went fine, though it took 30+ hours to compile 1200+ jobs (over a minute per job). When they moved my code to the production server so it would be in position to activate when the time comes. However, when Release Management tries to compile the jobs, we get many errors for the majority of my jobs and job control batch jobs.

Any jobs that are Batch::JobControl type jobs throw the following errors/warnings:

Code: Select all


>> Batch::JobControl_AIC_uCWS - Failed <<
Error compiling Job Control Subroutine Batch::JobControl_AIC_uCWS
Compiling: Source = 'RT_BP2/JOB.501835091.DT.1489860873', Object = 'RT_BP2.O/JOB.501835091.DT.1489860873'
***************************************************************************************************************************
WARNING: Variable 'JobHierarchyFile' never assigned a value.
WARNING: Variable 'StartingMilestone' never assigned a value.
WARNING: Variable 'EndingMilestone' never assigned a value.
WARNING: Variable 'JobLinkStatisticChecksFile' never assigned a value.
WARNING: Variable 'ResurrectLogFile' never assigned a value.

Compilation Complete.
 (Batch::JobControl_AIC_uCWS)
All jobs of this type did this with the very same warnings. However, I am thinking that they actually compiled fine, but just warned that default values were not provided for those variables. Am I correct in that thought?

The other type of error I am getting deals with all other jobs and some routines ported over from the V8 Dev server. This is what those errors looked like:

Code: Select all


>> Deletes_ADM_ABSENCE - Failed <<
ROOT Job Definition Object not found. (Deletes_ADM_ABSENCE)


or 


>> BTSDatabaseActivity - Failed <<
Compiling: Source = 'DSU_BP/DSU.BTSDatabaseActivity', Object = 'DSU_BP.O/DSU.BTSDatabaseActivity'

WARNING: Variable 'Ans' never assigned a value.

Compilation Complete.
I am puzzled as to why this would happen. Just exporting from V7 to a .dsx file, importing into V8 and compiling with no changes worked fine. Yet when I export from V8 Dev, import to V8 Prod and try to compile, we get few successful compiles.

Ideas??

Thanks in advance for your assistance,
Bestest!

John Miceli
System Specialist, MCP, MCDBA
Berkley Technology Services


"Good Morning. This is God. I will be handling all your problems today. I will not need your help. So have a great day!"
ArndW
Participant
Posts: 16318
Joined: Tue Nov 16, 2004 9:08 am
Location: Germany
Contact:

Post by ArndW »

All jobs of this type did this with the very same warnings. However, I am thinking that they actually compiled fine, but just warned that default values were not provided for those variables. Am I correct in that thought?
Yes, the compilations went through and DS will substitute empty strings.

The "WARNING: Variable 'Ans' never assigned a value." warninghas always existed, so I don't see how this should be any different between versions.
jdmiceli
Premium Member
Premium Member
Posts: 309
Joined: Wed Feb 22, 2006 10:03 am
Location: Urbandale, IA

Post by jdmiceli »

Any thoughts on the "ROOT Job Definition Object not found" part of the error message?
Bestest!

John Miceli
System Specialist, MCP, MCDBA
Berkley Technology Services


"Good Morning. This is God. I will be handling all your problems today. I will not need your help. So have a great day!"
lstsaur
Participant
Posts: 1139
Joined: Thu Oct 21, 2004 9:59 pm

Post by lstsaur »

I have encountered this "ROOT Job Definition Object not found" problem before for version 8.0.1. It took IBM almost two months but still couldn't figure out the real root casue especially Oracle is used for the repository.
I mean I was told by the engineer that he did everything on the UV side, but that still couldn't solve the problem. To make long story short, your best and fastest solution is clean up the whole project. Of course, before delete the project, you should back up your dsenv, dsparams, .odbc.ini, uvodbc.config. Good luck.
Post Reply