import a iSeries trace to Wireshark

25 pts.
Tags:
AS/400
ASCII
Wireshark
Can anyone tell me how to import a TRCCNN ASCII trace to Wireshark? In Wireshark, I  import as a TXT file, but it doesn't work.  Thank you for any help that you can provide.    

Software/Hardware used:
AS/400 TCPIP

Answer Wiki

Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Discuss This Question: 1  Reply

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
  • TomLiotta
    Well, I suppose you'd start by converting the QPCSMPRT spooled file in a physical file. It might be useful to use QShell utilities to do that because you could strip out nearly all of the non-HEX data while doing it. At the same time, you could pipe it all into some utility that you created (or found/downloaded) to convert the hex to the format required by Wireshark. Or you could put it directly into your physical file. If you didn't format in your QShell script, you'd need to write something that read the file and added the required Wireshark formatting. Once you had it formatted, you could use CPYTOSTMF to give a streamfile that would import directly into Wireshark. Otherwise, I'm not sure why you'd want to do this. Did you have some reason to think it should be easily possible? The only stuff that Wireshark wants for import is the hex data. And it wants it as single blank-separated hex-bytes with file offsets at the beginning of each line in the file. Obviously, the trace data would need to be appropriate for ASCII to start with. It doesn't seem terribly difficult. It just doesn't seem useful if Wireshark is already available. Tom
    125,585 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Thanks! We'll email you when relevant content is added and updated.

Following