I have a several batch processes that abort with this message, however, none of the jobs seem to be affected. Any ideas as to why the jobs would not start periodically?
Batch::DailyRejectPercent.JobControl (fatal error from DSRunJob): Job control fatal error (-14)
(DSRunJob) Job DailyRejectPercentNCSHP7 has not logged any events since #7282, and appears not to have started after 1800 secs
---------------------------------------------------------
The sender of this electronic message intends that this e-mail be used exclusively by the individual or entity to which it is intended to be addressed. This message may contain information that is privileged and confidential and thereby exempt and protected from unauthorized disclosure under applicable law. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering the message to the intended recipient, be aware that any disclosure, dissemination, distribution or copying of this communication, or the use of its contents, is not authorized and is strictly prohibited. If you have received this communication in error and are not the intended recipient, please notify the sender immediately and permanently delete the original message from your e-mail system.
Batch Aborts
This is almost impossible to answer without knowing fairly precisely what your jobs are trying to do. In general, something somewhere is waiting for a resource for more than 1800 seconds - this might be an FTP connection or something like that. While waiting, the job is not logging any events, so the supervising process (the one executing DSD.RUN) detects that fact and aborts the job with the indicated message. I have seen this once where two streams were trying to write to the one sequential file, and in another case where a job was trying to write to and read from the same hashed file through the same stage (violating the rule that a passive stage cannot open its output until all its inputs are closed).
There is an option in DS Administrator to set Inactivity Timeout. Follow these steps to set Inactivity Timeout
Go to DS Administrator.
Set time for Inactivity in Inactivity Timeout box.
Do not timeout option can also be selected.
Once this option is set any job will not get aborted even it takes long time to complete.
But you have to find out why this job takes long time.
Hope this will help you.
lhamilto@ncsh
ealth.com To: datastage-users@oliver.com
cc:
28-Sep-2001 Subject: Batch Aborts
06:48
Please
respond to
datastage-use
rs
Sender Info:
No Sender
Info found in
the address
Book
I have a several batch processes that abort with this message, however, none of the jobs seem to be affected. Any ideas as to why the jobs would not start periodically?
Batch::DailyRejectPercent.JobControl (fatal error from DSRunJob): Job control fatal error (-14)
(DSRunJob) Job DailyRejectPercentNCSHP7 has not logged any events since #7282, and appears not to have started after 1800 secs
---------------------------------------------------------
The sender of this electronic message intends that this e-mail be used exclusively by the individual or entity to which it is intended to be addressed. This message may contain information that is privileged and confidential and thereby exempt and protected from unauthorized disclosure under applicable law. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering the message to the intended recipient, be aware that any disclosure, dissemination, distribution or copying of this communication, or the use of its contents, is not authorized and is strictly prohibited. If you have received this communication in error and are not the intended recipient, please notify the sender immediately and permanently delete the original message from your e-mail system.
______________________________________________________________________________________
Visit us at www.singaporeair.com. ______________________________________________________________________________________
Go to DS Administrator.
Set time for Inactivity in Inactivity Timeout box.
Do not timeout option can also be selected.
Once this option is set any job will not get aborted even it takes long time to complete.
But you have to find out why this job takes long time.
Hope this will help you.
lhamilto@ncsh
ealth.com To: datastage-users@oliver.com
cc:
28-Sep-2001 Subject: Batch Aborts
06:48
Please
respond to
datastage-use
rs
Sender Info:
No Sender
Info found in
the address
Book
I have a several batch processes that abort with this message, however, none of the jobs seem to be affected. Any ideas as to why the jobs would not start periodically?
Batch::DailyRejectPercent.JobControl (fatal error from DSRunJob): Job control fatal error (-14)
(DSRunJob) Job DailyRejectPercentNCSHP7 has not logged any events since #7282, and appears not to have started after 1800 secs
---------------------------------------------------------
The sender of this electronic message intends that this e-mail be used exclusively by the individual or entity to which it is intended to be addressed. This message may contain information that is privileged and confidential and thereby exempt and protected from unauthorized disclosure under applicable law. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering the message to the intended recipient, be aware that any disclosure, dissemination, distribution or copying of this communication, or the use of its contents, is not authorized and is strictly prohibited. If you have received this communication in error and are not the intended recipient, please notify the sender immediately and permanently delete the original message from your e-mail system.
______________________________________________________________________________________
Visit us at www.singaporeair.com. ______________________________________________________________________________________
You need to be aware that the job message indicates
that the job is believed to be started, but there are
no indications that the job actually started.
I recommend SHRINKING this value, because what is
happening is the job is in LA-LA-LAND, and did not
respond to the job start command. I have only seen
this problem occur maybe 10 times since I started
working with DS 3.1. All of the occurrences for me
were on different platforms, UNIX and NT, different
versions of DS. I have never been able to reproduce
this issue.
My feeling is that if a job is issued the start
command using the BASIC APIs and it fails to start
within 5 minutes, then its the same as the job
failing. The sooner you know this the better.
Good luck!
-Ken
--- Saravanan_Thirugnanam@singaporeair.com.sg wrote:
>
> There is an option in DS Administrator to set
> Inactivity Timeout. Follow
> these steps to set Inactivity Timeout
>
> Go to DS Administrator.
> Set time for Inactivity in Inactivity Timeout
> box.
> Do not timeout option can also be selected.
>
> Once this option is set any job will not get aborted
> even it takes long
> time to complete.
>
> But you have to find out why this job takes long
> time.
>
> Hope this will help you.
>
>
>
>
>
> lhamilto@ncsh
>
> ealth.com To:
> datastage-users@oliver.com
> cc:
>
> 28-Sep-2001 Subject:
> Batch Aborts
> 06:48
>
> Please
>
> respond to
>
> datastage-use
>
> rs
>
>
>
> Sender Info:
>
> No Sender
>
> Info found in
>
> the address
>
> Book
>
>
>
>
>
>
>
>
>
>
>
> I have a several batch processes that abort with
> this message, however,
> none of the jobs seem to be affected.
> Any ideas as to why the jobs would not start
> periodically?
>
> Batch::DailyRejectPercent.JobControl (fatal error
> from DSRunJob): Job
> control fatal error (-14)
> (DSRunJob) Job DailyRejectPercentNCSHP7 has not
> logged any events since
> #7282, and
> appears not to have started after 1800 secs
>
---------------------------------------------------------
> The sender of this electronic message intends that
> this e-mail be used
> exclusively by the individual or entity to which it
> is intended to be
> addressed. This message may contain information
> that is privileged and
> confidential and thereby exempt and protected from unauthorized
> disclosure under applicable law. If the reader of this message
> is not the intended
> recipient, or an employee or agent responsible for
> delivering the message
> to the intended recipient, be aware that any
> disclosure, dissemination,
> distribution or copying of this communication, or
> the use of its contents,
> is not authorized and is strictly prohibited. If
> you have received this
> communication in error and are not the intended
> recipient, please notify
> the sender immediately and permanently
> delete the original message from your e-mail system.
>
>
>
>
>
>
______________________________________________________________________________________
>
> Visit us at www.singaporeair.com.
>
______________________________________________________________________________________
>
__________________________________________________
Do You Yahoo!?
Listen to your Yahoo! Mail messages from any phone. http://phone.yahoo.com
that the job is believed to be started, but there are
no indications that the job actually started.
I recommend SHRINKING this value, because what is
happening is the job is in LA-LA-LAND, and did not
respond to the job start command. I have only seen
this problem occur maybe 10 times since I started
working with DS 3.1. All of the occurrences for me
were on different platforms, UNIX and NT, different
versions of DS. I have never been able to reproduce
this issue.
My feeling is that if a job is issued the start
command using the BASIC APIs and it fails to start
within 5 minutes, then its the same as the job
failing. The sooner you know this the better.
Good luck!
-Ken
--- Saravanan_Thirugnanam@singaporeair.com.sg wrote:
>
> There is an option in DS Administrator to set
> Inactivity Timeout. Follow
> these steps to set Inactivity Timeout
>
> Go to DS Administrator.
> Set time for Inactivity in Inactivity Timeout
> box.
> Do not timeout option can also be selected.
>
> Once this option is set any job will not get aborted
> even it takes long
> time to complete.
>
> But you have to find out why this job takes long
> time.
>
> Hope this will help you.
>
>
>
>
>
> lhamilto@ncsh
>
> ealth.com To:
> datastage-users@oliver.com
> cc:
>
> 28-Sep-2001 Subject:
> Batch Aborts
> 06:48
>
> Please
>
> respond to
>
> datastage-use
>
> rs
>
>
>
> Sender Info:
>
> No Sender
>
> Info found in
>
> the address
>
> Book
>
>
>
>
>
>
>
>
>
>
>
> I have a several batch processes that abort with
> this message, however,
> none of the jobs seem to be affected.
> Any ideas as to why the jobs would not start
> periodically?
>
> Batch::DailyRejectPercent.JobControl (fatal error
> from DSRunJob): Job
> control fatal error (-14)
> (DSRunJob) Job DailyRejectPercentNCSHP7 has not
> logged any events since
> #7282, and
> appears not to have started after 1800 secs
>
---------------------------------------------------------
> The sender of this electronic message intends that
> this e-mail be used
> exclusively by the individual or entity to which it
> is intended to be
> addressed. This message may contain information
> that is privileged and
> confidential and thereby exempt and protected from unauthorized
> disclosure under applicable law. If the reader of this message
> is not the intended
> recipient, or an employee or agent responsible for
> delivering the message
> to the intended recipient, be aware that any
> disclosure, dissemination,
> distribution or copying of this communication, or
> the use of its contents,
> is not authorized and is strictly prohibited. If
> you have received this
> communication in error and are not the intended
> recipient, please notify
> the sender immediately and permanently
> delete the original message from your e-mail system.
>
>
>
>
>
>
______________________________________________________________________________________
>
> Visit us at www.singaporeair.com.
>
______________________________________________________________________________________
>
__________________________________________________
Do You Yahoo!?
Listen to your Yahoo! Mail messages from any phone. http://phone.yahoo.com
The controlling job is looking at the job log to determine if the job has started.
If you have a before job routine, or code in the job control area of the job that takes a while to run, then this can result in the job legitimately running but with nothing being logged.
If this is the case, then I recommend logging something with DSLogInfo as the first thing in the job control or the before job routine.
-----Original Message-----
From: Kenneth Bland [mailto:kcbland_2000@yahoo.com]
Sent: Monday, 1 October 2001 12:20 PM
To: datastage-users@oliver.com
Subject: Re: Batch Aborts
You need to be aware that the job message indicates
that the job is believed to be started, but there are
no indications that the job actually started.
I recommend SHRINKING this value, because what is
happening is the job is in LA-LA-LAND, and did not
respond to the job start command. I have only seen
this problem occur maybe 10 times since I started
working with DS 3.1. All of the occurrences for me
were on different platforms, UNIX and NT, different
versions of DS. I have never been able to reproduce
this issue.
My feeling is that if a job is issued the start
command using the BASIC APIs and it fails to start
within 5 minutes, then its the same as the job
failing. The sooner you know this the better.
Good luck!
-Ken
--- Saravanan_Thirugnanam@singaporeair.com.sg wrote:
>
> There is an option in DS Administrator to set
> Inactivity Timeout. Follow
> these steps to set Inactivity Timeout
>
> Go to DS Administrator.
> Set time for Inactivity in Inactivity Timeout
> box.
> Do not timeout option can also be selected.
>
> Once this option is set any job will not get aborted
> even it takes long
> time to complete.
>
> But you have to find out why this job takes long
> time.
>
> Hope this will help you.
>
>
>
>
>
> lhamilto@ncsh
>
> ealth.com To:
> datastage-users@oliver.com
> cc:
>
> 28-Sep-2001 Subject:
> Batch Aborts
> 06:48
>
> Please
>
> respond to
>
> datastage-use
>
> rs
>
>
>
> Sender Info:
>
> No Sender
>
> Info found in
>
> the address
>
> Book
>
>
>
>
>
>
>
>
>
>
>
> I have a several batch processes that abort with
> this message, however,
> none of the jobs seem to be affected.
> Any ideas as to why the jobs would not start
> periodically?
>
> Batch::DailyRejectPercent.JobControl (fatal error
> from DSRunJob): Job
> control fatal error (-14)
> (DSRunJob) Job DailyRejectPercentNCSHP7 has not
> logged any events since
> #7282, and
> appears not to have started after 1800 secs
>
---------------------------------------------------------
> The sender of this electronic message intends that
> this e-mail be used
> exclusively by the individual or entity to which it
> is intended to be
> addressed. This message may contain information
> that is privileged and
> confidential and thereby exempt and protected from unauthorized
> disclosure under applicable law. If the reader of this message
> is not the intended
> recipient, or an employee or agent responsible for
> delivering the message
> to the intended recipient, be aware that any
> disclosure, dissemination,
> distribution or copying of this communication, or
> the use of its contents,
> is not authorized and is strictly prohibited. If
> you have received this
> communication in error and are not the intended
> recipient, please notify
> the sender immediately and permanently
> delete the original message from your e-mail system.
>
>
>
>
>
>
____________________________________________________________________________
__________
>
> Visit us at www.singaporeair.com.
>
____________________________________________________________________________
__________
>
__________________________________________________
Do You Yahoo!?
Listen to your Yahoo! Mail messages from any phone. http://phone.yahoo.com
If you have a before job routine, or code in the job control area of the job that takes a while to run, then this can result in the job legitimately running but with nothing being logged.
If this is the case, then I recommend logging something with DSLogInfo as the first thing in the job control or the before job routine.
-----Original Message-----
From: Kenneth Bland [mailto:kcbland_2000@yahoo.com]
Sent: Monday, 1 October 2001 12:20 PM
To: datastage-users@oliver.com
Subject: Re: Batch Aborts
You need to be aware that the job message indicates
that the job is believed to be started, but there are
no indications that the job actually started.
I recommend SHRINKING this value, because what is
happening is the job is in LA-LA-LAND, and did not
respond to the job start command. I have only seen
this problem occur maybe 10 times since I started
working with DS 3.1. All of the occurrences for me
were on different platforms, UNIX and NT, different
versions of DS. I have never been able to reproduce
this issue.
My feeling is that if a job is issued the start
command using the BASIC APIs and it fails to start
within 5 minutes, then its the same as the job
failing. The sooner you know this the better.
Good luck!
-Ken
--- Saravanan_Thirugnanam@singaporeair.com.sg wrote:
>
> There is an option in DS Administrator to set
> Inactivity Timeout. Follow
> these steps to set Inactivity Timeout
>
> Go to DS Administrator.
> Set time for Inactivity in Inactivity Timeout
> box.
> Do not timeout option can also be selected.
>
> Once this option is set any job will not get aborted
> even it takes long
> time to complete.
>
> But you have to find out why this job takes long
> time.
>
> Hope this will help you.
>
>
>
>
>
> lhamilto@ncsh
>
> ealth.com To:
> datastage-users@oliver.com
> cc:
>
> 28-Sep-2001 Subject:
> Batch Aborts
> 06:48
>
> Please
>
> respond to
>
> datastage-use
>
> rs
>
>
>
> Sender Info:
>
> No Sender
>
> Info found in
>
> the address
>
> Book
>
>
>
>
>
>
>
>
>
>
>
> I have a several batch processes that abort with
> this message, however,
> none of the jobs seem to be affected.
> Any ideas as to why the jobs would not start
> periodically?
>
> Batch::DailyRejectPercent.JobControl (fatal error
> from DSRunJob): Job
> control fatal error (-14)
> (DSRunJob) Job DailyRejectPercentNCSHP7 has not
> logged any events since
> #7282, and
> appears not to have started after 1800 secs
>
---------------------------------------------------------
> The sender of this electronic message intends that
> this e-mail be used
> exclusively by the individual or entity to which it
> is intended to be
> addressed. This message may contain information
> that is privileged and
> confidential and thereby exempt and protected from unauthorized
> disclosure under applicable law. If the reader of this message
> is not the intended
> recipient, or an employee or agent responsible for
> delivering the message
> to the intended recipient, be aware that any
> disclosure, dissemination,
> distribution or copying of this communication, or
> the use of its contents,
> is not authorized and is strictly prohibited. If
> you have received this
> communication in error and are not the intended
> recipient, please notify
> the sender immediately and permanently
> delete the original message from your e-mail system.
>
>
>
>
>
>
____________________________________________________________________________
__________
>
> Visit us at www.singaporeair.com.
>
____________________________________________________________________________
__________
>
__________________________________________________
Do You Yahoo!?
Listen to your Yahoo! Mail messages from any phone. http://phone.yahoo.com