CAVF0002E NO SVA MEMORY AVAILABLE CAVF0009E INTERNAL ERROR 0C-84-12-251 TERMID=xxxx

Products

• Vollie

Issue/Introduction

The following error messages are appearing in the log - what is the cause and how can it be resolved?

CAVF0002E NO SVA MEMORY AVAILABLE
CAVF0009E INTERNAL ERROR 0C-84-12-251 TERMID=xxxx

 

 

 

Environment

Release: VOLLIE00100-5-Vollie
Component:

Cause

This problem usually happens when users are importing / viewing / saving extremely large members in their OLL libraries.

VOLLIE allocates the maximum of 3x20K pools in SVA, regardless of the total free space available. If you are dealing with large members or when using many OLL files or when many users are signed on to VOLLIE, it is possible to reach the maximum SVA memory allocation.

Resolution

Cause:

This problem usually happens when users are importing / viewing / saving extremely large members in their OLL libraries.

 

VOLLIE allocates the maximum of 3x20K pools in SVA, regardless of the total free space available. If you are dealing with large members or when using many OLL files or when many users are signed on to VOLLIE, it is possible to reach the maximum SVA memory allocation.

Resolution:

Enter SET DISPLAY SVA on the Vollie console, and the resulting output will show if all the secondary allocations are in use, as in the following example:

*** SVA Memory Allocation ***
Allocation Parameters: 20480, 20K, 3   Size of file table: xxx

Total allocated: 40960  in use: 20560  max. reached: 58920
Secondary allocation,   current count: 1  max. reached: 3
                                                               
              Total     Largest Block   Smallest Block
Pool Size    In Use    Free   In Use    Free   In Use    Free
                                                               
  19488       15408    3056    10656     800       16       8
                                                               
  20480        3160   17064     1776   11768       56     496

To increase the Primary allocation to 99K instead of 20K, take the following steps.

1. Check with the SYSTEM command which OLL files are defined in the Filetable and take note of the information.
   
   
2. LIST %@SYS2
   
   
3. Go to line 215.
   
   
4. At line 215 change @strsoll="20200303Y" to "99200303Y".
   This will increase the primary allocation to 99K.
   
   
5. Create the following VOICE proc:
   @A = COPIES(CHR(5),3)".FILETABL"
   "LIST "@A" 0"
   
   
6. Run the VOICE proc.
   
   
7. DEL ete the filetable member.
   
   
8. Rebuild File Table using SYSTEM command, option 2.
   
   
9. Ensure that all users are signed off from VOLLIE.
   
   
10. Run an OLLX6100 RELOAD in batch.
    
    
11. Sign on to VOLLIE and execute SET DISPLAY SVA.
    The allocation parameters should now be: 101376, 20K, 3
    The first number is the primary allocation in bytes (102376 bytes = 99K) the second number is the size of the secondary allocation and the third number is the number of secondary allocation.

Additional Information

In order to conserve storage further, you may wish to refer to section 4.11.2 of the CA-VOLLIE SYSTEMS PROGRAMMERS GUIDE which documents the removing of sign on records after system termination and section 4.13 which documents the USRSGNON command which allows an individual user to remove their own Sign On records.