HP3000-L Archives

September 2000, Week 4

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Reply To:
Date:
Thu, 28 Sep 2000 00:26:09 -0600
Content-Type:
text/plain
Parts/Attachments:
text/plain (48 lines)
MPEX has a function called NTOKEN:

SETLVAR TEMPVAR1,NTOKEN(TEMPVAR,1,".")
SETLVAR TEMPVAR2,NTOKEN(TEMPVAR,2,".")
SETLVAR TEMPVAR3,NTOKEN(TEMPVAR,3,".")


[log in to unmask] wrote:
>
> My Salaam to all,
>
> The possible combinations of values for a particular variable TEMPVAR could
> be as follows:
>
> 1. TEMPVAR = "[log in to unmask]"
> 2. TEMPVAR = "@.GROUP2.ACCT2@"
> 3. TEMPVAR = "@[log in to unmask]"
> 4. TEMPVAR = "[log in to unmask]@.ACCT4@"
>
> How do I break this up into 3 different variable TEMPVAR1, TEMPVAR2,
> TEMPVAR3 such that the results should be as follows:
>
> 1. TEMPVAR1 = "AI@J", TEMPVAR2 = "GROUP1", TEMPVAR3 = "ACCOUNT1"
> 2. TEMPVAR1 = "@", TEMPVAR2 = "GROUP2", TEMPVAR3 = "ACCT2@"
> 3. TEMPVAR1 = "@J", TEMPVAR2 = "GRP3@", TEMPVAR3 = "ACCOUNT3"
> 4. TEMPVAR1 = "AI@", TEMPVAR2 = "GRP4@", TEMPVAR3 = "ACCT4@"
>
> Is there any option other than involving a WHILE loop with continious read
> till I reach "." in each attempt and process it accordingly. Any better,
> fast and best ideas ? Thanks in advance.
>
> With Best Regards
> Raghu.
>
> The information contained in this message and any attached documents is
> intended only for the personal and confidential use of the designated
> recipient(s).  This message may be a confidential and privileged
> communication.  If the reader of this message is not the intended recipient
> (or an agent responsible for delivering it to the intended recipient), you
> are hereby notified that any unauthorized distribution or copying of this
> email or the information contained in it is strictly prohibited.  If you
> have received this communication in error, please notify us immediately by
> replying to this message and deleting it from your computer.  BlueCross
> BlueShield of Tennessee, Inc., and its subsidiary and affiliate companies
> are not responsible for errors or omissions in this e-mail message.  Any
> personal comments made do not necessarily reflect the views of BlueCross
> BlueShield of Tennessee, Inc.

ATOM RSS1 RSS2