Title: | *OLD* ALL-IN-1 (tm) Support Conference |
Notice: | Closed - See Note 4331.l to move to IOSG::ALL-IN-1 |
Moderator: | IOSG::PYE |
Created: | Thu Jan 30 1992 |
Last Modified: | Tue Jan 23 1996 |
Last Successful Update: | Fri Jun 06 1997 |
Number of topics: | 4343 |
Total number of notes: | 18308 |
Hi, Using the DSAB QUI$QUEUE the QUEUE_STATUS_TEXT field is empty if the queue is busy. On a VMS V5.4-3 system the $SHOW QUEUE also didn't give a status when the queue was busy or idle (on $ SHOW QUEUE). But VMS 5.5 will return the status, f.e. Stopped, Idle or Busy. But still the QUI$QUEUE DSAB won't return the status when the queue is busy. Problems will araise if you want to build an index-form in which you can display queues and their status. You cannot simply BIND *Q TO QUI$QUEUE but have to do some extra work for it (just like in DL$INDEX). Performance will decrease. Any comment on this one? Thanks in advance. Sjaak.
T.R | Title | User | Personal Name | Date | Lines |
---|---|---|---|---|---|
670.1 | QUI$QUEUE is based on VMS V5.4 | IOSG::BUTTON | Tue May 12 1992 14:52 | 18 | |
Sjaak, The busy status value is a feature of the new job controller in VMS V5.5. The QUI$QUEUE data set only supports features up to VMS V5.4, so will not know anything about the new features. The behaviour that you are experiencing will continue until the QUI$QUEUE data set is updated to support the new features of VMS V5.5. I do not know if there are any plans to do this in a PFR - I suggest you contact Product Management if you want this to happen. As long as the named data on the index form continues to use QUI$QUEUE in a FOR loop, and in the efficient manner described in the API Reference Guide, then the performance degredation should not be too bad. Jon | |||||
670.3 | IQ option - blank status field | UTRTSC::BOSMAN | We're just sugar mice in the rain | Mon May 18 1992 14:20 | 4 |
I just tested this on a V3.0 system using the option IQ on the 'Manage Jobs and Queues". It also results in a blank status field! Sjaak. |