After applying CA Datacom SQL Version 14.0 PTF RO87076, why is the format of the output (STDOUT) for some requests different? That is, embedded blanks are now removed between columns for some requests.

Document ID : KB000039355
Last Modified Date : 14/02/2018
Show Technical Document Details

Question:

After applying CA Datacom SQL Version 14.0 PTF RO87076, why is the format of the output (STDOUT) for some requests different? 

For example, using these options and request:

//OPTIONS  DD  *                       
AUTHID=SYSADM                          
STRDELIM=A                             
DATASEPARATOR=,                        
NOECHO                                 
NOPAGES                                
NOPAGEHDR                              
NOCOLHDR                               
NOTYPE                                 
ROWLIMIT=9000                          
/*                                     
//SYSIN        DD DATA,DLM=$$          
SELECT DBID,AREA_NAME,OCCURRENCE       
FROM SYSADM.DIR_AREA WHERE DBID = 002 ;                    
$$                                     

Prior to PTF RO87076, the result was:

...+....10...+....20...+....30...+....40 

    2,DD1        ,DATA-DICT-AREA-1

With PTF RO87076, the result is:

...+....10...+....20...+....30...+....40

    2,DD1,DATA-DICT-AREA-1

Answer: 

The result with PTF RO87076 is correct and as intended. PTF RO87076 also corrected this problem:

When the DBSQLPR options "NOCOLHDR" and "NOTYPE" are specified along with "DATASEPARATOR," and a column name is longer than the length of the data, the data will be output using the space for the column name rather than the shorter length of the data itself. 

Additional Information: 

For more information on CA Datacom/DB SQL batch utility DBSQLPR that enables users to execute SQL statements through CA Datacom/DB, refer to the CA Datacom/DB SQL User Guide at 

https://supportcontent.ca.com/cadocs/0/CA%20Datacom%2014%200%20Public-ENU/Bookshelf_Files/PDF/DatacomDB1402--SQL_User_ENU.pdf