Results 1 to 4 of 4

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,288

    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
    119
    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,288
    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
    416
    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

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.