I will be replacing the 2 physical disk drives in a shadow set
shortly.

The easiest way I can think of is to:

1. Dismount dka100:
2. Power down
3. Swap out dka100:
4. Reboot on dka0:
5. Merge the shadow set
6. Dismount dka0:
7. Power down
8. Swap out dka0:
9. Reboot on dka100:
10. Merge the shadow set

Is there a better way?

I have a need to set up a VAX test environment with 4GB drives. I have
a VAXstation 4000-60 available as the test bed. Unfortunately, I do not
have narrow RZ29 drives.

I do have several RZ29B-VWs available.

I know I can't use RZ29B-VWs in a BA350. (I tried it anyways, it still
doesn't work.)

I set up a BA356 with a BA35X-MG (8 bit) card. (There are previous
usenet reports of this working with RZ29B-VWs and a MicroVAX 3100/98.)

With the BA35X-MG card, the VAXstation 4000-60 can still only see narrow
drives in the BA356. It does not see the RZ29B-VWs, even if one of
these is the only drive in the chassis.

The BA356 appears to be terminated correctly. It has a 16 bit
terminator behind slot 1 and no card behind slot 7.

Can anyone provide a suggestion on how to get this to work? Is there
some switch setting I am missing?

Thanx!

--
-----------------------------------------------------------------------
Chris Scheers, Applied Synergy, Inc.

From: Chuck Moore hotmail.com>

Which port on the WY-160? This page looks more useful than yours:

http://www.wyse.com/service/support/kbase/Intface1.asp?Q=17

From: Chuck Moore hotmail.com>

"[M]y Alpha" is not a well-defined object.

Knowing nothing about how you're connecting this thing, I'd worry
more about the cable and the speed settings than I would about the
personality. What do "show term tta0" and "show term ttb0" say? Have
you tried both ports? What are the terminal settings?

Hi,

If anyone out on this group has a Wyse-160 connected to an Alpha/Vax,
please contact me. I've not been able to get my Wyse-160 working.

My Wyse-160 is connected to serial port 1 of my Alpha (the upper one
of the two that came with the Alpha). I normally connect my VT420 to
this port for booting the system, so I know the port works. The
Wyse-160 is set for VT220-8 "personality" with a VT220 ID (see
http://www.wyse.com/service/support/kbase/Setup1.asp?Q=17 section
"General Level" if you're wondering what a "personality" is). I've
tried VT220-7 and VT100, with no results.

Chuck

Does anyone have some examples of extracting jpg, doc,txt files from
an Oracle BLOB field under OpenVMS using ProC?

I have put in some requests re this over in the Oracle groups, but
99.999%% of the people
there are Unixers/Windowers and many things do not apply ( or other
things like setting logicals DO!) to OpenVMS!

bob y

I think the answer is 'no' but I thought I'd ask. Since DSPP
discontinued the Alpha media kit as part of the service, severely
downgrading their usefulness to us, we only get very rare updates.
Usually when a new OS release comes out we'll get the next quarterly
kit.

OpenVMS Alpha V8.3 includes DCPS 2.5 on the layered products disk.
I've been asked to see if getting V2.6 is possible without spending
unhealthy gobs of money on a CONDIST set.

If it still isn't I'll just tell them they need to shell out some more
cash.

I'll echo an earlier post here on this subject; it would be awfully
nice if HP made layered products that are licensed with the OS
available without spending so much on a media kit.

Thanks

Rich

From: Pierre gmail.com>

You mean like this?

[.$(DEST)]ZIPCLOAK.EXE : [.$(DEST)]ZIPCLOAK.OBJ \
$(LIB_ZIPUTILS) \
$(OPT_ID) $(OPT_FILE)
$(LINK) $(LINKFLAGS) $(MMS$SOURCE), -
$(LIB_ZIPUTILS) /include = (GLOBALS) /library, -
$(LFLAGS_ARCH) -
$(OPT_ID) /options

(I tend to use "\" in the dependencies, and "-" in the (DCL) action
lines, but I may be eccentric.) You may be trying to solve problems
which do not exist in MMS/MMK.

------------------------------------------------------------------------

AEF yahoo.com> wrote on 02/28/2008 10:58:27 AM:

From: Pierre gmail.com>

That may depend on what you mean. I don't use it on VMS, but I'd
expect GNU "make" to act more like a UNIX "make" than, say, MMK. MMK,
like MMS, needs more white space in some places than is typical in a
UNIX "make" file, because ":" is different/special on VMS. For example,
"target : source", instead of "target: source".

Define "unix syntax". (I also know nothing about the other
"make-xxx" programs in that collection.)

Possibly relevant:

http://forums.itrc.hp.com/service/forums/questionanswer.do?threadId=1207552

(If you get lucky, and the ITRC forum is less messed up than usual.)

------------------------------------------------------------------------