Universe: Is there a way to tell if a SELECT Channel is active?
George Gallen
I'm putting together a subroutine that needs to do it's own SELECT TO / READNEXT FROM
usually, I just use channel 6 - but wanted to put together another subroutine that would
return all active channels (basically loop through the 10 channels and determine if it's active)
The problem is if there is an active READNEXT going on, and you execute a new SELECT using the existing active channel, you clobber the existing position.
Example SYSTEM(11) will return a 1 if select list 0 is active -
I didn't see any SYSTEM() calls to check channels other than 0
I tried adding the channel # as the second parameter like SYSTEM(11,4) but it seems to be ignored an only checks channel 0
Thanks
Steve Johnson
Stephen Johnson
--
You received this message because you are subscribed to
the "Pick and MultiValue Databases" group.
To post, email to: mvd...@googlegroups.com
To unsubscribe, email to: mvdbms+unsubscribe@googlegroups.com
For more options, visit http://groups.google.com/group/mvdbms
George Gallen
How did I miss that one? Looks like it time for new glasses.....
Thanks
Sent: Thursday, February 22, 2018 10:42 AM
To: mvd...@googlegroups.com
Subject: Re: [mvdbms] Universe: Is there a way to tell if a SELECT Channel is active?
George Gallen
Just in case anybody needs this.....
usage:
CALL *FIRST.CHANNEL(CHANNELNO)
CMD="SELECT VOC SAMPLE 10 TO ":CHANNELNO
EXECUTE CMD RTNLIST CAPTURING JUNK
LOOP
READNEXT ID FROM CHANNELNO ELSE EXIT
....
REPEAT
*
FIRST=""
CHANNELS=""
*
FOR T=0 TO 10
IF SELECTINFO(T,1)=0 THEN CHANNELS<T+1>=1 ELSE CHANNELS<T+1>=0
NEXT T
FOR T=1 TO DCOUNT(CHANNELS,CHAR(254))
IF CHANNELS<T>=1 THEN FIRST=T-1 ; EXIT
NEXT T
*
RETURN
STOP
END
Sent: Thursday, February 22, 2018 10:27 AM
To: mvd...@googlegroups.com
Subject: [mvdbms] Universe: Is there a way to tell if a SELECT Channel is active?
Steve Trimble
--
You received this message because you are subscribed to
the "Pick and MultiValue Databases" group.
To post, email to: mvd...@googlegroups.com
To unsubscribe, email to: mvdbms+unsubscribe@googlegroups.com
George Gallen
Doesn't look like Universe likes that on.
SELECT filename TO MYLIST cause an error on Universe. From the TCL you can use a number from 0 to 99
however, in Basic you can only reference 0 to 10 (so it says) - although I haven't tried higher than 10
George
Sent: Thursday, February 22, 2018 12:23 PM
To: mvd...@googlegroups.com
Subject: Re: [mvdbms] Universe: Is there a way to tell if a SELECT Channel is active?
George Gallen
Not sure now where I saw list# from 0 to 99 for Universe - but even at the TCL you can only
use 0 to 10, same as with basic.
George
Sent: Thursday, February 22, 2018 4:13 PM
Steve Trimble
Ed Clark
To unsubscribe, email to: mvdbms+un...@googlegroups.com
Martin Phillips
This thread seems to have started in UniVerse and now drifted to QM.
QM has the same approach to select lists as UV, supporting both the numbered lists (as originated by Prime Information) and the Pick style select list variables. These are provided by the SELECTN and SELECTV statements and, just like UV, we have a compiler directive, $MODE SELECTV, that controls which style is used by SELECT. Rather than putting this in every program, it can go in the $BASIC.OPTIONS record to simplify things.
Martin Phillips
Ladybridge Systems Ltd
17b Coldstream Lane, Hardingstone, Northampton NN4 6DB, England
+44 (0)1604-709200
--
George Gallen
these are only for use for non filtered SELECTs. If you need to filter your select you have to use EXECUTE with the RTNLIST clause ,
which (at least in UV), TCL does not support named lists - only channels 0-10.
By filtered I mean using the WITH clause or sorting using the BY clause of the SELECT.
George
Sent: Friday, February 23, 2018 4:36 AM
To: mvd...@googlegroups.com
Subject: RE: [mvdbms] Universe: Is there a way to tell if a SELECT Channel is active?
Steve Trimble
--
To unsubscribe, email to: mvdbms+unsubscribe@googlegroups.com
For more options, visit http://groups.google.com/group/mvdbms
--
You received this message because you are subscribed to
the "Pick and MultiValue Databases" group.
To post, email to: mvd...@googlegroups.com
To unsubscribe, email to: mvdbms+unsubscribe@googlegroups.com
For more options, visit http://groups.google.com/group/mvdbms
--
You received this message because you are subscribed to
the "Pick and MultiValue Databases" group.
To post, email to: mvd...@googlegroups.com
To unsubscribe, email to: mvdbms+unsubscribe@googlegroups.com
For more options, visit http://groups.google.com/group/mvdbms
--
You received this message because you are subscribed to
the "Pick and MultiValue Databases" group.
To post, email to: mvd...@googlegroups.com
To unsubscribe, email to: mvdbms+unsubscribe@googlegroups.com
For more options, visit http://groups.google.com/group/mvdbms
--
You received this message because you are subscribed to
the "Pick and MultiValue Databases" group.
To post, email to: mvd...@googlegroups.com
To unsubscribe, email to: mvdbms+unsubscribe@googlegroups.com
For more options, visit http://groups.google.com/group/mvdbms
--
You received this message because you are subscribed to
the "Pick and MultiValue Databases" group.
To post, email to: mvd...@googlegroups.com
To unsubscribe, email to: mvdbms+unsubscribe@googlegroups.com
For more options, visit http://groups.google.com/group/mvdbms
--
You received this message because you are subscribed to
the "Pick and MultiValue Databases" group.
To post, email to: mvd...@googlegroups.com
To unsubscribe, email to: mvdbms+unsubscribe@googlegroups.com
For more options, visit http://groups.google.com/group/mvdbms
--
You received this message because you are subscribed to
the "Pick and MultiValue Databases" group.
To post, email to: mvd...@googlegroups.com
To unsubscribe, email to: mvdbms+unsubscribe@googlegroups.com
George Gallen
I'll have to try this with UV. I've always used the RTNLIST Clause and skipped right to the READNEXT loop.
George
George Gallen
in reading the help for SELECTE on UV - it allows you use the name in place of channel 0.
That being said...it does appear that when you use SELECTE to transfer to the variable name it
releases channel 0 - so a subsequent SELECT to channel 0 does not clobber the placeholder
within the variable the first SELECTE assigned to.
I never tried nesting these variants prior - and appears you can nest them without corruption.
Thanks
George