× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: Varying fields in debug
  • From: Jon.Paris@xxxxxx
  • Date: Mon, 24 Jul 2000 18:38:17 -0400

Hi John - I played with this some (needed a break from beating my head into
a brick wall - the wall and myself are both feeling much better now!)

You can in fact do an Eval varyfield = X'0000' and the whole field will be
reset to blanks with a zero length!  Why the debugger won't take eval
varyfield = '' (i.e. null string) I have no idea.

You can get a hint as to why this works by doing an eval with the :X
extension.  For example if I say Eval varyfield = ' ' then doing a straight
eval of that field shows spaces.  If however I use eval varyfield:x then
what I see is "000140.........." in other words use of the hex option makes
it take the length portion into account.  I presume that when you set it
using the hex option it makes the same assumption i.e. that the first four
digits are the length piece - neat eh!

Don't know if its documented anywhere but I'm sure going to remember it!

+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.