Question & Answer
Question
How do I calculate the value for the parameter T30FILE in the uvconfig file?
Answer
The T30FILE parameter in the uvconfig file specifies the number of dynamic hashed files that can be opened concurrently in DataStage Server. This setting is system wide, not by project. Some examples of dynamic files are job control files in projects (such as RT_LOGn, RT_STATUSn, and RT_CONFIGn) and also the hash files you can create by using server jobs. By default, this value is set to 512 but a system running multiple jobs concurrently might need to open more than that number of dynamic files at once.
If DataStage hits the limit of open dynamic files, jobs abort. The phantom record for the job run contains the error Unable to allocate Type 30 descriptor, table is full. The error might also be found in the job's log.
If DataStage hits the limit of open dynamic files, jobs abort. The phantom record for the job run contains the error Unable to allocate Type 30 descriptor, table is full. The error might also be found in the job's log.
Using the following steps, initially increase T30FILE to 768 since the current limit is inadequate.
1. Make a backup of the uvconfig file. On UNIX platforms, this file is located in IISPath/Server/DSEngine where IISPath is /opt/IBM/InformationServer by default. On Windows, the location is C:\IBM\InformationServer\Server\DSEngine by default or under a different drive.
2. Stop DataStage.
On UNIX with the dsadm user:
cd IISPath/Server/DSEngine
. ./dsenv
bin/uv -admin -stop
On Windows with an administrator user, use the DataStage Control Panel to stop all services, or from the command-line run:
net stop DSRPC
net stop dstelnet
net stop DSEngine
3. Edit the uvconfig file and set T30FILE to the new value.
4. Regenerate the configuration.
On UNIX:
bin/uvregen
On Windows:
cd C:\IBM\InformationServer\Server\DSEngine
bin\uvregen
5. Restart DataStage.
On UNIX:
bin\uv -admin -start
On Windows, use the DataStage Control Panel to start all services, or from the command-line run:
net start DSEngine
net start dstelnet
net start DSRPC
To monitor the number of dynamic files your system is opening during peak usage, use the smat command. This command lists all the dynamic files currently open (each line of the report represents a file).
You can use wc to count the number of lines the command smat returns. On UNIX, before you run this command source the dsenv file.
$DSHOME/bin/smat -d | grep '^[ \t0-9]' | wc -l
On Windows environments, use the Command button in the Projects tab of the Administrator client to execute:
SH -c "C:/IBM/InformationServer/Server/DSEngine/bin/smat -d | grep '^[ \t0-9]' | wc -l"
This command does not affect the execution of your jobs. Rather, it confirms how many dynamic files are open at the time. Using this value, you can identify whether the number of opened dynamic files is approaching the T30FILE limit. On UNIX, a script can be written to periodically collect output from the smat command. On Windows, a DataStage job can be created to do the same.
[{"Type":"MASTER","Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSVSEF","label":"IBM InfoSphere DataStage"},"ARM Category":[{"code":"a8m50000000L0twAAC","label":"DataStage-\u003EEngine Config and Management"}],"ARM Case Number":"","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF016","label":"Linux"},{"code":"PF033","label":"Windows"}],"Version":"All Versions"}]
Was this topic helpful?
Document Information
Modified date:
01 February 2022
UID
swg21390117