Period or dot in Invocation ID

rroy2 · Post by **rroy2** » Tue Apr 03, 2012 5:57 pm

Hi,

I have a multi-instance parallel sequencer invoking a multi-instance server job.
The seqencer is receving a value in 'pJobName' job parameter as ABC.123 (some jobname.Runid)

We are passing this pJobName value to server job as the invocation id. But the job gets triggered with name as 'ServerJobName.ABC' only. It misses 123 in name (we want it to be like 'ServerJobName.ABC.123)

Is it that Invocation Ids dont take '.' (dot/period) in the values??
If not is ther a way to pass this, and make the job name further unique by adding .123 to it?

Please help

Thanks

chulett · Post by **chulett** » Tue Apr 03, 2012 6:51 pm

No, you can't have a dot in the actual Invocation ID value. Why not replace the second dot with something like an underscore?

qt_ky · Post by **qt_ky** » Tue Apr 03, 2012 6:57 pm

I think extra dots will confuse it, as the dot is a delimiter. If you're set on using a dot, check with IBM. You may be able to request it as an enhancement for a future release. If other people are not requesting the same thing though, then I don't think it's too likely to be added.

ray.wurlod · Post by **ray.wurlod** » Tue Apr 03, 2012 9:29 pm

Dots are not and never will be accepted, for the same reason that (in most databases anyway) they're not permitted in identifier names such as schema, table and column names.