RE: starting other subsystems when STRSBS QCTL -- MIDRANGE-L

With all due respect to Charly, I think that QBASE somehow gets them into
the correct pool, although I have no systems available for a test.  To
further that thought, the system value QTSEPOOL was added in V1R3 so that
S/36 batch type work, which was being run interactively, would be moved to
the batch (base) pool.

If anyone thinks, I'm wrong, please free to pipe up and dissent.

Al

Al Barsa, Jr.
Barsa Consulting Group, LLC

400>390

914-251-1234
914-251-9406 fax

http://www.barsaconsulting.com
http://www.taatool.com






                    "Charly Jones"
                    <charly301@hotmail.       To:     midrange-l@midrange.com
                    com>                      cc:
                    Sent by:                  Subject:     RE: starting other 
subsystems when STRSBS QCTL
                    midrange-l-admin@mi
                    drange.com


                    10/28/01 12:01 PM
                    Please respond to
                    midrange-l







"but it goes back to System/38 days"

If I remember correctly, QBASE was invented for the AS/400 S/36
"ease-of-use" customers.  The S/38 always used QCTL.

And if you care about performance, you will too.  The important thing is
not
which subsystem a job runs in, but what memory pool it runs in and what
other jobs are in the pool with it.  Just like you probably don't want to
spend lots of time in a swimming pool with a lot of babies, you probably
don't want your performance critical jobs running in a memory pool with
compiles, sorts, index builds, or any other badly behaving jobs...

The best default ocnfiguration is the one provided by
QCTL/QINTER/QBATCH/QSPL.  If you want the best performance you will
probably
want to add memory pools (and subsystems that refer to them).

Charly

----------------------------
Sanders Sauls for President!

For their next act, they'll no doubt be buying a firewall running under NT,
which makes about as much sense as building a prison out of meringue.  --
Tanuki

Charly Jones
253 851-9876
Gig Harbor Washington




>From: "Reeve Fritchman"
>
>It's always been QBASE.  That's not much of a rationalization, but it goes
>back to System/38 days.  There was a time when adding/removing devices
from
>interactive subsystems couldn't be done if the subsystem was active.  It's
>likely IBM set it up this way to give users the opportunity to tweak
QINTER
>and QCTL during the first few IMPL's.
>
>-----Original Message-----
>On Behalf Of William Corbett
>
>Dan,
>Just so happens I'm working on a similar problem for a client.  They're
>starting up in QBASE, I'm changing it to QCTL (as I believe it should be)
>If you'll look at the default QSYS/QSTRUP you'll see an IF statement which
>starts up some subsystems IF the controlling subsystem is QCTL.
>Ships with QBASE as the controlling subsystem, I've been changing it to
>QCTL
>since V3.
>I do not know why it ships as QBASE?????
>



_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp

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