Job Parameter Limit

tathoong · Post by **tathoong** » Wed Jul 26, 2006 8:01 pm

Hi All,

Is there any limit for the job parameter in a server job? Currently one of my server job is having 62 job parameters. The encyrpted
parameter was passed wrongly after I changed other parameter which was not encrypted.

In order to avoid the reoccur of this problem, everytime I change job parameter I needed to re-key in all the encrypted parameter.

tathoong

chulett · Post by **chulett** » Wed Jul 26, 2006 8:26 pm

No limit that I've ever run into, though I'm sure there is one. But then I've never seen a job that needed 62 job parameters. :shock:

I have, however, seen problems in older versions with encrypted parameters needing their values to be rekeyed at times, but seem to recall it was only if you 'arrowed' down through it on your way to another parameter. But not something I've seen in the last few years that I recall.

kcbland · Post by **kcbland** » Wed Jul 26, 2006 9:34 pm

Hmmm, sounds like you're using defaults in jobs rather than feeding at runtime with job control. Maybe you should consider changing your standard?

kumar_s · Post by **kumar_s** » Wed Jul 26, 2006 10:29 pm

Try to have a lookup table in the job design with the static informations, to avoid fuzzy.

ray.wurlod · Post by **ray.wurlod** » Wed Jul 26, 2006 11:38 pm

I have seen master job sequences with this many and more.

There is no theoretical limit to the number of job parameters than may exist in a job or job sequence. If there is a practical limit, it is running out of memory to store the lists of names, default values, prompt texts and so on. Thousands, if not more.