DCL (F$GETQUI) Problem
UK Garage Scene
single user (USERX for example), then $SET ENT/HOLD for the rest of the entrys
leaving USERX released for completion, then releasing the rest of the entrys
once the USERX entrys have all been completed. Had a look in the DCL
dictionary at the F$GETQUI lexical but it went straight over my head, too many
commands. Can anybody help me?
Tim Llewellyn
yes, I am currently available :-)
alternatively, read the manual some more or look for postings here demonstrating
how to use F$GETQUI (I may well have posted one or more in the past, I'm sure
I saw something recently also). The examples in the manual are a decent starting
point.
regards
Standard disclaimer applies. My views in no way represent those of
my employers or service provider.
CSABA HARANGOZO
Another solution could be :
$STOP/QUEUE/NEXT <your_queue>
then once you have your list of entries extracted in a loop for
that user ( USERX ) set the priorities of the entries higher
than the default ( usually 100 ), e.g. 110 :
$SET ENTRY/PRIO=110 <entry_no>
$START/QUEUE <your_queue>
This makes the jobs submitted by USERX to "jump the queue" :-),
executing before all the other jobs with default priority...
Once all jobs by USERX have finished, the rest will get their turn.
Hope this helps...
Cheers, Csaba
----------------------------------------------------------------------
* Csaba I. Harangozo | 'To err is human', said the hedgehog
* csa...@zipworld.com.au | as he dismounted a wirebrush.
----------------------------------------------------------------------
EARTH::AUSTRALIA:[SYDNEY]HARANGOZO.CSABA;1, delete? [N]:
Alan E. Feldman
The best way to get up to speed quickly with F$GETQUI is to start with
the examples in DCL HELP Lex F$GETQUI Examples or the examples in the
DCL Dictionary. Find the one that is closest to what you want to do,
see what it does, and then modify it to do what you want. Find the
table in the DCL Dictionary with the keyword in the example you wish
to modify. Then change that keyword to the one you want.
Yes, it's not explained very well at all. You really have to study the
exmaples to learn it. (Well, I did.)
WARNING! Running any DCL queue-related command (like SHOW QUEUE, SHOW
ENTRY, etc.), will destroy your context if you are looping through
queues, jobs, or files. Use SPAWN SHOW ENTRY, etc., to avoid this
trap!
Disclaimer: JMHO
Alan E. Feldman
afeldman;gfigroup.com
Steve....@yellgroup.com
There was a VERY useful file in the DSN database which contained examples
etc of the use of F$GETQUI which, although quite large, was a great help to
me in the beginning. Presumably it's still available somewhere? I might
have a copy myself, but I'm not sure how you stand with posting it in C.O.V
given the usual copyright notices.
Steve S
SPAMSI...@YAHOO.COM (Alan E. Feldman) on 01/14/2002 02:49:43 PM
To: Info...@Mvb.Saic.Com
cc:
From: SPAMSI...@YAHOO.COM (Alan E. Feldman), 14 January 2002, 2:49
p.m.
Re: DCL (F$GETQUI) Problem
______________________________________________________________________
[Information] -- PostMaster:
This transmission is intended solely for the addressee(s) and may be
confidential. If you are not the named addressee, or if the message has
been addressed to you in error, you must not read, disclose, reproduce,
distribute or use this transmission.
Delivery of this message to any person other than the named addressee is
not intended in any way to waive confidentiality. If you have received
this transmission in error please contact the sender or delete the message.
Thank you.
Yell Limited, Queens Walk, Oxford Road, Reading, Berkshire, RG1 7PT.
Registered in England and Wales, registered number 4205228.
Yellow Pages Sales Limited, Queens Walk, Oxford Road, Reading, Berkshire,
RG1 7PT. Registered in England and Wales, registered number 1403041.
Rob Young
>
> WARNING! Running any DCL queue-related command (like SHOW QUEUE, SHOW
> ENTRY, etc.), will destroy your context if you are looping through
> queues, jobs, or files. Use SPAWN SHOW ENTRY, etc., to avoid this
> trap!
>
Thanks a bunch for this. I had given up trying to figure out what
was whacking my context.
Rob
Tim Llewellyn
its a shame F$GETQUI doesn't have a feature like F$SEARCH's stream ID
to work around this limitation
Simon Clubley
>
> Rob Young wrote:
>>
>> In article <343f30ae.02011...@posting.google.com>, SPAMSI...@YAHOO.COM (Alan E. Feldman) writes:
>> >
>> > WARNING! Running any DCL queue-related command (like SHOW QUEUE, SHOW
>> ^^^^^^^^^^
>> > ENTRY, etc.), will destroy your context if you are looping through
>> ^^^^^^^^^^^^^^^^^^^^
>> > queues, jobs, or files. Use SPAWN SHOW ENTRY, etc., to avoid this
>> > trap!
>>
>> Thanks a bunch for this. I had given up trying to figure out what
>> was whacking my context.
>>
> to work around this limitation
>
It took me a few hours to work out what was going on as well when I first
encountered this a few years ago. I think that the VMS documentation for
F$GETQUI should be enhanced to document this restriction.
I will send a copy of this to openv...@zko.mts.dec.com (as per the
V7.2 DCL Dictionary address).
Simon.
--
Simon Clubley, simon_clubley@remove_me.altavista.co.uk-Earth.UFP
Microsoft: The Lada of the computing world.
Simon Clubley
>
> I will send a copy of this to openv...@zko.mts.dec.com (as per the
> V7.2 DCL Dictionary address).
>
It appears to be openv...@compaq.com now. It's a pity that CPQ
couldn't keep a published email address working for longer.