Page 2 of 2 FirstFirst 1 2
Results 11 to 11 of 11

Thread: How to get a Subsystem to produce an output

  1. #11
    Join Date
    Jun 2001
    Colorful Colorado
    Quote Originally Posted by BOster View Post
    ... To be honest, with multi-threaded queues I never really understood the need for the default JDE sub-system anyway. Other than a guaranteed "slot" in the job queue what are the other advantages?

    Since subsystems init the EOne environment and load specs into RAM (even for child UBEs) via Metadata kernel only once, they have a much higher throughput for the very short jobs. Once the jobs get long enough that starting the environment/reading specs is a tiny fraction of the time, then you don't need subsystem.

    Also, since they process as data enters the F986113 as triggers, it can automate a lot of things. Although BSSV is another way of triggering a lot of things, as is using the AIS notification framework.
    Last edited by Segfault; 07-23-2018 at 02:37 PM.

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
The legal restrictions and terms of use applicable to this site are available here.
Use of this site signifies your agreement to the terms of use.
JDELIST is NOT affiliated with JD Edwards® & Company, Oracle or Peoplesoft. Contents of this site are neither endorsed nor approved by JD Edwards® & Company and, or Oracle.