DB2 FOR LUW / DB2FORLUW / 970 - DB2

Once you create db2support.profile file on Windows like 
following: 
 
<COLLECTION> 
<NAME>...</NAME> 
<CMD>...</CMD> 
<OUTFILE>...</OUTFILE> 
<TIMEOUT>..</TIMEOUT> 
</COLLECTION> 
 
you will notice that file in binary format is following: 
 
3c43 4f4c 4c45 4354 494f 4e3e 0d0a 3c4e   <COLLECTION>..<N 
414d 453e 2e2e 2e3c 2f4e 414d 453e 0d0a  AME>...</NAME>.. 
3c43 4d44 3e2e 2e2e 3c2f 434d 443e 0d0a  <CMD>...</CMD>.. 
3c4f 5554 4649 4c45 3e2e 2e2e 3c2f 4f55   <OUTFILE>...</OU 
5446 494c 453e 0d0a 3c54 494d 454f 5554  TFILE>..<TIMEOUT 
3e2e 2e3c 2f54 494d 454f 5554 3e0d 0a3c   >..</TIMEOUT>..< 
2f43 4f4c 4c45 4354 494f 4e3e 0d0a            /COLLECTION>.. 
 
 
Once file similar to above will be parsed by db2support command, 
you will receive an error: 
 
Collecting user-specified profile collection 
 
                2013-04-08-11.4.50.730000 [db2supp_col.C:1179] 
RC=2      Error: Parse error while reading profile file.: line 6 
 
 
Cause for the error is incorrectly parsed carriage return char 
"\r" (HEX 0d) in new line sequence (0d0a). Once file contains 
Linux/UNIX style new line (0a) problem does not occur.

**************************************************************** 
* USERS AFFECTED:                                              * 
* WINDOWS                                                      * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 version 9.7 fixpack 9                         * 
****************************************************************

Create db2support.profile with Linux/UNIX style new line 
sequence (0a)

DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
 

Problem was first fixed in DB2 version 9.7 fixpack 9

not known / see Local fix

forerunner  : APAR is sysrouted TO one or more of the following: IC95251 IC96261 
follow-up : 

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

11.04.2013
02.10.2013
02.10.2013

9.7.FP9