Previous Thread
Next Thread
Print Thread
Linux: ashell job count #36241 09 Jun 23 03:53 PM
Joined: Sep 2002
Posts: 5,450
F
Frank Online Content OP
Member
OP Online Content
Member
F
Joined: Sep 2002
Posts: 5,450
Good day -

I have a background task that i have labeled "PSH001" (see below). It is being counted in the current licensed job count. I thought that background tasks were exempt. I am wondering if its because of how i have assigned the job name. Please advise how to keep background tasks from being counted. TIA.

.about
A-Shell/Linux Version 6.4.1547.0
Release Date: 17-Mar-2017
Licensed to: XXXXXXXXX
Serial # XXXX
A-Shell Key: XXXXXXXXXXXXXXX
Nodes Licensed: 6
Nodes / Jobs in Use: 6 / 6
License Options: POLY ATE ATS APEX
Maintenance Expiration: 31-Aug-2028
INI File: XXXXXXXX
ATE Licensing: Server
Nodes Licensed: All
JOBTBL.SYS File:
Spec: XXXXXXXXXX
Inode: 11051012
Created: 9-Jun-23 11:47

.systat/n
Status of A-Shell Version 6.4.1547.0 on Friday, June 09, 2023 11:51:51
TSKAAA TSKAAA xxxxx DSK1:50,1 RN SCHED2 62798 9686K
TSKAAB TSKAAB xxxxx DSK1:50,1 RN SCHED2 61023 10M
TSKAAC TSKAAC xxxxx DSK1:50,1 RN SYSTAT 63212 6487K
PSH001 PSH001 xxxxx DSK1:50,1 RN PSHOT 96108 6348K
TSKAAF TSKAAF xxxxx DSK1:50,1 RN SCHED2 58060 9089K
TSKAAI TSKAAI xxxxx DSK1:50,1 RN SCHED2 58969 11M
6 jobs allocated on system, 6 in use
Total memory on system: 7994320 kB
Sys Up: 11:51:51 up 246 days, 22:42, 31 users, load average: 0.07, 0.03, 0.0

Re: Linux: ashell job count [Re: Frank] #36243 09 Jun 23 04:56 PM
Joined: Jun 2001
Posts: 11,645
J
Jack McGregor Online Content
Member
Online Content
Member
J
Joined: Jun 2001
Posts: 11,645
The general principle is to allocate a license to each client entity. Typically that entity is the workstation. So if you make two ATE connections from the same workstation, they will normally share one license. The client entity for background jobs is typically the server, so in principle all background jobs share a license between them. So in other words, the first background job uses a license; beyond that, additional background jobs would share the same license.

There are some other limits and exceptions. For example, CGI sessions do not get to share licenses. And on a system with N licenses, the maximum number of jobs sharing any individual license would be N. But I think the main issue in your case is just that the first background job uses up a license.

One can debate about whether that's fair, or what the fairest method would be. Minutes connected? CPU cycles? Keystrokes? Screen updates? File I/O? End-user revenue? (Be prepared for a long discussion!)

As an aside, SYSTAT has /LIC switch which indicates which jobs have licenses assigned to them. But note that the assignment is dynamic. For example, your first connection will get a license assigned. Your second connection will not (i.e. it will share the first connection's license.) But if you then disconnect from the first connection, the license will jump to the second connection.

Re: Linux: ashell job count [Re: Frank] #36244 09 Jun 23 06:09 PM
Joined: Sep 2002
Posts: 5,450
F
Frank Online Content OP
Member
OP Online Content
Member
F
Joined: Sep 2002
Posts: 5,450
Thanks for the reply.

I recall now that all background tasks occupy 1 license.


Moderated by  Jack McGregor, Ty Griffin 

Powered by UBB.threads™ PHP Forum Software 7.7.3