Jim,
1) BRMS does NOT see each of the 4 TAPXX devices, only the library as TAPMLB01.
The stand alone devices actually remain varied off, accessed via the library.
TAPMLB01 VARIED ON
TAPMLB02 VARIED OFF
TAPVRT01 VARIED ON
TAP01 VARIED OFF
TAP02 VARIED OFF
TAP03 VARIED OFF
TAP04 VARIED OFF
TAPMLB01 VARIED ON
TAP02 OPERATIONAL UNPROTECTED
TAP03 OPERATIONAL UNPROTECTED
TAP04 OPERATIONAL UNPROTECTED
TAP01 OPERATIONAL UNPROTECTED
2) Although 4 devices available, I have BRMS configured only to use 1 device.
Parallel device resources:
Minimum resources . . . . . . . . . . 1
Maximum resources . . . . . . . . . . 1
I5/OS actually does the request to mount the volume, BRMS is out of the picture at this point.
I've seen where if volume is already loaded in a drive from a previous job, and a new request requires the same volume,
a different TAP device may be selected.
Volume is unloaded from one device, loaded into the newly selected device.
Neither i5/OS nor BRMS know what volumes are loaded in the library devices.
3) SST only showing normal 63A0FFF6 Statistic Tape volume statistics logged (no action required)
With the new tape technology, the actual drive itself handles 99% of the tape errors, most never make it to i5/OS.
Paul
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jim Oberholtzer
Sent: Thursday, April 16, 2015 9:45 AM
To: 'Midrange Systems Technical Discussion'
Subject: RE: Possible TAP02 drive issue
Paul,
Are the devices set in BRMS Backup Devices? If there are multiple I think BRMS is going to grab the first one available where it can match the device
and an available tape cart. Then it pays attention to the parallelism
that's set.
I don't know of another way to find the device that was used, but I have to wonder if that is in the BRMS database somewhere that we could run and SQL to find it.
Maybe post a question on KnowledgeWorks and let Mervin pipe in?
You might be correct about the device, assuming it's been cleaned; it might
be getting out of alignment. What do the stats in SST say about it?
--
Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Steinmetz, Paul
Sent: Thursday, April 16, 2015 8:35 AM
To: 'Midrange Systems Technical Discussion'
Subject: Possible TAP02 drive issue
I noticed that both backups from 2 different LPARS took extra time, longest they ever ran.
No errors logged on the 3573 Tape library or on either LPAR.
I reviewed BRMS log, each library took a bit longer than normal.
Additional research revealed that both LPARS used TAP02.
Previous nights, a different TAP device was used.
Our config is Power7 740 8205-E6C, V7R1.
BRMS
3573 LTO5 with 4 HH FC drives.
1) Is there an easy way to determine which TAP device is used daily, for both saves and/or dups?
To the best of my knowledge, you can only see which TAP device is used at the end of the CPI6705 message.
Message ID . . . . . . . . : CPI6705 Severity . . . . . . . : 10
Job . . . : BRMCHOB06 User . . : PRODUCT Number . . . . : 324839
Date sent . . . . . . . . : 4/15/15 Time sent . . . . . . : 18:55:21
Program . . . . . . . . . : Q1AXCMD Area . . . . . . . . . : *BKU
Message . . . . : 12 blocks processed for sequence 51510, volume 001073,
on device TAPMLB01.
Cause . . . . . : 12 blocks were processed for file label CHRISV, sequence
51510 for volume 001073 loaded on device TAPMLB01. The maximum block size
is 262144. The tape file was opened at 04/15/15 18:55:21 and closed at
04/15/15 18:55:21. The total time the file was open was 0 seconds. If the
device is a tape library the cartridge is 001073 and the resource is TAP02.
2) I suspect TAP02 is having an issue, possibly doing retries within the drive. These retries are not logged, but would explain for longer run times.
Thank You
_____
Paul Steinmetz
IBM i Systems Administrator
Pencor Services, Inc.
462 Delaware Ave
Palmerton Pa 18071
610-826-9117 work
610-826-9188 fax
610-349-0913 cell
610-377-6012 home
psteinmetz@xxxxxxxxxx
http://www.pencor.com/
midrange.com
