Page 1 of 1

13.17.25 JOB04043 $HASP398 JOBNAME QUEUED FOR RE-EXECUTION

PostPosted: Thu Dec 03, 2009 5:12 pm
by samb01
hello,

i've got a problme whith a job which ended in error under SDSF.

This job was running by OPC (TWS) but it stayed started under OPC... :?: (not in error)

But the job restarted immeditly with the follwing message :

13.17.25 JOB04043 $HASP398 JOBNAME QUEUED FOR RE-EXECUTION

I can't anderstand why...

Could you help me please ?

Re: 13.17.25 JOB04043 $HASP398 JOBNAME QUEUED FOR RE-EXECUTION

PostPosted: Fri Dec 04, 2009 2:13 am
by Bill Dennis
Probably an operator issued a $E Jnnnnn command and restarted the job.

Re: 13.17.25 JOB04043 $HASP398 JOBNAME QUEUED FOR RE-EXECUTION

PostPosted: Wed Dec 09, 2009 6:13 pm
by samb01
Yes, you're right.

But do you know how can we desactivate this command ?

Because it's too dansgerous...

Thanks

Re: 13.17.25 JOB04043 $HASP398 JOBNAME QUEUED FOR RE-EXECUTION

PostPosted: Wed Dec 09, 2009 7:28 pm
by expat
You will need to make a formal request to the systems programmers to see if it is possible to deactivate, or to your security administration to limit the number of persons able to issue the command.

You will need a solid business case in order to achieve this request.

Also, please explain your reasons for believing that this is a dangerous command.

Re: 13.17.25 JOB04043 $HASP398 JOBNAME QUEUED FOR RE-EXECUTION

PostPosted: Thu Dec 10, 2009 12:08 am
by Bill Dennis
There is a JES Exit for command processing where these could be intercepted. I did this at a prior employer.

The danger of the command is that all the existing SYSOUT is blown away. It's bad if the job has started and someone issues the command in error.