Does anyone have specific information on DEBE? Which system it ran on,
about what time-frame it occupied, what functions it actually had? I
would like to look at some specific documentation for it, but don't
have enough to go on yet.
This is for a comparison I'm making between integrating single-function
modules into a custom application vs. creating a single application that
does the integration for you. My premise is that the advent of graphical
user interfaces has led to a decline of script language integration,
resulting in some of the very large programs that are presently seen on
X-windows, Windows 3.1, and OS/2.
Comments?
Brian Cooper
b...@infonaut.com
Rumor has it that our friend "dd"--far from being ++(cc)--_really_ means
"Do DEBE". Examination of the command-line switches _does_ tend to imply a
non-Unix origin.
Adam
--
ad...@io.com | ad...@phoenix.princeton.edu | Viva HEGGA! | Save the choad!
"Double integral is also the shape of lovers curled asleep" : Pynchon
64,928 | TEAM OS/2 | "Ich habe einen Bierbauch!" | Linux | Fnord
You can have my PGP passphrase when you pry it from my cold, dead brain.
Ran on IBM mainframes. Mostly used with MVS, but I last used it about 10
years ago on VM. Couldn't be beat for what it did.
[old-timer folklore warning--"you've got it easy; when I started..."]
Back in the Olde Days, information was stored on "Count Key Data" disks--you
could have a different block length for each physical block of data on the
disk track. (Compare with, say, MS-DOS, where each disk block is 256 bytes
long, or most UNIXes, where block size is always 512 bytes). Back then,
every patch of oxide was valuable, so you'd physically format the disk data
for optimal retrieval, and be careful not to overflow the disk buffer on the
32K of main memory your program and data areas would have to fit in.
You also had problems like: you'd have to know the maximum size your file
could become, because OS would allocate that many contiguous disk tracks
(and cylinders) for that particular file. (Well, you could start small and
add "secondary allocations", but you were limited to no more than 16
"extents").
But to copy files around, or move them to and from tape, was a big challenge
since you had to preserve the physical format. And you usually had to
submit a card deck to perform the job. And though the OS knew on disk where
the file was located (usually), it generally didn't know the physical format
of the data. So if you didn't maintain the program that worked with that
particular file, you'd have lots of trouble just moving it from one place to
another. And recall that all the OS default actions were defined in 1964.
DEBE could analyze the data stored on a disk (or tape), and deduce the
format. It also had options to copy the file around various disks and
tapes. It could even move data from, say, a 3330 disk to a 3340 disk, which
had different track sizes (which meant that you sometimes had to rearrange
the physical records). Or you could print a report on the sizes of the
records, or a hex dump of the records. Or you could easily move data from
one tape to another. And you could use it (gasp) interactively on a
terminal. It did everything but ate, and was rumored to be named after the
author's daughter.
Today, in the Modern Era (post-1969), you have commands like "copy" or "od"
or "tar" that do the same thing. But back then, DEBE was it.
(The scary thing is, on MVS, much of this is *still* true. I used DEBE to
copy data from 3420 (9-inch) tapes to 3480 (cartridge) tapes.)
--
Eric Burch -- Loral Federal Systems -- Gaithersburg, MD
er...@lfs.loral.com usual disclaimers apply
imagine a " :-) " after each period above
[v]program called 'DEBE' which stood for 'Does Everything But Eat'. The
[v]article says that this was a system utility intended to be all-encompassin
BC[v]Does anyone have specific information on DEBE? Which system it ran on,
[v]about what time-frame it occupied, what functions it actually had? I
[v]would like to look at some specific documentation for it, but don't
[v]have enough to go on yet.
DEBE was a DOS/360 program. It would have run on S/360 Models 25 to maybe
50. Timeframe would have been middle 60's to say mid 70's. I think there
MAY have been a port to OS/360, but I don't think it ever became as
popular as it was in DOS. It was on the SHARE tapes, you might contact
SHARE or COMMON, the IBM mainframe user's groups.
---
* SLMR 2.1a * In the eyes of cats, all things belong to cats.
AS I recall the port was in the the other direction which is why the
DOS version was generally referred toi as DOS-DEBE. It was certainly
heavy used on OS-360. Those of you who grew up with Unix would not
believe how complex OS/360 and DOS/360 could make simple operations
like copying or dumping a file. DEBE reduced this type of operation to
something no more than 10 times as hard as using DD on a Unix system.
Bye
Erhard Vieth
------------------------------------------
Erhard Vieth, Ratingen, Germany - evi...@ibm.net
- 7100...@compuserve.com
also reachable at
Torsten Vieth - vie...@gismo.rhein-ruhr.de
>But - DEBE had a follow-on product named DITTO, to be used with VS/1 and
>MVS operating systems. It's still in use (under MVS/ESA) for some tape
>recovery operations (tape block patching or skipping etc.) or for browsing
>tapes with unknown file structures.
I was waiting for someone to mention DITTO. Someone ported it to
the UNIVAC 9400. I got my hands on the source, and turned it into
something semi-civilized by making the command names more consistent,
and allowed multiple parameters to be entered on a single line
instead of having to play "Twenty Questions" with the system.
I even got it handling sequential disk files.
When the 90/30 and OS/3 came out, DITTO resurfaced in the System
Utility (SU), original warty commands and all. I never did get
around to porting my 9400 version. But that's probably because
I was too busy writing my own assembler, since I was so grossed
out by theirs, which they ripped off from the DOS/360 one. I
couldn't stand the fact that theirs wasn't half a good as the
one I had already written for the 9300.
It sometimes makes you wonder what went on in those huge software
departments the big vendors had...
Charli...@mindlink.bc.ca
I used to be indecisive, but now I'm not so sure.