LOL! I'm reminded that DYL-280II was advertised as a 4GL, with English-like
syntax. Neither is true, to my mind. I like DYL-280II, and taught classes in
it at my employer of the time (Volvo Truck NA) as well as workshops at the
DYLAKOR conferences. But it's not a 4GL.
Well, not in the
I haven't written anything in FORTRAN since some time in the late '70s. But
even much more recently I heard it's regarded by number crunchers, engineers
say, as the best language for sheer speed. Not so great for report writing
and formatting.
---
Bob Bridges, robhbrid...@gmail.com, cell 336
On Mon, 8 Jun 2020 20:50:12 -0500, Joe Monk wrote:
>In this case, because we are PERFORMing THRU, then GO TO exit, merely
>causes an iterate.
>
It's so nice of COBOL to be written in common language so
any English speaker can intuitively grasp it correctly.
>On Mon, Jun 8, 2020 at 7:36 PM Frank
FORTRAN 90 was a significant upgrade over previous standards. Mainly, free-form
input source statements.
Also, increase the length of identifiers from 6 characters to 31 characters,
and upper/lowecase keywords/identifiers.
The latest standard is Fortran 2018.
I still teach Fortran to my Honor
On 2020-06-09 5:02 AM, Kirk Wolf wrote:
used as an alternative. I doubt that ISPF is POSIX pipe-savvy.
What does UNIX have to do anything in this specific context?
Bottom line: I can't imagine that you couldn't write a "PyISPF" package
with wrappers for all of the functions.
It can be done
June 6 was Ibm-main's 34th birthday. Darren's been the list owner the whole
time.
In a message dated 6/8/2020 2:21:57 PM Central Standard Time,
frank.swarbr...@outlook.com writes:
I can't seem to find any way to give a "thumbs up" to a listserv post. So
consider this to be a virtual thumbs
On, long ago and on some DOS/VS Cobol compiler, after a compiler upgrade,
there was a problem with a statement something like this:
READ some-file AT END do somethingMOVE A TO B.
See the problem? The period after the AT END was omitted. The old compiler
only allowed one statement after AT
In this case, because we are PERFORMing THRU, then GO TO exit, merely
causes an iterate.
Joe
On Mon, Jun 8, 2020 at 7:36 PM Frank Swarbrick
wrote:
> GO TO to an "exit" procedure (that is, a procedure that terminates
> unconditionally terminates the program) is, in my mind, acceptable as
>
I've been teaching myself (modern) Fortran the last few weeks. Just because.
It has an interesting behavior that I kind of like.
Normal IF statement:
if (something) then
end if
But it also has a "one line IF" (not sure offhand of the Fortran "name" for
this):
if (something)
must
Metz wrote:
> Wrong again. As with any other expression, quotes are for string literals,
> not variables, and it is legitimate to use variables
either by themselves or as part of a more complex expression, e.g., address
value 'FOO'bar
"I believe I said that, Doctor." OK, I didn't say it
Were there really three releases of VS COBOL II that didn't implement COBOL
1985? I thought there was only one. But I didn't live through it. I
generally think of COBOL II and COBOL 1985 as being "the same", since that was
(essentially) the case by the time I became a COBOL developer (in
Apologies again if this has already been answered. I'm a few days behind.
You can use a full stop (period) to terminate an IF statement. The "problem"
is (and one of the any reasons I elide all periods that are not absolutely
required) it terminates an entire COBOL "sentence" (not just a
GO TO to an "exit" procedure (that is, a procedure that terminates
unconditionally terminates the program) is, in my mind, acceptable as well. In
fact, if you try to "perform" a "terminal" exit procedure the compiler will
give you a warning that your "calling" procedure will never reach its
With Enterprise COBOL V5 and up you could do the following:
PERFORM VARYING JC FROM 1 BY 1 UNTIL JC > 99
IF X > 999 EXIT PERFORM CYCLE END-IF
IF FIRST-NAME = "ROBERT" EXIT PERFORM CYCLE END-IF
IF TYPE <> 195 EXIT PERFORM CYCLE END-IF
IF NOT SO-ON EXIT PERFORM CYCLE END-IF
IF
The boss said that he understood why I would want to wait
A week or two to run the PUT, but not six months or eight
He made me do a mass APPLY, but later said to me
The reason for the long delay I now begin to see!
Mañana, mañana, mañana is soon enough for me.
I once installed a FUNCTION, with
On Mon, Jun 8, 2020 at 2:04 PM Paul Gilmartin <
000433f07816-dmarc-requ...@listserv.ua.edu> wrote:
> On Mon, 8 Jun 2020 13:08:44 -0400, Tom Conley wrote:
>
> >On 6/8/2020 12:56 PM, Frank Myers wrote:
> >> Can ISPF services, such as panel display, be called from Python? I know
> they can be
I can't seem to find any way to give a "thumbs up" to a listserv post. So
consider this to be a virtual thumbs up.
(Yes, I am kidding about not being able to find how to do it. I realize that
listserv far pre-dates Twitter, Facebook and the like.)
From:
On Mon, 8 Jun 2020 13:08:44 -0400, Tom Conley wrote:
>On 6/8/2020 12:56 PM, Frank Myers wrote:
>> Can ISPF services, such as panel display, be called from Python? I know they
>> can be called from rexx & TSO clists.
>
>Try using Python's equivalent of CALL ISPLINK (use the COBOL and PL/I
I got a 404 clicking on one of the links, but
http://bitsavers.org/pdf/ibm/_by_part_number_online_20191026.txt worked.
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
From: IBM Mainframe Discussion List on behalf of
Richards, Robert B.
The old Share Sing Along book had an orange cover, I have one in the office but
since I've been working from home since March I can't put my hands on it right
away.
Ken Mazer
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Dave Jones
Sent: Monday, June 08, 2020
On 6/8/2020 12:56 PM, Frank Myers wrote:
Can ISPF services, such as panel display, be called from Python? I know they can be
called from rexx & TSO clists.
Frank
Frank,
Try using Python's equivalent of CALL ISPLINK (use the COBOL and PL/I
examples in the ISPF doc).
Regards,
Tom Conley
Did you try looking on SHARE.ORG to see if they are listed there? You might
need to be a member to do this
Lizette
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Dave Jones
Sent: Monday, June 8, 2020 9:03 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Old SHARE
I hope I'm understanding what you are saying.
Localhost is for use ONLY within a single TCPIP stack or system. It is another
way of writing non-routable IP address '127.0.0.1'.
Maybe configuring host files will allow you to do this but that will be very
confusing and awkward to support.
You
No, I mean the ones put out by SHARE itself. I seem to remember that they were
orange in color, but that could very well be incorrect. Thanks, though.
DJ
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send
If you mean those books, I found this link at Watson and Walker:
https://watsonwalker.com/publications/ibm-systems-center-books/
-Original Message-
From: Richards, Robert B.
Sent: Monday, June 8, 2020 12:09 PM
To: IBM Mainframe Discussion List
Subject: RE: Old SHARE publications?
Don't you mean WSC (Washington System Center) Orange books?
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Dave Jones
Sent: Monday, June 8, 2020 12:03 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Old SHARE publications?
I'm trying to locate some old SHARE
I'm trying to locate some old SHARE documentation. IIRC, back in the 1980s and
early 90s SHARE published technical contributions from the members as "Orange
Books:; anybody know where they might be found these days?
Many thanks.
DJ
Only if localsthost is defined as such in the RESOLVER configuration or your
DNS systems
> -Original Message-
> From: IBM Mainframe Discussion List On
> Behalf Of Sean Gleann
> Sent: Monday, June 08, 2020 6:15 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: AZD messages?
>
> As far as
On 6/6/2020 2:53 PM, Bill Giannelli wrote:
This is command I am currently using:
SET BOUNDARY (GLOBAL) .
RECEIVE
FROMNETWORK(
SERVER(SERVINFO)
CLIENT(CLNTINFO)
)
.
So because I am NOT specifying "transferonly" all the
As far as I understand things, 'localhost' is just another way of saying
'127.0.0.1' meaning 'this computer', so - yes, localhost is defined.
I have an SSH connection defined in PuTTY that associates my local 10443
with the host system's 10443, and I start that connection before attempting
to go
Is localhost defined?
Sent from my iPad
> On Jun 8, 2020, at 8:16 AM, Sean Gleann wrote:
>
> Thanks for the hint about thoroughly checking output, Michael.
> I went back and studied all the saved outputs, hoping to find something
> that might be helpful.
> In the event, there were no
Thanks for the hint about thoroughly checking output, Michael.
I went back and studied all the saved outputs, hoping to find something
that might be helpful.
In the event, there were no indications of such problems - no error
messages or non-zero return codes - but it's as well to be sure.
Can I
In PL/I, yes, but not in REXX.
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of
Wayne Bickerdike [wayn...@gmail.com]
Sent: Monday, June 8, 2020 12:59 AM
To:
Didn't Datamation introduce COMEFROM much earlier?
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of
Peter Sylvester [peter.sylves...@gmail.com]
Sent: Monday, June 8,
It didn't help that he contradicted himself as to whether GOTO should be banned.
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of
Wayne Bickerdike [wayn...@gmail.com]
I learned JSP back in the early 90's. It was popular in the UK (Jackson
was British) and most large mainframe companies adopted it. It was good.
There was even tooling that
could create code from charts.
Dijkstra's paper is one of the most controversial CS papers ever
written. It was written
Some wag published this in an internal IBM publication back in 1978, with
full examples. It sucked us in at the time.
On Mon, Jun 8, 2020 at 6:01 PM Peter Sylvester
wrote:
> Hi,
>
> Presented in an April 84 edition of a scientific journal. The fortran
> COMEFROM nnn :-)
>
> A student in
Dijkstra wrote his missive around 1968. Knuth made a meal of it and after
reading his paper which was published 5 years later, it was too hard a read.
Around the same time Michael Jackson was distilling this information and
produced his structured programming book "Principles of Program Design".
Hi,
Presented in an April 84 edition of a scientific journal. The fortran COMEFROM
nnn :-)
A student in internship in the 80 implemented it (as a joke to see whether his prof reads the work)
for his fortran 88 compiler.
The implementation is simple.
Peter Sylvester
On 2020-06-07 10:48 PM, Paul Gilmartin wrote:
I consider the out of line PERFORM to be far more dangerous. I have a similar
issue with REXX; it does not have lexical scope, and you can fall into a
procedure.
A noteworthy 1976 paper (behind a paywall):
Software malpractice — a
Results:
1
0
0
0
***
On Mon, Jun 8, 2020 at 4:06 PM Wayne Bickerdike wrote:
> /* REXX */
> COUNTT = 0
> COUNTU = 0
> COUNTV = 0
> COUNTW = 0
> TAB.T = "COUNTT=COUNTT+1"
> TAB.U = "COUNTU=COUNTU+1"
> TAB.V = "COUNTV=COUNTV+1"
> TAB.W = "COUNTW=COUNTW+1"
> IDX = 'T'
>
> INTERPRET
/* REXX */
COUNTT = 0
COUNTU = 0
COUNTV = 0
COUNTW = 0
TAB.T = "COUNTT=COUNTT+1"
TAB.U = "COUNTU=COUNTU+1"
TAB.V = "COUNTV=COUNTV+1"
TAB.W = "COUNTW=COUNTW+1"
IDX = 'T'
INTERPRET TAB.IDX
SAY COUNTT
SAY COUNTU
SAY COUNTV
SAY COUNTW
On Mon, Jun 8, 2020 at 3:10 PM Wayne Bickerdike
42 matches
Mail list logo
