Re: Delete/Entry=### fails to stop job execution
From: Tom Simpson (thomas.simpson1_at_fubar.comcast.net)
Date: 10/20/05
- Next message: Alan Greig: "Re: OT: Is your HP printer spying on you?"
- Previous message: _at_SendSpamHere.ORG: "Re: URL grumble"
- In reply to: Alan Greig: "Re: Delete/Entry=### fails to stop job execution"
- Next in thread: JF Mezei: "Re: Delete/Entry=### fails to stop job execution"
- Reply: JF Mezei: "Re: Delete/Entry=### fails to stop job execution"
- Reply: Alan Greig: "Re: Delete/Entry=### fails to stop job execution"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Wed, 19 Oct 2005 19:34:17 -0400
What bothers me is why doesn't the entire job abort when you issue the
DELETE/ENTRY command? The DELETE/ENTRY command appears to be doing a force
exit on the running image only, returning control to the batch command file.
I would think it should also delete process that is executing the command
file too.
Regards,
Tom
"Alan Greig" <greigaln@netscape.net> wrote in message
news:1129749397.071288.39610@g43g2000cwa.googlegroups.com...
>
> jlmadden wrote:
>> We're running OpenVMS 7.3 and have come across the following. A job
>> was found to be executing a program that was in a loop. The operator
>> performed a Delete/Entry=### on the job. The job stopped executing the
>> program, printed "job aborted" in the log, then proceeded to execute
>> all the remaining commands in the DCL command file. After
>
> I am guessing you may be running "$ SET NOON". If so try running "SET
> ON". Or use ON ERROR to jump to an exit routine. I think you would
> probably find the batch job would go away but it probably completes the
> remaining DCL too quickly.
>
>> experimenting with the use of Delete and Stop/ID, we found that the
>> problem seems to occur only when the line in the com file following the
>> command that is executing does NOT start with a $ symbol. We have a
>> 4GL report writer that requires this:
>> eg: $ SET DEFAULT JOBSPACE
>> $!
>> $ Quiz
>> exe PDRM1401_01
>> exe PDRM1401_02
>> $!
>> $ PRINT PDR1401PRT.LIS /QUEUE=SYSQUEUE1
>> .
>> .
>> .
>> When the Delete/Entry=456 command was entered while the PDRM1401_01
>> module was executing, the following messages were placed into the log
>> file and the job continued executing with the
>> print statement:
>>
>> $!
>> $ Quiz
>> exe PDRM1401_01
>> %JBC-F-JOBABORT, job aborted during execution
>> %DCL-W-SKPDAT, image data (records not beginning with "$") ignored
>> $!
>> $ PRINT PDR1401PRT.LIS /QUEUE=SYSQUEUE1
>> .
>> .
>> .
>>
>> Has anyone else seen this in either 7.3 or later versions of OpenVMS?
>
- Next message: Alan Greig: "Re: OT: Is your HP printer spying on you?"
- Previous message: _at_SendSpamHere.ORG: "Re: URL grumble"
- In reply to: Alan Greig: "Re: Delete/Entry=### fails to stop job execution"
- Next in thread: JF Mezei: "Re: Delete/Entry=### fails to stop job execution"
- Reply: JF Mezei: "Re: Delete/Entry=### fails to stop job execution"
- Reply: Alan Greig: "Re: Delete/Entry=### fails to stop job execution"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|