RE: Running jobs on a separate core

There have been several threads about how to do this on Midrange L too.

I thought I posted a step by step with commands awhile back. If you need
help give me a shout off line.

--
Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects


-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Brian
Piotrowski
Sent: Thursday, May 22, 2014 12:01 PM
To: Midrange Systems Technical Discussion
Subject: RE: Running jobs on a separate core

Thanks, Steve.

I've made a few attempts at this in the past, but I didn't really have a
good guide to complete this process. This Wiki will sure help. Thanks for
the link!

/b;

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Steve
Landess
Sent: Thursday, May 22, 2014 10:15 AM
To: midrange-l@xxxxxxxxxxxx
Subject: Re: Running jobs on a separate core

Brian wrote:
In reviewing various documents a lot of them point to

creating a new subsystem and pushing the QZDASOINIT jobs onto
it<<<<<.

I guess it's something we'll have to investigate once the new box arrives.



Brian:

Isolating the QZDASONIT jobs to an "ODBC" subsystem with its own memory pool
is probably going to fix your problem.

Here are the instructions provided by Bryan Dietz for isolating QZDASOINIT
jobs:
http://wiki.midrange.com/index.php/QZDASOINIT

-sjl



--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe,
or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at http://archive.midrange.com/midrange-l.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe,
or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at http://archive.midrange.com/midrange-l.