Target(L'=C'very long string'),=C'very long string')
hoping you made the two instances identical. It seems preferable to me 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
--
John
The GETMAIN is inessential and usually undesirable.
Many statement-level languages use a stack---typically but not always one
provided by the LE---for both DSA and automatic (COBOL local) storage, and
I do this in assembly language using my own stack(s).
LIFO stacks being very easy to manage,
operation of moving a pointer forward and
backward.
The traditional, high-overhead use of heap-based storage for this
purpose is/was only excusable absent an easy-to-use FIFO alternative
to it.
John Gilmore, Ashland, MA 01721 - USA
is usually a mug's game. Like all of us, he
can be guilty of a fat-finger typo; but I have never known him to be
substantively wrong about a quantity.
John Gilmore, Ashland, MA 01721 - USA
.
John Gilmore, Ashland, MA 01721 - USA
0C133
| . . .
| DC 0C133
leaves the location counter unchanged.
John Gilmore, Ashland, MA 01721 - USA
of those already available meets
his|their needs, he should write a new one that does so.
John Gilmore, Ashland, MA 01721 - USA
detail-ridden when first encountered one's
cat brain takes over very quickly. They become very easy to use with
practice.
John Gilmore, Ashland, MA 01721 - USA
.
Without information about the maximal sizes of the problems you want
to treat, I shall assume trhat they are fairly large but not huge.
John Gilmore, Ashland, MA 01721 - USA
and j. We have
i = floor[p/8] + 1
j = mod(p,8) + 1
The construction of a one-origin lexicographically ordered sequence of
flag names is thus the only really interesting task here.
John Gilmore, Ashland, MA 01721 - USA
Bernd,
I think I in fact do something very like what you do, and I of course
agree that the user should deal only in a flag or modal-switch names
and never in addressing information for them.
John Gilmore, Ashland, MA 01721 - USA
Program objects may, currently, be only as much as 1 gigabyte in
size. Load modules must be less rthan 16 megabytes in size.
John Gilmore, Ashland, MA 01721 - USA
said, it doesn't.
John Gilmore, Ashland, MA 01721 - USA
with RPG II.
John Gilmore, Ashland, MA 01721 - USA
such
assembler is very unlikely to be developed. I use others from time to
time, and they all seem to have discouragement of their use as a
principal design objective.
John Gilmore, Ashland, MA 01721 - USA
character one and then 2) to convert it back
into an arithmetic one within the invoked macro. (This notation
looks complicated the first few times it is encountered, but it is in
fact trivial and comes to seem so very quickly.)
John Gilmore, Ashland, MA 01721 - USA
different merit, identified by Gibbon long ago
--
John Gilmore, Ashland, MA 01721 - USA
of the strongbox is at once exiguous and
delusive.
John Gilmore, Ashland, MA 01721 - USA
What is a negative absolute value?
John Gilmore, Ashland, MA 01721 - USA
mnote is almost as ugly as that of triggering an ABEND by
using an irrelevant divide-by-zero operation.
John Gilmore, Ashland, MA 01721 - USA
this
distinction is prima facie evidence of technical incompetence
John Gilmore, Ashland, MA 01721 - USA
My point, which I thought obvious, was that restricting access to
tools is worse than silly. It is also otiose, and thus even less
defensible---an aggravated not a mitigated offense---when data are
locked up appropriately.
John Gilmore, Ashland, MA 01721 - USA
work.
John Gilmore, Ashland, MA 01721 - USA
For a straightforward masking operation like the one under discussion
hexadecimal is clearly the appropriate choice. In other situations
binary is better.For example,
BL4'01010101010101010101010101010101'
is, I think, more perspicuous, even though long-winded, than
XL4''.
John Gilmore
, the notion that mainframe purity should be considered in
taking technical decisions, that we should eschew anything the PC
people use as a contaminant, seems to me to be a surpassingly silly
one.
John Gilmore, Ashland, MA 01721 - USA
, North Harbour, Portsmouth, Hampshire PO6 3AU
--
John Gilmore, Ashland, MA 01721 - USA
most things. I will arrange a small public
celebration when I find that we in fact agree about something
significant.
John Gilmore, Ashland, MA 01721 - USA
There is a typo in my post that rather destroys its value. The line
|us_64 . . .
lost its first three characters. It should be
|plus_64 seta BYTE(x'40')--signed single-byte +64
The notion trhat the HLASM should be e
On 8/4/14, Bob Rutledge deerh...@ix.netcom.com wrote:
John Gilmore
that generated code corresponding to what I had intended to write
rather than what I did in fact write.
John Gilmore, Ashland, MA 01721 - USA
they are, if not wholly
trivial, easy enough.
John Gilmore, Ashland, MA 01721 - USA
abbreviations are
often tone-deaf to culture and class differences. (Quite stupid
upper-class Americans know what a regatta is; brilliant working-class
ones usually do not.)
Consensus is not likely to emerge from these discussions, but they
were not time-wasting.
John Gilmore, Ashland, MA 01721
, en, ent, entr, entry, or
o f, fi, fin, fina, final
is func tionally eq
On 7/28/14, Ed Jaffe edja...@phoenixsoftware.com wrote:
On 7/25/2014 8:17 AM, Paul Gilmartin wrote:
On 2014-07-25, at 08:40, John Gilmore wrote:
We disagree, sharply. The abbreviation of long keyword/set element
values
continuing . .
is functionally e
On 7/28/14, John Gilmore jwgli...@gmail.com wrote:
EJ's distinction between, say, command-language option values and
macro-instruction keyword-parameter values is not always a firm one.
I often make a CL available for use in generating macro instructions
value instead of one
of its CIDTs.
John Gilmore, Ashland, MA 01721 - USA
for using macros ii
will be normalizations, sequencing and comparisons.
John Gilmore, Ashland, MA 01721 - USA
, should be criticized when this is the case. (The
rhetorical device of confusing bad exempla with a scheme itself in
fact has an impressive Greek name.)
John Gilmore, Ashland, MA 01721 - USA
it argument seems to me to be not just
without merit but vicious.
John Gilmore, Ashland, MA 01721 - USA
such recurrent requirements.
John Gilmore, Ashland, MA 01721 - USA
with this more complex case, you need to decide what to do with
zero values. The tradition is usually to make them positive, but you
could instead elect to use a blank 'sign character' for zero values.
John Gilmore, Ashland, MA 01721 - USA
the sides of the Grand Canyon of the Colorado
have, some of them, been doing their surefooted jobs for many years;
but it would be a mug's game to consult them about the geology of the
Canyon.
John Gilmore, Ashland, MA 01721 - USA
poster that LIBMAC makes relevant macro
definitions readily and immediately available.
John Gilmore, Ashland, MA 01721 - USA
values.)
John Gilmore, Ashland, MA 01721 - USA
a mechanism for dealing with these complications.)
I am planning to package them together within a single email because
attachments are now so problematic.
John Gilmore, Ashland, MA 01721 - USA
but very likely in the near-term
future).
Yesterday I quoted Wittgenstein's apophthegm,
About things we know not, we ought to be silent.
There is a more abrasive variant of the same principle that is due to
one of our own. The late John McCarthy wrote
Do the math or shut up.
John Gilmore
or needs to be a valid UTC value is
without merit. The use of the adjective 'leap' was, I suppose,
inevitable; but leap seconds are not in fact at all like leap-year
days or gravid, Hebrew-calendar months: we don't need calendrical
names for them.
John Gilmore, Ashland, MA 01721 - USA
not arise.
I am not so great an admirer of Ludwig Wittgenstein as some
professional philosophers whom I respect, but he did make some points
memorably, and among them was that
About things we know not, we ought to be silent.
John Gilmore, Ashland, MA 01721 - USA
John [McKown],
A superb post!
Most discussions of calendrical arithmetic here have a strongly emetic
effect upon me. (They make me want to vomit.)
It is a great pleasure to read one that gets things right.
John Gilmore, Ashland, MA 01721 - USA
.
John Gilmore, Ashland, MA 01721 - USA
Bob Raicer can defend his own positions, but it does seem to me that
he made it clear, with appropriate extracts from the manual, that
DUMMY is usable only with BSAM, QSAM, and VSAM, i.e., not with BPAM.
That being the case, most of this backing and filling is, at best, irrelevant.
John Gilmore
To retired mainframer's post my response can be brief: I think not.
A single member of a PDS[E] can be accessed in the usual way using
BSAM or QSAM. A list of them cannot. For that operation BPAM must be
used. BPAM does not support the use of DUMMY.
John Gilmore, Ashland, MA 01721 - USA
this and all such questions are
delusory. Any answer must be local and contextual. Pipelining has
made it so.
John Gilmore, Ashland, MA 01721 - USA
with this, give up single-instruction timings; but it will
apparently be very difficult for some of us to discard old epistemes.
John Gilmore, Ashland, MA 01721 - USA
The single millicoded z/Architecture machine instruction CHECKSUM,
CKSM, documented on page 7-45 of the current PrOp, would have been a
much better choice than your loop; but it would not, of course, have
been nearly so much fun.
John Gilmore, Ashland, MA 01721 - USA
a
notorious use-and-mention pedant.]
--
John Gilmore, Ashland, MA 01721 - USA
I suspect that Robin's question was rhetorical/tongue-in-cheek, not a
request for information. He is a very old hand at this game.
John Gilmore, Ashland, MA 01721 - USA
David Stokes saw calumny---a lie spoken or written to damage someone
else's reputation---where none was intended. I suspect that he did
not know quite what this word means. Now he does.
John Gilmore, Ashland, MA 01721 - USA
On 5/26/14, John Gilmore jwgli...@gmail.com wrote:
David Stokes saw calumny---a lie spoken or written to damage someone
else's reputation---where none was intended. I suspect that he did
not know quite what this word means. Now he does.
John Gilmore, Ashland, MA 01721 - USA
--
John
1964 a code-base register (CBR)instead. Fortunately, I find that I
need to talk about CBRs less and less because I now use them very
little.
John Gilmore, Ashland, MA 01721 - USA
they are less onerous than any list of them makes
them seem. They can be embodied in reusable parameterized macros, and
doing so is 1) time-saving 2) much less error-prone than rewritten,
i.e., copied, code.
John Gilmore, Ashland, MA 01721 - USA
and
non-moot ones).
That said, Rob's posts in this thread have been particularly valuable;
and I would not want this nit picking to suggest that I think
otherwise.
John Gilmore, Ashland, MA 01721 - USA
.
--
John Gilmore, Ashland, MA 01721 - USA
them, employing PC routines instead.
--
John Gilmore, Ashland, MA 01721 - USA
-by-single-character operations on strings are, I
think, not just tedious but ugly where better approaches are
available.
John Gilmore, Ashland, MA 01721 - USA
As I thought, indeed still think, I had made clear, it will stop on
the first, leftmost or rightmost, non-blank.
John Gilmore, Ashland, MA 01721 - USA
the halfword|fullword prefix is a
very much better device for doing so than the null delimiter.
John Gilmore, Ashland, MA 01721 - USA
in conditional-assembly [assembler] instructions.
This is a lot of similarity, but the differences are crucial. They
are horses of another color.
John Gilmore, Ashland, MA 01721 - USA
I seemed to have botched SharufF Morsa's name, for which I apologize.
In mitigation I can only plead that two of my former students, one
Pakistani and one Persian/Bahktiari transliterate their names as
'Sharuf' with only one 'f' and that I had never before seen this
transliteration.
John Gilmore
, as in
|ASCII_blank_rank seta X2A('20')
Set symbols can of course be used both in open code and within macro definitions
John Gilmore, Ashland, MA 01721 - USA
it bears (a little) study.
--
John Gilmore, Ashland, MA 01721 - USA
that are COBOL
and pl/1.
PCRE itself is somewhat complicated, but so is the runtime library regex
functionality supplied by IBM as a standard feature. Would you disallow
your programmers to call those standard functions as well?
ZA
Sent from Yahoo Mail on Android
--
John Gilmore, Ashland
say, should not be
employed anywhere as a programmer. Others clearly have different
views.
John Gilmore, Ashland, MA 01721 - USA
Mark Slater's is the first automatic reply to an automatiic reply
that I can remember encountering.
It would be easy to imagine a scenario in which such traffic grew exponentially.
--
John Gilmore, Ashland, MA 01721 - USA
I don't use rhetoricons. They're self-defeating. The intent of the
comment Paul Schuster quotes was, however, whimsical..
John Gilmore, Ashland, MA 01721 - USA
; but theirs are, of course,
wrongheaded.
John Gilmore, Ashland, MA 01721 - USA
that machine-translation schemes are most prone
to botch
This is important; but its relevance to programming-language
identifiers is limited, even exiguous. More later.
John Gilmore, Ashland, MA 01721 - USA
to their defense, diligently if not with great
zeal. My view of Mr. Walker's problem is much the same.
John Gilmore, Ashland, MA 01721 - USA
.
Making such a change will certainly produce more ABENDs than result
from its current, occasionally greedy behavior.
John Gilmore, Ashland, MA 01721 - USA
I think it would be worthwhile to propose to John Ehrman that the
maximum for BL fields be upped to 64 kibibytes - 1 (65535). This is
already the [DS-only] limit for C and X data. (For DBCS G data it is
64 kibibytes - 2 (65534) for obvious reasons. )
John Gilmore, Ashland, MA 01721 - USA
to be the best
compromise available. If everyone were a mathematician case
sensitivity would be feasible, but I suspect that such a universe
would be disagreeable in other ways.
John Gilmore, Ashland, MA 01721 - USA
be conceded,
ingenious; but, to borrow Thorstein Veblen's phrase, it is misspent
ingenuity.
John Gilmore, Ashland, MA 01721 - USA
default, case-iunsensitive behavior (outiside of
quoted strings, where case is respected), but the CASE | NOCASE and
MACROCASE | NOMACROCASE suboptions of the COMPAT | NOCOMPAT option of
the ACONTROL assembler statement can be used to modify this behavior.
John Gilmore, Ashland, MA 01721 - USA
The answer to Paul Gilmartin's question
Can this not be done without retyping the string twice?
is, of course, yes; but I judged that the longwinded example was the
more perspicuous. Brevity is putatively the soul of wit, but it is
not always pedagogically advisable.
John Gilmore, Ashland, MA
, say, machine instructions and assembler
instructions is of course correct. That is the point. If they were
not, they too would be otiose.
John Gilmore, Ashland, MA 01721 - USA
research that establishes conclusively that the rich
live in larger houses than the poor. Consider an old-style hard-copy
newspaper comprised only of page after page of headline text.
John Gilmore, Ashland, MA 01721 - USA
Paul Gilmartin wrote:
| And six-hex-digit addresses in a 31-bit assembly?
This can be an artefact of omitting to specify LINESIZE(133) for an
assembly. LINESIZE(133) is, as I remember, coerced with an error
message when GOFF is specified but not otherwise.
John Gilmore, Ashland, MA 01721
.
John Gilmore, Ashland, MA 01721 - USA
disagree, sharply, about
this issue and may others; but that is no bad thing.
--
John Gilmore, Ashland, MA 01721 - USA
continued. . .
|padkseta 3-k
|seqcs setcd 'zeros2'(1,0).'seqcs'
yields label segments that are ALL three characters in length, even
for seqno 99 for which 'zeros2'(1,0) yields the nul string.
On 2/12/14, John Gilmore jwgli...@gmail.com wrote:
A distinction is called for here
In the 2nd segment of my response 'setcd' should of course be 'setc'.
--
John Gilmore, Ashland, MA 01721 - USA
, of a nominated character
string of non-identical characters.
John Gilmore, Ashland, MA 01721 - USA
Chris,
Look at page 184 of the HLASM LR. Location-counter references are a
little tricky, but I think (without having tested it) that Bill
Planer's idea is a good one.
John Gilmore, Ashland, MA 01721 - USA
the longest possible instance
of some arithmetic data type.
John Gilmore, Ashland, MA 01721 - USA
I have said it before, and I really should not need to say it again.
The HLASM's BYTE bif addresses these problems.
John Gilmore, Ashland, MA 01721 - USA
I going through my technical books I found that I have an extra,
excellent-condition copy of
Advanced assembler language and MVS interfaces, Wiley 1991.
The fifth person who sends me his|her mailing address gets it postage free.
John Gilmore, Ashland, MA 01721 - USA
Cliff McNeill gets the book, which I'll put into the mail on Saturday
after we've dug out from under a mini-blizzard---just over a foot of
snow and still falling---here in Ashland.
I should have liked to reward Kurt LeBesco's persistence, but I did
say 'person' not 'message'.
John Gilmore
As a known advocate of metric units I've been rebuked for writing
about a foot of snow. I should of course have written 30.48 cm of
snow instead.
John Gilmore, Ashland, MA 01721 - USA
On 1/2/14, Tony Thigpen t...@vse2pdf.com wrote:
Just wondering, what position did my name come in? :-)
Tony Thigpen
Tony,
You were fourth.
John Gilmore, Ashland, MA 01721 - USA
Thu, Jan 2, 2014 at 3:43 PM
Manning, Rick F Thu, Jan 2, 2014 at 3:43 PM
Mike Shaw Thu, Jan 2, 2014 at 3:44 PM
Tony Thigpen Thu, Jan 2, 2014 at 3:44 PM
McNeill,Cliff Thu, Jan 2, 2014 at 3:51 PM
--John Gilmore, Ashland, MA 01721 - USA
are and
have always been immediately available at the IBM Publications
website. It was not hidden away.
John Gilmore, Ashland, MA 01721 - USA
benign. Moreover, their judicious use
often makes it possible to avoid what Tony Harminc has just called
fancier ORGs.
John Gilmore, Ashland, MA 01721 - USA
1 - 100 of 329 matches
Mail list logo
