Problem with Autogen: "Undefined symbol \pagefile3_cursize\"

[Guillou_2]

Hi,

During an attempt to install Decnet OSI when I tried to do an Autogen it failed with these errors:
undefined sysmbol \pagefile3_cursize\
Autogen-f-symovf,noroom for symbol definition
Autogen-f-del_exp,delete some symbols or expand clisymtbl
Autogen-f-error, testfiles phase was aborted due to an unexpected error

What is the meaning of these errors, how can I avoid it?

Regards

Steph

[Ian Miller. · Accepted solution]

the process had a lot of global symbols which filled the memory available (see SHOW PROC/MEM).
The size of this memory area is governed by the system parameter CLISYMTBL (as mentioned in the AUTOGEN-F-DEL_EXP message).

You could try
$ DELETE/SYMBOL/GLOBAL/ALL
before running the autogen. This will delete all global symbols.

[Daniel Fernandez Illan]

Steph

If you use help/message symovf you see a explanation to error:

The command interpreter cannot hold any more symbol definitions or labels. Note that this error can occur when a nested procedure is executed, because the command interpreter defines the symbols P1 through P8 before executing the procedure.

and offers two solutions:

delete unused symbols to recover symbol table space or increase CLISYMTBL using SYSGEN SET CLISYMTBL n.

Note that the SYSGEN SET command sets the new value for the duration of your process only. It does not change the permanent parameter value.

Saludos.
Daniel.

[Jan van den Ende]

Steph,

modifying CLISYMTBL is best done with SYSGEN.
Add an entry in MODPARAMS.DAT & run AUTOGEN is the approprate way, but issuing SYSGEN WRITE CURRENT will directly put it in xxVMSSYS.PAR for next reboot, and WRITE ACTIVE will update currently active params. (I have now no docs at hand, and I do not know by head if it is a Dynamic param, but if it is, it will be active for any process created after the WRITE).
SYSGEN also shows the limit to what you can set it, and if I am not mistaken, that limit is not very high.

hth,

Have one on me.

Jan

[Kris Clippeleyr]

Steph,

As already said, you might have to delete some symbol definitions before running AUTOGEN. Increasing the CLISYMTBL value using SYSGEN is also an option. The maximum value of CLISYMTBL is 1024 pagelets (i.e. 64 Alpha pages), and it's a DYNAMIC parameter. Make sure to do a WRITE ACTIVE if you change the parameter (and a WRITE CURRENT, if you want the value to survive a reboot).

Regards,

Kris (aka Qkcl)

[Ian Miller.]

If you do increase CTLSYMTBL then I expect you will have to logout/in so that your process get s the new larger size. SHOW PROCESS/MEM shows the current size.

I think VMSINSTAL deletes all global symbols. You can try deleting local symbols too then increase CTLSYMTBL if still a problem.

[Jan van den Ende]

Kris, thanks for confirming it IS Dynamic.

( I guess I really have to convince my wife that the extra garage heating & extra electricity bill for re-activating my Alpha 1000 ARE worthwhile!).

Ian, I already stated that it would only take effect for processes started AFTER the changing of the param.
If you read the OP carefully, he got the error running AUTOGEN, not VMSINSTAL.
Not the faintest info whether that was in the same session, and if so, what was executed in between that might have (re-)created al lot of symbols.

_IF_ the problem rose while running AUTOGEN in the context of the instal (cannot check now, but does DECnet OSI use VMSINSTAL? It think I' guess PCSI), then really there is hardly any option BUT increrasing CLISYMTBL.


Proost.

Have one on me.

Jan

[Lawrence Czlapinski]

Steph,
1. When you get noroom for symbol definitions you could also try logging out and logging back in. Decnet OSI is done with $ PRODUCT INSTALL DNVOSIECO01/SOURCE=[location of the ...
The install or other activity since login could have added a lot of symbols. So you might also have been able to logout. Then login and the Autogen might have run.
2. Using Alpha VMS 7.3-2, we did have to increase CLISYMTBL for a system that uses Oracle.
Lawrence

[Guillou_2]

Thanks all for your help