s)
that has some case studies with examples of the power of this base-
and macro-language interaction HLASM's conditional assembly and
macro facilities. If you have access to SHARE proceedings you can
find it there.
John Ehrman
releases.
As I remember, the problem with adcons containing literals is that they can
lead to recursions such as A(=A(...)) and the like.
John Ehrman
' is valid, and the operand has value X'1FE'
DC 2X'FF' generates X''
DC 2*X'FF' is invalid because the operand is not a duplication factor
So I see no language "anomaly", but perhaps a lack of detailed explanation in
the Language Reference.
John Ehrman
Well, maybe not. I was laid off ("retired") by IBM last June, and managed to
get back to this list only a few days ago. I'll try to keep active if I haven't
forgotten too much.
John Ehrman
- Original Message -
From: "ASSEMBLER-LIST automatic digest system" <li
Another reason not to allow DC-type operands in immediate operands: consider
AHI 0,(N)X'F'
The Assembler can't tell that the instruction is indeed 4 bytes long.
I suppose it could do some acrobatics, but the cost vs. value seems excessive.
John
would try it!
John Ehrman
--
Date: Wed, 22 Feb 2017 16:18:38 -0500
From: Melvyn Maltz <zarf77...@blueyonder.co.uk>
Subject: HLASM anomaly
Immediate operands won't accept a duplication factor...why not ?
Can't find a
Rob Van der Heij noted:
>> Is the request you mentioned a SHARE requirement or an IBM RFE? In any
>> case, can you point us where to vote on that request?
>John referred to this RFE, I think
The original posting was by Sharuff Morsa in Hursley, which gave this link
and request:
Some materials that may be useful to teachers of IBM mainframe Assembler
Language are now available on the Marist College web site, along with the
text itself.
The two items are PDFs with (1) lecture slides for Chapters 1-8 (sorry, I
ran out of time before I could do the rest), and (2) pages
Two comments:
(1) Mike La Martina wrote
>One would think so but HLASM does not have scoped namespaces.
>My suggestions for such have been summarily dismissed.
Your suggestion wasn't "summarily dismissed" -- it's just that it would
require substantial internal modifications to the assembler.
Nope! I'm hoping I can find things to keep mind and body active. (Two of
the reasons I'm hoping we can get OKs to do the A.U. in San Jose.) Also
looking for occasional consulting gigs.
We do have some travels planned: Carmel Bach Festival last week of July,
and a "remembering D-Day tour to
The second edition of my Assembler Language textbook is available for
download at
http://idcp.marist.edu/enterprisesystemseducation/assemblerlanguageresources-1.html
The text is a PDF file (it's big: 1346 pages). The simple conversion and
I/O macros decscribed in Appendix B are also
Paul Gilmartin suggested...
>Given that the hardware now supports unsigned halfwords, perhaps
HLASM should accommodate. Perhaps HU'65535' or YU(65535).
Unsigned integer values are supported by HLASM,, but the syntax is
slightly different:
DC H'U65535'
John Ehrman
Michael Butz wrote:
>I am sorry i had multiple definitions of IBM
>Mapping macros IHAPSA IHAASCB
>Wonder why it didn't flag it as ** previously defined
It should; otherwise there's no way to locate the problem.
Lizette Koehler asked...
>Would it make more sense to change 0CL512 to 0LQ32 ?
>Does the 0CL512 place it on a quad word boundary?
C-type constants are always aligned on the next available byte, no matter
what the value of the Length attribute is.
Regards... John Ehrman
'll notify the HLASM team.
Regards... John Ehrman
appear in the final
assembled version of the program.
Second, a "determined" programmer can indeed decide on the correctness of
a such program; but it's much easier to let HLASM do the work for you.
I hope this helps clarify both situations.
Regards... John Ehrman
Definition).
ER is created from either an EXTRN statement, or from the operand of a
V-type address constant.
John Ehrman
Bob Netzlof wrote in response to a problem I posed:
Suppose the desired length is to be the value of symbol T
T EQU (F+1)*(256+A*(1-L)*65280)
Very elegant! (Much better than my solution.)
Regards... John Ehrman
For those needing something to think about
In the description of the TRTE and TRTRE instructions in the POP, there's
a table giving the expected length of the function-code table for various
combinations of the three bits named A, F, and L in the M3 mask field.
Your exercise:
Suppose the
-mail or posted on
the Assembler-List). But we do encourage discussion on the list!
John Ehrman
Peter Farley noted about ASMIDF (in part):
(Start)
The last time I used it, there was also no capability to directly debug an
executing batch job like z/XDC and other HLL language debuggers provide.
(End)
More recent versions of ASMIDF do support debugging of batch jobs.
Regards... John
Have any of the responders to the original query used ASMIDF, the debugger
in the High Level Assembler Toolkit Feature? It's tailored specifically
for assembler applications.
John Ehrman
conventions). However, I can’t seem to find a combination of
assembler options to cause it to create an object module that has lower
case csect/entry names. Is this possible?
Use the ALIAS statement.
John Ehrman
to
define the literal as a character constant:
LS DCC'very long string'
and then use its length attribute:
MVC Target(L'LS),LS
John Ehrman
to indicate the
new format.
What you're suggesting seems very much like what the HLASM input exit
ASMAXINV does: it re-formats the input into FB80-like records. (Have you
tried it?)
John Ehrman
Steve Smith asked for the answer to my quiz question of March 23:
While we're having fun: under what circumstances is the character
sequence
(4)(3)(2)(1)
legal as part of a machine instruction operand, not part of a quoted
string, not part of a macro operand, and not part of a SETC
instructions over that time. (As my
grandmother said, It just growed that way.)
I learned recently that STM was not included in the initial instruction
set, but was added closer to System/360 availability.
As Peter said, maybe others may have insight as well.
John Ehrman
While we're having fun: under what circumstances is the character sequence
(4)(3)(2)(1)
legal as part of a machine instruction operand, not part of a quoted
string, not part of a macro operand, and not part of a SETC statement?
Regards... John
close
to the present?
John Ehrman
the Programmer's Guide.
Making the tab character a white space should be easy, but might require
an option of some sort.
John Ehrman
Richard Lawrence posted:
The long awaited John Ehrman Assembler book as available at the
Marist College web site:
http://idcp.marist.edu/enterprisesystemseducation/Assembler%20Language%20Programming%20for%20IBM%20z%20System%20Servers.pdf
I appreciate the many kind comments posted
Tony Thigpen, Joey Capps, Rich Smrcina, and others have asked:
Did you ever finish the text book?
Yes, it's done (or at least, I've stopped adding to it) (for now).
I've gotten permission to make it available, and am working on a
convenient distribution mechanism. I'm hoping you'll be able to
not done any longer.
John Ehrman
Dave Cole noted...
Correct me if I'm wrong (John Ehrman),
but I thought that IBM once upon a time,
way back when they started to create mnemonics longer than 5 characters...
I thought they said
their new limit was going to be seven characters.
Well... VSTRCZFS.
I don't remember any such claim
Dave Cole noted again...
But it does make me wonder if they might eventually go to 9 or
longer...
I think HLASM has supported operation field entries longer than 8
characters for a long time, but resolution was possible only to source
macros. (No, I haven't tried it.)
John Ehrman
John, can you send your e-mail ID to me? It's about some material you
reviewed for me. (Apologies to everyone else.)
ehr...@us.ibm.com
A new Principles of Operations should be available at GA.
John Ehrman
It's probably because the notations .A and .B represent the DBCS
codings for those double-byte characters, not the EBCDIC characters .
and A.
If you can enter data in hex, try assembling G'42C142C2' (where I wrote
the hex representations of each byte) -- this is the DBCS representation
of AB
You must enter those 4 bytes as hex values, not as 8 EBCDIC characters. (I
assume you're specifying the DBCS option.)
Regards... John
From the description of the DS instruction in the HLASM Language
Reference:
The maximum length is 65535 for types X and C, 65534 for G.
For DC, the maximum length for type C is (indeed) 256.
Appendix B has a summary of all DC constant types.
Regards... John
Micheal, Could you write DS 0CL(11*133) ?
Regards... John Ehrman
As others have noted, the PoP is quite large and dense. Changing the
formatting would be a significant effort.
The z Architects are always very busy, and I suspect would have difficulty
finding resources needed to adopt any of the suggestions on this list.
Regards... John
Robin Vowels noted:
CVB and CVD have always been part of the fixed-point instruction
set (the basic set), and are not part of the decimal set.
That's what my antique Green Card says!
I believe the USING range limits are currently tested only for unsigned
12-bit displacements; you happen to have chosen a test case in which the
LG instructions use signed 20-bit displacements. To see the effects of
USING range limits, try dropping a zero from the ends of all the offsets,
and
Wish you well, Steve, and I appreciate your contributions both at SHARE and
to the Assembler List.
Regards... John
-
555 Bailey Ave, San Jose CA 95141 USA
+1-408-463-3543 (fax -3873) TIE 543-
ehr...@us.ibm.com; VMID = EHRMAN at STLVM27
Tony Harminc noted:
There were a number of efforts to produce compatible PL/S compilers
even in the absense of formal language specs, the most notorious of
which was the Rand Corporation's RL/S.
There was also one at Princeton by ?? Varian (Melinda's husband, I think).
It was also squelched by
Ed Jaffe commented:
If such rewrite were viable, one could argue that all existing ISV
product code would have already been rewritten in METAL or Dignus C,
which it has not. New modules? Possibly. But, not existing ones.
Confirmed by academic studies. See
(1) P.J.Middleton, The Costs of Changing
Gil asked why an algebraically equivalent form won't work:
It's because AREA-8192 (in Jonathan Scott's example) is addressable by an
existing base register; but AREA-10 (in your example) is not.
Addressability of the base location is a requirement for Dependent USINGs.
Gil noted that I wrote:
Addressability of the base location is a requirement for Dependent
USINGs.
and replied:
Who made that rule? Why? Can it be appealed? And why
addressability with 12-bit displacement (you neglected or
deliberately omitted to say that), rather than one of the
longer
Gil asked:
When is an RFE necessary? Who submitted the RFE to add long
displacement capability other than in USINGs? Who submitted
the RFE to add z196 capability to HLASM? Etc.
Support for z196 and long displacements came from IBM Processor
Architecture, as do requirements for supporting new
Paul, your description is unclear. Can you provide an example of a couple
of typical sets of 8 (non-hex?) input bytes and what you expect as the
corresponding 4 (non-hex??) output bytes?
Can someone provide me with sample code that uses RADIX13 or Modulo55. My
Modulo55 code is burried in a
FORMAC was a symbolic computation, algebraic manipulation system writtten
(I believe) in PL/I. All symbolic algebra systems I know of require
variable-precision arithmetic. (I wrote a couple of System/360 assembler
subroutines for George Collins' SAC-1 system in the early 1970s.)
... John Ehrman
to control the CA'...' mapping.
You can control the CA'...' mapping by implementing your own set of
translation tables for use with the TRANSLATE option.
When that was implemented, we didn't see a need to enter what others have
called the swamp of multiple source and target code pages.
John Ehrman
in a source scan.
John Ehrman
The distances from instruction to instruction are unchanged; HLASM will
divide by 2 when calculating the halfword offsets. So, 4+4 rather than 2
+2, etc.
John Ehrman
been no
need for it.
John Ehrman
The reason is that other z platforms (VM, VSE, zLinux) don't support
relative-immediate external references.
An easy way to suppress the diagnostic is to specify SUPRWARN(215) as an
invocation parameter or on a *PROCESS statement at the head of the source
program.
Steve Smith asked:
External
Martin Truebner asked:
Underlying question - what do I have to specify to make it handle
label HANS as different from Hans or am I totally off target and
it will never do that.
There is no mixed-case support for *internal* symbols. You can generate
*external* symbols with mixed case and
Paul Gilmartin noted:
XREF doesn't reliably list register references.
That's why HLASM provides a register cross-reference (use the RXREF
option). It not only references explicit register use, symbolic or not,
but also implicit uses for instructions like LM, M, D, SRDL, and the like.
For
Dave Gibney guessed:
I will guess IUP to be Independent User Program.
I believe it's Installed User Program.
I am out of the office until 07/29/2013.
Note: This is an automated response to your message Question About
storing a Value in a Macro sent on 07/21/2013 14:47:57.
This is the only notification you will receive while this person is away.
I am out of the office until 07/08/2013.
SVL closed for electrical upgrades.
Note: This is an automated response to your message short video on
instructions sent on 07/05/2013 6:44:13.
This is the only notification you will receive while this person is away.
Mike Ward asked:
Hello friends, I was wondering if any of you know of any assembler
teaching tools that might be available for free.
What do you need, and at what level(s)?
John Ehrman
Steve Hazzard wrote:
... - looks like there's not much interest in Assembler these days.
I would like to code more, however the directive is to plug-in a vendor
product instead of RYO - is this what you are hearing from other Sys Progs?
I you are facing issues of converting from Assembler
Performance concerns about individual instructions aren't worth much
effort. Things like operand alignment, data and instruction cache
retention, locality of reference, branch frequency etc. can have really
significant effects.
Remember that CPU speeds have increased much faster than memory
, anyway.
John Ehrman
, useful new instructions appear in groups, so a simple
SYSPARM or global variable symbol value can determine which of possibly
many such macros should expand to use emulation or the new instruction.
John Ehrman
Ed Jaffe noted...
The oldest assembler I ever used was IFOX00. ISTR, it did not
have support for LOCTR but my memory could be faulty.
I think your memory is correct.
As I remember the IFOX assembler used basically the four-pass structure of
Assembler F. It was developed and supported by a
; both were based on ASMF. I
doubt IFOX was a from scratch implementation.
I gave a short talk on Assembler History at the San Francisco SHARE
conference; look for the proceedings of session 12235.
John Ehrman
John McKown noted...
IIRC, some models of the S/360 had a BAS instruction. But I don't have
an old S/360 POPS to make sure exactly what it did.
My old System/360 Green Card has no BAS, but I believe it was available on
Models 20 and 67. I don't think it would have been in the 360 PoP.
John
This green card documents BAS as Branch and Store with footnote (e)
Model 67.
http://archive.computerhistory.org/resources/access/text/2010/05/102678081-05-01-acc.pdf
Must be newer (and therefore less green) than mine (X20-1703-3).
And only if the target is relatively addressable. I.e. In the same section
or object.
sas (phone)
On Apr 5, 2013 7:21 PM, John Ehrman ehr...@us.ibm.com wrote:
You can use LARL to replace LA only if the target is at an even address.
John Ehrman
This may not be relevant to the original question
You can use LARL to replace LA only if the target is at an even address.
John Ehrman
I am trying to use ASMPUT and need help with creating ADATA file. Can
anyone point me to a user manual on ASMPUT, thanks.
The Toolkit User Guide is GC26-8710.
John Ehrman
familiarity with the representation you're working with.
John Ehrman
Alex Kodat noted:
... depends on one's view of the assembler. If the view is that it's gone
about as fer as it can go ...
Oh, there's lots more we'd love to do, had we but world enough, and time.
8-)
John Ehrman
Paul Gilmartin noted:
Isn't there lately a construct that explicitly invokes a macro rather than
an opcode? There should be.
There is indeed! Suffix ':MAC' or ':ASM' as appropriate, as in 'MSG:MAC'
and 'MSG:ASM'.
John Ehrman
People are prepared to argue PoPs interpretation with John Ehrman ???.
I appreciate the laudatory comment, but I'm as blunder-prone as anyone
else. (And a very poor chess player.)
To me, the topic we're discussing is with the word operand.
(1) In the PoP, an operand is an object being
Martin Truebner asked:
wouldn't that be ALSI and ALGSI? With LAA/LAAG/LAAL/LAALG the load
from memory-part is missing.
As I understand the PoP, it says:
The second operand is added to the third operand,
and the sum is placed at the second-operand location.
Subsequently, the original contents of
I'm looking at LAA on page 7-222 of SA22-7832-09, where the 2nd operand has
B2 | DL2 | DH2.
John Ehrman
I am out of the office until 02/11/2013.
Note: This is an automated response to your message Re: SVC 34 sent on
02/06/2013 14:26:23.
This is the only notification you will receive while this person is away.
Try a technique like that illustrated in this example:
Macro , Defined in the source program
L READ A,B,C
READ_XX OpSyn READ Save Wrapper's definition as READ_XX
READOpSyn , Nullify this macro's definition
- - -
The problem is with the original USING range: the HLASM Language Reference
says that if the upper limit of the USING range exceeds the lower limit
+4095, it's reduced to that value. That's why the labeled dependent USING
for EXT2 is flagged.
Apologies for the tardy response.
Dave Kreiss wrote
This reply has been edited to save space --
The types are fixed by the verb: SETAF, SETBF, or SETCF.
As noted in an earlier post, there's no SETBF statement.
What happens if an external function called with a SETB-type
argument attempts to return, for example a SETC-type result?
You can do
macro facility in any
programming language I know of.)
John Ehrman.
to (for example) capture information about the CPU on
which the assembler is executing.
Will that help, or do you have something else in mind?
John Ehrman
Dave Cole asked:
Does anyone know if the internal format of ASMLANGX files has been
published?
Why do you want to know?
Kirk Talman commented:
A business person at our company asked me if it was possible to flowchart
HLASM programs.
The ASMPUT (Program Understanding Tool) component of the HLASM Toolkit
Feature creates flowcharts of one or more assembler programs, with links
between nodes on the graph and the
Tony Harminc commented:
I see that SA22-7832-09 is now available on ResourceLink. That
Transactional Execution is cool stuff, or would be if I could find a
use for it. Like most things these days, it seems that Java is the
likely exploiter.
We hope to give a presentation on TE at the next SHARE
On Tue, Sep 18, 2012 at 1:23 PM, McKown, John
john.mck...@healthmarkets.com
wrote:
Damn, it's 100 years until that Share presentation? Or, by chance, did
you
mean 2013? GRIN--
1000 years John... ;-)
I meant 2013 (next year). Even if I'm not around in 1000 years, IBM
mainframes will be...
Binyamin Dissen commented:
Yes, the difference between real world programming and ivory tower
programming. In real world programming you want the sequences to be
familiar so that others can more easily maintain the programs. Those
with a view from the top of Mt. Olympus may think otherwise, but
John McKown wrote:
As an example of (1), I quite often do:
CALL PROGRAM,(PARM1,PARM2),VL
CHI R15,=Y(MAXENTRIES)
JH INVALID_RC
B*+4(R15)
START JRC0
JRC4
JRC8
MAXENTRIES EQU *-START/4
There's no need for a based branch: just
Binyamin Dissen noted:
For some unknown reason, the assembler requires EQU to be in a section,
be it CSECT or DSECT. Move the REGS macro after the CSECT.
The assember must assume that an EQU statement might depend on a location
counter value, so it must establish a control section if none
is just a convenient name for a constant, the same
function as in statement 4 above could be achieved by writing
DC S(F42) followed by
F42 DC F'42'
John Ehrman
Jake Anderson asked
is IEV90 supported ?
IEV90 (Assembler H V2) was withdrawn from service on October 31, 1995.
Its replacement is the IBM High Level Assembler V1.6 (ASMA90).
All previous releases of ASMA90 have been withdrawn from service.
Paul Gilmartin noted:
And I have an example where base and displacement are
successfully evaluated in an R[SX] instruction where an
S-constant with the same argument in apparently the same
context causes an error.
Can you post an example?
I am out of the office until 07/30/2012.
Note: This is an automated response to your message Re: Subject: AW: **
ASMA030E Invalid literal usage - =CL8'MARTINWH' sent on
7/23/12 9:05:14.
This is the only notification you will receive while this person is away.
Happy Birthday! Do we assemble at SHARE for a party? ;-)
I'd love to, but I can't be at the next SHARE in Anaheim. ;-(
John Ehrman
not
unthinkable. But it would introduce a class of addressability
errors that could be detected only at link time, not at assembly.
Probably not justified by ROI.
Relative-immediate references to external symbols has been available for
both old OBJ and new GOFF object formats since 2004.
John Ehrman
1 - 100 of 144 matches
Mail list logo
