Sauro Menna

Hi, I’ve done some in-depth research on the topic of floating-point numbers. I need to make a correction. According to the official IBM documentation for DFSORT, it is not possible to directly specify a native constant (literal constant) in floating-point (FL) or double format in control statements (such as INCLUDE, OMIT, INREC, or OUTREC). Instead, the documentation and the tool’s behavior specify that floating-point values are handled according to the following rules: 1. Constants Allowed in DFSORT...

Hi @sf-mensch, I've integrated the patch you suggested to avoid unnecessary jmp instructions. I wanted to make a proposal (with Claude's help) regarding the handling of float and double fields. The idea, as you mentioned, is to add the definition of a double field to struct fieldValue_t. For this: 1) In gcsort, FL is mapped only to COB_TYPE_NUMERIC_FLOAT (length ≤ 4) and COB_TYPE_NUMERIC_DOUBLE (length > 4), so the other FP types mentioned in the ticket (L_DOUBLE, FP_BIN, FP_DEC) cannot end up in...

* Version 01.05.01

GCSORT 1.05.00 fails to parse command line

Hi David, Thank you for reporting the issue. Tonight, I'll release an update to GCSort that will also include the patches you reported for AIX. Thank you. Best regards, Sauro

Hi, Okay, I'll look into it. I'll investigate as soon as possible and post an update on ticket #1254. Thanks, everyone.

Hi, Attached is a ZIP file with two examples in Windows environment. readme.txt contains the details. 1) Example - SYMNAMES definition in the take file gcsort TAKE take_symb.prm 2) Example - SYMNAMES definition in an external file set SYMNAMES=fsymb.txt gcsort TAKE take_symb_file.prm Sauro

ver. 1.05.00 - Update Makefile.