Jobs not getting compiled

maheshsada · Post by **maheshsada** » Tue Jan 06, 2009 5:01 am

Hi

Currently we are facing a issue where in a job which has shared container is getting compiled in designer but showing as 'Not Compiled' from director and hence the job is not running.
The jobs where working fine previously but suddenly now giving issues. the only change we have done is increasing the T30File value from 200 to 500.
Can you please suggest what is the sudden problem in jobs

regards
Magesh S

chulett · Post by **chulett** » Tue Jan 06, 2009 8:58 am

I don't see the connection but wondering if you change the T30FILE value back does the problem go away?

Also, is it "job" or "jobs" that you have this problem with?

ArndW · Post by **ArndW** » Tue Jan 06, 2009 2:00 pm

I dobn't see the connection between increasing the T30FILE setting and job compilation but it might be worth going back to the original value and seeing if the job now compiles.

Have you tried "force compile"?

maheshsada · Post by **maheshsada** » Wed Jan 07, 2009 10:19 am

We did "force compile" but still the problem exists. We have not yet reverted the T30 variable as we think it is not related to this issue. any more suggestions

Magesh S

chulett · Post by **chulett** » Wed Jan 07, 2009 10:45 am

chulett wrote:is it "job" or "jobs" that you have this problem with?

Since you used both words in your post. This is a problem with a single job, all jobs, only certain jobs?

maheshsada · Post by **maheshsada** » Wed Jan 07, 2009 12:03 pm

All the jobs which are using shared container are having this issue. Moreover this is also affecting jobs in different projects. These jobs where working fine before the change in server configuration.

Magesh S

chulett · Post by **chulett** » Wed Jan 07, 2009 12:05 pm

Again, since your alleged 'only change' was the T30 one, as a test change it back. Only way to get that off the table as a suspect.

Mike · Post by **Mike** » Wed Jan 07, 2009 12:38 pm

Any chance that somebody could have made a change to uvconfig long ago without a uvregen? and your T30 change just happened to pick that change up as well?

Mike

kandyshandy · Post by **kandyshandy** » Wed Jan 07, 2009 4:05 pm

May be funny.. but some time it happens.

Is your DS designer and director connected to the same environment? Hope you are not compiling the job in DEV but looking at director connected to some other environment

kandyshandy · Post by **kandyshandy** » Wed Jan 07, 2009 4:07 pm

May be funny.. but some time it happens.

Is your DS designer and director connected to the same environment? Hope you are not compiling the job in DEV but looking at director connected to some other environment

maheshsada · Post by **maheshsada** » Fri Jan 09, 2009 10:53 am

atlast we found the issue.......
The uvconfig parameter - PAKTIME was changed by some team member from 300 to 60 but regeneration was not done, when we changed the T30FILE value we did a regeneration hence the new value got configured. Once we reverted PAKTIME - 300 and regenerated the uvconfig file the jobs where showing as compiled in director.

Thanks everyone for the valuable suggestions

regards
Magesh S

chulett · Post by **chulett** » Fri Jan 09, 2009 10:56 am

Ah... someone needs a good smack upside the head.

ray.wurlod · Post by **ray.wurlod** » Fri Jan 09, 2009 3:42 pm

Just curious: would you mind asking said team member WHY the decision was made to use 60 as the new PAKTIME value?

chulett · Post by **chulett** » Fri Jan 09, 2009 3:49 pm

I had to go look up PAKTIME as it was not one I was familiar with.

Code: Select all

# PAKTIME - sets the number of seconds query is to
#       wait at the Press Any Key to continue message
#       before releasing a pending group lock.
PAKTIME 300

Odd that this would affect your ability to compile.

maheshsada · Post by **maheshsada** » Mon Jan 12, 2009 6:23 am

ray

we had a contractor who was looking after the server and currently left the organisation hence cannot get the reason for change.

Magesh S