B From:	MERC::"uunet!WKUVX1.BITNET!MacroMan" 27-APR-1993 00:26:20.39# To:	MACRO32 <MACRO32@WKUVX1.BITNET>  CC:	) Subj:	Re: Patching call to CLI$DCL_PARSE?   J >        I'm trying to find a way to grab onto all command lines passed toO >CLI$DCL_PARSE by *another* process for the life of the image they are running. N >Are the DCL callback routines stored in a library, or are they a part of each/ >process' permanent P1 space?  My thoughts are:  > C >Requesting process queues an AST to the target process which does:  > N >-       Add an image exit handler to delete the AST memory upon image rundown4 >-       Find local address for CLI$DCL_PARSE symbolC >-       Search through P0 image sections for calls to that address K >-       Change the code to call into the AST (kernel mode AST - no delete) N >        *before* calling CLI$DCL_PARSE.  My code would do it's thang and jump= >        into CLI$DCL_PARSE so the stack remains hunky-dorey.  > K >        Any thoughts on why this might not work, or better ways to achieve G >the same result?  I'm having a hard time figuring out how to determine L >what the address for CLI$DCL_PARSE is.  The requesting process will go intoO >action when an image-activation-audit-alarm is triggerred upon running certain N >images.  Is the alarm generated before or after the image fixup phase?  If itM >is before, am I gonna be unable to change the CLI$DCL... address because the N >fixer-upper will just change it back on me?  Any good thoughts on methods for; >scanning through the image sections in search of the call?   G CLI$DCL_PARSE (or any other CLI$xxx's) is _not_ a system service nor is G it a tranfser vector in a shareable image.  It's supported by an object F module in starlet.olb. and is linked into your image.  If you can find2 its address within an image, all the power to you!  J However, if you must know, it requests the services of the CLI by buildingI a cli service request block and then, calls SYS$CLI.  SYS$CLI _is_ a sys. 3 service vector and it's address is known and fixed.   H You could look into intercepting the SYS$CLI system service.  As for theI rest, the structure of the service request blocks and the service request % codes are in $CLIDEF and $CLISERVDEF.   - >What exactly *IS* the price of tea in China? " Who cares!  I buy mine in america!  H BJS- /Brian Schenkenberger/Schenkenberg@Eisner.DECUS.Org/Space for Rent/G     /VMS Software Support/Vitronics, Inc./Eatontown, NJ/(908) 542-0600/ F    /Independent Consult./Tmesis Consulting/Jackson, NJ/(908) 363-7551/E   /<VAXman or Schenkenberger>@Monmouth-ETDL1.Army.Mil/CIS: 70253,114/ 