LoadRunStats.AutoMeter has never been run

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
olgc
Participant
Posts: 145
Joined: Tue Nov 18, 2003 9:00 am

LoadRunStats.AutoMeter has never been run

Post by olgc »

Hi There,

LoadRunStats is an "Allow Multiple Instance" job.

When the following statement is executed in Job Control tab of a job properties

LdJobHandle=DSAttachJob("LoadRunStats.AutoMeter", DSJ.ERRWARN)

The error below is showed. How to fix the problem?

Thanks in advance,

EEROR Message:

Project:***
Job name:AuditInfo
Event #:1446
Timestamp:13-Aug-2009 2:12:47 PM
Event type:Warning
User:****
Message:
AuditInfo..CollectAuditInfo_Trns (DSRunJob): Job control error (-2)
(DSRunJob) LoadRunStats.AutoMeter has never been run.
ArndW
Participant
Posts: 16318
Joined: Tue Nov 16, 2004 9:08 am
Location: Germany
Contact:

Post by ArndW »

Are you certain that the message is at the DSAttachJob()? Try a DSLogWarn() before and after to make certain - I've never seen that message triggered from that call.
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

Neither have I. :?
-craig

"You can never have too many knives" -- Logan Nine Fingers
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

It appears that AutoMeter is an invocation ID, and I am guessing that the message derives from DSPrepareJob() - you can't reset a job that has never been run. It may be innocuous.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

Looks like it came from DSRunJob() so perhaps with a DSJ.RUNRESET RunMode? Does your code always attempt a reset or only if the job 'needs' it? I would think this would actually be avoided by use of the DSPrepareJob() function. :?
-craig

"You can never have too many knives" -- Logan Nine Fingers
olgc
Participant
Posts: 145
Joined: Tue Nov 18, 2003 9:00 am

Post by olgc »

Thanks for all your responses.

Now I know what's the problem. The key word here is "Allow multiple Instance" Job. It is the attach command. Only when this command succeeds, other operations can be followed.

If it's executed once from a regular sequence job with a job activity, it can be attached by a call to DSAttachJob() (After the call, a new instance will be showed up in Datastage Director). That's why it "has never been run".

Thanks,
Post Reply