|
The fact that .0 starts with "our customer" is a good
clue that you should file an IPMT.
This is almost certainly a customer configuration issue.
One would need to see the contents of the file lee.com
Such things take time. IPMTs give a 'charge number' for
the time invested.
That said...
I am not the Rcommands maintainer, but I did just
fix a series of bugs in the Rcommands. I know of
nothing such as you report. This would be a
new situation.
RSH is used in the build of UCX for Alpha, so we
are pretty sensitive to it being broken ;-)
Two things that you can check:
1) You could check that the
sys$sysdevice:[ucx$rsh]ucx$rsh(d?)_startup.com is the
same as the one in the UCX 4.1 kit. If this was a new, clean
installation, this is probably so. If UCX was upgraded
from a pre-existing version, it is possible that an old
file was left around. Now, I know of no changes in this
file from UCX X.X to 4.1, but there may have been.
2) (John G. please keep me on the straight and narrow here).
For complex reasons, some of the Rcommands do not like
keyboard input/activity while they are processing. That
is typeahead at the keyboard can mess-up (technical term)
the command. I'm not sure if RSH is one of these.
I hope this helps,
Lee
|
| re .3. Actually I upgraded from UCX 3.3 to 4.1 on my Alpha just to
play around with this problem. It seems that the UCX$RSHD_STARTUP.COM
file did change from 3.3 to 4.1. The new file is
$ ! UCX$RSHD_STARTUP.COM
$ !
$ ! Copyright (c) Digital Equipment Corporation, 1990, 1992, 1996
$ ! All Rights Reserved. Unpublished rights reserved
$ ! under the copyright laws of the United States.
$ !
$ ! The software contained on this media is proprietary
$ ! to and embodies the confidential technology of
$ ! Digital Equipment Corporation. Possession, use,
$ ! duplication or dissemination of the software and
$ ! media is authorized only pursuant to a valid written
$ ! license from Digital Equipment Corporation.
$ !
$ ! RESTRICTED RIGHTS LEGEND Use, duplication, or
$ ! disclosure by the U.S. Government is subject to
$ ! restrictions as set forth in Subparagraph (c)(1)(ii)
$ ! of DFARS 252.227-7013, or in FAR 52.227-19, as
$ ! applicable.
$ !***************************************************************
$ !
$ ! Parse out the BG devices for error and output, and the command
string
$ !
$ set noverify
$ on error then goto exit
$ sys_net = f$trnlnm ("SYS$NET")
$ s = f$locate ("$" , sys_net) + 1
$ l = f$length (sys_net)
$ z_net = f$extract (0, s-1 , sys_net)
$ s_command = f$extract (s, l-s , sys_net)
$ z_net = f$extract (0, s-1 , sys_net)
$ l1 = f$length (z_net)
$ s1 = f$locate (":" , z_net) + 1
$ ss_bg1 = f$extract (0, s1 , z_net)
$ ss_bg2 = f$extract (s1, l1 , z_net)
$ if ("''ss_bg2'" .eqs. "") then ss_bg2 = ss_bg1
$ !
$ !Now:
$ ! ss_bg1 has the output device,
$ ! ss_bg2 has the error device, and
$ ! s_command has the command.
$ ! Allocate the devices so they stay around, define the output and
execute
$ ! the command. Wait a bit so output buffer is flushed.
$ !
$ alloc/nolog 'ss_bg1'
$ alloc/nolog 'ss_bg2'
$ if ss_bg1 .nes. ss_bg2 then define sys$error 'ss_bg2'
$ define sys$output 'ss_bg1'
$ write sys$output ""
$ 's_command'
$ write sys$output ""
$exit:
$ exit $status
$
The old file had a $ WAIT 00:00:01 just before the $EXIT:
I wish I had saved it before upgrading.
Do you think this might make a difference?
|
|
Hi all,
one customer (check Nice call #5500) has the same RSH pb highlighted under .0
using the following configuration:
RSH-clnt RSH-srv
- OVMS AXP V6.2-1H3 - DECBrouter90 2TA
- UCX V4.1-ECO4 - Firmware 10.3.17
*** WARNING: first UCX installation ;-(
TCP traces attached to #5500 report the same RSH behaviour described under .0
More informations from UCX-Engineering ? Should i IPMT ?
Did you already IPMT ? If yes, which CFS nr ?
Many thanks in advance.
gianbattista 760-2717
|