Scheduler Issue

[CKilgore]

I have several scheduler jobs that are aborting.  The issue has just started in the last 24 hours and only affects jobs that were submitted or modified by a particular user.

The PH file shows:

Code: [Select]

cat SCHED26753_22348018
COMMAND IS SCHEDULER.BRAKE.846
À20À4ÀÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿À1-3ÀÀ20À5À³À279À5À³À20À6À³À279À6À³À20À7À³À279À7À³À20À8À³À279À8À³À20À9À³À279À9À³À20À10À³À279À10À³À20À11À³À279À11À³À20À12À³À279À12À³À20À13À³À279À13À³À20À14À³À279À14À³À20À15À³À279À15À³À20À16À³À279À16À³À20À17À³À279À17À³À20À18À³À279À18À³À20À19À³À279À19À³À20À20À³À279À20À³À20À21ÀÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙÀ222À4ÀAccounts Payable Discrepancy InquirypÀ241À6ÀDisc/DueÀ22À5ÀBuyerÀ22À6ÀReceiverÀ214À6ÀVendorÀ221À6ÀInvoice NumberÀ253À6ÀMerch AmtÀ267À6ÀAPPO AmtÀ276À6ÀFrt0À20À23À4F2-Finish F5-AP/PO Entry F6-Buyer Hold Notes F8-Log F9-Goto Line F10-Action À1-4À000À28À5ÀÀ28À5À### À211À5À À28À5À### À213À5À###########                   À22À7À10193841-2 À214À7À104373À214À8À######################### À221À7ÀD553110            À250À7À       77.32À263À7À       71.62À276À7ÀYÀ241À7À01/17/12À241À8À02/16/12À22À9À           À214À9À      À214À10À                          À221À9À                   À250À9À            À263À9À            À276À9À À241À9À        À241À10À        À22À21À1/1À213À5À###########                   À22À7À10193841-2_ À22À7ÀIn /usr/udthome/sys/CTLG/X/_SB543_SB.INPUT at line 459 Phantom require input.
In /usr/udthome/sys/CTLG/c/CHECK.PHANTOM at line 481 Phantom run basic error, exit 1.
PHANTOM process 22348018 has completed.

Any idea what could be causing this?  I have additional auditing in SCHEDULE.RUNNER and RUNNER.  The processes that abort are not making it to auditing in RUNNER.  At this point I'm at a loss for what to check.

[Colin Alfke]

It looks like it's ending up in a screen that requires input and has none to give it. UniData will abort the process when this condition occurs as the alternative is to hang there.

You'll have to look at what's being scheduled.

hth
Colin

[CKilgore]

But I can't figure out how it is ending up at that screen.  The jobs are reports and if I schedule the report it works just fine but if this user schedules or modifies the same report, it aborts.

[Tom Pellitieri]

Which user is listed in the scheduler for this job?  Is that user authorized to use the screen?  For example, even though I'm in the ROOT group for SB+, I'm not listed as a Buyer in /USER.ID.MNT, so I can't access the A/P Discrepancy Inquiry screen.

[CKilgore]

Kevin was able to find the problem.  At some point years ago, we had a modification done for buyers.  If they have a buyer hold, the system automatically brings up the A/P Discrepancy Inquiry screen when they log in.  Our IT department has recently started handling our own purchasing so that caused this user to get a buyer hold and kill the phantom jobs.