DB2 FOR LUW / DB2FORLUW / A50 - 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:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to V105FP4.                                          * 
****************************************************************

N/A

DB2 Version 10.5 Fix Pack 3 for Linux, UNIX, and Windows
 DB2 Version 10.5 Fix Pack 3a for Linux, UNIX, and Windows
 DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
 DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows
 

From V105FP4, db2support -pf with large output will output the 
results in the output file.

keiner bekannt / siehe Local-Fix

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

01.08.2013
03.03.2014
03.03.2014