Hi Chris, I don't understand your issue, can you please give a precise example?

Hey Bruno, My issue is that the trace file is not being read correctly. It is concatenating all of the strings together. This was not an issue in v11 but is an issue with this new version for me. For example, my trace file would read like this: 

#<AdxVL>@(#)%I% 06/09/2022 10:05:31 (ADMIN) EXECIML ZSDH
----------------------------------------------------------------------
File Importing Sage\SAGEX3\folders\83197.txt
----------------------------------------------------------------------
-------------------- Record No. 1 (Line Number 1)
Creation of Delivery D-12167664

1 records created

Normal end of log file 06/09/2022 10:05:35

When I try to read it useing rdseq, sage is reading it as 1 string so it would come back like this rather than it should be able to detect the new line...

#<AdxVL>@(#)%I% 06/09/2022 10:05:31 (ADMIN) EXECIML ZSDH----------------------------------------------------------------------File ImportingSage\SAGEX3\folders\83197.txt------------------------------------------------------------------------------------------ Record No. 1 (Line Number 1)Creation of Delivery D-121676641 records createdNormal end of log file 06/09/2022 10:05:35

I think something is wrong with your configuration as I tried right now on V12P29 and it works fine:

I would advise to check your adxifs and adxirs variables to see how field and record separators are set.
I don't believe this to be a bug, otherwise can you imagine all the rdseq in the product would do the same everywhere !

How would you advise on what I can see is my adxifs or adxirs? I feel like something may have been setup incorrectly when we migrated over to V12. Is there like some system setting that may be resetting my adxirs value? Currently, I am setting my adxirs value to be chr$(13)+chr$(10)

You're not supposed to set them, they are set automatically, notably depending if you're using Windows or Linux.
Generally X3 is using LF (chr$(10)) as end of line character, but it can be CR+LF sometimes. Have you tried to read the content of a trace file directly without calling the importsil? It might be that the importsil is changing the adxirs value.
FYI, if you need to modify adxirs or adxifs, use IOMODE instruction to only modify it for the file you are working with and not the whole product.

Chris, we just started encountering this same issue, where it reads the entire trace file as one text glob, and doesn't recognize the line feeds.  It is happening on some versions of V12 and not others, so we are thinking of patch level affecting it.  We ended up inserting this line of code before the first openi statement, where you open the trace file.  This has resolved the issue for us, but we are still trying to determine why it only does this one some X3 instances and not others. 

adxirs = chr$(10)

That is super weird ! Would you have the X3 and runtime version you are both using ?

That is super weird ! Would you have the X3 and runtime version you are both using ?

We encountered this issue on Release 2022 R1 (12.0.29), Version 90.29.58, Runtime 94.1.15

It really had us stumped, because we have been using RDSEQ to read lot files for quite awhile.

I am currently on 12.0.29, Version 90.29.58, runtime 94.1.15

I've tested on the exact same version and I don't have this issue.

Hi Bruno Gonzalez I came across the same issue on the V12P30. It seems something has changed on the default setting of "Rdseq" command. And thanks to Denise Hartman your solution worked for me as well.