Configuring the Global Default Log Size

The global default log size is controlled by the variable LogSize. It contains the following items:

prg=logname=LogSizevalue=size	(in Mbyte units)

description="descriptive text"	(optional)

enabled | disabled	(default is enabled)

The global default log size can only be configured using the command line interface (see Appendix B).

Group-Screen installations are configured on the primary Screen.

The following is an example of what you type to display the global default log file size, while logged in to the primary Screen:

admin% ssadm -r primary edit Initialedit> vars print prg=log name=LogSize PRG="log" NAME="LogSize" ENABLED VALUE="100" DESCRIPTION="global
log capacity (MB)" ...

The following is an example of what you type to set the global default log file size, while logged in to the primary Screen:

admin% ssadm -r primary edit Initialedit> vars add prg=log name=LogSize value=new size description=new description
edit> quit

It is not necessary to type save before quit above if only authuser, proxyuser, logmacro, or vars entities are altered.

The following is an example of what you type to set the global default log file size to 250 Mbytes, while logged in to the primary Screen:

edit> vars add prg=log name=LogSize value=250 description="log size (MB)"

Although, the output produced by print surrounds the value of each item in double quotes, these are only necessary on input to protect embedded spaces within the values of items. Also, although print outputs all tag names in capital letters (for example, PRG=), these tags are recognized in a case-insensitive manner on input (for example, prg=, Prg=, PRG= are equivalent).

The following is an example of what you see if you attempt to save without changing entities other than these types, you are reminded by a message:

edit> savelock not held
failed (status 244)

This is a non-fatal message and you can simply quit the configuration editor.

Once a log file size has been changed, the system configuration must be activated to propagate the change. Then the effected Screen(s) must be restarted for the log file size change to take effect. (In the case of a change to the global default log file size, the effected Screens are all Screens except those for which a log file size has been specifically configured.)