I have been testing a new workstation using an Intel Xeon dual-processor.
If I manually ran 2 jobs Simultaneously via a DOS prompt,
each job takes the full processing power of a processor each.
If however, I run the same 2 jobs via the scheduler,
they only use one processor and try to share its resouces between them.
Any idea why and how I can ensure that each job uses a single processor.
Each job has its own JAL script, both waiting for a certain file.
The actual executable is run using the RunAndWait command.
We are using the latest version 3.4.7 on a Windows 2000 platform.

Many thanks,

Lionel

You can use BindCPU utility available in the "Tips and Script Archive" to bind jobs to different CPUs.

Visit http://www.softtreetech.com/24x7/script.htm

: I have been testing a new workstation using an Intel Xeon dual-processor.
: If I manually ran 2 jobs Simultaneously via a DOS prompt,
: each job takes the full processing power of a processor each.
: If however, I run the same 2 jobs via the scheduler,
: they only use one processor and try to share its resouces between them.
: Any idea why and how I can ensure that each job uses a single processor.
: Each job has its own JAL script, both waiting for a certain file.
: The actual executable is run using the RunAndWait command.
: We are using the latest version 3.4.7 on a Windows 2000 platform.

: Many thanks,

: Lionel

Thanks for the speedy response, testing now, looking good.

: You can use BindCPU utility available in the "Tips and Script
: Archive" to bind jobs to different CPUs.

: Visit http://www.softtreetech.com/24x7/script.htm

It seems we have solved one problem, but created another.
This worked fine, in that I managed to run 2 jobs using different processors.
But using the RunAndWait command, it runs the job, but does not wait for completion,
it simply moves on to the next line of code although the job is still running.
Has this got anything to do with using the BindCPU command?

: Thanks for the speedy response, testing now, looking good.

Please provide the complete code for RunAndWait.

: It seems we have solved one problem, but created another.
: This worked fine, in that I managed to run 2 jobs using different processors.
: But using the RunAndWait command, it runs the job, but does not wait for
: completion,
: it simply moves on to the next line of code although the job is still
: running.
: Has this got anything to do with using the BindCPU command?

It looks like the RunAndWait command initiates a call of BindCPU,
which inturn calls my .bat file.
Therefore once the BindCPU has done its job it moves on to the next line.

The batch file CreateClient.bat looks like this:
%1 is the Date yyyymmdd, %2 is the log file

..\Converters\DB2Conv.exe ..\ClientParams\%1 %2 ..\cfg >> ..\joblog\%1.log

Sample taken from my .JAL script:

Dim BatchFile, string "BindCPU 1 CreateClient.bat StandEVENTSC.cli "
Dim DirMAINlog, String
Dim FnameLog, string "StandEVENTSC.cli.log"
Dim CreateSpots, String
Dim ClientFrom, String
Dim not_found, boolean
.....................
......................
// Build Run Command using date
ConCat ( BatchFile, ConsDate, CreateSpots)
// Run batch job
RunAndWait (CreateSpots, "" , 0 , process_id )
// Check Output files exist & zip them
NotFileExists ( ClientFrom, not_found )
IfThen ( not_found, No_Zip1 )
.....................
.......................
: Please provide the complete code for RunAndWait.

Please try moving BindCPU into the batch file to run DB2Conv.exe rather then using it to run the entire batch.

: It looks like the RunAndWait command initiates a call of BindCPU,
: which inturn calls my .bat file.
: Therefore once the BindCPU has done its job it moves on to the next line.

: The batch file CreateClient.bat looks like this: %1 is the Date yyyymmdd, %2
: is the log file

: ..\Converters\DB2Conv.exe ..\ClientParams\%1 %2 ..\cfg >>
: ..\joblog\%1.log

: Sample taken from my .JAL script: Dim BatchFile, string "BindCPU 1
: CreateClient.bat StandEVENTSC.cli "
: Dim DirMAINlog, String
: Dim FnameLog, string "StandEVENTSC.cli.log"
: Dim CreateSpots, String
: Dim ClientFrom, String
: Dim not_found, boolean
: .....................
: ......................
: // Build Run Command using date
: ConCat ( BatchFile, ConsDate, CreateSpots)
: // Run batch job
: RunAndWait (CreateSpots, "" , 0 , process_id )
: // Check Output files exist & zip them
: NotFileExists ( ClientFrom, not_found )
: IfThen ( not_found, No_Zip1 )
: .....................
: .......................

The problem still remains, although the jobs were successfully split between the processors, RunAndWait thinks that once BindCPU has made its call, the job has completed.
The actual run of Db2conv takes approx 1.5 hours to run, but I put
a messagebox after the RunAndWait, and this is called almost immediately.

: Please try moving BindCPU into the batch file to run DB2Conv.exe rather then
: using it to run the entire batch.

Please use the modified version of BindCPUw which will wait for launched process to complete before returning control back to the system.

Here is the download link
http://www.softtreetech.com/24x7/extras/BindCPUw.exe

: The problem still remains, although the jobs were successfully split between
: the processors, RunAndWait thinks that once BindCPU has made its call, the
: job has completed.
: The actual run of Db2conv takes approx 1.5 hours to run, but I put
: a messagebox after the RunAndWait, and this is called almost immediately.

I've run a quick test and so far it all looks really promising.
Thanks for the solution and quick response,
Much appreciated.

: Please use the modified version of BindCPUw which will wait for launched
: process to complete before returning control back to the system.

: Here is the download link
: http://www.softtreetech.com/24x7/extras/BindCPUw.exe