-
Notifications
You must be signed in to change notification settings - Fork 0
Bug: source member won't open (broken hex with db2util) #80
Comments
Hey @richardm90 What is the name of the member? Any odd characters in there? We'll get some feedback in. Are you using |
@worksofliam , the member name does include a hash (pound symbol) but then a lot of my member names do. In the image you'll see the four members I mentioned. All but the last member will open. Could there be something within the member (unusual character) that stops it loading? I've scanned through the source and can't see any obvious problem characters. I have db2util loaded on the server. Do I specifically need to do something to/with it? |
@richardm90 thanks for this info!
No, but it uses a different mechanism to fetch the content of the source. Are you able to use I am hoping we can recreate this on our end. Thanks! |
OK, I found it. There is an unusual character in the file, which is obvious when I view the source through SEU but was hidden when viewed through RDi. It was part of a comment that I copied in (using RDi) from a PDF. In RDi it shows as a dash (minus), which is what I expected but in SEU it shows as a ?. The source file has CCSID 285 and the hex of the rogue character is x'3F'. For completeness I'll send the source file as requested. |
x'3F' is end of transmission. Is there any reason you've got this in your source? I've seen it a few times but the reason isn't clear to me. Edit: turns out it adds color to SEU.... |
This wasn't deliberate. I copied some comment text in from a PDF file and the dash came across as x'3F' rather than a dash. Visually it looked fine in RDi, and it opened in RDi, but when I looked at it in SEU it was obvious there was an untranslatable character. |
Ah, ok. Thanks @richardm90!! I am currently looking into methods of removing the odd characters when the member is being downloaded. Of course, this only happens with db2util enabled. |
Hi, |
@dkJohan Are you using db2util or not? |
We are not using db2util / Johan |
Use tags for the following:
Using the member browser I filtered on one of my source files, this produced a list of the four members I was interested in.
I was able to open all but one of the four members.
When I click that source member I get the Loading... message briefly but then nothing. No feedback at all. As I say the other three source members opened fine.
The member that doesn't open is the largest of the four, 513 lines, but I can open larger members.
The text was updated successfully, but these errors were encountered: