Unfortunately I can't really answer your question, but I am familiar with
STK silos and with ADSM V2 Enhanced Server for AIX.
Since you haven't gotten any answers to your question, I will hazard a
guess:
I am sure the problem is NOT the STK robot microcode. The robot microcode
would affect only the movement and mounting of tapes with the robot arm, not
the reading of tapes. Once a tape is mounted, ADSM reads tapes directly
using the operating system device drivers, and the robot is no longer
involved.
On your AIX system, if you enter the command lsdev -Cctape, you will
probably see the device drivers for your Timberline drives listed as
something like "OMI Advantape Twin Peaks Tape Drives". These AIX device
drivers are used to write tapes on your AIX system. These drivers do not
come from IBM; they came from a company called OMI and were installed as
part of ADSM ENhanced Server.
Once your tape is mounted on your OS/390 system, ADSM on MVS will try to
read the tape using MVS device drivers (or what corresponds to a device
driver on MVS). If the OMI driver on AIX and the MVS device driver are not
compatible, you could get an "invalid block header" message.
I know that for DLT drives, there was an incompatibility between the OMI
device drivers for DLT on AIX, and the ADSM V3 for AIX device drivers from
IBM, and it caused an "invalid block header" error. A fix to the ADSM V3
server was required to correct it.
Anyway, I really think you should report this error to ADSM defect support.
I think only the ADSM support group is going to be able to tell you whether
this is a bug, or an unsupported configuration.
Anybody else out there find a flaw in my logic?
************************************************************************
Wanda Prather
The Johns Hopkins Applied Physics Lab
443-778-8769
wanda_prather AT jhuapl DOT edu
"Intelligence has much less practical application than you'd think" -
Scott Adams/Dilbert
************************************************************************
> -----Original Message-----
> From: Mariajo Rodriguez Canales [SMTP:mari_jose AT ES.IBM DOT COM]
> Sent: Thursday, March 11, 1999 4:32 AM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Silo 9310 shared between ADSM AIX and MVS
>
> Hi everybody, could anybody help me?.
>
> I have a customer who has a Silot STK 9310 shared between an ADSM AIX
> Server and MVS. They are using ADSM Enhanced Server for STK as an
> interface
> between AIX and MVS for tape mounts. ADSM AIX is using four Timberline
> drives for backup of files from clients. ADSM AIX Server is V2.1.06 and
> now they are migrating to an ADSM MVS Server V3.1.2.
>
> After installing ADSM server on OS/390, I tried to export information from
> Data Base in AIX Server (admin and policy information), to a tape
> controlled by ADSM on AIX. It worked, but, when I tried to import that
> tape
> on ADSM OS/390, I got several error messages, identifying an invalid block
> header on device where the volume tape is mounted. ADSM on MVS dismounts
> the volume and IMPORT ends with a failure of internal error encountered in
> accessing data.
>
> I don't know which the problem is. Is that an export on ADSM version 2
> can't be imported on ADSM version 3 server?. Is the problem that an export
> on AIX platform has a different block header information than on MVS
> platform?. Do we have to update microcode on STK Silo for version 3
> server?. Or maybe the problem is a bad definition of device classes
> between
> server on AIX and server on OS/390.
>
> The device class definitions are the following:
>
> AIX Server: Devclass= CINTA_STK Devtype=STK Format=STK9490
> Library=Robot Libtype=SSI
>
> OS/390 Server: Devclass=CINTA_STK Devtype=CART UNIT=3490
>
> Are they compatible? any suggestions?.
>
> Please, if anybody could help I would be very pleased, because we don't
> have a lot of time and my customer is waiting for an answer.
>
> Thank you very much,
> Mariajo.
>
>
> Marma Josi Rodrmguez Canales
> Dpto. Gestisn de Sistemas y Redes - IBM
> e-mail: mari_jose AT es.ibm DOT com
> Tf: 91 - 397 70 19
|
