JR50208: SCHEMA USING NULL_FIELD WITH NULL_FIELD_SEP DOES NOT HANDLE EMPTY STRINGS.

APAR status

• Closed as program error.

Error description

• Back in 7.5.2, we changed the default behavior for null string
  to be equal to APT_IMPEXP_ALLOW_ZERO_LENGTH_FIXED_NULL.
  
  This behavior does not support the use of null_field_sep (in
  other words, multiple nullable string values does not include
  the empty string support.)
  

Local fix

Problem summary

• Back in 7.5.2, we changed the default behavior for null string
  to be an equivalent to APT_IMPEXP_ALLOW_ZERO_LENGTH_FIXED_NULL.
  
  This behavior does not support the use of null_field_sep (in
  other words, multiple nullable string values does not include
  the empty string support.)
  
  Given this:
  
   import -schema record
   {final_delim=end, delim=',',
  timestamp_format='%yyyy%mm%dd%hh%nn%ss'}
   (
   record:int32;
   currentfield:nullable timestamp
  {null_field='42,,55555555555555'};
   dummy:string[max=50];
   )
   -rejects continue -reportProgress yes -file
  '/tmp/timestamp.txt'
   0> [] 'Sequential_File_0:DSLink2.v'
   ;
   peek -all -name
   0< [] 'Sequential_File_0:DSLink2.v'
   ;
  
   Data:
  
   1,20040101010203,dummy
   2,42,dummydummydummydummy
   3,,dummydummydummydummy
   4,55555555555555,dummy
  
  This rejects record #3.  This is incorrect.
  

Problem conclusion

• Patces are available which fix the problem
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  WIS DATASTAGE

• Fixed component ID

  5724Q36DS

Applicable component levels

• R850 PSY

     UP

• R870 PSY

     UP

• R910 PSY

     UP

• R912 PSY

     UP

• RB30 PSY

     UP