DB2 FOR LUW / DB2FORLUW / A10 - DB2

Here you have an example of such behave. 
 
When one directly executes SQL statement in CLP: 
 
?db2 -v "select routineschema, routinename, specificname, 
fenced, owner, implementation, create_time, alter_time from 
syscat.routines order by routinename asc? 
 
time-out issue doesn't occur and statement returns some results, 
which is expected, but calling above command via user-specified 
profile(example below) won't return any results, and time-out 
appear. 
 
<COLLECTION> 
<NAME>USER SCRIPT: SQL TO RUN</NAME> 
<CMD>db2 -v "select routineschema, routinename, specificname, 
fenced, owner, implementation, create_time, alter_time from 
syscat.routines order by routinename asc" </CMD> 
<OUTFILE>outputFile</OUTFILE> 
<TIMEOUT>200</TIMEOUT> 
</COLLECTION> 
 
The issue is related to size of the output produces by CMD 
command.

**************************************************************** 
* USERS AFFECTED:                                              * 
* db2support users                                             * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* Plese See Error Description.                                 * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Plese See Error Description.                                 * 
****************************************************************

N/A

DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
 

not known / see Local fix

Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

01.08.2013
02.10.2013
02.10.2013