[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference vaxaxp::vmsnotes

Title:	VAX and Alpha VMS
Notice:	This is a new VMSnotes, please read note 2.1
Moderator:	VAXAXP::BERNARDO

Created:	Wed Jan 22 1997
Last Modified:	Fri Jun 06 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	703
Total number of notes:	3722

543.0. "lib$do_command problem on ALPHA" by DPPSYS::BOLLAND () Mon Apr 28 1997 11:43

    
            I'm having a problem with the lib$do_command routine.
    
            I have a program which has a call to lib$do_command which runs
            a command file which sends me a mail message.
    
            When I compile and run my program on a VAX everything works OK, 
            the mail is sent, the program terminates, and I'm left at the $
    	    prompt.
    
            When I compile (/standard=vaxc) and run my program on an ALPHA
            the mail is sent but the program does not terminate it just hangs.
    
            I've tried LIB$SPAWN to see if I was returned to the calling
    	    program and the same thing happens.
    
            Anyone idea ideas ?
    
    
                    thanks,
                            stephen

T.R Title User Personal
Name Date Lines

543.1 Code Needed XDELTA::HOFFMAN Steve, OpenVMS Engineering Mon Apr 28 1997 13:31 23

T.R	Title	User	Personal Name	Date	Lines
543.1	Code Needed	XDELTA::HOFFMAN	Steve, OpenVMS Engineering	`Mon Apr 28 1997 13:31`	23
	<<< TURRIS::DISK$NOTES_PACK:[NOTES$LIBRARY]DECC.NOTE;1 >>> -< DECC >- ================================================================================ Note 2165.3 lib$do_command routine 3 of 3 XDELTA::HOFFMAN "Steve, OpenVMS Engineering" 16 lines 28-APR-1997 13:32 -< lib$do_command... >- -------------------------------------------------------------------------------- lib$do_command is a "chaining" function, it stuffs the command into the command buffer for execution, and causes the current image to exit. If the mail is sent, I'd look in the DCL procedure with a SET VERIFY (or f$verify lexical) to see where the hang occurs -- the image that called lib$do_command has already exited by the time the mail is sent... I can send you some C code which sends e-mail via the callable mail interface -- the C code will resolve this particular problem. This C code will not address your immediate question -- this question is better suited to VMSNOTES. if you cross-post, we will need the C and the DCL code needed to duplicate this problem. We will also need to know the OpenVMS version.

           <<< TURRIS::DISK$NOTES_PACK:[NOTES$LIBRARY]DECC.NOTE;1 >>>
                                   -< DECC >-
================================================================================
Note 2165.3                  lib$do_command routine                       3 of 3
XDELTA::HOFFMAN "Steve, OpenVMS Engineering"         16 lines  28-APR-1997 13:32
                             -< lib$do_command... >-
--------------------------------------------------------------------------------

   lib$do_command is a "chaining" function, it stuffs the command into
   the command buffer for execution, and causes the current image to
   exit.  If the mail is sent, I'd look in the DCL procedure with a
   SET VERIFY (or f$verify lexical) to see where the hang occurs -- the
   image that called lib$do_command has already exited by the time the
   mail is sent...

   I can send you some C code which sends e-mail via the callable mail
   interface -- the C code will resolve this particular problem.

   This C code will not address your immediate question -- this question
   is better suited to VMSNOTES.  if you cross-post, we will need the C
   and the DCL code needed to duplicate this problem.  We will also need
   to know the OpenVMS version.