Re: iSphere data queue monitor -- WDSCI-L

Paul,

Eventually I could recreate the problem. While the IBM character converter class ignores non-displayable characters, such as x'00', the Windows clipboard stops adding text at a x'00' character.

I am going to change my "retrieve message text" procedure to replace characters that are a control character (Java: Character. isISOControl()).

Thomas.

-----Ursprüngliche Nachricht-----
Von: WDSCI-L [mailto:wdsci-l-bounces@xxxxxxxxxxxx] Im Auftrag von Thomas Raddatz
Gesendet: Mittwoch, 28. September 2016 08:34
An: Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries
Betreff: Re: [WDSCI-L] iSphere data queue monitor

Paul,

Can you please create a CL or RPG program, such as TSTDTAQ1.CLP, that produces a data queue with entries to demonstrate the issue? I need something to debug the problem. If that is not possible, then please save such a data queue to a save file and send it to me or attach it to an iSphere ticket at SourceForge. We are on 7.2.

Regards,

Thomas.

-----Ursprüngliche Nachricht-----
Von: WDSCI-L [mailto:wdsci-l-bounces@xxxxxxxxxxxx] Im Auftrag von Paul Bailey
Gesendet: Dienstag, 27. September 2016 14:45
An: Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries
Betreff: Re: [WDSCI-L] iSphere data queue monitor

Thanks Thomas. I know about the double-click and that isn't working either.

Here are some specific details.

I find my (max length 1024) data queue in RSE, and right-click and select iSphere Data Queue Monitor. The View appears and shows me 5 of 14 records.
I change the number of messages to 50 to show the hidden messages, but this makes no difference to the problem.

The first and second entries are exactly 1024 characters long, with 4 characters at the start and 1020 spaces after. The data queue monitor view tells me it is 1024 characters long. I double-click either and the view shows the full text and 1024 hex digits (it tells me it is showing 2048 hex digits, but that is 1024 bytes/characters).

The third entry is more complex. The view tells me that the entry is 752 characters long. Double-clicking that entry shows 128 hex digits, and 64
characters:
"*PDFWTR 0101NC_EMAIL HOWARDP 597277CLMFRM" + 4 spaces (i.e. hex(40))
+ hex(000000000001) + 8 spaces

There should be another 242 spaces followed by more text (a path name) then lots more spaces and finally a user name.

When I right-click a message and "copy as text" I get only 50 characters and nothing more. If I right-click and "copy as hex" I get 1024 characters (with the last 260+ being spaces).

I'm not sure how to best present this to you so that you can see the problem. Any ideas?

-Paul.

On 27 September 2016 at 08:26, Thomas Raddatz <thomas.raddatz@xxxxxx> wrote:

I forgot to mention that you can also double click a message to open
the "Data Queue Entry" viewer to display the whole message text. From
the viewer you can use the "Previous" and "Next" buttons to move forth
and back through the messages.

Thomas.

-----Ursprüngliche Nachricht-----
Von: WDSCI-L [mailto:wdsci-l-bounces@xxxxxxxxxxxx] Im Auftrag von
Thomas Raddatz
Gesendet: Dienstag, 27. September 2016 09:21
An: Rational Developer for IBM i / Websphere Development Studio Client
for System i & iSeries
Betreff: Re: [WDSCI-L] iSphere data queue monitor

Hi Paul,

So far I could not exactly reproduce the bug. I used RDP 8.0 and RDi
9.5.0.3 and Windows 7 to debug the problem. For me the text is
truncated after the 259th character. That seems to be a known Windows limitation:

https://bugs.eclipse.org/bugs/show_bug.cgi?id=259013
https://bugs.eclipse.org/bugs/show_bug.cgi?id=257815

Please open a monitor for your data queue. Then right-click a
truncated message and select "Copy message as text" or "Copy message
as hex". This way you should get the complete message data. Please let
me know if that is true for you.

What RDi and what operating system do you use to run your IDE?

Thomas.

-----Ursprüngliche Nachricht-----
Von: WDSCI-L [mailto:wdsci-l-bounces@xxxxxxxxxxxx] Im Auftrag von
Tools/400
Gesendet: Montag, 26. September 2016 17:48
An: wdsci-l@xxxxxxxxxxxx
Betreff: Re: [WDSCI-L] iSphere data queue monitor

Hi Paul,

It should be not a big deal to implement option a).

Your bug is under investigation. I will keep you updated regarding to
option a) and the bug.

Regards,

Thomas.

Am 23.09.2016 um 11:15 schrieb Paul Bailey:

Hi Thomas,

For (a) I'd point out that hexadecimal values are reasonably
familiar to a fair number of programmers on this list and so
entering packed decimals aren't totally strange, but maybe just a
simple editor that takes either Hex or Char and the data formatting is up to the user?

I thought (b) might be too much. As you are passively reading the
data queue with the QMHRDQM API, you are not affecting the data that
could be processed by another program at any time and it would be a
shame to risk data damage by trying to be too clever.

After several weeks of playing with the data queue monitor, I have
only just found a bug! There is an option to display any data queue
entry (as both hex and char) but it *only* ever displays the first
100 characters
(bytes?) of the entry. There is an option to change how much of the
data is displayed, but this appears to have no effect on the display
of data queues longer than 100 chars. (I was using one of 1024 chars
in length.)

Thanks for your continuing hard work!

-Paul.

On 20/09/2016 12:44, Thomas Raddatz wrote:

Hi Paul,

The data queue monitor uses the QMHRDQM API to read the messages of
a given data queue. Since the QMHRDQM API does not remove messages
from the queue, reposting of messages is not required.

Honestly I already thought about posting and deleting messages. Here
are my concerns about that:

a) I think that we can safely assume that people usually use data
structures to build the message data. So what shall we do when the
message data is composed of binary or packed values?

b) Removing messages from a data queue is not easy. As you already
pointed out, iSphere had to receive and repost the messages,
ignoring the messages to be removed. Can you think of a save way to do that?
Actually the plug-in cannot do that, because of network problem that
may happen all the time. Most likely iSphere had to use commands to
dump the queue to a physical file and to repost the messages from
the file. Both commands had to be called from a CL program on the
IBM i server. Just reading and reposting the messages one by one is
not save enough because of possible network problems. Another option
could be to create an empty "staging" queue (save/restore and
QCLRDTAQ,
problem: produce temporary name), then populate that queue with the
remaining messages and eventually rename that queue to the original
name. Another problem is that the messages that are removed could
only be identified by their index number, when the whole thing runs
on the IBM I server. Last but not least there had to be an exclusive
lock on the queue from the point when the user selects the messages
to the end of the job.

Everybody: What are your ideas for solving the problem?

Regards,

Thomas.

-----Ursprüngliche Nachricht-----
Von: WDSCI-L [mailto:wdsci-l-bounces@xxxxxxxxxxxx
<wdsci-l-bounces@xxxxxxxxxxxx>] Im Auftrag von Paul Bailey
Gesendet: Dienstag, 20. September 2016 12:32
An: Rational Developer for IBM i / Websphere Development Studio
Client for System i & iSeries
Betreff: [WDSCI-L] iSphere data queue monitor

Hi Thomas/Frank,

I've been playing with the data queue monitor recently and I like it.
I have a question, and a possible enhancement request.

Is the monitor displaying the data in the data queue passively, or
is it reading and reposting the data queue items?

Can we have a feature to enable posting and deleting items from a
data queue? The posting part should be fine, using the QSNDDTAQ api,
but removing an item might require removing all and reposting the
ones still required.

What do you think?

-Paul.
--
This is the Rational Developer for IBM i / Websphere Development
Studio Client for System i & iSeries (WDSCI-L) mailing list To post
a message email: WDSCI-L@xxxxxxxxxxxx To subscribe, unsubscribe, or
change list options,
visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at http://archive.midrange.com/wdsci-l.
--
IMPORTANT NOTICE:
This email is confidential, may be legally privileged, and is for
the intended recipient only. Access, disclosure, copying,
distribution, or reliance on any of it by anyone else is prohibited
and may be a criminal offence. Please delete if obtained in error
and email confirmation to the sender.

--
This is the Rational Developer for IBM i / Websphere Development
Studio Client for System i & iSeries (WDSCI-L) mailing list To post a
message
email: WDSCI-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list
options,
visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at http://archive.midrange.com/wdsci-l.
--
IMPORTANT NOTICE:
This email is confidential, may be legally privileged, and is for the
intended recipient only. Access, disclosure, copying, distribution, or
reliance on any of it by anyone else is prohibited and may be a
criminal offence. Please delete if obtained in error and email
confirmation to the sender.
--
This is the Rational Developer for IBM i / Websphere Development
Studio Client for System i & iSeries (WDSCI-L) mailing list To post a
message
email: WDSCI-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list
options,
visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at http://archive.midrange.com/wdsci-l.
--
IMPORTANT NOTICE:
This email is confidential, may be legally privileged, and is for the
intended recipient only. Access, disclosure, copying, distribution, or
reliance on any of it by anyone else is prohibited and may be a
criminal offence. Please delete if obtained in error and email
confirmation to the sender.
--
This is the Rational Developer for IBM i / Websphere Development
Studio Client for System i & iSeries (WDSCI-L) mailing list To post a
message email: WDSCI-L@xxxxxxxxxxxx To subscribe, unsubscribe, or
change list options,
visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at http://archive.midrange.com/wdsci-l.

--
This is the Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries (WDSCI-L) mailing list To post a message email: WDSCI-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at http://archive.midrange.com/wdsci-l.
--
IMPORTANT NOTICE:
This email is confidential, may be legally privileged, and is for the intended recipient only. Access, disclosure, copying, distribution, or reliance on any of it by anyone else is prohibited and may be a criminal offence. Please delete if obtained in error and email confirmation to the sender.
--
This is the Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries (WDSCI-L) mailing list To post a message email: WDSCI-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at http://archive.midrange.com/wdsci-l.
--
IMPORTANT NOTICE:
This email is confidential, may be legally privileged, and is for the intended recipient only. Access, disclosure, copying, distribution, or reliance on any of it by anyone else is prohibited and may be a criminal offence. Please delete if obtained in error and email confirmation to the sender.