Page 1 of 2 1 2 LastLast
Results 1 to 10 of 11

Thread: How to get a Subsystem to produce an output

  1. #1
    Senior Member johndanter's Avatar
    Join Date
    Sep 2003
    Location
    Cork, Ireland
    Posts
    1,316

    How to get a Subsystem to produce an output

    Hi folks,

    I've just written a subsystem to help with our shipping info. All this is working fine except I now have no visibility of it's output.

    I see the record added to F986113, I see it then clear down, I can also see all the relevant database updates occurring in F4943 F4216 too. So I know it works, I just have no trace or CSV/PDF that this job ever executed.

    So how do I get get my subsystem to produce it's CSV each time? I need this as if there is an error I am reporting them in the CSV

    Thanks

    John
    John Danter
    You don't go out looking for a job dressed like that do you, on a weekday?

    E900 TR 9.1.5.3 Unix

  2. #2
    Member ONYX's Avatar
    Join Date
    Dec 2002
    Location
    Melbourne, AU
    Posts
    123
    Hi John,
    This might not be exactly relevant to what you are asking but have you thought about utilizing JDE Work Center?
    https://www.jdesource.com/enterprise...e-work-center/

    It is standard and very convenient way of communicating messages (errors, warnings) from UBEs and can be easily instrumented to expose those to Splunk/Grafana etc.
    Serg Kurian
    E1 9.2

  3. #3
    Senior Member johndanter's Avatar
    Join Date
    Sep 2003
    Location
    Cork, Ireland
    Posts
    1,316
    Hi Serg

    Yes I use this often, I love it. I meant the actual UBEs output. I email people if things go wrong and direct them to the job number but I'd like them to be able to see the PDF themselves.
    But I could always attach it to the email

  4. #4
    Member
    Join Date
    Oct 2001
    Location
    New Zealand
    Posts
    425
    Subsystems don't produce a PDF per trigger. Going from memory here ... the PDF only appears when you end the subsystem is ended and IIRC it will be the most recent triggered run of the job.

    If you want the PDF from each triggered event, I think could have your subsystem be a driver and do async launches of the PDF producing UBE (into a different queue if the subsystem queue is not multithreaded)
    Contract JD Edwards Development Consultant.
    EnterpriseOne Xe through 9.2. Windows/Unix/OS400. SQLServer/Oracle/DB2 for i.
    ER, C/C++, BI Publisher, SQL, DSI dcLink

  5. #5
    Senior Member johndanter's Avatar
    Join Date
    Sep 2003
    Location
    Cork, Ireland
    Posts
    1,316
    Thanks
    What me and CNC team seem to have spotted is this:

    If I launch the SBS and it has job number 7382370 then everytime, everytime you launch the SBS a file can be found in the print queue under the name

    R554216_RRD0001_7382370_PDF but.......

    The contents of this file gets overwritten each time. It's quite interesting. So I've ran this twice today and each time there is only one file in the servers print queue with this name.
    However the content changed each time

  6. #6
    Senior Member Larry_Jones's Avatar
    Join Date
    Nov 2000
    Location
    Spokane, WA, USA
    Posts
    3,186
    That's one of the reasons we don't use Sub-System Jobs here but instead have a Driver UBE that polls for Data (Event), if found submits child UBE otherwise sleeps 30 seconds and repeats.
    If we want to stop the driver we just insert a special STOP message into the table its monitoring.
    Larry Jones
    E1 9.1 - TR 9.1.5 on Win 2012 R2. Oracle DB 11.2.04
    Wintel, BI Publisher

    Migrating to JDE 9.2 (TR 9.2.2.4) and SQL Server 2016

  7. #7
    Senior Member
    Join Date
    Mar 2004
    Location
    Fort Worth, Texas
    Posts
    1,513
    Quote Originally Posted by Larry_Jones View Post
    That's one of the reasons we don't use Sub-System Jobs here but instead have a Driver UBE that polls for Data (Event), if found submits child UBE otherwise sleeps 30 seconds and repeats.
    If we want to stop the driver we just insert a special STOP message into the table its monitoring.
    You rolled your own sub system. 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?
    Brian Oster
    Application Development Manager
    E1: 9.0 (TR9.1.5.1) / 9.2 (TR9.2.2.2)
    JAS/BSSV: Weblogic 12.1.2 / Weblogic 12.2
    ES: Win2008 / Win2016
    DB: MSSQL 2014 / 2016
    WebDev Client: Win7Pro / Win10Pro

  8. #8
    Member ONYX's Avatar
    Join Date
    Dec 2002
    Location
    Melbourne, AU
    Posts
    123
    Quote Originally Posted by Larry_Jones View Post
    That's one of the reasons we don't use Sub-System Jobs here but instead have a Driver UBE that polls for Data (Event), if found submits child UBE otherwise sleeps 30 seconds and repeats.
    If we want to stop the driver we just insert a special STOP message into the table its monitoring.
    On one of the previous projects we used exactly the same approach, with several master UBEs (one per required schedule) and a bunch of child UBEs spawned from the master.
    It had been working like a charm for years, but eventually was completely phased out by the real-time BSSV integration.
    Serg Kurian
    E1 9.2

  9. #9
    Senior Member johndanter's Avatar
    Join Date
    Sep 2003
    Location
    Cork, Ireland
    Posts
    1,316
    Tell me more please Larry

  10. #10
    Senior Member Larry_Jones's Avatar
    Join Date
    Nov 2000
    Location
    Spokane, WA, USA
    Posts
    3,186
    Not much more to tell John. All UBE's are regular UBEs.
    The Driver UBE just doesn't end normally. Just loops reading a table that tells it what to do/process. Based on data/parameters read it can:
    - Process the data itself
    - Submit a child UBE passing parameters
    - End if Quit message read or you may hard code a time to stop processing (like 7am)
    If you need to do something with the Output created (email, etc) then the Child UBE is the way to go.

    The Driver UBE is normally launched via scheduled jobs at startup however we did create a simple application (normal JDE app) that can launch the driver ube or stop it gracefully under User control.
    Larry Jones
    E1 9.1 - TR 9.1.5 on Win 2012 R2. Oracle DB 11.2.04
    Wintel, BI Publisher

    Migrating to JDE 9.2 (TR 9.2.2.4) and SQL Server 2016

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.