GEN productline query in ProcessFlow

 4 Replies
 0 Subscribed to this topic
 27 Subscribed to this forum
Sort:
Author
Messages
Shane Jones
Veteran Member
Posts: 460
Veteran Member
    I was told that I could use processflow to query the Job Queue to determine when a job is complete, needs recovery or still active?

    However, the GEN productline is not available and the table(file) named QUEUEDJOB is not available in the processflow query builder? I know that someone is doing this an I am trying to find out how to make this file show up when creating a query in processflow.

    Anyone know how to make GEN tables(files) show up when creating a query????
    Shane Jones
    Tools: HR, Payroll, Benefits, PFI, Smart Office, BSI, Portal and Self-Service
    Systems: Lawson, Open Hire, Kronos, Crystal Reporting, SumTotal Learning
    ** Teach others to fish...
    Shane Jones
    Veteran Member
    Posts: 460
    Veteran Member
      Okay...

      I just made it work:
      PROD=GEN&FILE=QUEUEDJOB&FIELD=STATUS;JOBNAME;USERNAME&OUT=CSV&DELIM=~

      I just need to determine the criteria for the pull.... and the various nodes.

      This might be a good topic for tips and tricks. With an AGS, JOBRUN, AGS, BRANCH, EMAILS a processflow could be run to update a job like PA100, run the job, verify when done... and email someone. A more advanced use would be to loop the query on QUEUEDJOB until the job is complete and then run another job that relies on the completion of the first job...

      (Does anyone know where I can get a list of the fields in the QUEUEDJOB table?)

      Shane Jones
      Tools: HR, Payroll, Benefits, PFI, Smart Office, BSI, Portal and Self-Service
      Systems: Lawson, Open Hire, Kronos, Crystal Reporting, SumTotal Learning
      ** Teach others to fish...
      Phillip Feller
      Basic Member
      Posts: 12
      Basic Member
        Hi Shane,

        The command 'dbdesc gen queuedjob' will give you a list of the fields, and cryptic information about each of them. The command 'prtdict gen queuedjob' will give you more information about how QUEUEDJOB is defined in the data dictionary, but it is not particularly easy to parse. I wrote a Java progam to read a Lawson data dictionary, so that I could get GEN information in a more readily understanable format. For QUEUEDJOB, it shows:

        QUEUEDJOB

        FIELD NAME DESCRIPTION

        JobNumber ALPHA 10

        UserName ALPHALC 10

        JobName ALPHA 10

        JobQueue ALPHA 10

        Status BINARY 1

        Type BINARY 1

        SeqNumber NUMERIC 5

        RstStepNbr NUMERIC 5

        StartDate YYYYMMDD 8

        StartTime TIME 6

        ActStartDate YYYYMMDD 8

        ActStartTime TIME 6

        StopDate YYYYMMDD 8

        StopTime TIME 6

        ProductLine ALPHA 14

        Token ALPHALC 10

        Filler2 ALPHA 2

        ProcessId BINARY 4

        UserId BINARY 4

        MachineName ALPHALC 10

        QUEUEDJOB FILE INDEX

        NAME KEY FIELDS DESCRIPTION / SUBSET CONDITION

        QJBSET1 JobNumber keyChange

        QJBSET10 StopDate* keyChange, Subset (COMPLETED)
        StopTime* Where Status >= 060+
        UserName AND Status <= 089+
        JobName
        JobNumber

        QJBSET2 Status keyChange
        JobNumber

        QJBSET3 Status keyChange
        JobQueue
        SeqNumber
        JobNumber

        QJBSET4 JobQueue keyChange
        Status
        SeqNumber
        JobNumber

        QJBSET5 ProductLine keyChange
        Token
        Status
        JobNumber

        QJBSET6 UserName keyChange, Subset (ACTIVE)
        ActStartDate Where Status >=
        ActStartTime AND Status <= 029+
        JobName
        JobNumber

        QJBSET7 JobQueue keyChange, Subset (ACTIVE)
        ActStartDate Where Status >=
        ActStartTime AND Status <= 029+
        UserName
        JobNumber

        QJBSET8 UserName keyChange, Subset (WAITING)
        ActStartDate Where Status >= 030+
        ActStartTime AND Status <= 059+
        JobName
        JobNumber

        QJBSET9 JobQueue keyChange, Subset (WAITING)
        ActStartDate Where Status >= 030+
        ActStartTime AND Status <= 059+
        UserName
        JobNumber

        QJBSET911 UserName keyChange
        JobName
        Status
        JobNumber

        QJBSET912 UserName keyChange, Subset (COMPLETED)
        StopDate* Where Status >= 060+
        StopTime* AND Status <= 089+
        JobName
        JobNumber
        Sanford Barton
        Basic Member
        Posts: 10
        Basic Member
          I wouldn't use processflow for batch monitoring if it's terribly critical. I ended up writting my own batch monitor and paging system. Be happy to share it with anyone who would like it. Must be on UNIX/Oracle to work as I wrote it in oratcl. Also requires it's own Oracle tablespace to store info about users, jobs, etc. Uses sendmail to page but could use pretty much anything you like.
          Greg Moeller
          Veteran Member
          Posts: 1498
          Veteran Member
            Sanford: I'd be interested in what you have got written.
            Contact me at moellerg@genesishealth.com or here.