There is no upper limit on T30FILE explicitly.
All of the structures sized within uvconfig must fit into a shared memory segment (sized by shmmax kernel parameter).
T30FILE sets the maximum number of slots (rows) in a table of open dynamic hashed file information in memory. This table can be viewed using the $DSHOME/bin/analyze.shm -d command. Each new row takes 114 bytes. Increasing this to 2000 means that you can have 2000 dynamic hashed files simultaneously open system-wide.
When you regenerate the shared memory segement (uvregen) you get a report about the size required. If that's nowhere near shmmax, then you have some headroom.
Job appears not to have started after 60 secs
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Upper limit on T30FILE
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.