Sybase NNTP forums - End Of Life (EOL)

The NNTP forums from Sybase - forums.sybase.com - are now closed.

All new questions should be directed to the appropriate forum at the SAP Community Network (SCN).

Individual products have links to the respective forums on SCN, or you can go to SCN and search for your product in the search box (upper right corner) to find your specific developer center.

Why 8 connections for Job Schedule

3 posts in General Discussion Last posting was on 2010-03-01 06:42:48.0Z
Yaniv C. Posted on 2010-02-28 17:24:35.0Z
Sender: 77de.4b84ebfc.1804289383@sybase.com
From: Yaniv C.
Newsgroups: sybase.public.ase.general
Subject: Why 8 connections for Job Schedule
X-Mailer: WebNews to Mail Gateway v1.1t
Message-ID: <4b8aa6d3.7578.1681692777@sybase.com>
NNTP-Posting-Host: 10.22.241.41
X-Original-NNTP-Posting-Host: 10.22.241.41
Date: 28 Feb 2010 09:24:35 -0800
X-Trace: forums-1-dub 1267377875 10.22.241.41 (28 Feb 2010 09:24:35 -0800)
X-Original-Trace: 28 Feb 2010 09:24:35 -0800, 10.22.241.41
Lines: 76
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.ase.general:29007
Article PK: 78247

Hi
I am using ASE 15.0.2ESD 6 on Linux and using job schedule.
- Why Job schedule uses 8 connections as I can see in
sp_who?
- Can the number of connections be configured?
- Why 8 and not 2 or 4 or 40?

Here is output of sp_who:

1> sp_who
2> go | grep jstask
0 13 recv sleep
jstask jstask
NULL 0
sybmgmtdb
tempdb AWAITING
COMMAND
0
0 20 recv sleep
jstask jstask
NULL 0
sybmgmtdb
tempdb AWAITING
COMMAND
0
0 21 recv sleep
jstask jstask
NULL 0
sybmgmtdb
tempdb AWAITING
COMMAND
0
0 52 recv sleep
jstask jstask
NULL 0
sybmgmtdb
tempdb AWAITING
COMMAND
0
0 53 recv sleep
jstask jstask
NULL 0
sybmgmtdb
tempdb AWAITING
COMMAND
0
0 103 recv sleep
jstask jstask
NULL 0
sybmgmtdb
tempdb AWAITING
COMMAND
0
0 154 recv sleep
jstask jstask
NULL 0
sybmgmtdb
tempdb AWAITING
COMMAND
0
0 205 recv sleep
jstask jstask
NULL 0
sybmgmtdb
tempdb AWAITING
COMMAND
0


1> sp_who
2> go | grep jstask | wc -l
8


Thanks,
Yaniv


"Mark A. Parsons" <iron_horse Posted on 2010-02-28 18:22:02.0Z
From: "Mark A. Parsons" <iron_horse@no_spamola.compuserve.com>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
MIME-Version: 1.0
Newsgroups: sybase.public.ase.general
Subject: Re: Why 8 connections for Job Schedule
References: <4b8aa6d3.7578.1681692777@sybase.com>
In-Reply-To: <4b8aa6d3.7578.1681692777@sybase.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Antivirus: avast! (VPS 100227-0, 02/27/2010), Outbound message
X-Antivirus-Status: Clean
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <4b8ab44a$1@forums-1-dub>
Date: 28 Feb 2010 10:22:02 -0800
X-Trace: forums-1-dub 1267381322 10.22.241.152 (28 Feb 2010 10:22:02 -0800)
X-Original-Trace: 28 Feb 2010 10:22:02 -0800, vip152.sybase.com
Lines: 93
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.ase.general:29008
Article PK: 78245

From solved cases @ sybase.com:

================================
Why are 8 tasks started when Adaptive Server Enterprise (ASE) starts?

Resolution

The behaviour is normal and by default when starting the job scheduler, 8 jstasks will be started. These are hardcoded
system tasks and they cannot be configured.

The New Feature Request CR#451546 is open. Its description reads, "Job scheduler: New Feature Request for to be able to
configure the number of JS Tasks.". The implemenataton release for CR#451546 is not available at this point.

Resolutions: feature request
================================

Yaniv C. wrote:
> Hi
> I am using ASE 15.0.2ESD 6 on Linux and using job schedule.
> - Why Job schedule uses 8 connections as I can see in
> sp_who?
> - Can the number of connections be configured?
> - Why 8 and not 2 or 4 or 40?
>
> Here is output of sp_who:
>
> 1> sp_who
> 2> go | grep jstask
> 0 13 recv sleep
> jstask jstask
> NULL 0
> sybmgmtdb
> tempdb AWAITING
> COMMAND
> 0
> 0 20 recv sleep
> jstask jstask
> NULL 0
> sybmgmtdb
> tempdb AWAITING
> COMMAND
> 0
> 0 21 recv sleep
> jstask jstask
> NULL 0
> sybmgmtdb
> tempdb AWAITING
> COMMAND
> 0
> 0 52 recv sleep
> jstask jstask
> NULL 0
> sybmgmtdb
> tempdb AWAITING
> COMMAND
> 0
> 0 53 recv sleep
> jstask jstask
> NULL 0
> sybmgmtdb
> tempdb AWAITING
> COMMAND
> 0
> 0 103 recv sleep
> jstask jstask
> NULL 0
> sybmgmtdb
> tempdb AWAITING
> COMMAND
> 0
> 0 154 recv sleep
> jstask jstask
> NULL 0
> sybmgmtdb
> tempdb AWAITING
> COMMAND
> 0
> 0 205 recv sleep
> jstask jstask
> NULL 0
> sybmgmtdb
> tempdb AWAITING
> COMMAND
> 0
>
>
> 1> sp_who
> 2> go | grep jstask | wc -l
> 8
>
>
> Thanks,
> Yaniv


Yaniv C. Posted on 2010-03-01 06:42:48.0Z
Sender: 77de.4b84ebfc.1804289383@sybase.com
From: Yaniv C.
Newsgroups: sybase.public.ase.general
Subject: Re: Why 8 connections for Job Schedule
X-Mailer: WebNews to Mail Gateway v1.1t
Message-ID: <4b8b61e8.d0e.1681692777@sybase.com>
References: <4b8ab44a$1@forums-1-dub>
NNTP-Posting-Host: 10.22.241.41
X-Original-NNTP-Posting-Host: 10.22.241.41
Date: 28 Feb 2010 22:42:48 -0800
X-Trace: forums-1-dub 1267425768 10.22.241.41 (28 Feb 2010 22:42:48 -0800)
X-Original-Trace: 28 Feb 2010 22:42:48 -0800, 10.22.241.41
Lines: 104
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.ase.general:29010
Article PK: 78248

Thanks


Yaniv

> From solved cases @ sybase.com:
>
> ================================
> Why are 8 tasks started when Adaptive Server Enterprise
> (ASE) starts?
>
> Resolution
>
> The behaviour is normal and by default when starting the
> job scheduler, 8 jstasks will be started. These are
> hardcoded system tasks and they cannot be configured.
>
> The New Feature Request CR#451546 is open. Its description
> reads, "Job scheduler: New Feature Request for to be able
> to configure the number of JS Tasks.". The implemenataton
> release for CR#451546 is not available at this point.
>
> Resolutions: feature request
> ================================
>
> Yaniv C. wrote:
> > Hi
> > I am using ASE 15.0.2ESD 6 on Linux and using job
> > schedule. - Why Job schedule uses 8 connections as I can
> > see in sp_who?
> > - Can the number of connections be configured?
> > - Why 8 and not 2 or 4 or 40?
> >
> > Here is output of sp_who:
> >
> > 1> sp_who
> > 2> go | grep jstask
> > 0 13 recv sleep
> > jstask jstask
> > NULL
> > 0 sybmgmtdb
> > tempdb
> > AWAITING COMMAND
> > 0
> > 0 20 recv sleep
> > jstask jstask
> > NULL
> > 0 sybmgmtdb
> > tempdb
> > AWAITING COMMAND
> > 0
> > 0 21 recv sleep
> > jstask jstask
> > NULL
> > 0 sybmgmtdb
> > tempdb
> > AWAITING COMMAND
> > 0
> > 0 52 recv sleep
> > jstask jstask
> > NULL
> > 0 sybmgmtdb
> > tempdb
> > AWAITING COMMAND
> > 0
> > 0 53 recv sleep
> > jstask jstask
> > NULL
> > 0 sybmgmtdb
> > tempdb
> > AWAITING COMMAND
> > 0
> > 0 103 recv sleep
> > jstask jstask
> > NULL
> > 0 sybmgmtdb
> > tempdb
> > AWAITING COMMAND
> > 0
> > 0 154 recv sleep
> > jstask jstask
> > NULL
> > 0 sybmgmtdb
> > tempdb
> > AWAITING COMMAND
> > 0
> > 0 205 recv sleep
> > jstask jstask
> > NULL
> > 0 sybmgmtdb
> > tempdb
> > AWAITING COMMAND
> > 0
> >
> >
> > 1> sp_who
> > 2> go | grep jstask | wc -l
> > 8
> >
> >
> > Thanks,
> > Yaniv