IBM Mainframe Forum Index
 
Log In
 
IBM Mainframe Forum Index Mainframe: Search IBM Mainframe Forum: FAQ Register
 

DASD Stress Testing.


IBM Mainframe Forums -> All Other Mainframe Topics
Post new topic   Reply to topic
View previous topic :: View next topic  
Author Message
Anuj Dhawan

Superior Member


Joined: 22 Apr 2006
Posts: 6250
Location: Mumbai, India

PostPosted: Tue Jul 17, 2012 11:15 am
Reply with quote

Hi,

This thread SPOOL VOLUMES ARE FULL' issue during a longtime job talks about DASD stress testing and that got me curious.

I did a bit of homework with google and end-up with Storage Calculations, DASD Utilization Tables -- these are not what I'm looking for. Looks like "DASD stress testing" is yesteryear thing - however, it'd be nice to hear back from who had been involved in this.

It looks like - when DASD were evolving they did test them on their I/O speeds, response time, their block sizes -- but is this all, or there is more to it.

Thanks for stopping by,
Back to top
View user's profile Send private message
dick scherrer

Moderator Emeritus


Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix

PostPosted: Wed Jul 18, 2012 5:55 am
Reply with quote

Hi Anuj,

In addition to what you mention, we intentionally tried to "break" new devices and device types by putting more of a load on them than would be seen in "real world" situations. Sometimes either a new device of an old model or some new "improved" device failed . . .

We also had some benckmark jobs that we ran on any new device or channel/device configuration to ensure critical systems would not be negatively impacted by the change.

d
Back to top
View user's profile Send private message
Pedro

Global Moderator


Joined: 01 Sep 2006
Posts: 2546
Location: Silicon Valley

PostPosted: Thu Jul 19, 2012 5:50 am
Reply with quote

It was fairly early in my career, so I do not recall all that we did.

Similar to Dick, our effort was to try to break new devices. If it did not break in the first week of testing, the new DASD was added to our scratch volumes, then possibly later for the SMS primary storage pools.

I recall having to write something on each byte of the track, on each cylinder. And doing so multiple times.

Sometimes we would find hardware errors with the read/write head.

Sometimes we found surface defects. When it cannot write to a track, an alternate is used. I think there were only 15 alternate tracks. And if you used most of them the first few day, the DASD was reported to the vendor.

Quote:
they did test them on their I/O speeds, response time, their block sizes

We never worried about those things.
Back to top
View user's profile Send private message
expat

Global Moderator


Joined: 14 Mar 2007
Posts: 8797
Location: Welsh Wales

PostPosted: Thu Jul 19, 2012 1:04 pm
Reply with quote

That's why there are SMS storage classes defined for defining required response times
Back to top
View user's profile Send private message
David Robinson

Active User


Joined: 21 Dec 2011
Posts: 199
Location: UK

PostPosted: Thu Jul 19, 2012 1:37 pm
Reply with quote

I rememer a long time ago when I was in Ops a sysprog "repairing" some damaged DASD. I was impressed at the time, but although it's not something I've ever done I guess it was just using ICKDSF to mark a track as unavailable.

Probably not something we ever do nowadays.
Back to top
View user's profile Send private message
Anuj Dhawan

Superior Member


Joined: 22 Apr 2006
Posts: 6250
Location: Mumbai, India

PostPosted: Thu Jul 19, 2012 4:20 pm
Reply with quote

Thanks for reading through.

dick scherrer wrote:
In addition to what you mention, we intentionally tried to "break" new devices and device types by putting more of a load on them than would be seen in "real world" situations. Sometimes either a new device of an old model or some new "improved" device failed . . .
Just a curious mind, what DASDs were in use that time? Not 3390,yes?
Back to top
View user's profile Send private message
expat

Global Moderator


Joined: 14 Mar 2007
Posts: 8797
Location: Welsh Wales

PostPosted: Thu Jul 19, 2012 5:03 pm
Reply with quote

Probably the old fixed platter types, 3330, 3350, older 3390, which could be physically removed from the drives
Back to top
View user's profile Send private message
Bill Woodger

Moderator Emeritus


Joined: 09 Mar 2011
Posts: 7309
Location: Inside the Matrix

PostPosted: Thu Jul 19, 2012 6:57 pm
Reply with quote

3301 Model 1 had removable platters :-) Two seniors swore to me that OPS lost an hour when they got one "stuck" half-in-half-out.

Even after all this time, I'd appreciate knowing if that was possibly true. I still think the little minkies were pulling-my-leg.
Back to top
View user's profile Send private message
expat

Global Moderator


Joined: 14 Mar 2007
Posts: 8797
Location: Welsh Wales

PostPosted: Thu Jul 19, 2012 6:58 pm
Reply with quote

Could have been a mechanical failure Bill, it did happen from time to time
Back to top
View user's profile Send private message
Robert Sample

Global Moderator


Joined: 06 Jun 2008
Posts: 8696
Location: Dubuque, Iowa, USA

PostPosted: Thu Jul 19, 2012 7:10 pm
Reply with quote

Back in my college days when I worked in the school's computer center, I used to mount 2314 disks, so I can tell you that the disks could get stuck (it was rare, but sometimes the hardware failed). And the noise they made when the power went off ... WOW! They had very strong relays that the disk arm motor pulled against. If the power went out, the relays yanked the arms off the platters before (theoretically) any physical damage could occur. They were quite loud. Once that happened, the IBM CE had to reset the relays before the drives could be powered up again. We kept a disk pack around where there had been a hardware failure. Hold the disk pack up to the light at the right angle, and you could see through the hole that went through all the platters.
Back to top
View user's profile Send private message
dbzTHEdinosauer

Global Moderator


Joined: 20 Oct 2006
Posts: 6966
Location: porcelain throne

PostPosted: Thu Jul 19, 2012 7:12 pm
Reply with quote

back in the early 70's i worked on a lot of ncr hardware.
they had removable discs,
problem was, you removed the dust cover then closed the cabinet.

needless to say, the discs would have read/write errors,
and since it was normally due to the dust
(or cigarette ashes from the operators)
not only was the platter physically scratched, it normally meant the read/write heads were also damaged.
compound that with an unknowing operator,
who would mount the unreadable disc in another unit (in an attempt to read the disc)
....
one night we lost 5 units to this silliness until I made it to the operations room
and flung the disc, frisbee-like, into a cement wall.
nobody said a word to me, we recovered and reran the previous days run, then ran the update for that night.
fortunately we had 20 units (actually, by this time only 15).

removable disc units - talk about planned-obsolescence.
Back to top
View user's profile Send private message
Akatsukami

Global Moderator


Joined: 03 Oct 2009
Posts: 1788
Location: Bloomington, IL

PostPosted: Thu Jul 19, 2012 7:40 pm
Reply with quote

About 30 or so years ago, I worked at a company that at one time had had a GE-235 computer. When it was finally scrapped, an operator took a disk "platter" (more like a cartwheel, IIRC) and made a tabletop from it.
Back to top
View user's profile Send private message
dick scherrer

Moderator Emeritus


Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix

PostPosted: Thu Jul 19, 2012 10:24 pm
Reply with quote

Hello,

Quote:
Just a curious mind, what DASDs were in use that time? Not 3390,yes?
Nope, not 3390's. . .

When i first began with the company they still had an old IBM 305 RAMAC system that still would run, but the "real" work had been moved off. I guess it was impressive when someone came thru the data center on a tour.

People were quite happy they were done upgrading from 2311s to 2314s. Then came the 3330's followed by the 3350's (the 50's did Not have removable disk packs) and later the 3380's and 90's (i was full-time consulting by then but was in contact, and even went back on contracts, until the company "went away" - still chat with several from the old days).

One of the operational challenges then was having many removable packs but only a few disk drives. . . And the scheduling was done manually . . .
Back to top
View user's profile Send private message
expat

Global Moderator


Joined: 14 Mar 2007
Posts: 8797
Location: Welsh Wales

PostPosted: Thu Jul 19, 2012 10:38 pm
Reply with quote

Dick, I'm pretty sure that the Memorex 3350's were removables
Back to top
View user's profile Send private message
dick scherrer

Moderator Emeritus


Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix

PostPosted: Thu Jul 19, 2012 11:30 pm
Reply with quote

Hi Expat,

Quote:
I'm pretty sure that the Memorex 3350's were removables

Might have been . . . We tried Telex but i don't recall having Memorex (we also had Telex tape drives for a while).

One configuration of the Telex (30's iirc, but maybe 50's) were in a "thing" that looked rather like a big washing machine that housed 4 drives. Knowing that when a load of laundry gets out of balance, the washer would "walk" across the room. We decided to try this on the Telex by throwing the heads back and forth to cause the same sort of vibration. Yup, it Was possible to move the unit.

We did find ways to change the speed the box moved on the floor (limited of course by cable length). When we decided we'd try to race 2 of the units, we were told that needed to cease icon_rolleyes.gif

ps. the Telex dasd did not last very long. . .
Back to top
View user's profile Send private message
Bill Woodger

Moderator Emeritus


Joined: 09 Mar 2011
Posts: 7309
Location: Inside the Matrix

PostPosted: Fri Jul 20, 2012 12:28 pm
Reply with quote

Our 3350s were Memorex. Definitely non-removable, although there could have been other models?

Whole place was "plug compatible" apart from the 3800 printers.
Back to top
View user's profile Send private message
Anuj Dhawan

Superior Member


Joined: 22 Apr 2006
Posts: 6250
Location: Mumbai, India

PostPosted: Fri Jul 20, 2012 2:24 pm
Reply with quote

I feel overwhlemed with the responses in this thread. Thanks for stopping by, icon_smile.gif

Regards,
Back to top
View user's profile Send private message
Anuj Dhawan

Superior Member


Joined: 22 Apr 2006
Posts: 6250
Location: Mumbai, India

PostPosted: Fri Jul 20, 2012 2:44 pm
Reply with quote

Pedro wrote:
Similar to Dick, our effort was to try to break new devices. If it did not break in the first week of testing, the new DASD was added to our scratch volumes, then possibly later for the SMS primary storage pools.
.
.
Sometimes we found surface defects. When it cannot write to a track, an alternate is used. I think there were only 15 alternate tracks. And if you used most of them the first few day, the DASD was reported to the vendor.
Thanks Pedro.

What the vendors were reported with - I mean, when one tried to load it and it broke - then what? As an observer, what next you could want - a sustainability with 'same load' or there was an entire statistical analysis on many other parameters too?


PS. These question might sound pretty loose-ended and with no dedicated goal. Well, Yes - I look at it as open discussion where I look forward to the experiences of the time when information was not so easily available. (read it as -- No internet).

Today I can (re)search in any "search engine", for that matter, you get the ready-made-code avaialble at times -- but how it happened when all this was not there, these "stories" interest me.

Hope I don't bother any one,
Back to top
View user's profile Send private message
Anuj Dhawan

Superior Member


Joined: 22 Apr 2006
Posts: 6250
Location: Mumbai, India

PostPosted: Fri Jul 20, 2012 4:00 pm
Reply with quote

Thanks expat.
expat wrote:
That's why there are SMS storage classes defined for defining required response times
But SMS is "software part", I was talking about "mechnical arm movement" or "actuator move" when I talked about the "response time" initially.
Back to top
View user's profile Send private message
expat

Global Moderator


Joined: 14 Mar 2007
Posts: 8797
Location: Welsh Wales

PostPosted: Fri Jul 20, 2012 4:17 pm
Reply with quote

Those were the days when storage management would analyse the dataset usage and then position datasets on physical volumes for performance reasons.
Back to top
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic View Bookmarks
All times are GMT + 6 Hours
Forum Index -> All Other Mainframe Topics

 


Similar Topics
Topic Forum Replies
No new posts DASD - non SMS - volser change - VSAM... JCL & VSAM 2
No new posts Related to Unit Testing Testing & Performance 2
No new posts IMS DB / DB2 simulator for ETL testin... IMS DB/DC 1
No new posts Rename dasd IBM Tools 11
No new posts Regression testing of date format con... CLIST & REXX 0
Search our Forums:

Back to Top