Multi-step Job Execution in IPD

The job is clearly defined on the server and in my reference in the query call. However, I'm getting a [JOBNAME] NOT FOUND error. We recently upgraded to 10.

Are you trying to change the job parameters? or just execute it? If you're trying to change the parameters, I don't think that is possible since you can't update it on the AP150 screen online. If you're trying to execute it, then you should be using the webrun node to use the jobrun cgi. That should work. There are some other posts about newer methods of executing jobs as well that I hear are needed for newer versions of 10. I've been on 10 for a while so jobrun still works for me.

Sorry. Bad terminology. Update the parameters. Here's my S3 query below.

Here's my S3 query:

_PDL=TEST&_TKN=AP150&_EVT=CHG&_RTN=DATA&_LFN=ALL&_TDS=IGNORE&FC=C&ADDENDA-OPTION=N&CURRENCY-OPT=I&DISC-OPTION=N&JOB-DESCRIPTION=&JOB-NAME=&PAY-GROUP=&PAY-INV-IMMED=N&PAY-THRU-DATE=&PAYMENT-CODE=CHK&PAYMENT-DATE=&PRINT-VOUCHER=N&RECONCILE-ADV-EXP=N&REPORT-SEQ=N&SEL-CASH-CODE=&_STEPNBR=1&SPEC-HANDLING=N&UPDATE-OPTION=Y&USER-NAME=&VOUCHER-NBR-FLAG=N&_DELIM=%09&_OUT=XML&_EOT=TRUE

I didn't paste in the parameters for security purposes. Just wondering if the base query is accurate. Or, perhaps a simple learning of the strategy to submit a multi-step job (query updates) and webrun job executions. I wish I could submit a screen capture to show the progress..

The job has 3 steps. So, how do you define each step update in query nodes?

Hi there. Any thoughts folks?

Hi TimC,

I really don't have an answer to your question, but I am going to ask a question for you to consider. If you are using IPA to trigger this, why don't you separate it into three separate single-step jobs rather than one multi-step job? This would greatly simplify things within IPA even though it adds additional nodes.

Multi-step jobs are convenient for human users, but IPA doesn't care if it's one step or three.

Kelly

Hi Kelly,
That is a consideration and we'll be testing that. Was just wondering if it was possible to do and how to define update of parameters of each step.

I think the job has to be defined in Portal, not LID, in order for the Web Run to 'see' it.

My current issue is that the S3 query node that performs the update doesn't see the job name. As mundane as it sounds, the job absolutely exists and the JOB-NAME parameter matches that name. However, it's throwing an error saying that it's not found.

Here's the query. Parameter values left out for security reasons.

_PDL=TEST&_TKN=AP150&_EVT=CHG&_RTN=DATA&_LFN=ALL&_TDS=IGNORE&FC=C&ADDENDA-OPTION=N&CURRENCY-OPT=I&DISC-OPTION=N&JOB-DESCRIPTION=&JOB-NAME=&PAY-GROUP=&PAY-INV-IMMED=N&PAY-THRU-DATE=20170101&PAYMENT-CODE=CHK&PAYMENT-DATE=20170101&PRINT-VOUCHER=N&RECONCILE-ADV-EXP=N&REPORT-SEQ=N&SEL-CASH-CODE=&_STEPNBR=1&SPEC-HANDLING=N&UPDATE-OPTION=Y&USER-NAME=&VOUCHER-NBR-FLAG=N&_DELIM=%09&_OUT=XML&_EOT=TRUE

a job record is a job record.....there is no difference between a portal and LID job record

if you are in a windows system, remember that the user name must include the domain when you are setting the jobname in the query

yeah, if it is multistep, then the S3 query and S3 transaction node won't be able to interact with it. Essentially, unless you can open up the AP150 and inquire on this job, the S3 nodes won't be able to do anything with it. For multistep, you have to manage them either in the special form in Portal or on jobdef which the S3 nodes can't do.

Your best bet if you need to update parameters is to split it apart and run them as individual jobs, not multistep.

OK. The error that I'm getting is "JOB NAME $$$$$$ NOT FOUND", when it clearly exists. Even if we create it as a simple job type (single job). How does my query above look? I must be missing a parameter somewhere I suspect.....

That job is a multistep, not an AP150 job. If you try to inquire on AP150 with that user id and that job name, it will tell you it isn't found.

we have a service account that IPA is running as, and, I'm logged into IPD as that same user.

We tested this by creating a single step job and I received the same error.

i don't see jobname defined in the query.

here is a query that works:

_PDL=&_TKN=AP520&_EVT=CHG&_RTN=DATA&_LFN=ALL&_TDS=IGNORE&FC=C&BATCH-NUM=&JOB-DESCRIPTION=PATIENT REFUNDS INTERFACE&VENDOR-SEQUENCE=N&COMPANY=1000&JOB-NAME=AP520&USER-NAME=INFORBC\lawson&_DELIM=%09&_OUT=XML&_EOT=TRUE

note the domain name in the user name.....

my earlier attempt got weirded out......

_PDL=&_TKN=AP520&_EVT=CHG&_RTN=DATA&_LFN=ALL&_TDS=IGNORE&FC=C&BATCH-NUM=&JOB-DESCRIPTION=PATIENT REFUNDS INTERFACE&VENDOR-SEQUENCE=N&COMPANY=1000&JOB-NAME=AP520&USER-NAME=INFORBC\lawson&_DELIM=%09&_OUT=XML&_EOT=TRUE

"JOB 101EMP NOT FOUND". The job is owned by a service account and I am logged into IPD as that user and trying to run an S3 update node. Heres the output.

<_PDL>TEST<_TKN>AP150<_LFN>TRUE<_PRE>TRUE<_JOBTYPE>SIMPLEAP150 CSubmitReportsJob SchedPrint Mgr101EMP101EMPdomain\svcaccount000000000002101YN20170303N20170303NAP PaymentsNNo0101CSHCD0CHKNNIVENDRNN0Job 101EMP Not Found***001JOB-NAME

it appears that this website is dropping text enclosed in angle brackets. there are variable values for prodline and batchnumber in the "real" query

Ah.... I guess I have to escape out the brackets.
More to come....

OK. I hope this is better...

<_PDL>TEST<_TKN>AP150<_LFN>TRUE<_PRE>TRUE<_JOBTYPE>SIMPLEAP150 CSubmitReportsJob SchedPrint Mgr101EMP101EMPccmc\svclawfinbuser000000000002101YN20170303N20170303NAP PaymentsNNo0101CSHCD0CHKNNIVENDRNN0Job 101EMP Not Found***001JOB-NAME";

OK. It doesn't like the xml format... Here's the actual query:
_PDL=TEST&_TKN=AP150&_EVT=CHG&_RTN=DATA&_LFN=ALL&_TDS=IGNORE&FC=C&ADDENDA-OPTION=N&CURRENCY-OPT=I&DISC-OPTION=N&JOB-DESCRIPTION=101EMP&JOB-NAME=101EMP&PAY-GROUP=999&PAY-INV-IMMED=N&PAY-THRU-DATE=20170101&_JOBTYPE=MULTISTEP&&_STEPNBR=1&PAYMENT-CODE=CHK&PAYMENT-DATE=20170101&PRINT-VOUCHER=N&RECONCILE-ADV-EXP=N&REPORT-SEQ=N&SEL-CASH-CODE=999&SPEC-HANDLING=N&UPDATE-OPTION=Y&USER-NAME=domain\serviceuser&VOUCHER-NBR-FLAG=N&_DELIM=%09&_OUT=XML&_EOT=TRUE