Non-numeric data where numeric required. (was: Job Hangs an
Non-numeric data where numeric required. (was: Job Hangs an
This is a topic for an orphaned message.
Another thing to look for is an uninitialised variable used within a routine.
X += 1 assumes that X has a value to begin with. If no value has been assigned prior, X is assumed to have a value of VARCHAR[0]. Thus Datastage is forcing a conversion of the datatype from VARCHAR to Integer. Datastage also likes to warn the programmer it is taking this type of action as it usually indicates a programming error.
Cheers,
Ray D
----- Original Message -----
From: "Ray Wurlod"
To:
Cc:
Sent: Tuesday, August 15, 2000 3:02 PM
Subject: RE: Non-numeric data where numeric required. (was: Job Hangs and Job Lock (but isnt))
> This is almost certainly a problem in one of your job designs or
> routines, rather than in DataStage. Its reported by DSD.RUN because
> this is the program that runs a job. "Non-numeric data where numeric
> required. Zero used." is DataStage (UniVerse RDBMS) trying to be
> helpful. Somewhere you have provided a non-numeric value, perhaps to
> an arithmetic function. UniVerse has
replaced
> this with zero, so that the calculation can continue. This is an
> artifact of DataStage working without data types, so that you have
> received input data that is not numeric, and attempted to use it in a
> numeric context.
You
> can test whether an item of data is numeric using the Num() function.
>
> > ----------
> > From: sudhir.mahendru@db.com[SMTP:sudhir.mahendru@db.com]
> > Sent: Saturday, 12 August 2000 18:21
> > To: informix-datastage@oliver.com
> > Cc: David.Barham@anglocoal.com.au; ray.wurlod@informix.com
> > Subject: RE: Job Hangs and Job Lock
> >
> > I have found following observation in &PH&, for all the jobs which
> > complete successfull I get this kind of message message.
> >
> > DataStage Job 701 Phantom 26099
> > Program "DSD.RUN": Line 274, Nonnumeric data when numeric required.
Zero
> > used.
> > DataStage Phantom Finished
> >
> > ( the middle line is coming in all the logs )
> >
> > and the job which hangs have the message as
> > DataStage Job 996 Phantom 21258
> > Program "DSD.RUN": Line 274, Nonnumeric data when numeric required.
Zero
> > used.
> >
> > please advice as early as possible.
> >
> > regards
> > Sudhir
> > APHOIT/CA$H Datawarehouse Team
> > (65) 423-7449
> >
> >
> > ---------------------------------------- Message History
> > ----------------------------------------
> >
> >
> > From: David.Barham@anglocoal.com.au on 10/08/2000 05:32 GMT
> >
> > Please respond to informix-datastage@oliver.com
> >
> > To: informix-datastage@oliver.com
> > cc:
> > Subject: RE: Job Hangs and Job Lock
> >
> >
> >
> > Sudhir,
> >
> > In my references to the &PH& directory, I wasnt suggesting that
> > there
is
> > a
> > problem here that needs addressing, but rather, that these work
> > files might contain a clue as to what is wrong with your job that
> > keeps hanging.
> >
> > Are you able to tell from Unix if the hanging job is using CPU (eg
endless
> > loop) or not (eg waiting on something)?
> >
> > David
> > -----Original Message-----
> > From: sudhir.mahendru@db.com [SMTP:sudhir.mahendru@db.com]
> > Sent: Thursday, 10 August 2000 14:47
> > To: informix-datastage@oliver.com
> > Subject: RE: Job Hangs and Job Lock
> >
> > In this case will CLEAR.FILE DATA &PH& help
> > if i do it on regular basis does it have any impact on jobs
> > please clarify
> >
> > thanks and regards
> > Sudhir
> > APHOIT/CA$H Datawarehouse Team
> > (65) 423-7449
> >
> >
> > ---------------------------------------- Message History
> > ----------------------------------------
> >
> >
> > From: ray.wurlod@informix.com on 10/08/2000 04:50 GMT
> >
> > Please respond to informix-datastage@oliver.com
> >
> > To: informix-datastage@oliver.com
> > cc:
> > Subject: RE: Job Hangs and Job Lock
> >
> >
> >
> > Job Hangs
> > As David pointed out, you can get more information about the
> > actual status
> > of each active stage in a job by using the Monitor. Choosing
> > "show links"
> > can provide more information. Double clicking on any line in
> > the Monitor
> > view will reveal the process ID associated with that active
> > stage, which can
> > be helpful when using the Job > Cleanup Resources option in
> > Director.
> > Occasionally a child process (e.g. active stage running
> > DSD.StageRun) is
> > unable to notify its parent (e.g. job running DSD.RUN) that it,
> > the child
> > process, has finished, leaving the job process awaiting
> > notification. This
> > will be clear from the Monitor, as all the active stages will
> > have
a
> > status
> > of Finished, but the jobs status will still be Running. In
> > this case, you
> > can clear the jobs status file reasonably safely.
> >
> > Job Locks
> > Usually "cannot get exclusive access to job" indicates that
> > another process,
> > such as a DataStage client, has the job open in some kind of
editor.
> > For example, the Manager may have the job properties open, or
> > the job may be
> > open in Designer, or the job may be being monitored. What are your
> > DataStage developers doing?
> >
> > > ----------
> > > From: sudhir.mahendru@db.com[SMTP:sudhir.mahendru@db.com]
> > > Reply To: informix-datastage@oliver.com
> > > Sent: Thursday, 10 August 2000 12:12
> > > To: informix-datastage@oliver.com
> > > Subject: Job Hangs and Job Lock
> > >
> > > I have two types of problem in datastage
> > > job hangs and job locked
> > > Some times the job hangs with out any reason.
> > > Some times the the job control job hangs because the
> > > called job has got exclusive lock
> > > (cannot get exclusive access to job ).
> > >
> > > what could be the possible solution for this?
> > >
> > > thanks and regards
> > > Sudhir
> > > APHOIT/CA$H Datawarehouse Team
> > > (65) 423-7449
> > >
> > >
> >
> >
> >
> >
> >
> >
*************************************************************************
> > This e-mail and any files transmitted with it may be confidential
> > and are intended solely for the use of the individual or entity to
> > whom they are addressed. If you have received this e-mail in error,
> > please notify the sender by return e-mail, and delete this e-mail
> > from your in-box. Do not copy it to anybody else
> >
> >
*************************************************************************
> >
> >
> >
> >
>
X += 1 assumes that X has a value to begin with. If no value has been assigned prior, X is assumed to have a value of VARCHAR[0]. Thus Datastage is forcing a conversion of the datatype from VARCHAR to Integer. Datastage also likes to warn the programmer it is taking this type of action as it usually indicates a programming error.
Cheers,
Ray D
----- Original Message -----
From: "Ray Wurlod"
To:
Cc:
Sent: Tuesday, August 15, 2000 3:02 PM
Subject: RE: Non-numeric data where numeric required. (was: Job Hangs and Job Lock (but isnt))
> This is almost certainly a problem in one of your job designs or
> routines, rather than in DataStage. Its reported by DSD.RUN because
> this is the program that runs a job. "Non-numeric data where numeric
> required. Zero used." is DataStage (UniVerse RDBMS) trying to be
> helpful. Somewhere you have provided a non-numeric value, perhaps to
> an arithmetic function. UniVerse has
replaced
> this with zero, so that the calculation can continue. This is an
> artifact of DataStage working without data types, so that you have
> received input data that is not numeric, and attempted to use it in a
> numeric context.
You
> can test whether an item of data is numeric using the Num() function.
>
> > ----------
> > From: sudhir.mahendru@db.com[SMTP:sudhir.mahendru@db.com]
> > Sent: Saturday, 12 August 2000 18:21
> > To: informix-datastage@oliver.com
> > Cc: David.Barham@anglocoal.com.au; ray.wurlod@informix.com
> > Subject: RE: Job Hangs and Job Lock
> >
> > I have found following observation in &PH&, for all the jobs which
> > complete successfull I get this kind of message message.
> >
> > DataStage Job 701 Phantom 26099
> > Program "DSD.RUN": Line 274, Nonnumeric data when numeric required.
Zero
> > used.
> > DataStage Phantom Finished
> >
> > ( the middle line is coming in all the logs )
> >
> > and the job which hangs have the message as
> > DataStage Job 996 Phantom 21258
> > Program "DSD.RUN": Line 274, Nonnumeric data when numeric required.
Zero
> > used.
> >
> > please advice as early as possible.
> >
> > regards
> > Sudhir
> > APHOIT/CA$H Datawarehouse Team
> > (65) 423-7449
> >
> >
> > ---------------------------------------- Message History
> > ----------------------------------------
> >
> >
> > From: David.Barham@anglocoal.com.au on 10/08/2000 05:32 GMT
> >
> > Please respond to informix-datastage@oliver.com
> >
> > To: informix-datastage@oliver.com
> > cc:
> > Subject: RE: Job Hangs and Job Lock
> >
> >
> >
> > Sudhir,
> >
> > In my references to the &PH& directory, I wasnt suggesting that
> > there
is
> > a
> > problem here that needs addressing, but rather, that these work
> > files might contain a clue as to what is wrong with your job that
> > keeps hanging.
> >
> > Are you able to tell from Unix if the hanging job is using CPU (eg
endless
> > loop) or not (eg waiting on something)?
> >
> > David
> > -----Original Message-----
> > From: sudhir.mahendru@db.com [SMTP:sudhir.mahendru@db.com]
> > Sent: Thursday, 10 August 2000 14:47
> > To: informix-datastage@oliver.com
> > Subject: RE: Job Hangs and Job Lock
> >
> > In this case will CLEAR.FILE DATA &PH& help
> > if i do it on regular basis does it have any impact on jobs
> > please clarify
> >
> > thanks and regards
> > Sudhir
> > APHOIT/CA$H Datawarehouse Team
> > (65) 423-7449
> >
> >
> > ---------------------------------------- Message History
> > ----------------------------------------
> >
> >
> > From: ray.wurlod@informix.com on 10/08/2000 04:50 GMT
> >
> > Please respond to informix-datastage@oliver.com
> >
> > To: informix-datastage@oliver.com
> > cc:
> > Subject: RE: Job Hangs and Job Lock
> >
> >
> >
> > Job Hangs
> > As David pointed out, you can get more information about the
> > actual status
> > of each active stage in a job by using the Monitor. Choosing
> > "show links"
> > can provide more information. Double clicking on any line in
> > the Monitor
> > view will reveal the process ID associated with that active
> > stage, which can
> > be helpful when using the Job > Cleanup Resources option in
> > Director.
> > Occasionally a child process (e.g. active stage running
> > DSD.StageRun) is
> > unable to notify its parent (e.g. job running DSD.RUN) that it,
> > the child
> > process, has finished, leaving the job process awaiting
> > notification. This
> > will be clear from the Monitor, as all the active stages will
> > have
a
> > status
> > of Finished, but the jobs status will still be Running. In
> > this case, you
> > can clear the jobs status file reasonably safely.
> >
> > Job Locks
> > Usually "cannot get exclusive access to job" indicates that
> > another process,
> > such as a DataStage client, has the job open in some kind of
editor.
> > For example, the Manager may have the job properties open, or
> > the job may be
> > open in Designer, or the job may be being monitored. What are your
> > DataStage developers doing?
> >
> > > ----------
> > > From: sudhir.mahendru@db.com[SMTP:sudhir.mahendru@db.com]
> > > Reply To: informix-datastage@oliver.com
> > > Sent: Thursday, 10 August 2000 12:12
> > > To: informix-datastage@oliver.com
> > > Subject: Job Hangs and Job Lock
> > >
> > > I have two types of problem in datastage
> > > job hangs and job locked
> > > Some times the job hangs with out any reason.
> > > Some times the the job control job hangs because the
> > > called job has got exclusive lock
> > > (cannot get exclusive access to job ).
> > >
> > > what could be the possible solution for this?
> > >
> > > thanks and regards
> > > Sudhir
> > > APHOIT/CA$H Datawarehouse Team
> > > (65) 423-7449
> > >
> > >
> >
> >
> >
> >
> >
> >
*************************************************************************
> > This e-mail and any files transmitted with it may be confidential
> > and are intended solely for the use of the individual or entity to
> > whom they are addressed. If you have received this e-mail in error,
> > please notify the sender by return e-mail, and delete this e-mail
> > from your in-box. Do not copy it to anybody else
> >
> >
*************************************************************************
> >
> >
> >
> >
>