Queued Jobs flow

Sort:
You are not authorized to post a reply.
Author
Messages
TBonney
Veteran Member
Posts: 277
Veteran Member
    I am trying to set up a flow to generate an email to advise of the jobs in needs recovery status by doing a rngdbdump, like the one referenced in the "Tips & Tricks" section.

    Has anyone done this as suggested by John?

    If so, please advise which nodes I would use and how I woudl write the command syntax to be executed. The article John provides in Tips & Tricks suggest a great usage of process flow. However, unfortunately, my lack of familiarity and experience with P-Flow renders the details provided in the article lacking.

    Thanks for any advice you can provide!

    (We're on 9.0.0.7 environment & apps, Windows platform, use 9.0 Security and Process Flow Integrator.)
    David Williams
    Veteran Member
    Posts: 1127
    Veteran Member
      You can create a flow that queries the QUEUEDJOB table in the GEN productline for the status codes you want.

      // PROD=GEN&FILE=QUEUEDJOB&FIELD=JOBNAME;USERNAME;STATUS;STOPDATE&SELECT=STATUS=34%7CSTATUS=35&OUT=CSV&DELIM=~

      Then have your flow send an email to the email address associated to the user name (ResourceQuery to get email out of Lawson Security set up).
      David Williams
      TBonney
      Veteran Member
      Posts: 277
      Veteran Member
        Thanks David.

        When I try to build my query and select the GEn database, it shows 4 tables, but none of them is the QUEUEDJOB table and none of them display any fields when I choose them. (They are CS, IS, LA and UN.)

        So I copied your text above and tried it with that, but for some reason, in spite of the criteria limiting it to status 33 & 34, I am getting status 63 (completed) jobs in my return results. Any ideas why this might be?
        David Williams
        Veteran Member
        Posts: 1127
        Veteran Member
          Off the top of my head, no. Can you send me your flow and I'll look at it?
          David@ConsutlDavidW.com
          David Williams
          TBonney
          Veteran Member
          Posts: 277
          Veteran Member
            Thanks David.

            I appreciate your willingness to look at this for me. Attached is the version of the flow that I run on our test server, which still returns statuses other than those defined in the query node.

            I am also attaching one of the output files (for status 34 query) so you can see that statuses other than the one indicated within the flow itself are included in the output that is built (33 and 63) .

            Thank you for any light you can shed. I appreciate it!
            Attachments
            David Williams
            Veteran Member
            Posts: 1127
            Veteran Member
              This is going to seem crazy but change your select criteria to:

              &SELECT=PRODUCTLINE=DEV%26STATUS=31 instead of using the & symbol
              David Williams
              David Williams
              Veteran Member
              Posts: 1127
              Veteran Member
                You should also be able to reference the // <!appProdline> variable instead of hard coding DEV
                David Williams
                You are not authorized to post a reply.