Issue with variable

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
srinivas.g
Participant
Posts: 251
Joined: Mon Jun 09, 2008 5:52 am

Issue with variable

Post by srinivas.g »

Hi All,

In my project there are so many jobs with job parameter REPORT_DATE. These jobs are in production for long time.

Now with the export this project I have created new project and started compiling jobs. Some of the jobs with this parameter are not compiling, throughing following error message,

Error preprocessing Transform Derivation for stage CFlyCtDeltaload.XTERM.

Link DSLink52, Column REPORT_DATE: Oconv(Iconv(ReportDate,'D-MDY[2,2,4]'),'D-MDY[2,2,4]')

Expected: left parenthesis ("(")

When I correct the name with Rdate job is working fine. But I cant actually change like this since this programs are in production.

Some more information

Both are same environment and same version of DataStage and UNIX not change.

Please advice.

Prakash
ArndW
Participant
Posts: 16318
Joined: Tue Nov 16, 2004 9:08 am
Location: Germany
Contact:

Post by ArndW »

If the job parameter is "REPORT_DATE" then how is the value of "ReportDate" being derived?
laknar
Participant
Posts: 162
Joined: Thu Apr 26, 2007 5:59 am
Location: Chennai

Post by laknar »

this seams that ReportDate parameter is not specified for that job.
check the job parameters , the parameter name should be the ReportDate name.
srinivas.g
Participant
Posts: 251
Joined: Mon Jun 09, 2008 5:52 am

Post by srinivas.g »

Actually this is a sequencer and ReportDate is the sequencer parameter and this param is being assigned to the job which sequencer is calling and in the job the param name ins REPORT_DATE.

Also this is jobs are already running in production for years and never had this problem.

Just when I am importing and compiling this jobs in new development project I am getting this compilation error.

Yet in production this jobs are still running with out any changes.
Last edited by srinivas.g on Fri Sep 04, 2009 5:16 am, edited 1 time in total.
Sainath.Srinivasan
Participant
Posts: 3337
Joined: Mon Jan 17, 2005 4:49 am
Location: United Kingdom

Post by Sainath.Srinivasan »

Then what is Rdate?
laknar
Participant
Posts: 162
Joined: Thu Apr 26, 2007 5:59 am
Location: Chennai

Post by laknar »

Andy is correct .
If the job parameter is "REPORT_DATE" then how is the value of "ReportDate" being derived?
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Re: Issue with variable

Post by chulett »

srinivas.g wrote:When I correct the name with Rdate job is working fine. But I cant actually change like this since this programs are in production.
What is this 'correction' that you need to do?
-craig

"You can never have too many knives" -- Logan Nine Fingers
srinivas.g
Participant
Posts: 251
Joined: Mon Jun 09, 2008 5:52 am

Post by srinivas.g »

Hi All,

Issue is now resloved. There is one routine created one year back with name ReportDate. After this point this problem is started. we just identified and renamed the routine now every other jobs are fine.

some time it looks little ill logic but that what was happed.
Thx to all
Post Reply