error while executing a program in C

[mi7ssana]

hi,
i try to execute my program and i get this error:

Erreur execution SYS$TRNLNM ; code retour : 444
and when i tryed with another program i get a new error:
%DCL-W-ACTIMAGE, error activating image TEST1
-CLI-E-IMGNAME, image file $1$DGA102:[000000.][env.EXE]TEST1.EXE;3
-IMGACT-F-NOT_I64, image is not an HP OpenVMS Industry Standard 64 image

someone could help me?

regards

[Hein van den Heuvel]

mi7ssana,

"step away from the machine"

But errors suggest a failure to operate the system, not a failure in the system

Please ask your peers and /or superiors how to use system.

To translate the code 444 to meaningful text you can use : $ EXIT 444
It will indicate: %SYSTEM-F-NOLOGNAM, no logical name match.

So there is a logical name (environment variable) not defined. Often those are setup system wide, sometimes for all application users, sometime per user.
You may have to execute a setup or init script before running the program.

The second error message indicates the you are using OpenVMS on Itanium, but try run an Alpha program. This too can be cause by not having the rigth logical names in place.

Ask the folks immediately around you!

Bon courage,
Hein.

[Richard Brodie_1]

Erreur execution SYS$TRNLNM ; code retour : 444

$ exit(444)
%SYSTEM-F-NOLOGNAM, no logical name match

Check that you are passing the logical name parameter correctly, and with correct length and case.

-IMGACT-F-NOT_I64, image is not an HP OpenVMS Industry Standard 64 image

Means what it says, you probably have compiled on another platform (e.g. Alpha). Or maybe it's not really an executable at all.

[mi7ssana]

the problem that i didn't pass a logical name in my program. the program is just a test which include a simple display. and that gives me the folllowing error:
%DCL-W-ACTIMAGE, error activating image TEST1

but for the first error :
Erreur execution SYS$TRNLNM ; code retour : 444

same thong i have no link or reference to a logical name.

and honestly i dont how to do it.

thanks

[mi7ssana]

i do the same thong before with a program who display hello world and it works. i try to do the same thing and now it doesn't work.

[Hein van den Heuvel]

To get that IMGACT message, did you just type 'run TEST1' ? That TEST1 may have been interpreted as a logical. $SHOW LOG TEST*
Notice how in the reported file name for the IMGACT message it reads " [env.EXE] "
That suggests to me that there may was been an attempt to create CPU-architecture dependend directories like [I64.EXE] and [ALPHA.EXE] maybe 'env' was supposed to be a variable but used as string? Mind you, apparently this [env.EXE] does exist.

So how did you make your 'hello world'.
Just CC, Link and run or something 'clever'?
Hint: check for the DATEs for the EXE to make sure you are running the intended program


>> but for the first error :
Erreur execution SYS$TRNLNM ; code retour : 444
same thong i have no link or reference to a logical name.

Not the same thing. That is NOT a standard OpenVMS error text. The system is not making that up. So somewhere in the program, directly or indirectly a function was called which 99% sure tried to call SYS$TRNLNM for a logical name which was not defined.
( The remaining 1% is for the case where someone thought if funny to provide a function which just prints "Erreur execution SYS$TRNLNM ; code retour : 444" when called. :-)

Honestly, this will be easy to resolve working with folks who are on the actual system and familiar with the system (mixed cluster). Much too hard to do in this conversation.

Good luck,
Hein

[Hoff]

Know the VMS debugger.

Use the VMS debugger.

Embrace the VMS debugger.

Got errors?

The VMS debugger is your best friend.

Even if you don't have visible errors, use the debugger.

Whatever you might think the source code is doing here and however the source code is constructed, bluntly, you're quite wrong here with your "no logical names", and your code IS translating a logical name somewhere.

Learn and then use the VMS debugger to locate the source code or the call within this application that is very clearly translating a logical name.

The debugger then will allow you to easily identify which source code or source code call translates that logical name.

[mi7ssana]

thank you for your response :)
this is my program test1:

#include
#include

main()
{
printf("Hello, World!\n" );
exit( EXIT_SUCCESS );
}

actualy i execute the following commands:
cc test1
link test1
in an environnement and after i make a copy of my test1.exe in an another environnement and i execute the program run test1
and the result is
%DCL-W-ACTIMAGE, error activating image TEST1
-CLI-E-IMGNAME, image file $1$DGA102:[000000.][env.EXE]TEST1.EXE;3
-IMGACT-F-NOT_I64, image is not an HP OpenVMS Industry Standard 64 image

the problem is that people who work whith me don't know too much about language C the work with Cobol so i have to find a solution by myself.

and what confusing me is that i do the same thing with the same program before and it works.

and for the second errror i have no idea about how to figure it out.
regards

[mi7ssana]

i may seem stupid but i don't use a vms debugger before could you show me an example i mean how to use it. thanks

regards

[Joseph Huber_1]

The IMGACT error has nothing to do with the source language at all.

Would You please tell us what copying to and changing the environment means ?
Just make the simplest test, and just RUN TEST1 immediately after the LINK test1, and before "changing environment", whatever that means.

[mi7ssana]

when i run it in the same environnement it works
what i mean by copying in another environnement is i make a cop/ftp of my test1.exe to another environnement ( actually the environnement of test) and the program send an error

[Hoff]

Using "TEST" or "TEST1" or "DEBUG" is poor practice; too many folks do that, and collisions are common, and confusion ensues, and those names are not at all descriptive of the application itself. Add some extra characters to the names, both to describe that this example is HELLOWORLD.C and to avoid logical name collisions with the logical names that can be defined and used on VMS systems. Getting into the habit of good names and good comments is good programming.

How to use the Debugger? Read the manuals. The two manuals you should have already read are:

http://h71000.www7.hp.com/doc/84final/4538/4538pro.html

http://h71000.www7.hp.com/doc/82final/5841/5841pro.html

The documentation shelf is here, including OpenVMS and the above manuals, as well as the C programming shelf:

http://www.hp.com/go/openvms/doc

The C library manual is (confusingly) in the base OpenVMS documentation set and not in the C shelf.

As for your direct question on the debugger...

$ CC x.c /DEBUG /NOOPTIMIZE
$ LINK x.obj /DEBUG
$ RUN x

Common Debugger Commands:

SET MODE SCREEN
STEP
STEP /INTO
EXAMINE
GO
SET BREAK line
HELP

And the next error you'll almost certainly hit is the Access Violation (ACCVIO), and the stackdump provides a wealth of information:

http://labs.hoffmanlabs.com/node/800

You're probably colliding with a logical name TEST1 or whatever you've named this as defined on the target system; you're not running the application you think you're running. This can be a direct logical name collision with the filename, or somebody might have a "creative" DCL$PATH definition, or such. Pick a different filename; test this with HELLOWORLD.EXE or such.

Reposting this. ITRC choked again, as is its wont. Apologies on any dups.

[Joseph Huber_1]

[ i make a cop/ftp of my test1.exe to another environnement ( actually the environnement of test) ]

"another environment" in this case is another system having a different CPU architecture:
You build the program on an Alpha (or vax), and try to run it on an Itanium system, I bet.

[Jan van den Ende]

Hi,

>>>
what i mean by copying in another environnement is i make a cop/ftp of my test1.exe to another environnement
<<<

This may well be the explanation of
>>>
-IMGACT-F-NOT_I64, image is not an HP OpenVMS Industry Standard 64 image
<<<

It looks like you do the COMPILATION on a system running the Alpha architecture, and then copy the executable to an IA64 system.

YES, the BOTH run VMS (actually, so does Vax), and they appear much alike, but ünder the hood" they are quite different.
Camppare automobiles: they a very similar to drive, but "under the hood" it DOES make a different if it runs on Diesel, Gasoline, (or LPG, just to add the 3rd).

The very same would apply to your Cobol colleagues, so they should be able to help you in this.

hth

Proost.

Have one on me.

jpe

[mi7ssana]

thanks for helping me i finally found the cause of my error . thanks again

[abrsvc]

Could you post the final solution? Many users use this forum as a reference when encountering problems. The solution here might be of assistance to others.

Thanks,
Dan

[Stanley F Quayle]

And please assign point values to the responses -- some were quite detailed and helpful.