Great notes, thanks! But real geeks know Warp Drive will be invented in
2063 and with that humans can easily catch up with Voyager, well, unless
it becomes Vger.
Here in the Los Angeles area a few years ago I went to see a guitar
player and happened to meet a few guys who engineered and
Kekronbekron wrote:
>Thinking about it ... it would be far simpler (than anti-ransomware
>capability in storage, or lock-all behaviour) if there were a RACF
>HealthChecker that looks for abnormal enc/dec activity. What 'normal'
>is can be learnt from a year's worth of actual enc/dec-related SMF
On Tue, 8 Sep 2020 03:33:18 +0100, CM Poncelet wrote:
>You said, "It isn't boolean; everything in REXX is a character string."
>�
>I agree that "it's all strings", but not that "everything in REXX is a
>*character* string."
>�
Persuing the Rexx Reference, SA32-0972-40, I find various
You said, "It isn't boolean; everything in REXX is a character string."
I agree that "it's all strings", but not that "everything in REXX is a
*character* string."
Try the following:
ARG DEBUG
IF ABBREV(DEBUG,D,1) THEN ,
TRACE I
SIGNAL ON SYNTAX NAME ERROR0
TRUE = 1
SAY 'TRUE NUMERIC =
On Tue, 8 Sep 2020 02:30:01 +0100, CM Poncelet wrote:
>
>My mistake was to think that setting a variable to a quoted value, in
>REXX, made that variable a type CHAR. But REXX considers it to be NUM if
>it contains only numerics, regardless of whether its set value was
>
Not only numerics. For
Thinking about it ... it would be far simpler (than anti-ransomware capability
in storage, or lock-all behaviour) if there were a RACF HealthChecker that
looks for abnormal enc/dec activity.
What 'normal' is can be learnt from a year's worth of actual enc/dec-related
SMF data.
- KB
‐‐‐
No. REXX has built in functions to test the value of a string, but it's all
strings
foo =01
bar = '01'
baz = 0||1
all yield the same value,
shmuel@linux-gn5l:~> rexxtry
/usr/local/bin/rexxtry lets you interactively try REXX statements.
Each string is executed when you hit Enter.
Poor product management on the part of the ransomware malefactors. At $50K they
might have had a deal.
Charles
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Joe Monk
Sent: Monday, September 7, 2020 5:25 PM
To:
No, REXX has both DATATYPE CHAR and NUM strings.
Meanwhile C2D, D2X etc. would be useless if REXX could not then process
binary data - as in IPCS REXX:
ADDRESS IPCS
PSA_ADDRESS = ''
"EVALUATE" PSA_ADDRESS||. ,
"POSITION("X2D(224)") LENGTH(4) REXX(STORAGE(OLD_ASCB_ADDRESS))"
"EVALUATE"
Well, my father was a journalist and a bibiliophile, so I was exposed to the
ambiance early on, but I only started programming in 1960, in tenth grade, on a
machine that absolutely immunized me against nostalgia.
If you think I'm old, I once saw a post from Werner Bucholz on this list. Gone,
I will tell you that when it happened to my client, the "ransom" was
$1million.
It was less expensive to lose a days work. in restoring from backups.
Joe
On Mon, Sep 7, 2020 at 6:53 PM Charles Mills wrote:
> > It should be a moral decision to *never* pay any ransom, no matter what
> the cost
"Mehitabel" - wow! You're a lot older than I assumed, Mr Metz!
---
Bob Bridges, robhbrid...@gmail.com, cell 336 382-7313
/* In its state of nature [a dog] has a smell, and habits, which frustrate
man's love; he washes it, house-trains it, teaches it not to steal, and is
so enabled to love it
> It should be a moral decision to *never* pay any ransom, no matter what the
> cost to the business. Of course that will never fly in reality.
All the InfoSec consultants talk a great game with "never pay" but the dirty
little secret is that many or most do. In many cases it is not just the
While I really like your new term, "ransomwared", I have to disagree
with the conclusion. Of course we need to try to prevent the attack,
but we also need to have some kind of backup to get things at least
somewhat back to normal. And that doesn't mean a single backup method
for all kinds of
On Mon, 7 Sep 2020 18:52:55 +, Seymour J Metz wrote:
>Hindsight? I never understood the purpose of the web, given that gopher and
>SGML were already here. All we were missing was a protocol called Mehitabel ;-)
>
It's easy to understand. Just remember, you're not the customer;
you're the
Hindsight? I never understood the purpose of the web, given that gopher and
SGML were already here. All we were missing was a protocol called Mehitabel ;-)
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
From: IBM Mainframe Discussion List
On Tue, 8 Sep 2020 01:04:43 +1000, Greg Price wrote:
>On 2020-09-05 3:01 AM, Paul Gilmartin wrote:
>
>... A few years back there seemed to be a
>religious phase where IBM ID went on a crusade to remove weasel words
>from documentation.
>...
>As it was, whole sections of text I wrote for
WSL doesn't have anything to do with cloud.
It's just the running of Linux within Windows, using bits of Hyper-V
internally, I think.
That said, Joe's point about securing this new vector is one to pay attention
to.
And since z/OS is also working on improving/expanding z/OS NFS implementation..
Use DS8880 SafeGuardCopy
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
What release of what compiler. I remember when IBM changed the default for
FIXED BIN from (31,0) to (15,0) in order to eliminate some annoying anomalies
that didn't occur in
FORTRAN. Of course, back in those days there were fewer compiler options to
muddy the waters.
--
Shmuel (Seymour J.)
So, does this mean that a cloud environment is more or less likely to be
attacked than the same on premise environment?
Such an attack could cause a major disruption in operations and thinking.
Sent from my iPhone — small keyboarf, fat fungrs, stupd spell manglr. Expct
mistaks
> On Sep 7,
A good tech writer is a joy forever; one who will polish prose describing the
delivered product in such a way that it still describes the delivered product.
The other type is more common, and is reminicent of root canal.
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
On 2020-09-05 2:11 AM, Jim Mulder wrote:
MVS had simulation for DAS in its program check handler, which
allowed SP1.2 and its successors to run on machines which did not
have DAS. DAS was first implemented via a microcode update
on the 3033. It was never implemented on 158 and 168.
Well,
Let me tell you why it is not such a hypothetical problem...
As we all know, Microsoft now allows under Windows for Linux, Windows
access to Linux datastores. So, imagine I have a mainframe data store
mounted as a Linux FS on a Windows box running Windows for Linux. Now, the
windows box gets
... and the compile options
On 2020-09-07 10:48, Bob Bridges wrote:
All of this is really fascinating (and no, I'm not being facetious): A
bunch of apparently knowledgeable PL/1 programmers cannot agree on a point
that would seem to have a single indisputable answer. Rather than keep on
On 2020-09-05 3:01 AM, Paul Gilmartin wrote:
If the number 3.1416 is used in more than one place in the program,
or if it requires specific data or precision attributes, you must declare
it as a named constant.
In the olden days - years before the iPhone 6 was a thing - there
"The maximum number of decimal digits allowed is 15. Default precision,
assumed when no specification is made, is (5,0). The internal coded
arithmetic form of decimal fixed-point data is packed decimal. Packed
decimal is stored two digits to the byte, with a sign indication in the
rightmost four
On 2020-09-08 00:15, Seymour J Metz wrote:
Did you read what I wrote? The code you wrote has nothing to do with
the expression I gave.
Oops, a typo.
The PUT should have read
PUT ( (I/J)*6 );
to produce 6.
How about
DECLARE (I, J) FIXED DECIMAL (15);
I = 4; J = 3;
PUT ((I/J*J));
That's
All of this is really fascinating (and no, I'm not being facetious): A
bunch of apparently knowledgeable PL/1 programmers cannot agree on a point
that would seem to have a single indisputable answer. Rather than keep on
saying "yes it is" / "no it isn't", couldn't one or two of you from both
"DECLARE (I, J) FIXED DECIMAL (15);
I = 4; J = 3;
PUT ((I/J*J));"
Well, just doing the math, that should give an answer of 4.
4/3 * 3/1 = 4/1 = 4 ...
Joe
On Mon, Sep 7, 2020 at 9:15 AM Seymour J Metz wrote:
> Did you read what I wrote? The code you wrote has nothing to do with the
>
Did you read what I wrote? The code you wrote has nothing to do with the
expression I gave. How about
DECLARE (I, J) FIXED DECIMAL (15);
I = 4; J = 3;
PUT ((I/J*J));
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
From: IBM Mainframe
Flash Express is dead end.
z14 and z15 has no Flash Express. Both have Virtual Flash Express, which
is part of regular RAM assigned to this role.
It is paid feature, IMHO it is much more efficient to buy this memory as
central memory and have much less paging.
Note, VFM is cut from same memory
No,it is not and that LE manual does not claim that it is. What that table
describes is how to declare parameters of various types. It's analogous to they
way you used to deal with character data in FORTRAN IV; you have to fudge using
the available types.
--
Shmuel (Seymour J.) Metz
"I see no relationship to the ransomware problem,..."
The whole topic is a hypothetical discussion.. don't know what to say for the
relation not being understandable.
Just a thought for damage control..
Obviously, obvious security measures have still let this hypothetical problem
through
You think that I am not looking at IBM's PL/I LRM?
On 2020-09-07 23:25, Joe Monk wrote:
The answer is here:
https://www.ibm.com/support/knowledgecenter/SSY2V3_5.2.0/com.ibm.ent.pl1.zos.doc/lr/resarithoprt.html
Joe
--
For
W dniu 07.09.2020 o 14:57, kekronbekron pisze:
Makes me wonder.. some network products have a 'total lockdown' mode that stops
*anything* network. Like pulling the plug.
IBM can have a similar thing for z/OS TCPIP/SNA networks but I reckon it's more
effective if a similar lockdown (ugh)
The answer is here:
https://www.ibm.com/support/knowledgecenter/SSY2V3_5.2.0/com.ibm.ent.pl1.zos.doc/lr/resarithoprt.html
Joe
On Mon, Sep 7, 2020 at 8:12 AM Robin Vowels wrote:
> You are looking at the wrong part of the table.
> This discussion is about DECIMAL operands.
> what I wrote is
You are looking at the wrong part of the table.
This discussion is about DECIMAL operands.
what I wrote is correct for such.
See Table 15 top entry, for ANS rules for division;
Table 16 top entry, for IBM rules.
On 2020-09-07 22:19, Joe Monk wrote:
Actually it does...
Under the IBM suboption:
Makes me wonder.. some network products have a 'total lockdown' mode that stops
*anything* network. Like pulling the plug.
IBM can have a similar thing for z/OS TCPIP/SNA networks but I reckon it's more
effective if a similar lockdown (ugh) feature exists for RACF instead.
Of course, this will
Thanks. I didn't know about that hidden panel. Yes, it does report on SCM;
ASID=0003 JOB=RASP SLOTS= VIO= SCM=17A9
Mark Jacobs
Sent from ProtonMail, Swiss-based encrypted email.
GPG Public Key -
Actually it does...
Under the IBM suboption:
- Nonzero scale factors are permitted in FIXED BIN declarations.
- If the result of any precision-handling built-in function (ADD,
BINARY, and so on) has FIXED BIN attributes, the specified or implied scale
factor can be nonzero.
Under
"No, FIXED BIN(15,0) is not an integer, and the precision rules can be very
annoying to those with a Fortran mindset."
Yes it is...
Table 1. Data type definitions for PL/I
Data typeDescriptionPL/I
INT2 A 2-byte signed integer REAL FIXED BINARY (15,0)
INT4 A 4-byte signed integer REAL FIXED
Yes, you are right. And it is described in the table, but it seems not
clearly visible IMHO.
Regarding performance - I did a lot of courses on MP 2000 and some on MP
3000. And yes, MP2k was not a daemon of speed. And there was some old
stinking unpatched OS/390 system with ugly bug which forced
My €0,02
Ransomware on z/OS is very unlikely, but it is possible. We cannot say
it is impossible.
The possibility depends on some circumstances which affect the results
and possible prevention. It will be disscuessed. below (a little bit).
Will backup help? NO!
Backup may be last resort,
On 2020-09-07 16:13, Seymour J Metz wrote:
PL/I has never had integers.
You are still wrong.
Recently you have made numerous erroneous claims about PL/I.
4 is an integer in PL/I.
3 is an integer in PL/I.
The arithmetic rules for scaled fixed
point are different from those for integers.
PL/I has never had integers. The arithmetic rules for scaled fixed point are
different from those for integers. In integer arithmetic, (4/3)*6 is 6 That's
not the result you get in PL/I.
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
From:
The value 00110001 in REXX is an 8 character string. The value '00110001'b in
PL/I is an 8 bit string. The REXX equivalent would be X2C(B2X(00110001)).
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
From: IBM Mainframe Discussion List on
47 matches
Mail list logo
