[Info-vax] GNV V2.1-2, DCL escape

[RobertsonEricW]

On Mar 22, 4:23 pm, RobertsonEricW <robertsoner... at netzero.net> wrote:
> On Feb 7, 2:26 am, "John E. Malmberg" <wb8... at qsl.network> wrote:
>
>
>
>
>
> > JBloggs wrote:
> > > from theGNVbash shell, one can  exec aDCLcommand, like so:
>
> > >  $dcl'show time'
>
> > > with Alpha 8.3, (all patches/eco's)
> > >GNV2.1-2 I see the following accvio:
>
> > >   $ @PSX$ROOT:[LIB]GNV_SETUP.COM
> > >   %DCL-I-SUPERSEDE, previous value of VI_SECTION has been superseded
> > >   $ bash
> > >   (gnv-bash)$
> > >   (gnv-bash)$dcl"sh sys/noproc"
> > >   %DCL-W-ACTIMAGE, error activating image SYS$COMMON:[SYSEXE]DCL.EXE
> > >   -CLI-E-IMGNAME, image file $1$DKA0:[SYS0.SYSCOMMON.][SYSEXE]DCL.EXE
> > >   -SYSTEM-F-ACCVIO, access violation, reason mask=28, virtual
> > > address=000000007FFD1160, PC=000000000000001A, PS=7FF9DEA5
> > >   (gnv-bash)$
>
> > > Has anyone run across this themselves,
> > > or better yet, know of a work-around?
>
> > EAGLE> @gnv$gnu:[lib]gnv_setup.com
> > EAGLE> bash
> > bash$dcl"show sys/noproc"
> > OpenVMS V8.3  on node EAGLE  7-FEB-2009 00:19:58.07  Uptime 252 03:21:35
>
> > EAGLE> dirgnv$gnu:[bin]bash.exe/date/size
>
> > DirectoryGNV$GNU:[bin]
>
> > BASH.EXE;1              1534   6-DEC-2006 17:52:19.67
>
> > I am not seeing an issue.
>
> > -John
> > Personal Opinion Only
> > -email address temporarily out of order, but monitoring newsgroup-- Hide quoted text -
>
> > - Show quoted text -
>
> I have just encountered this problem. In my case it was caused by
> installing the VMS83A_UPDATE V8.0 patch. I had to restore my system
> from backups in order to use this feature ofGNV. I have not had a
> chance to look at the release notes for this patch update to see why
> it might cause this problem. So, for right now I would advise you to
> restore your system to the state it was in prior to installing this
> patch. I am also going to post this problem to the HP support forum
> (just in case anybody their might care). When I find out more I will
> post another reply to this goup.
>
> Eric- Hide quoted text -
>
> - Show quoted text -

Everybody,

I am turning a very dark shade of crimson as I type this in. The
problem was not the patch! In order for GNV bash to function properly,
the path, GNU and PSX$ROOT logicals must be setup correctly. In
particular the GNV and PSX$ROOT logicals are setup in SYS$STARTUP:GNV
$STARTUP.COM which is one of the commands in my SYS
$MANAGER:SYSTARTUP_VMS.COM. However, before rebooting I had removed an
older version of Python for VMS (Python V2.52) and replaced it with a
new version of python for VMS (Python V2.54). However, this Python
upgrade required a change of the startup command in SYS
$MANAGER:SYSTARTUP_VMS.COM from @SYS$STARTUP:PYTHON252_STARTUP.COM to
@SYS$STARTUP:PYTHON254_STARTUP.COM. My blunder was ommitting this
necessary change before rebooting. So, when I rebooted,
SYSTARTUP_VMS.COM promptly exited when it could not find the startup
file for the old version of Python referenced in SYSTARTUP_VMS.COM (I
don't have a SET NOON in SYSTARTUP_VMS.COM). Having thus exited
prematurely, it never got to execute the GNV$STARTUP.COM. Thus not
configuring the necessary logicals for GNV bash and ultimately leading
to the observed access violation when attempting to execute a DCL
command from within GNV bash.

UGH!

My abject apologies for this errant post!

Eric