× 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.



Hi, Chris:

&1 = 1
&2 = 11
&3 = 21
&4 = 31
etc., ad nauseum


HTH....
Dennis







"Chris Devous" <cdevous@antigua.com>@midrange.com on 02/05/2003 10:44:13 AM

Please respond to Midrange Systems Technical Discussion
       <midrange-l@midrange.com>

Sent by:    midrange-l-bounces@midrange.com


To:    Midrange Systems Technical Discussion <midrange-l@midrange.com>
cc:
Subject:    Re: system reply list entry problem, how to calc position


Tom,

I changed my reply list entry to 1, and it worked, but I'm sooooo confused!

OK, I read the help text and I get that the comparison position for &1 is
1, because it
is the first field in the replacement text.  Each field is 10 characters,
so wouldn't &4
be 41 and not 31?  I guess I don't understand how to calculate the
position.

TIA,

Chris

On 4 Feb 2003 at 16:48, Tom Jedrzejewicz @ San Pedro wrote:

> Your calculation of the position is not correct.  The position is not
> the character position of LANPRT03 in the message, is it the character
> position of LANPRT03 in the message VARIABLE data.
>
> Looking at the replacement fields in the message description (wrkmsgd
> cpa3394, 5), you want replacement variable &1.  So you want to use
> position 1.  Note that is you wanted to test for a particular form
> value (like '*STD'), you would want variable &4, so you would use
> position 31.





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.