MASM Book Interest?
Mike
It is out of print, but I could make it available again. Any interest
out there?
Mike Maddox
Richard C. Steiner
Sure! What machines does it cover?
--
-Rich Steiner >>>---> rste...@visi.com >>>---> Bloomington, MN
Written online using slrn 0.9.5.4!
The Theorem Theorem: If If, Then Then.
Mike Maddox
It covers Unisys (Sperry/Univac) 1100/2200 MASM (meta-assembly language)
programming. The Sperry 1100/2200 series first came to popularity as the
1108; my first exposure at University of Houston in 1970 was an 1108.
The book is an introduction to MASM, shares a number of techniques garnered
from over 15 years' experience with MASM (but specifically steers clear of
code that is hard to understand), and presents a style guide, as well. I
worked as a site support specialist and/or systems programmer for the Air
Force, the IRS, the US Dept of Agriculture, Bell Laboratories, the Texas
Dept of Human Services, a couple of Memphis commercial customers,
Petro-Canada, and other Sperry/Unisys customers. I poured all my expertise
and experience into this work. I hope it will work for you.
Mike Maddox
Mike Maddox
essentially any 1100 or 2200 since the 1110 and 1100/40. The book
specifically avoids the extended-mode instruction set. (Excluding these was
a condition of the permission I received from my employer, Unisys, to write
the book. At the time I wrote the book, extended-mode programming was
supported only as far as required to make Unisys softare products work.)
Hope that clears it up. The basic-mode instruction set worked so
consistently across a huge number of machines that it's easy to forget that
they were different machines!
William J. Toner
"Mike Maddox" <dma...@rmi.net> wrote in message
news:398F748E...@rmi.net...
Andrew Williams
ACOB, FTN and whatever) and really need some way forward on Extended-mode MASM
(and mixed-mode - interfaces between one and the other).
Does anyone know of any decent guides in this area?
Are you still bound by that agreement?
Mike Maddox wrote:
--
Mielipiteet omiani - Opinions personal, facts suspect, especially on my
http://home.germany.net/101-69082/samba.html
Simple Samba Solutions web page
Richard C. Steiner
>Richard -
>
>It covers Unisys (Sperry/Univac) 1100/2200 MASM (meta-assembly language)
>programming. The Sperry 1100/2200 series first came to popularity as the
>1108; my first exposure at University of Houston in 1970 was an 1108.
I guess I was more curious which machine-specific instructions (if any)
you might cover. For example, the 1110, 1100/40, and 1100/80 had various
Byte Move instructions that I think were removed in the 1100/90 machines
(and probably the 2200/400 and on) and replaced with much efficient Bit
Move instructions.
Does it also cover the basics of extended mode MASM coding? Or doesn't
that exist outside of Unisys? :-)
>The book is an introduction to MASM, shares a number of techniques garnered
>from over 15 years' experience with MASM (but specifically steers clear of
>code that is hard to understand), and presents a style guide, as well.
That sounds potentially very useful. I only dabble in MASM a little here,
but the only references I have here are my AIM manual and MASM Programmer
Reference from my 1100/80 days at Mankato State, and my old yellow copy of
_UNIVAC 1100 MASM PROGRAMMING - A Basic Approach_ by Richard Weisgerber
and John Odom which is good but very basic.
Richard C. Steiner
>Oops! Richard, you asked which machines the book covers. The answer is
>essentially any 1100 or 2200 since the 1110 and 1100/40. The book
>specifically avoids the extended-mode instruction set. (Excluding these was
>a condition of the permission I received from my employer, Unisys, to write
>the book. At the time I wrote the book, extended-mode programming was
>supported only as far as required to make Unisys softare products work.)
I see I should have read this before responding to the first message. :-)
That's unfortunate. I have a particular interest in extended mode, but I
realise that Unisys had a problem releasing that information, sometimes
even internally. Strange. :-)
David W. Schroth
Mike wrote:
>
> Hi folks - I wrote a book on 1100/2200 MASM programming some years ago.
> It is out of print, but I could make it available again. Any interest
> out there?
>
> Mike Maddox
I'd find it difficult to answer the question without having first seen
the book. My general rule of thumb is that any book teaching MASM
programming that teaches the student to use ER SNAP$ for debugging is of
dubious utility - not having seen your book, I don't where it fits with
regard to this criterion.
I suspect I'd be interested in looking at the book if I could find a
copy.
Regards,
David W. Schroth
Mike Maddox
extended-mode MASM during my last three years. I really enjoyed the almost 20
years I had with the company, but I have no dreams of going back to a market
that's just a shell of what it once was.
I doubt anyone in Unisys would attempt to enforce that agreement, but my knowledge
of extended mode was shaky at its best, and that was four long years ago. I've
done Windows programming, a smattering of OS/2 programming, lots and lots of
distributed systems performance work, SAS data analysis, and ANYTHING but Unisys
work since then.
I wish you the best of luck finding a guide to extended-mode MASM. Unisys's
suppression of the technology may make it hard.
Mike Maddox
Andrew Williams wrote:
> rats - I have been writing basic-mode MASM for 20 years now (subroutines to my
> ACOB, FTN and whatever) and really need some way forward on Extended-mode MASM
> (and mixed-mode - interfaces between one and the other).
>
> Does anyone know of any decent guides in this area?
> Are you still bound by that agreement?
>
> Mike Maddox wrote:
>
> > Oops! Richard, you asked which machines the book covers. The answer is
> > essentially any 1100 or 2200 since the 1110 and 1100/40. The book
> > specifically avoids the extended-mode instruction set. (Excluding these was
> > a condition of the permission I received from my employer, Unisys, to write
> > the book. At the time I wrote the book, extended-mode programming was
> > supported only as far as required to make Unisys softare products work.)
> >
> > Hope that clears it up. The basic-mode instruction set worked so
> > consistently across a huge number of machines that it's easy to forget that
> > they were different machines!
> >
> > Mike Maddox
> >
> > Richard C. Steiner wrote:
> >
> > > In article <398C8A0B...@rmi.net>, Mike wrote:
> > >
> > > >Hi folks - I wrote a book on 1100/2200 MASM programming some years ago.
> > > >It is out of print, but I could make it available again. Any interest
> > > >out there?
> > >
> > > Sure! What machines does it cover?
> > >
> > > --
> > > -Rich Steiner >>>---> rste...@visi.com >>>---> Bloomington, MN
> > > Written online using slrn 0.9.5.4!
> > > The Theorem Theorem: If If, Then Then.
>
Mike Maddox
book in loose-leaf, 3-hole punched format. I'll let each copy go for US$37.50
postage paid, first class, to a US address. Please respond to me privately and
I'll give you my street address for a check or money order.
I can make lots more on request. I will hold off re-producing the book (e.g.,
reformatting it in MS-Word and redoing the diagrams in Visio) until it looks as
if there will be substantially more interest. I can also publish it via
iUniverse.com or other Internet-based channel if that makes sense. (Of course,
I may have to reinstall my 5-1/4-inch diskette drive.... :-) )
Mike Maddox
dma...@rmi.net or
mike....@wcom.com (Worldcom)
William J. Toner wrote:
> Count me in as well.
>
> "Mike Maddox" <dma...@rmi.net> wrote in message
> news:398F748E...@rmi.net...
Doug Vaselaar
following:
>William, Richard and other MASM fans: I have a couple of copies of the MASM
>book in loose-leaf, 3-hole punched format. I'll let each copy go for US$37.50
>postage paid, first class, to a US address. Please respond to me privately and
>I'll give you my street address for a check or money order.
>
>I can make lots more on request. I will hold off re-producing the book (e.g.,
>reformatting it in MS-Word and redoing the diagrams in Visio) until it looks as
>if there will be substantially more interest. I can also publish it via
>iUniverse.com or other Internet-based channel if that makes sense. (Of course,
>I may have to reinstall my 5-1/4-inch diskette drive.... :-) )
>
>Mike Maddox
>dma...@rmi.net or
>mike....@wcom.com (Worldcom)
Count me in amongst the interested, unless Rich will let me make a copy...;-).
Doug Vaselaar
--
- Sig Comimg Soon to This Space -
kcs...@my-deja.com
"David W. Schroth" <David....@unisys.com> wrote:
> My general rule of thumb is that any book teaching MASM
> programming that teaches the student to use ER SNAP$ for debugging is
of
> dubious utility - not having seen your book, I don't where it fits
with
> regard to this criterion.
I agree, any MASM programmer worth their salt knows that SLJ TON$ is the
way to go. ;-)
Sent via Deja.com http://www.deja.com/
Before you buy.
Mike Maddox
overlap, moved on to Unisys World in 1987. I worked with a number of other
publications, including The WordPerfectionist (through two publishers),
Corel Magazine, and Government Computer News--120 articles in all through
April of last year. It was the articles on the Windows programming
environment that netted me software tools I was able to learn to get myself
into a more promising market.
Changing careers in one's mid-40s can be wrenching, but it can also be
rewarding.
I used MASM extensively to write a multitude of tools for MFD maintenance
and inspection. And there's no better way to collect performance data from
ER SYSBAL$ (SIP). From my college classes in 1971 into the late 1980s, I
wrote thousands of lines of MASM for a wide variety of customers. I really
kind of miss MASM and the kind of control one has over the machine. With
the right temperament, MASM can be an art form. I've never gotten that kind
of feeling from C. (Heck, I still think of C as a fast way to generate
assembly code, although I never see it.)
Appreciation of that art form is what I tried to share in my book. I hope
others share that enthusiasm. There really is nothing like coding "right
down on the bare metal."
Thanks for recognizing me.
Oh, and by the way, what is your "real addiction"?
Mike
Steve J. Martin wrote:
> In article <398C8A0B...@rmi.net>, Mike <dma...@rmi.net> wrote:
> > Hi folks - I wrote a book on 1100/2200 MASM programming some years
> ago.
> > It is out of print, but I could make it available again. Any interest
> > out there?
> >
> > Mike Maddox
>
> I also remember some excellent articles on MASM programming style
> that Mike contributed to, if memory serves, Unisys World.
>
> I too would probably spring for a copy of the book, although these
> days I use MASM mostly as a way of turning system data structures (MFD,
> MCT, PCT, ALAT, etc.) into SGSs to feed my real addiction ...
>
> Cheers,
> Steve J. Martin
> http://www.sjmsoft.com
Steve J. Martin
Paul
wrote:
>kind of miss MASM and the kind of control one has over the machine. With
>the right temperament, MASM can be an art form. I've never gotten that kind
>of feeling from C. (Heck, I still think of C as a fast way to generate
>assembly code, although I never see it.)
I once used Unisys' 2200 C compiler to port an app. That C compiler
release was so buggy we had to 1) turn off optimization, and 2) look
at the generated MASM code to look for bugs. What sort of bugs did we
find? Things like Q3 quarter words being referenced as Q1, etc.
Years later, I was asked to debug a multi-threaded app coded in 2200
C. Could not find the cause, threads simply started and stopped
without regard to the semaphores that were in use, Wish it was written
in MASM instead, and the whole thing would have taken a lot less time.
Steve J. Martin
Mike Maddox <dma...@rmi.net> wrote:
<snip>
>With the right temperament, MASM can be an art form.
> Oh, and by the way, what is your "real addiction"?
My real addiction, Mike, is SSG (writing Symstream skeletons). It
can also be an art form!
Regards,
AwfulAlex
Regards
AwfulAlex
awfu...@planetpastel.com
Mike Maddox
fact that it's block-structured is no more a guarantee of well-written code
than the "self-documenting" nature of Cobol. It takes the same kind of
mental discipline to create readable code that MASM takes.
What fascinated me about SSG is that it demands a special type of thought
process, essentially thinking on two levels at once (SSG and the output ECL
or whatever). You either start crazy, or it makes you crazy....
Mike
Mike Maddox
Please write me privately at dma...@rmi.net if you would like ordering information.
Thanks!
Mike Maddox
Erwin Richard
--
Erwin Richard
http://erwin.richard.net
"Mike" <dma...@rmi.net> schrieb im Newsbeitrag
news:398C8A0B...@rmi.net...
mpaulb...@gmail.com
> Hi folks - I wrote a book on 1100/2200 MASM programming some years ago.
> It is out of print, but I could make it available again. Any interest
> out there?
>
> Mike Maddox
Mike... are you still around and do you still have a copy of the book?
- Paul
Marc Wilson
<e1bc035a-4378-40c0...@googlegroups.com>::
--
Marc Wilson
Cleopatra Consultants Limited - IT Consultants
Fernrhoyd, Chester Road, Alpraham, Tarporley, Cheshire CW6 9JE
Tel: (44/0) 1829 262696 Tel: (44/0) 161 408 6449
Fax: (44/0) 844 779 0968 Mobile: (44/0) 7973 359850
Skype: cleo-marc Mail: enqu...@cleopatra.co.uk
Web: http://www.cleopatra.co.uk
Registered in England and Wales no: 2588943 VAT Reg: 561 1182 69
Registered office: St George's House, 215-219 Chester Road
Manchester M15 4JE
https://plus.google.com/100816173414569062406
ose...@gmail.com
> Hi folks - I wrote a book on 1100/2200 MASM programming some years ago.
> It is out of print, but I could make it available again. Any interest
> out there?
>
> Mike Maddox
Did you ever print more copies of your MASM book?
Jamie O'Sell
inter...@gmx.net
Louis Krupp
It looks like there's more bad news:
https://www.linkedin.com/in/michael-maddox-0034733b/
https://www.shrineofremembrance.com/michael-d-maddox/
However, whitepages.com links Mike Maddox to Aiden G. Koss, and here's
*his* LinkedIn profile:
https://www.linkedin.com/in/aiden-koss/
It's a long shot, but you could contact Mr. Koss and ask him if he was
in fact related to Mike Maddox and then ask if Mike left any documents
behind.
Louis
slax...@gmail.com
I'm trying to learn what I can about Unisys MASM, and saw mention of Mike Maddox's "Unisys 1100/2200 MASM" book (https://openlibrary.org/books/OL11697171M/Unisys_1100_2200_MASM).
Apparently another resource is "UNIVAC 1100 MASM PROGRAMMING - A Basic Approach" by Richard Weisgerber and John Odom.
Are either (or both) of these books available from someone in this group? It sounds like they could be really helpful.
Thanks,
Scott Adams
Scott Lurndal
this document interesting:
http://bitsavers.org/pdf/univac/1100/History_and_Evolution_of_1100_2200_Mainframe_Technology_Nov90.pdf
And this, for old info about MASM
http://bitsavers.org/pdf/univac/1100/asm/UP-8453_MASM_Programmers_Ref_1977.pdf
Stephen Fuld
architecture/instruction set, etc. (perhaps to write programs in
assembler, or just to learn about the architecture) or are you trying to
learn the details of the MASM program, including how to define "Proc"s
(Macros), details about how the multi pass nature of the program works,
etc. (this pretty much assumes you already know the instruction set, etc.)
If the first, then you really don't need to know a lot about the second.
A few concepts are enough, and they are pretty simply stated and
applied. Also, you should get to know the XPA Instruction Processor
PRM. The MASM manual doesn't cover what the instructions do, but rather
what the MASM processor does.
All the manuals are available free for the download it the Unisys web
site. I think registration is required.
--
- Stephen Fuld
(e-mail address disguised to prevent spam)
Scott
Regarding your question, it's the latter. There's a need to understand what instructions do (for example, I assume "LA" is Load Address), and how MASM packages PROC's and such together.
I've seen references to the "AIM" (Assembly Instruction Mnemonics Supplementary Reference) documentation, and I assume is the similar to (or is superseded) by the XPA Instruction Processor PRM (I guess XPA is the architecture the late generation 2200's are/were using).
I didn't find XPA Instruction Processor Programmer's Reference Manual readily available on the Unisys site.
Thanks,
Scott
inter...@gmx.net
LA is Load A-Register.
Names change frequently in the 2200 world. My paper manual from 2002 calls itself "XPA Instruction Processor PRM, 7833 4083-xxx" (xxx is the revision number), my more recent PDF is "ClearPath OS 2200 Instruction Processor PRM, 3850 7802-xxx. AIM was another name which was used at some point.
You will notice that most instructions can run under (E)xtended or (B)asic Modes, there is a massive difference between the two and I'd suggest starting with Basic Mode.
I can't imagine trying to learn this stuff without a running 2200 and some example routines, Basic Mode subroutines need to follow the conventions of their <ACOB / FTN / whatever> calling programs and you would need to read the appropriate manuals there.
Stephen Fuld
part means. Procs are what MASM calls what other systems call macros.
They are a way to generate say a sequence of assembler instructions.
They are not "packaged together" You need to understand basic assembler
before you get to procs.
> I've seen references to the "AIM" (Assembly Instruction Mnemonics Supplementary Reference) documentation, and I assume is the similar to (or is superseded) by the XPA Instruction Processor PRM (I guess XPA is the architecture the late generation 2200's are/were using).
>
> I didn't find XPA Instruction Processor Programmer's Reference Manual readily available on the Unisys site.
https://public.support.unisys.com/search2/DocumentationSearch.aspx?ID=1154&pla=ps&nav=ps
You might not be able to get there directly as it is past the agree to
terms page. If this doesn't work, start at www.unisys.com, the go to
support, then Documentation Libraries, then Access Documentation.
Then select
"ClearPath Forward OS 2200 Servers and Software"
then
"OS 2200 Server Products"
pick say "Dorado 8400 Series"
then "ClearPath OS 2200 Release 18.0"
Then "ClearPath and OS 2200 General"
and finally "ClearPath OS 2200 Instruction Processor Programming
Reference Manual"
That is a PDF of the manual.
There are slight differences in the different releases, but for the
basic stuff, this should be fine.
es
I've just cleaning my place and found a copy of Mike's Programming Guide. Drop me a note (prefer email) if interested. Rgds
Cherngchai Sangklai
Thanks,
Cherngchai
es
Cherngchai Sangklai
I'm interested in MASM and DMS 1100 to.
Thanks,
Cherngchai
Bill Gunshannon
>
> I'm interested in MASM and DMS 1100 to.
>
bill
Cherngchai Sangklai
There are some companies. My last job was joining Unisys DBA, DB2 DBA and MS SQL DBA to convert to MS SQL server and created SSRS reports to look the same. I did not believe I could do it. There were so many store procedures. Many thing were in-house. I could not remember even how to compile and map. I'm refreshing my skill set via PS2200. :) My first job with UNIVAC I followed student guide and up and ran. :)
Cherngchai
Cherngchai
Stephen Fuld
There is at least one change; It is now called DMS 2200. :-)
The DDL language manual says it refers to level 20R3. I have no idea
how much it has changed since 8R2, but the date on the manual is 2010.
inter...@gmx.net
This all happened around the time Sperry became Unisys so I can't remember the differences between the two but they were relatively minor.
Did 8R2 have the TIMER background run controlling the common Dbank? 8R3 certainly did. 8R3 could also be set up for single-thread mode, fast updates with physical exclusive use rather than any other kind of locking. It did not work very well with TIP-DMS files (no X-Use with TIP, fixed file numbers for the TIP Quick-Look files so only one run at a time was possible).
9R1 was released while the 8R3 versions were still being maintained, this was the first UDS level. I never used that level but did use 10R1.
The UDS model has the following components:
- UDSC (UDS Control)
- RDMS (Relational DB)
- DMS (optional)
- DD (Data Dictionary) subsequently called UREP (Universal Repository, uses RDMS)
- SFS (Shared MSAM files, most sites did not install it)
- MCB (Message Common Bank)
All run together with a unified Locking / Recovery / Rollback mechanism using IRU (Integrated Recovery Utility), something which requires a large number of common banks.
The products UDSC, RDMS, DD/UREP, DMS and SFS were always installed together in that order, a new level of one meant a new level of the others (except SFS?). Most of the time a new IRU level was also necessary, the MCB was more independent for years.
Most DMS levels were virtually unchanged from their predecessors, there was a lot of activity on the UDSC, RDMS and IRU fronts.
I can't remember when UDSC and RDMS were converted to Extended Mode, the IRU went that way around 2003 and the MCB around 2017 which was far too late.
Most timestamps have been converted to Double-Word Nanoseconds-since-1899-12-31 because TDATE$ only handles up to the end of 2027. There is a TDATE$ replacement which is (days-since-1899-12-31, seconds), that should maybe have been introduced earlier.
The IQ+ DMS Database Reorganisation Suite still uses DMS 8R3 Single-Thread mode even now, not sure how that works with the TDATE$ problems.