CNC newbie question - AS400

Folks,

here's quick question to inquire if this is do-able..and if so... how ?

I am working on this AS/400 Xe install. The client is asking if there is a way to use a different subsystem other than QBATCH. They have a legacy software system that uses the same subsystem on the AS/400.

For example, under the QBATCH subsystem, I have QB7333 and PKGBUILD. Can the JDE related stuff be moved to another subsystem, that way, jobs from the other software won't get hung up.

What changes need to be made to OneWorld recognize a new subsystem..for example, I can call it QJDE etc..etc..


Any suggestions ? ?

Thanks a million
jr. cncadmin.

Here might be an answer,
JDE runs in JDEB7333 subsystem, we have JOBQs setup for departments that
the UBEs go to. Associate the JOBQs with a different subsystem. That might
work for you.



Jeremey Garcia
Greenville, SC, USA
Xe SP14; ES - AS/400; CO - AS/400; Deploy - NT Citrix - NT SP6; Report Distribution - Formscape;

It sounds like you are getting subsystems confused wuth jobqs. Yes you can
run JDE Applications in a different JOBQ and if that JOBQ is in a different
SUBSYSTEM then the jobs wil use the different subsystem.

The default for OW is to use jobq QB7333. Submitting jobs here will NOT
interfere with jobs running out of jobq QBATCH even if the two jobqs use
the same subsystem (also called QBATCH - go figure). The only way this
happens is if the MAX number of Subsystem jobs is less than the total
number of jobs the jobqs allow through.

ie: QBATCH1 = 1 job (single Threaded)
QBATCH2 = 2 jobs (dual threaded)
QB7333 = 1 job (single Threaded)

If the MAX Jobs allowed in Subsystem QBATCH is set to 3 then you have a
problem and you need to set it to 4 or higher (but watch out for memory
usage - this will let more jobs share the same memory pool).

Jobq maximums regulate what jobs can run side by side (multi-threaded)
Subsystem maximums regulate how many jobs can share the memory pool.

It sounds like your issue is at the subsystem level not the jobq level.
CHGSBSD should let you increase the max number of active subsystem jobs or
you can do this from WRKSYSSTS as well.

I hope this helps.

Regards,
Gerald.

What jobs do you want to run in this "other subsystem"? We just created another jobqueue in the subsystem QBATCH. If you are talking about business function builds (on the server)you need to change the JDE.INI file on your AS400. Change the "Qname=" to whatever jobqueue. If you are talking about UBE reports submitted to the server, change the JDE.INI "UBEqueue=" parameter on your workstation (or terminal server).

Yes, you can. Here are the steps (AS/400 specific, of course):

Use DSPSBSD QBATCH and take some print screens to refer to in the later
steps.
Create a new Subsystem. Use CRTSBSD to do this. You can call it QJDE
if you wish, but keep track of the LIB you put it in -- I suggest QGPL.
Check with your client.
Add a Routing Entry for the SBS. Use ADDRTGE to do this. Model this
after the QBATCH print screens. If you wish to create a new class for
this SBS, use CRTCLS to do this. You should be able to use the QBATCH
class.
Remove the Job Queue Entries from the QBATCH SBS. Use the RMVJOBQE
command to do this. Be careful to ONLY remove the JDE JOBQ entries, or
you might have an upset customer.
Add the Job Queue Entries to the QJDE SBS. Use the ADDJOBQE command to
do this. There is a Max Active field in this command. Be wary of this
and at first make this the same as it was setup in the QBATCH print
screens that you printed.
Start the new subsystem.

In reference to #6, the AS/400 has the ability to multi-thread the job
queues and define new ones very easily (be sure to add them to the correct
subsystem; the option on A98OWMNU will add them to QBATCH). There is an
entirely different debate on whether QB7333 should be multi-threaded (more
than 1 Max Active job). Please, check the archives for more information.
As with all things OneWorld, I recommend the conservative approach. That
is, keep QB7333 single-threaded and create a separate multi-threaded job
queue for multi-threaded jobs and move them when you know it is safe. Just
keep in mind the need to make sure it is associated with the correct SBS.

Also, a performance tuning note: Unless a separate pool is created for the
new SBS, it will still compete with QBATCH for resources. If a new pool is
created, then rescources will have to be "stolen" from other pools for the
new SBS. In either case, the end result might not be what you client
really wants.

Good luck!



Adam Clark
Corporate Information Services
Office: (626) 434-4275





cncadmin
<cncguy@hotmail To: [email protected]
.com> cc:
Sent by: Subject: CNC newbie question - AS400
owner-jdelist@j
delist.com


08/06/2002
12:12 PM
Please respond
to jdelist






Folks,

here's quick question to inquire if this is do-able..and if so... how ?

I am working on this AS/400 Xe install. The client is asking if there is a
way to use a different subsystem other than QBATCH. They have a legacy
software system that uses the same subsystem on the AS/400.

For example, under the QBATCH subsystem, I have QB7333 and PKGBUILD. Can
the JDE related stuff be moved to another subsystem, that way, jobs from
the other software won't get hung up.

What changes need to be made to OneWorld recognize a new subsystem..for
example, I can call it QJDE etc..etc..


Any suggestions ? ?

Thanks a million
jr. cncadmin.
--------------------------
To view this thread, go to:
http://www.jdelist.com/ubb/showthreaded.php?Cat=&Board=OW&Number=39262
+ - - - - - - - - - - - - - - - - - - - - - - - -+
This is the JDEList One World® / XE mailing list/forum.
Archives and information on how to SUBSCRIBE, and
UNSUBSCRIBE can be found on the JDEList Forum at
http://www.JDEList.com

JDEList is not affiliated with JDEdwards®

+ - - - - - - - - - - - - - - - - - - - - - - - -+






Adam Clark
Project Manager
Golden State Foods

B7331 -- NT/SQL 7.0 -- SP14.2 & SP15.1
Xe -- AS/400 V4R5 & V5R1 -- SP18.1_D1

Hi JR,

Change the JDE and ONEWORLD user profile/ job description on the AS/400 to default to another batch queue other than QBATCH. To test to see if it works, build an update package with one business function and see were it compiles.