I am having trouble getting a CALLX program to execute on the PEQS
file.

I suspect I am having trouble because it is a special type of system
single level file.

If I place the CALLX statement (with fully qualified path) in attribute
8 in DICT PEQS PEQS (a Q-pointer) and file an item in PEQS nothing
happens.

If I place the same call in the D-pointer and change a dictionary item
in PEQS then the program gets kicked off so I know the call syntax is
good.

I want to track print jobs with this CALLX program so it needs to work
against the data portion of the file but there is no data portion (not
like other user files anyways).

Has anyone tried this and do you know if it can be done?

Cliff

AFAIK a callx has to be on a "D" pointer to work, so I'm guessing you
will have no joy

If your programs all end up coming back to a common driver (menu
program) then you may be able to modify that so it does a SYSTEM(20)
call to get last peqs entry - assuming you only generate a single
(hold?) file, and then copy/log peqs entry as required

(we do something like this in our R5 application, with an sp-open
before any prints ... could also take a snapshot of [or clear] PEQS
before you start ... still assumes Hold option though)

Depending on WHAT you are trying to achieve, and structure of your
code, there may be other alternatives, but you also may need the
assistance of someone like Mark Brown or TonyG to save a lot of angst)


Cliff wrote: