Operating System - OpenVMS
1748195 Members
3256 Online
108759 Solutions
New Discussion юеВ

Re: VMS 7.3-2 giving error with too many symbols on f$search

 
SOLVED
Go to solution
Wim Van den Wyngaert
Honored Contributor

Re: VMS 7.3-2 giving error with too many symbols on f$search

I also tested the process context case. Not cancelling the context is no longer punished : no process memory stays allocated.
Did the test on 6.2 1h3 with the same result.

Was it only VMS 5.5 ?

Wim
Wim
Layne Burleson_1
Regular Advisor

Re: VMS 7.3-2 giving error with too many symbols on f$search

I can now reproduce the error on any 7.3-2 system. Here's the code I'm running. There are a few conditions that I found from the log files of the actual program: 1) delay_logical is not defined 2) noproc1.com and noproc2.com do not exist 3)pgm$debug is not defined.

When I run thru this procedure on a 7.3-2 system with clisymtbl set to 512, it runs thru the loop 61 times. On a 7.3-2 system with clisymtbl set to 1024, it runs thru the loop 124 times. I've been running the procedure all a.m. on a 7.3-1 box and have yet to get an error:

$ set noon
$ set ver
$ counter = 0
$ myPath := "csd$user:[csmlf.test]"
$!
$Holdit:
$ counter = counter + 1
$ delay := 'f$trnlnm("DELAY_LOGICAL")'
$ if delay .eqs. "" then delay:=00:00:02
$ wait 'DELAY'
$!
$ if f$trnlnm("DIRECTORY_RD1") .nes. "" then @CSD$USER:[CSMLF]NOPROC1.COM
$ sv$status = $status
$ show symbol sv$status
$ if sv$status .eqs. "%X00038138" then goto exitt
$!
$ if f$trnlnm("PGM$DEBUG") .eq. debug then goto seek
$ sv$status = $status
$ show symbol sv$status
$ if sv$status .eqs. "%X00038138" then goto exitt
$!
$Seek:
$ show time
$ dir/date/sec 'mypath'*.*;*
$ file==f$search("''myPath'*.*;*",1)
$ sv$status = $status
$ show symbol sv$status
$ if sv$status .eqs. "%X00038138" then goto exitt
$ sho sym file
$ if file .eqs. "" then goto bottom
$!
$ @CSD$USER:[CSMLF]NOPROC2 'file'
$!
$Bottom:
$ goto Holdit
$exitt:
$ write sys$output "number times thru loop ''counter'"
$ exit(sv$status)
Layne Burleson_1
Regular Advisor

Re: VMS 7.3-2 giving error with too many symbols on f$search

After more testing... it appears that when a command procedure calls another command procedure that does not exist, it eats away at the symbol table space. I've tested it on 3 7.3-2 systems with the same results. On 7.3-1 it does not appear to cause a problem.
Ian Miller.
Honored Contributor
Solution

Re: VMS 7.3-2 giving error with too many symbols on f$search

You are right - this DCL fails with %DCL-W-SYMOVF

$ SET NOON
$L1:
$ @ZYAAZ.COM
$ GOTO L1

____________________
Purely Personal Opinion
Ian Miller.
Honored Contributor

Re: VMS 7.3-2 giving error with too many symbols on f$search

On alpha VMS V7.3-2 the DCL I posted fails and returns to the $ prompt. On Alpha and I64 V8.2 it reports %DCL-W-SYMOVF and continues constantly reporting the same error.
____________________
Purely Personal Opinion
Layne Burleson_1
Regular Advisor

Re: VMS 7.3-2 giving error with too many symbols on f$search

Ian,
I ran your procedure on Alpha 7.3-2 and it worked properly thru about 60 iterations and then got the symovf error. Did not see same results on Alpha 7.3-1. I don't have an I64 box to test on.
Ian Miller.
Honored Contributor

Re: VMS 7.3-2 giving error with too many symbols on f$search

you should pass this new info on to hp and hopefully it will make its way to Mr.DCL to get fixed.
____________________
Purely Personal Opinion
Layne Burleson_1
Regular Advisor

Re: VMS 7.3-2 giving error with too many symbols on f$search

I already have an elevation with engineering. Hopefully it will get fixed soon.

Thanks to everyone for your help.
John Gillings
Honored Contributor

Re: VMS 7.3-2 giving error with too many symbols on f$search

Layne,

Keep an eye out for VMS732_DCL-V0500 - specificically for this issue. Due out in the next two weeks.
A crucible of informative mistakes