Subject: | |
From: | |
Reply To: | |
Date: | Fri, 26 Feb 1999 22:45:43 -0500 |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
Those MPE Classic systems just don't want to quit!:-)
Richard
Donna Garverick wrote:
>
> Tom Hula wrote:
>
> > Does the program read 'CALL INTRINSIC "QUIT" USING \25\' ?
> > It wouldn't work correctly if the word 'intrinsic' is left out...
>
> you know...it's soooo nice when you actually get an answer to a
> problem....
>
> yes (to answer tom's question) the program was doing an 'intrinsic
> "quit"' -- all quite normal. but the rc actually came thru for me
> (thanks susan). this is a known defect with the cm call to 'quit'.
> there's an sr for it (sr-5003342345) and hp has no plans to fix it.
> if you're doing a cm call to 'quit' you can get bizzarre behavior.
> providing that i'm understanding all of this correctly (haha) -- quit
> will report the last(?) message found on the error stack -- which may
> or may not have anything to do with what's actually causing the
> program to barf. there are a couple of suggested workarounds. 1) do
> nothing, ignore the message 2) certain instrinsics will zero-out the
> error stack, so call one of these 'magic' instrinsics prior to
> calling quit (the suggestion was to call 'print' with an empty
> buffer/length an cctl of %320 (no cr, no lf)) 3) write a switch (i
> guess) to call nm 'quit' (yeah, right -- this *is* classics-are-us
> longs :-). i think i like the sounds of #1 :-) - d
>
> --
> Donna Garverick Sr. System Programmer
> 925-210-6631 [log in to unmask]
>
> >>>MY opinions, not Longs Drug Stores'<<<
--
Richard Gambrell
Database Administrator and Consultant to Computing Services
University of Tennessee at Chattanooga, Dept. 4454
113 Hunter Hall, 615 McCallie Ave. Chattanooga, TN 37403-2598
phone: 423-755-4551 fax: 423-755-4025
e-mail: [log in to unmask]
(private email: [log in to unmask])
|
|
|