WRKJOBSCDE submission warning

[Newbie_Neil]

Hi all,

I encountered a real nasty with WRKJOBSCDE yesterday.

We were running some scheduled testing and user TESTA scheduled the
jobs. His current data library was TESTLIB.

Then the user went into WRKJOBSCDE, using his live profile with a
current data library of LIVELIB, and entered a 10 to submit one of the
scheduled jobs.

It went onto the system and processed as TESTA, but the data library
was LIVELIB!!

I now realise that WRKJOBSCDE uses SBMJOB to process option 10. But I
still cannot believe that it is not using the current library of the
person who scheduled the job.

OK, rant over.

Neil

[Madcap]

Had the job run at the scheduled time it would have used the "current"
library defined in the job description configured for that job
schedule entry, regardless of the current library that was set when he
issued ADDJOBSCDE. But even if the JOBD is set up properly, when you
use option 10 to submit a job from the scheduler it defaults to
*CURRENT for current library, user libl, and system libl. So he would
have submitted the job with LIVELIB anyway. Whenever using option 10
I nearly always change those parameters to *JOBD to have the job run
as configured. IMO *JOBD rather than *CURRENT should be the default.
I hope he didn't screw up production!

[Ad]

Newbie_Neil <ne...@village-street.co.uk> wrote in news:2b306f5e-1b01-45da-
a027-d8a...@g29g2000yqe.googlegroups.com:

I had the same problem
after that I allways change time to *CURRENT
then a refresh (F5)
and then change time back to original

--
Ad,

pas de probl�me, que des solutions