I wrote a program -- robust enough to be part of a vendor product -- that
read and processed assembler SYSADATA using LE-supported C++. I found no
problems with "flexibility." I would be curious in what way you found it
inflexible.
As is my general approach with C++, I did alpha testing on MS Visu
r Relson would be saying if he read this (“how did
they let that guy in the door”)
> On Jan 26, 2020, at 12:38 PM, Charles Mills wrote:
>
> I wrote a program -- robust enough to be part of a vendor product -- that
> read and processed assembler SYSADATA using LE-supported C++.
I believe you. The input for my program tends to be relatively smaller
assemblies.
> Correct me if I am wrong but total number of records are at the end of the
> file record type Two
Could be. That is how I read the following:
Record Count FL4 On an ADATA Compilation Unit End record, a count o
It IS available, apparently, for a fee. Speak with your friendly IBM rep.
And yes, if this answer makes you go "gr" then trust me, you are not alone.
Charles
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Steve Smith
Sent: Tues
Well you're right, but I wasn't even thinking of that aspect. I was just
thinking of "why 64-bit?"
I would think you ought to be able to safely guess you could do a 30MB GETMAIN
in 31-bit private. If every assembler statement generates 1000 bytes of ADATA,
or rather, ADATA that you need to save
If you're not a C++ person you may hit Delete at any time ...
I want to load a module that is a non-executable table (and non-reentrant)
and then modify it.
I have the entry point declared as
extern "OS" typedef int compiler_t(void *parm1);
compiler_t *opts;
(compiler_t is what is expected by
Hmmm.
V2R2
Charles
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Allan Kielstra
Sent: Wednesday, January 29, 2020 12:18 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: C++ reinterpret_cast question
FWIW, you don't get this warning w
@Allan and @Joseph, I should have said that this as an intellectual exercise I
want to write C++ that makes the warning go away, not a #pragma or similar that
suppresses the message.
Yes, I know that all casts are dangerous. A extern "OS" * is I believe always
the address of an "old-fashioned"
Charles
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Gord Tomlin
Sent: Wednesday, January 29, 2020 11:42 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: C++ reinterpret_cast question
On 2020-01-29 13:29, Charles Mills wrote:
> If you
Tried just a simple C-style cast (myStruct *)opts;
No joy. For some reason extern "OS" * to struct * seems to require a two-stage
cast.
Charles
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Charles Mills
Sent: Wednesda
X-posted IBM-MAIN and RACF-L.
Who do you trust? What CERTAUTH certificates do you have installed and
trusted?
I am contemplating purchasing an FTP server certificate for z/OS client FTP
access. I'd like to know which CA's are most likely to already be installed
in customers' CERTAUTH keyrin
https://www.nytimes.com/2020/01/30/technology/ginni-rometty-ibm-ceo.html
Charles
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
The allusion was intentional.
Someone wrote me offline to criticize the use of who rather than whom. I
responded that I doubted Bo Diddley would have had a hit with "Whom Do You
Love"? In his case, I believe there may also have been an allusion to "hoo-doo."
Charles
-Original Message-
95 Mobile
> 626-543-6132 Office ⇐=== NEW
> robin...@sce.com
>
> -Original Message-
> From: IBM Mainframe Discussion List On Behalf Of
> Charles Mills
> Sent: Friday, January 31, 2020 2:52 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: (External):Re: Who do you trust?
I would assume that Gord is using the EDCDSECT program which is legally part of
the XLC compiler. It assembles the DSECT -- can be either by itself or part of
some larger assembly -- and massages SYSADATA to produce a C-legal struct.
The result -- particularly for older IBM DSECTs -- is often sp
AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Convert a Metal C control block mapping to Assembler DSECT ?
On Fri, 14 Feb 2020 10:52:07 -0800, Charles Mills wrote:
>I would assume that Gord is using the EDCDSECT program which is legally part
>of the XLC compiler. It assembles the DSECT -- can be eit
el's recommendation.
That should have been "agree with Gord's recommendation."
Charles
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Charles Mills
Sent: Friday, February 14, 2020 12:27 PM
To: IBM-MAIN@LISTSERV
I have code that I maintain that supports (among other things) the
allocation of a DD to a software vendor-provided subsystem we will call
. My code does an SVC 99 dynamic allocation with text key 5F. At a
particular customer the allocation succeeds without error but subsequent
usage of the all
Thanks all (including someone in POK -- you know who you are -- thank you for
the background on SUBSYS).
I am regrouping. I have gotten the customer to agree to a de-prioritizing of
the problem, so it may be a little while before I tackle this.
I think I understand what is happening. Between my
There is at least a "technical" risk that the status of the address space
could change to swappable between your TM and whatever action you do based
on the determination of non-swappability, but for personal use software I
suppose you might find that risk acceptable.
Does non-swappable guarantee "
Huh? Void * specifically says "foo points to something but I won't say what" so
no, you can't reference members of something you have not specified. It is
equivalent to assembler FOO DS A. A of what? Who knows.
If you say myStruct * foo then yes you can say foo->myStructMember. Or you can
say "
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
____
From: IBM Mainframe Discussion List on behalf of
Charles Mills
Sent: Tuesday, February 25, 2020 12:26 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Convert a Metal C control block mapping to Assembler DSECT ?
H
ue, 25 Feb 2020 09:26:45 -0800, Charles Mills wrote:
>
>Continuing the assembler analogy, myStruct * foo is roughly equivalent to
>assembler L Rn,FOO/USING MYSTRUCT,Rn .
>
Pascal's WITH statement allowed brief member references without
the requirement for unique names.
>
> ________
> From: IBM Mainframe Discussion List on behalf of
> Charles Mills
> Sent: Tuesday, February 25, 2020 12:26 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: Convert a Metal C control block mapping to Assembler DSECT ?
>
> Huh? Voi
The basic starting point is
https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.2.0/com.ibm.zos.v2r2.ieaa600/subtcc.htm
.
SYS1.SAMPLIB(TESTEXIT) has some ATTACH and so forth.
Charles
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
OT. This forum is limited to questions related to punctuation and rotary dial
phones.
Charles
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Bernd Oppolzer
Sent: Friday, February 28, 2020 12:39 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subje
What did I hear once? If the prototype is not successful they don't ever do
the permanent solution. And if the prototype is successful it becomes the
permanent solution.
Charles
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf Of Seymour
Amen to every one of your points!
Charles
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Farley, Peter x23353
Sent: Friday, February 28, 2020 9:38 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: VSE related questions - VSAMIO on VSE
T
: Saturday, February 29, 2020 12:42 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: OT Boeing flight software
Charles:
Like we used to call Production testin, if the code doesnt work its test
and if it works its Production.
I used laugh at this line a lot.
Scott
On Fri, Feb 28, 2020 at 5:57 PM
> KKR, one of the world's largest private equity firms, owns 100% of BMC.
... and apparently believes in the mainframe. They're sure buying a lot of
mainframe software companies. (They bought my former employer, CorreLog, a
little over a year ago.)
Charles
-Original Message-
From: IBM M
.
KKR loves the cash flow generated..
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Charles Mills
Sent: Tuesday, March 3, 2020 8:55 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: BMC and Compuware
[CAUTION: This Email is from outside the Organization. Do not clic
Presumably SVC 99 to SYSOUT X is a minority of the cases. The OP might be happy
if he could prevent the majority.
Charles
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Paul Gilmartin
Sent: Tuesday, March 3, 2020 6:41 AM
To: IBM-MA
I hesitate a little to possibly just add to the noise because I don't really
know the answer; I'm just hypothecating.
Does a workstation necessarily have a name? In the protocol, I mean. A dumb
terminal with no name can do telnet. Is there anything to the connection
request other than "Hi, I'm
1. Is there a way to display the entry point address of a load module member
of a PDS? ISPF 3.1 shows Size, TTR, AM, RM, etc. but not the entry address.
The member in question is actually an alias FWIW.
2. The reason I ask is that I am trying to track down the following problem.
Perhaps someone kn
to
prevent that?
Charles
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf Of Charles Mills
Sent: Tuesday, March 3, 2020 11:35 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Two related alias entry address questions
1. Is there a way to display
n
Sent: Tuesday, March 3, 2020 11:43 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Two related alias entry address questions
On Tue, 3 Mar 2020 11:35:02 -0800 Charles Mills wrote:
:>1. Is there a way to display the entry point address of a load module
member
:>of a PDS? ISPF 3.1 shows Size,
Thanks. I had the same thought myself. Just tried it. No difference.
Charles
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf Of Seymour J Metz
Sent: Tuesday, March 3, 2020 11:51 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Two related al
s
word for word the same.
Charles
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Pew, Curtis G
Sent: Tuesday, March 3, 2020 11:59 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Two related alias entry address questions
On Mar 3, 2020,
] On Behalf
Of Paul Gilmartin
Sent: Tuesday, March 3, 2020 1:15 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Two related alias entry address questions
On Tue, 3 Mar 2020 12:37:31 -0800, Charles Mills wrote:
>"Getting the aliases" is not an issue; getting the alias's entry point off
COPYGRP produces exactly the same erroneous result.
Charles
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf Of Seymour J Metz
Sent: Tuesday, March 3, 2020 12:50 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Two related alias entry address
Got it! Not sure exactly what the key ingredient was but I suspect that the
problem was that I had @Gil's un-externally-named entry point:
BAR DS 0D
...
END BAR
I changed that to
BAR DS 0D
ENTRY BAR
END
My experimentation took wy longer than it should have and I am uncertain of
COPY?
Charles
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Dale R. Smith
Sent: Tuesday, March 3, 2020 4:51 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Two related alias entry address questions
On Tue, 3 Mar 2020 12:37:31 -0800, Charl
No one seems surprised or alarmed that IEBCOPY fails an operation but still
ends with RC=0 ?
Charles
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Charles Mills
Sent: Tuesday, March 3, 2020 4:36 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Peter, thanks for the note. I'm on a small screen with fat fingers. I will
reply fully, tonight or tomorrow. I know the paragraph makes my head spin.
CharlesSent from a mobile; please excuse the brevity.
Original message From: Peter Relson Date:
3/4/20 6:33 AM (GMT-08:00) To:
Sometimes you make a code change, and the problem is no better, so you wonder
"did I screw up the code change or am I still running the old code?"
CharlesSent from a mobile; please excuse the brevity.
Original message From: Binyamin Dissen
Date: 3/5/20 11:07 AM (GMT-05:00) To
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Charles Mills
Sent: Wednesday, March 4, 2020 1:50 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Two related alias entry address questions
Peter, thanks for the note. I'm on a small screen with fat fingers. I will
@Peter, did you have an ENTRY BAR statement in the assembly? I think that
statement was the key ingredient that made IEBCOPY consistently preserve the
alias entry point address. I am not certain of what was the key ingredient
because I kept running experiments, getting IEBCOPY RC=0, and finding no
Re: Two related alias entry address questions
On Fri, 6 Mar 2020 09:13:39 -0500, Charles Mills wrote:
>Third, with regard to IEBCOPY's failing and then exiting with return code
>zero, I can't find any documentation that specifies the >meaning of a zero
>return code, but
-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Paul Gilmartin
Sent: Friday, March 6, 2020 5:27 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Two related alias entry address questions
On Fri, 6 Mar 2020 16:44:09 -0500, Charles Mills wrote:
>> IEBCO
Well, I've got a smoking gun.
https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.3.0/com.ibm.zos.v2r3
.ieam900/iea3m9_IGW_messages.htm says of messages such as IGW01557W:
For messages with the prefix IGW01, the type codes indicate the severity of
the detected error and are:
E
Error: Return co
No, no, @Peter, that's not my point. System messages are system messages and
I don't have to like them but they are what they are. I get to vent here but
I accept that they are highly unlikely to change.
My point below is relative only to IEBCOPY. IGG0nnnW messages are documented
as resulting in a
List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf Of Charles Mills
Sent: Monday, March 9, 2020 6:24 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Two related alias entry address questions
My point below is relative only to IEBCOPY. IGG0nnnW messages are documented
as resulting in a return code 4. IEBCOP
: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Two related alias entry address questions
Seems to me that should be reported as a bug. It's not technically an
enhancement to make the program conform to its documentation.
sas
On Wed, Mar 11, 2020 at 4:18 PM Charles Mills wrote:
> If anyone el
A *very* crude approach is to look at any RACF violation message on the console
and translate that into a PERMIT command: PERMIT resource CL(class) ID(id)
ACC(acc). There is typically a resource, a class and the access in the
messages. You may have to apply some "intelligence" -- for example, if
I wrote a piece of software that processed *certain SMF 119 subtypes*. They
were all "event" type records such as a TN3270 connection, a TN3270
disconnection, and so forth. For those purposes I was if I recall correctly
able to utterly ignore this flag. Your mileage may vary.
An event record is
Does CLIST have the kind of debugging facility that Rexx has? Can you assign
some initial values and then step through the code seeing what is happening?
I am going to guess not, but thought it worth asking.
I know nada CLIST. When I left the OS/360 family of operating systems
somewhere around 197
Which it always should be, to avoid surprises.
Charles
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Paul Gilmartin
Sent: Friday, March 20, 2020 6:47 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Does anybody remember CLIST?
On Sat
SYSSTATE has never entirely "felt right" to me. For some things -- like ARCH --
it makes sense. "Hey assembler, when you assemble MVS macros, assume that the
XA instructions are available." That makes sense. Your routine might get called
by code running on a pre-XA box? Then don't specify that A
Perhaps a training concern?
I am not defending a lack of training -- just theorizing that "we would have to
train everyone in IPCS" is a management concern.
Granted, no one was born with SYSUDUMP debugging skills.
What about the various tools out there? Abend-AID and the like are not
sufficien
that training an application programmer to read a
SYSUDUMP is easier than training him to use IPCS? I don't buy it.
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of
Ch
"64-bit" has not really been on application programmers' plates until COBOL
6.3.
And yes, debuggers and dumps certainly overlap. I would guess that Compuware
would assert that Abend-AID plays in the debugger space, and it is very much
an alternative to the 3700-page dump.
+1 on the need for serio
I did not know that.
Hmmm. Neither does the JCL Reference, it appears: "[SYSMDUMP DD] must be
processed by the
interactive problem control system (IPCS) and therefore should not be
directed
to SYSOUT."
Or am I missing the concept?
Charles
-Original Message-
From: IBM Mainframe Discussio
Why the determination not to financially reward the developers for their
efforts? Why would I hypothetically write a 3270 emulator if it's not important
enough to pay for?
Why are computer people so loathe to financially reward computer people?
We're not talking 1% territory here. Tom Brennan's
I'm looking at Python on the Rocket site.
Practically speaking, is Python usable from TSO or only from the UNIX command
prompt? That is
> There's no advantage to REXX anymore, as fine a language as it is.
In Rexx under TSO, I can allocate couple of datasets and then run a "legacy
MVS" (you kno
> Are you actually seeing resistance to priced software, or only to OCO
software?
I was referring to the OP's "Is there a ... free alternative emulator ...?"
Frankly I don't think I have seen any resistance to OCO in twenty years,
other than on this list. Many, many customers nowadays would not k
From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of
Charles Mills [charl...@mcn.org]
Sent: Sunday, March 29, 2020 11:34 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Free 3270 emulator for Mac OS
> Are you actually seeing resistance to priced soft
A member name would quite typically be a character string enclosed in
apostrophes.
Also, it's not the assembler, it's the hardware, but assembler "processes"
distinguishes case. CLC of storage containing is not equal to storage
containing . A member name might be in storage passed to DESERV.
Ch
ch 28, 2020 11:23 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: strange python announcement
On 2020-03-29 7:42 AM, Charles Mills wrote:
> I'm looking at Python on the Rocket site.
>
> Practically speaking, is Python usable from TSO or only from the UNIX command
> prompt? That is
Charles
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Paul Gilmartin
Sent: Sunday, March 29, 2020 12:19 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: strange python announcement
On Sun, 29 Mar 2020 11:43:56 -0700, Charles Mil
Hardware upward compatibility of problem state code is darned near 100%.
Some privileged instructions have gone away, but that is only a concern if you
are porting an OS, or OS-like code such as "extreme" system exits.
Software compatibility is 98 or 99%. For example, application code that assum
As does IBM XLC. Supports fopen("//DD:ddname(member)", r);
But I suspect it allocates to the member as Shmuel alludes; it does not use
allocate/OPEN/FIND.
I just did a Find on in the XLC P/G and got zero hits. (For I got
15.)
There is no exposure of DESERV or anything like that (although I s
C has multi-dimensional arrays. True n-dimensional arrays, not arrays of
arrays.
Charles
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf Of Seymour J Metz
Sent: Monday, March 30, 2020 8:23 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: str
PuTTY.
Charles
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of David Crayford
Sent: Monday, March 30, 2020 2:30 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: strange python announcement
On 2020-03-30 3:30 AM, Charles Mills wrote:
>&g
Not beating up on VSE. ("My OS is better than your OS.") DOS/360 was my first
IBM OS.
But the negative -- what OS/360 was trying to avoid -- is deadly embrace. What
if that 5-hour job gets up to the end and then CANNOT allocate the VSAM file?
And worst case, what if the program that owns it is
Dynamic allocation? Just in time dynamic allocation DISP=OLD of the viewable
dataset?
Charles
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Bob Bridges
Sent: Monday, March 30, 2020 8:51 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re:
Shmuel I know you hate C and I am sure you can find things that C cannot do.
You name a language; there are things it cannot do. (You seem to be quite
the expert in C for a guy who hates it!) I'll admit it: I don't know what
most of the things you name are. No, it is not an array-processing languag
t of hereditary boredom with he
knows not what, and already weary of hearing what he has never heard. -from
the Introduction to _Everlasting Man_ by G K Chesterton */
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Charles Mills
Se
My wild-@ssed *guess* would be that the compiler is clever enough to avoid
the use of the "clobbers" registers, and save/restore them if it cannot do
so reasonably.
That darned C compiler is pretty smart about registers.
Charles
-Original Message-
From: IBM Mainframe Discussion List [ma
There were apparently several "VISAMs" around, because OCCURS DEPENDING is such
a basic feature of COBOL but RECFM=V was not supported by ISAM.
I had a client (not FSA but interestingly also in the financial package
software business) that had its own homegrown (AFAIK) VISAM. It used short
fixe
I think using the SVC 99 returned DD name is a "best practice" although if you
can make up a guaranteed-unique DD name of your own it's hard to see what's
wrong with that. If I had such code and it worked I would not touch it, but for
new code I would be using the SVC 99 service.
Charles
A "race condition" would refer in this case to two tasks both allocating the
same "unused" DD name at the same time. I would assume that SVC 99 uses ENQ to
prevent this from happening; your Rexx relies on luck (with mighty good odds in
its favor).
Charles
-Original Message-
From: IBM
2020 13:46:07 -0700, Charles Mills wrote:
>RECFM=V was not supported by ISAM.
It most certainly was. We used it in the early 1970s at Wayne State
University for the Admissions system.
--
For IBM-MAIN subscribe / signoff / archive ac
> By the way, what ~is~ SVC 99?
First, note that three terms are used pretty much interchangeably: SVC 99,
DYNALLOC, and "Dynamic Allocation." I will use the term SVC 99 here. DYNALLOC
is an assembler macro that does not do much of anything except issue SVC 99.
(You know what a supervisor call
: Wednesday, April 1, 2020 11:13 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: PARM= vs PARMDD= and symbol substitution
On Wed, 1 Apr 2020 09:01:12 -0700, Charles Mills wrote:
>I wonder if the true statement is "ISAM did not support updating a record if
>the length changed."
No,
Because Peter didn't write LE?
Charles
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf Of David Crayford
Sent: Thursday, April 2, 2020 8:04 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: ESPIE question (does ESPIE "cover" ATTACH'd sub-tas
I had the same observation. Sending every condition through the same handler
was advantageous for me.
You would want to keep the SPIE if program checks were expected: perhaps a
report generator where you anticipated that users might declare fields to be
packed when they were not always valid.
020-04-02 14:14, Charles Mills wrote:
> I had the same observation. Sending every condition through the same handler
> was advantageous for me.
Same here.
>
> You would want to keep the SPIE if program checks were expected: perhaps a
> report generator where you anticipated that us
Look at the Ratio column for "normalized" numbers.
ESPIE beats everything. That's the point. If (a.) all you need to trap is
program checks; and (b.) you expect a bunch of them -- use ESPIE.
Charles
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU
IE "cover" ATTACH'd sub-tasks)
I saw the Ratio column. comparing lines 2 and 3 of the chart, the ratio doesn't
make sense if the number of iterations for ESTAEX is only 1/10 of the number
for FRR, yet it took over twice as long. Perhaps Jim will clarify.
On Fri, 3 Apr
Let's say you were writing a report generator. You are processing data of
unknown quality using field definitions generated by inexperienced
programmers, and report programs written by non-programmers. You might
expect a fair number of arithmetic operations on packed fields that
contained invalid d
(does ESPIE "cover" ATTACH'd sub-tasks)
On 4/4/2020 10:29 AM, Charles Mills wrote:
> Let's say you were writing a report generator. You are processing data of
> unknown quality using field definitions generated by inexperienced
> programmers, and report programs wri
e interrupts?
Anything but a cache fault is cheap, and TP won't throw a cache
fault unless one was about to happen anyway.
>
>From: Ed Jaffe
>Sent: Saturday, April 4, 2020 2:03 PM
>
>On 4/4/2020 10:29 AM, Charles Mills wrote:
>>
Don't want to beat this thing to death but FWIW I meant "ABEND" in the sense
I hear it usually used: to abnormally end, to blow up, to go kaput. When
someone says "payroll ABENDed last night" they typically in my experience
don't mean it took an ESTAE exit and recovered transparently. They mean it
If there's a market for BSC-based 3270 emulators, let me know. I've written
two. (Well, one I only wrote the BSC to/from screen buffer part; my
associate John wrote the keyboard and display part.
Charles
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.U
I agree totally but FWIW I find that the line commands UC and UCC/UCC go a long
way toward making the process tolerable.
Charles
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of John McKown
Sent: Thursday, April 9, 2020 5:02 AM
To: I
SERV.UA.EDU] On Behalf
Of Paul Gilmartin
Sent: Thursday, April 9, 2020 9:01 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: JCL & UNIX coding.
On Thu, 9 Apr 2020 08:33:50 -0700, Charles Mills wrote:
>I agree totally but FWIW I find that the line commands UC and UCC/UCC go a
>long way
pril 9, 2020 10:18 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: JCL & UNIX coding.
On Thu, 9 Apr 2020 10:07:50 -0700, Charles Mills wrote:
>
>When what I would like is
>
>//SYSPRINT DD SYSOUT=*the blah blah report
>
>Need the "do what I meant" feature implemen
+1 on all counts.
And follow the interviewer's lead: if s/he says "we don't believe in those
illegal hippie bootleg mainframes!" then for gosh sakes don't bring it up again.
Charles
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of G
I have given this some more thought. I now think I would not mention Hercules,
but not for the reasons you suspect. I would not mention it because when I was
interviewing programmers I was looking for *accomplishments*, not products they
had had a proximity to. So in an interview I might say
"I
Also tells you something about the language. Consider Hello World in Rexx,
Assembler and COBOL. You would see that
- Rexx is pretty darned straightforward.
- COBOL is verbose.
- Nothing is trivial in assembler. (Not too bad if WTO is a valid approach, but
if it requires opening a DCB, ...)
When
801 - 900 of 4699 matches
Mail list logo
