MCDONALD@UMKCVAX1.BITNET (08/01/86)
One our operators was playing with DCL CALL in the following .com
$ CALL TEST
.
.
.
$ SUBROUTINE TEST:
.
.
$ ENDSUBROUTINE
The label, of course, should be the first thing on that line,
but you would thing that DCL would handle it a little more robustly.
It gives you a dump and kicks you out on your ear!
A one-liner, $CALL TEST, will do the same thing. We have SPRed it.
GaryM. BITNET contact UMKCVAXn (n=1,3)
Univ. of Mo. at K.C.
MCDONALD @ UMKCVAX1 . BITNEToberman@LLL-ICDC.ARPA ("Oberman, Kevin") (08/05/86)
>One our operators was playing with DCL CALL in the following .com >$ CALL TEST > . > . > . >$ SUBROUTINE TEST: > . > . >$ ENDSUBROUTINE > > The label, of course, should be the first thing on that line, >but you would thing that DCL would handle it a little more robustly. >It gives you a dump and kicks you out on your ear! > > A one-liner, $CALL TEST, will do the same thing. We have SPRed it. Any CALL to a non-existant subroutine will cause the process to crash. We detected the problem at the Dallas DECUS Symposium. Since it was in the VMS Campground with several VMS developer present, they were well aware of it. Not to mention a bit embarressed that we had found such an obvious bug in about 10 minutes. Kevin Oberman Lawrence Livermore Nat'l Lab ARPA: oberman@lll-icdc (415) 422-6955 ------