- Original Message -
From: "Seymour J Metz"
Sent: Thursday, September 10, 2020 1:02 AM
You did, in the comment.
No I didn't. You misread it.
From: IBM Mainframe Discussion List on behalf of Robin Vowels
Sent: Wednesday, September 9,
Yes. My post-grad thesis was on PL/I - and on its being originally
called Fortran VI in 1962, then NPL in '64, then distributed as PL/I in
'66 together with OS/360.
I wrote PL/I before Clist/CLIST and long before REXX.
Confused am I?
On 09/09/2020 05:49, Seymour J Metz wrote:
> Have you
[Default] On 9 Sep 2020 16:16:01 -0700, in bit.listserv.ibm-main
dspiegel...@hotmail.com (David Spiegel) wrote:
>Hi Clark,
>Did you run MVS on a 4341?
>If yes, which version?
Headquarters normally did our MVT sysgens for us so this was the first
MVT sysgen I had done. After checking with Paul
Seymour J Metz wrote:
I was asking whether it supported vector instructions for FIXED, not for
FLOAT.; in particular, whether it supported FIXED BIN(127,0).
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
You would not need vector instructions to support FIXED BIN(127,s)
OS/360 always runs in BC mode.
MVS 3.8J and earlier IPL in BC mode and then change the PSW to EC mode.
Joe
On Wed, Sep 9, 2020 at 4:47 PM Seymour J Metz wrote:
> In XA mode the problem is the SIO instruction. DOS.360, OS/360, OS/VS,
> etc. don't support SSCH. Does OS/360 need BC when you
There is an LE run time option that controls whether messages are produced
for errors, or not ... your installation option has chosen no message. You
can set runtime options at system, job or individual program level. Your
cobol program can even call CEEHDLR to set its own condition handler.
Hi Clark,
Did you run MVS on a 4341?
If yes, which version?
Thanks and regards,
David
On 2020-09-09 19:12, Clark Morris wrote:
[Default] On 9 Sep 2020 14:47:15 -0700, in bit.listserv.ibm-main
sme...@gmu.edu (Seymour J Metz) wrote:
In XA mode the problem is the SIO instruction. DOS.360,
[Default] On 9 Sep 2020 14:47:15 -0700, in bit.listserv.ibm-main
sme...@gmu.edu (Seymour J Metz) wrote:
>In XA mode the problem is the SIO instruction. DOS.360, OS/360, OS/VS, etc.
>don't support SSCH. Does OS/360 need BC when you sysgen for S/370? I'm
>certain;ly not aware of such a dependency
>Enterprise PL/I 5.2 supports ARCH(12) so has your desired vector instruction
>support. For completeness, so do Cobol 6.2, XL/C 2.3 and Java 8.5. >Again no
>source code change in PL/I is needed, just recompile with
>ARCH(12) option. Really sad that IBM doesn't publicize these features
z13 added many SIMD (vector) instructions for both binary arithmetic and
strings and most support from 8b to 128b wide operands. The compilers were
updated to use SIMD for some functions, including binary integer and
string; this was for PLI 4.5. You need PLI 5.3 (newest compiler) for
ARCH(13)
On Wed, 9 Sep 2020 14:31:24 -0700, Sri h Kolusu wrote:
>
>>>Are complicated Boolean expressions supported?
>
>Yes. Check this link
>
>https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.3.0/com.ibm.zos.v2r3.icea100/ice2ca_Relational_condition.htm
>
Thanks. I see:
AND statements are
I was asking whether it supported vector instructions for FIXED, not for
FLOAT.; in particular, whether it supported FIXED BIN(127,0).
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
From: IBM Mainframe Discussion List on behalf of
Attila
In XA mode the problem is the SIO instruction. DOS.360, OS/360, OS/VS, etc.
don't support SSCH. Does OS/360 need BC when you sysgen for S/370? I'm
certain;ly not aware of such a dependency in OS/VS or VM.
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
There is no source change as the DFP option applies only to DEC FLOAT and
not to FIXED BIN. The data element storage sizes remain the same, but with
DFP the DEC FLOAT items become decimal floating point data and instructions
(and BIF) while with NODFP the DEC FLOAT is HEXADECIMAL float (as
>>>Suppose the programmer wishes to compare to binary zeroes,
Gil,
Comparing to binary zeros will let you include short records who have
length less than 21 bytes. But that is an easy fix.
Since we are dealing with VB records, the actual length is in RDW so you
can add the RDW validation in
According to this guide, the 3090 could still start in BC mode when in 370
mode. See page 7-6.
http://vtda.org/docs/computing/IBM/Mainframe/Hardware/System/SA22-7121-6_3090ProcComplexFunctionalCharacteristics.pdf
Joe
On Wed, Sep 9, 2020, 16:07 Lennie Bradshaw <
On Wed, 9 Sep 2020 13:15:43 -0700, Sri h Kolusu wrote:
>
>VLSCMP tells DFSORT that you want to temporarily replace any missing
>compare field bytes with binary zeros, thus allowing the short fields to be
>validly compared (the binary zeros are not kept for the output records).
>
>So use the
I think this happened with the move to MVS/XA as XA does not recognise a BC
mode PSW.
So I guess it was the first machine which did not support architectures earlier
than MVS/XA.
I suspect that was the 3081.
All my conjecture of course. Let's see what the IBM oracles tell us.
Lennie
> A Google search seems to find those as SYNCSORT options but not as
> DFSORT options. Is that right? But on:
Gil,
Both products have different parms.
>>> What other comparison operators are available. For example, I'd
> be interested in whether: OMIT COND=(21,8,CH,NE,C'Type 200')
You need
There are two different issues. The free S/360 and S/370 operating systems
require S/370 mode, as do the proprietary systems prior to XA and ESA. They use
SIO, which does not exist in XA, ESA or z mode. Support for that disappeared
earlier than support for XA and ESA.
--
Shmuel (Seymour J.)
DFSORT and SYNCSORT options are just not the same for this feature.
The wording would seem to imply that *any* comparison will be treated as false.
The SYNCSORT description for VLTESTI=2 seems to imply the same behavior (note
the last sentence in this quote):
"When VLTESTI=2 is specified, MFX
z13 will IPL a 24 bit O/S. z14 will not support a 24 bit DAT.
ZZSA and non-virtual memory utilities should still run.
On Wed, Sep 9, 2020 at 12:35 PM Mark S Waterbury
<01c3f560aac1-dmarc-requ...@listserv.ua.edu> wrote:
>
> To add to this thread ...
>
> I would like to know at what point
On Wed, 9 Sep 2020 17:19:55 +, Farley, Peter x23353 wrote:
>Use these PARM options for SYNCSORT to allow field references beyond the
>actual input record length:
>
>PARM=VLLTEST=2,VLTESTI=2'
>
>One of your VB input records is less than 17 bytes long (21 - 4 = 17).
>
A Google search seems to
To add to this thread ...
I would like to know at what point during the evolution from S/370 to S/370-XA
to S/390 to zSeries, did the architecture stop supporting IPL of any OS that
runs in "BC mode" or that starts out in BC mode, before setting up page and
segment tables and control registers
Thanks
> On Sep 9, 2020, at 1:20 PM, Farley, Peter x23353
> <031df298a9da-dmarc-requ...@listserv.ua.edu> wrote:
>
> Use these PARM options for SYNCSORT to allow field references beyond the
> actual input record length:
>
> PARM='VLTEST=2,VLTESTI=2'
>
> One of your VB input records is
Use these PARM options for SYNCSORT to allow field references beyond the actual
input record length:
PARM='VLTEST=2,VLTESTI=2'
One of your VB input records is less than 17 bytes long (21 - 4 = 17).
HTH
Peter
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Joseph
Hi
I am getting the above message on sortin being a VB record lrecl 3196 blocksize
32000
The include is
Include cond=(21,1,BI,EQ,X’01’)
Looking for x’01’ in pos 21 ( including RDW)
--
For IBM-MAIN subscribe / signoff /
On Wed, 9 Sep 2020 00:45:12 -0400, Phil Smith III wrote:
>Y'all are dancing on the head of a pin. As Shmuel said, Rexx has one datatype,
>period. It has the DATATYPE function that can do some
>analysis on a variable's contents and tell you whether it's all numeric, hex,
>etc. That's basically
You did, in the comment.
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
From: IBM Mainframe Discussion List on behalf of
Robin Vowels
Sent: Wednesday, September 9, 2020 11:00 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: PL/I Integer
On 2020-09-10 00:33, Seymour J Metz wrote:
Since when is 1.33... an integer?
Who said it was?
A/B (both integers with values 4 and 3 respectively),
yield exactly 1.
From: IBM Mainframe Discussion List on
behalf of Robin Vowels
Sent: Wednesday,
On 2020-09-10 00:32, Seymour J Metz wrote:
The results that you have described are not integer arithmetic. In
integer arithmetic, 4/3 is 1.
Look at the second result following the program.
You will see that A/B == 4/3 yields 1.
From: IBM Mainframe
Since when is 1.33... an integer?
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
From: IBM Mainframe Discussion List on behalf of
Robin Vowels
Sent: Wednesday, September 9, 2020 10:08 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: PL/I
From: "Paul Gilmartin" <000433f07816-dmarc-requ...@listserv.ua.edu>
Sent: Sunday, September 06, 2020 1:33 PM
On Sat, 5 Sep 2020 08:13:42 +1000, Robin Vowels wrote:
As for writing formulas, I prefer to follow a well-known formula, thus:
volume = 4/3 * 3.14159 * radius**3
Beware!
The results that you have described are not integer arithmetic. In integer
arithmetic, 4/3 is 1.
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
From: IBM Mainframe Discussion List on behalf of
Robin Vowels
Sent: Wednesday, September 9,
If the results are as you claim then it isn't integer division. Make up your
mind.
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
From: IBM Mainframe Discussion List on behalf of
Robin Vowels
Sent: Wednesday, September 9, 2020 10:18 AM
To:
If you declare a variable with maximal precision for one compiler and later
compile it on a compiler with longer maximal precision, you get digits (bits)
after the decimal (binary) point, Is it your position that FIXED variables are
integers in one compiler but not in the other?
--
Shmuel
From: "Seymour J Metz"
Sent: Monday, September 07, 2020 4:30 AM
The default type for 3 and 4 is FIXED BINARY.
Definitely NOT.
3 and 4 are decimal digits.
PL/I does not have an integer type,
It does.
but the DIVIDE() BIF can be used to do an integer divide, and assigning a
quotient to
From: "Seymour J Metz"
Sent: Monday, September 07, 2020 5:33 AM
PL/I doesn't have integers.
It does.
Believe it or not, the constants 4 and 3 that you wrote in the
next sentence are decimal INTEGERS.
The ratiio 4/3 is FIXED BIN,
with some number of bits after the binary point.
No. The
No source change? Certainly the compiler could interpret FIXED BIN as FIXED
BIN(127,0), but if I've coded, e.g., FIXED BIN(60,3), I would hope that the
compiler would only use a doubleword unless and until I changed the source and
recompiled.
--
Shmuel (Seymour J.) Metz
From: "Joe Monk"
Sent: Monday, September 07, 2020 1:05 PM
"No it isn't. 4/3 yields 1.33... to 15 digits,
and is of precision (15,14)"
Depends on RULES(IBM) or RULES(ANS). If its RULES(IBM) it will never be
integer division. If its RULES(ANS) and the operands are unscaled, then it
will
AFAIK, the vector instructions don't support more than 128 bits, so even if I
need more I won't get it.
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
From: IBM Mainframe Discussion List on behalf of
Robin Vowels
Sent: Wednesday, September
- Original Message -
From: "Seymour J Metz"
Sent: Monday, September 07, 2020 3:02 PM
Subject: Re: Constant Identifiers
4/3 yields 1.3, 04/3 yields 1332, ...
Rubbish.
4/3 yields 1.33
INTEGER_DIVISION:
PROCEDURE OPTIONS (MAIN);
DECLARE (A, B) FIXED DECIMAL (15);
A =
From: "Seymour J Metz"
Sent: Monday, September 07, 2020 4:13 PM
PL/I has never had integers.
It always has 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.
Yes it
Thank you, Attila.
This clears up my doubt with the slash symbol in the parm.
On Tue, Sep 8, 2020 at 5:27 PM Attila Fogarasi wrote:
> You have to precede the parm with a "/" ... for LE-conforming programs the
> LE options appear on the JCL EXEC PARM='LEruntimeparm/programparms' ... so
> you
Yuksel
Thank you for that information and I'm sorry I haven't responded sooner
(other work took precedence, as is so often the case).
Your modification to the 'run' command has worked exactly as required. I
now have cadvisor running on my zcx system and overall CPU utilisation is
down to a much
On Wed, 9 Sep 2020 17:16:22 +1000 Robin Vowels wrote:
:>On 2020-09-09 14:53, Seymour J Metz wrote:
:>> Has IBM announced an intention to support the vector instructions to
:>> allow more precision for FIXED DEC and FIXED BIN in PL/I?
:>FIXED DECIMAL gives you up to 31 digits.
:>FIXED BINARY
If it supports being disabled, why not|?
On Tue, 8 Sep 2020 20:47:30 -0400 Joseph Reichman
wrote:
:>
:>
:>thanks
--
Binyamin Dissen
http://www.dissensoftware.com
Director, Dissen Software, Bar & Grill - Israel
Should you use the mailblocks package and expect a response from me,
you should
On 2020-09-09 14:53, Seymour J Metz wrote:
Has IBM announced an intention to support the vector instructions to
allow more precision for FIXED DEC and FIXED BIN in PL/I?
FIXED DECIMAL gives you up to 31 digits.
FIXED BINARY gives you up to 63 bits.
How much do you need?
Are there
other
Got it looked if the macro has to be enabled for interrupts thanks
> On Sep 9, 2020, at 1:49 AM, Jim Mulder wrote:
>
> The documentation for each macro has a section labeled
> "Environment". Is there a particular macro for which you have
> read the documentation and you are unable to
Enterprise PL/I 5.2 supports ARCH(12) so has your desired vector
instruction support. For completeness, so do Cobol 6.2, XL/C 2.3 and Java
8.5. Again no source code change in PL/I is needed, just recompile with
ARCH(12) option. Really sad that IBM doesn't publicize these features
better
For greater precision Enterprise PLI supports the hardware Decimal Floating
Point which is enabled with the compiler option of FLOAT(DFP), this then
changes all the DECIMAL FLOAT data declarations to be DFP allowing maximum
34 digits (and exact decimal precision, important for financial
51 matches
Mail list logo
