I didn't copy anything over or change anything. I'm running on exactly
the same z/VM 4.4 system on the z/9 that I ran on on the 9672, except
that at ipl time on the 9672, VM would see a 31 bit architecture and on
the z/9 it sees 64 bit. I didn't regularly mount tapes on the test lpar
from the robot, but I'm 99.999% certain that I have. I was able to load
a tape on a drive from the production system, still running on the 9672
using the NOASSIGN option and then read it on the test lpar, so I know
the test lpar can see the drives. I'm not sure how I would know if test
can see the robot. I'll find out in the a.m., tho, because I'm going in
for a Sunday a.m. test.
When the test lpar was ipl'd, however, the chpid with the robot and
tapes was not connected to the z/9. Perhaps at ipl time, not having the
robot online, hid it from subsequently connecting the chpid and tape
addresses. Morning will tell.
Jim
Steve Gentry wrote:
This is a multipart message in MIME format.
--=_alternative 005F33E505257270_=
Content-Type: text/plain; charset="us-ascii"
Hello. Are you sure you copied the various DATA files over or didn't
accidentally modify them?
RMCONFIG, RMBxxxxx, DGTVAUTH and DGTVCNTL.
The tape library and devices are on line? If you're running in an LPAR
can that LPAR see the
drives?
We are running on a z9, VM5.2 with a tape library and VM:Tape with no
problems.
Steve G.
Jim Bohnsack <[EMAIL PROTECTED]>
Sent by: The IBM z/VM Operating System <IBMVM@LISTSERV.UARK.EDU>
01/26/2007 09:50 PM
Please respond to The IBM z/VM Operating System
To: IBMVM@LISTSERV.UARK.EDU
cc:
Subject: RMSMASTR in 64 bits
We have just installed a z/9 and are in the testing stage, i.e. "what
works and what doesn't". The system is z/VM 4.4 since we are moving
from a 9672-G5 class machine. I have my test lpar running on the z/9
under z/VM 4.4 in 64 bit mode. Today, a path to the 3494 tape robot was
moved to the z/9 and I XAUTOLOG'd RMSMASTR to see if it would work and I
could control the 3494. RMSMASTR is unhappy about something. I'm
hoping that someone has seen the following and has a quick answer:
FSMRMBLC==> Diag 254 is
available
FSMBBC0505E Internal error from routine 2523, return code =
3
FSMBBC2028E The specified subsystem 03494 does not exist in VM real IO
config
FSMSMS3009E Errors have caused DFSMS initialization to
stop
FSMXXX0505E Internal error from routine 2522, return code =
3
FSMSMS3032I RMSMASTR is
stopping
RPICMS017I USER/RACF VM Racroute communication path has been
terminated.
Jim
--
Jim Bohnsack
Cornell University
(607) 255-1760
[EMAIL PROTECTED]
