Finding out what image is being executed by another process

[Jimson_1]

Hi,

From within a DCL script I need to see what image is being executed on another one of my processes.

Can't seem to do it with F$GETJPI or SHOW PROC/CO

Any ideas?

James

[Craig A Berry]

Yes, you can do with with F$GETJPI, for example:

$ write sys$output f$getjpi("1b1", "IMAGNAME")
DSA0:[SYS0.SYSCOMMON.APACHE.][000000]APACHE$HTTPD.EXE;1

[Craig A Berry]

Yes, you can do it with F$GETJPI, for example:

$ write sys$output f$getjpi("1b1", "IMAGNAME")
DSA0:[SYS0.SYSCOMMON.APACHE.][000000]APACHE$HTTPD.EXE;1

[labadie_1]

Hello

You have a command file in sys$examples that does it, just do

@ sys$examples:working_set.com

Comment the line
$ imagename = F$PARSE (imagename,,,"NAME") ! separate name from filespec

if you want the full image name (disk:image.exe;

[Jimson_1]

Cheers guys.

I've tried using F$GETJPI(pid,"IMAGENAME") but for some reason it returns a null string.

$ write sys$output f$getjp("370020F6","imagname")

$

[Jimson_1]

Sorry I should clarify this a little.

I'm trying to run the correct version of GAWK on one of my sessions, but it keeps picking up the wrong version.

I've checked symbol definitions and the DCL$PATH logical but can't see anythinhg wrong.

On the session running GAWK I have the following output (Control-T'd it to get the process name and then obtained the PID)

P_CC(H1-ACT)$ gawk
_data file(s):
HFCP01::_TNA15: 16:02:32 (DCL) CPU=00:21:02.77 PF=314530 IO=5301382 MEM=327
_data file(s):

[Ian Miller.]

Do you have the right privs?

[Jimson_1]

Yes I do have the right privileges.

For example, if I stop the GAWK image, and issue the command DUMP /PAGE A.DAT instead, I get:

$ write sys$output f$getjpi("370020F6","imagname")
DSA13:[SYS1.SYSCOMMON.][SYSEXE]DUMP.EXE;1
$

[labadie_1]

a basic
$ show proc/cont/id=pid_of_your_process

shows what image ?

[Phillip Thayer]

If I'm not mistaken you will get a blank imagename if it is in DCL. Best way I would say to do this is to run your GAWK and on another terminal use the SHOW PROCESS/CONTIN/ID=pid

Once there you will see the image name changing at the bottom as it runs different programs. Then you should be able to determine the version of GAWK that is running.

If your having problems with the wrong version of GAWK running from what you expect, then I would say you have an older version of GAWK installed as an installed image. Do the following:

MC INSTALL
/LIST

Look for a listing for GAWK and see what version it is. If it's wrong then install the proper onw with a replace command in the install utility.

Phil

[Jess Goodman · Accepted solution]

The output you posted verifies that you are not (yet) running any image.

The version of GAWK that you are using here must be a DCL verb. Required command line parameters for DCL verbs are prompted for and read by DCL *before* it invokes the image.

You need to get the VERB utility, available at:
http://vms.process.com/fileserv-software.html

Then the "image" line output with "VERB GAWK" will specify what version of GAWK it is running. The default path for an image is SYS$SYSTEM:, but it may also be a logical name.

To update your verb definition for your process use "SET COMMAND GAWK.CLD".
To update it permanantly for all users use:

$ SET COMMAND GAWK.CLD -
/TABLES=SYS$COMMON:[SYSLIB]DCLTABLES.EXE
/OUTPUT=SYS$COMMON:[SYSLIB]DCLTABLES.EXE
$ INSTALL REPLACE SYS$SHARE:DCLTABLES.EXE
(users must relogin to use the new definition).

You posted:
$ gawk
_data file(s):
HFCP01::_TNA15: 16:02:32 (DCL) CPU=00:21:02.77 PF=314530 IO=5301382 MEM=327

[John Reagan]

As just mentioned, the prompting is being done by DCL. To get past that, so you are actually waiting inside GAWK, try

$ gawk tt:

[John Gillings]

James,

>I'm trying to run the correct version of
>GAWK on one of my sessions, but it keeps
>picking up the wrong version.

A bigger (privileged) hammer to see what's going on:

$ SET PROCESS/PRIV=CMKRNL
$ SET WATCH/CLASS=MAJOR FILE
$ gawk

this will trace file system operations, which will reveal which directories and files are being accessed. It might not show *why*, but at least you can confirm your suspicion.

When finished:

$ SET WATCH/CLASS=NONE FILE

[Jimson_1]

Thanks to all who replied.

The problem was that the command GAWK.CLD had been installed, by something I have yet to discover.

So indeed, by executing GAWK with no arguments, it is DCL and the command interpreter that is prompting for the input files, and not the GAWK image itself.

Doing a SET COMMAND /DELETE=GAWK removed the command and allowed me to execute GAWK.EXE directly

JP.