topic F$GETQUI Playing Up in Operating System - OpenVMS

F$GETQUI Playing Up

Robert Atkinson — Mon, 11 Jul 2005 08:26:00 GMT

Please tell me why can't I use this item code???

$START:
$ !
$MONI_QUE:
$ QUE = F$GETQUI("")
$ QNAME = F$GETQUI("DISPLAY_QUEUE","QUEUE_NAME","FTG_ITOPS_PDF1","WILDCARD")
$ !
$MONI_QUE_LOOP:
$ ENTRY_NO = F$GETQUI("DISPLAY_JOB","ENTRY_NUMBER")
$ SH SYM ENTRY_NO
ENTRY_NO = 4993 Hex = 00001381 Octal = 00000011601
$ !
$ JOB_FILE = F$GETQUI("DISPLAY_JOB","FILE_SPECIFICATION",,"FREEZE_CONTEXT")
%JBC-F-INVITMCOD, invalid item code or option code

Cheers, Rob.

Re: F$GETQUI Playing Up

Bojan Nemec — Mon, 11 Jul 2005 09:04:41 GMT

Rob,

For the F$GETQUI specifications you must look to the SYS$GQTQUI system service:

http://h71000.www7.hp.com/doc/82FINAL/4527/4527pro_060.html#index_x_618

If you look at the QUI$_DISPLAY_JOB function, you will see that has no QUI$_FILE_SPECIFICATION item. This is an item for QUI$_DISPLAY_FILE function. To get the job file name use:

JOB_FILE = F$GETQUI("DISPLAY_FILE","FILE_SPECIFICATION")

Bojan

Re: F$GETQUI Playing Up

Bojan Nemec — Mon, 11 Jul 2005 09:06:31 GMT

Sorry,

I mean SYS$GETQUI system service :)

Bojan

Re: F$GETQUI Playing Up

Ian Miller. — Mon, 11 Jul 2005 09:06:47 GMT

The FILE_SPECIFICATION item code is used with DISPLAY_FILE not DISPLAY_JOB.

I think within the job context you have to do a DISPLAY_FILE loop for each possible file in the job (often just one file).

See
http://h71000.www7.hp.com/doc/82FINAL/4527/4527pro_060.html#jun_304

Re: F$GETQUI Playing Up

Robert Atkinson — Mon, 11 Jul 2005 09:10:27 GMT

Cheers guys.

I'd tried substituting with DISPLAY_ENTRY, but didn't spot DISPLAY_FILE.

I think I might try and get the help text updated so you can see what item codes match which calls.

Rob.

Re: F$GETQUI Playing Up

Dale A. Marcy — Mon, 11 Jul 2005 09:22:17 GMT

Best I can tell, it is a bug. FILE_SPECIFICATION is listed in the manuals and the footnote specifically references DISPLAY_JOB, so that combination should be allowed. I have not used this item code before, but I have used other item codes with the same setup. I took some of that code and changed the item code to be FILE_SPECIFICATION and received the same error. One difference I noted in my code is that I had to include a wildcard in the queue name string passed into the wildcard operation or it would not set the context.