John,
the problem is that if you initialize a PL/1 structure by simply writing
STRUCT = '';
and the structure contains pointers, these pointers are initialized
to NULL, not SYSNULL. Admitted: I did not check so far if there is
a compiler option to change this behaviour, but even if there was
I can only speak for C, we don't have C++ at our site.
So I would ask you to try the #include stdio.h first and leave out
the #include iostream for the beginning, because that is a C++ header
which you will not be able to use in a C program.
We allocate for USERLIB exactly the same DD chain as
Bernd,
Now that I have a better understanding of the full dimensions your
problem I will give it some further thought, and it may be that I will
be abe to make further suggestions.
In passing let me note that the usages
whatever = null() ;
whatever = sysnull() ;
are necessary and appropriate
W dniu 2014-03-28 18:30, ITURIEL DO NASCIMENTO NETO pisze:
Charles,
Thanks for your feedback.
I was thinking in some other table, containing messages prefix, not products.
Something like ICH (RACF), HASP (JES2), SBL (BETA88) and so on.
For IBM proudcts and components most (not all) prefixes are
John,
maybe we should move this conversation to the PL/1 list;
I don't know if the people there follow the IBM main list, too.
I'll start by cross-posting this post there.
For those who didn't follow the previous post: I tried to translate
NULL() pointers to SYSNULL() pointers in a C routine;
Radosla:
It is probably worth a RCF, no?
Ed
On Mar 29, 2014, at 7:28 AM, R.S. wrote:
W dniu 2014-03-28 18:30, ITURIEL DO NASCIMENTO NETO pisze:
Charles,
Thanks for your feedback.
I was thinking in some other table, containing messages prefix,
not products.
Something like ICH (RACF),
Yep, my mistake. But TSOEXEC is needed if LISTA is issued from Clist or
REXX ... which is what I was thinking of :-(
Ted MacNEIL wrote:
You don't need the TSOEXEC for LISTA.
-
-teD
-
Original Message
From: CM Poncelet
Sent: Friday, March 28, 2014 18:34
To: IBM-MAIN@LISTSERV.UA.EDU
Reply
I don't think so.
I've never used it within CLIST or REXX.
-
-teD
-
Original Message
From: CM Poncelet
Sent: Saturday, March 29, 2014 13:15
To: IBM-MAIN@LISTSERV.UA.EDU
Reply To: IBM Mainframe Discussion List
Subject: Re: Clist character string compare
Yep, my mistake. But TSOEXEC is needed
In 5335f8d2.4040...@bcs.org.uk, on 03/28/2014
at 10:33 PM, CM Poncelet ponce...@bcs.org.uk said:
You can store/execute a REXX exec in your Clist library if you code
/* REXX */ as the first line.
That doesn't address his TSOLIB issue, nor the other CLIST-REXX
issues.
--
Shmuel
In 5335f952.3010...@woodsway.com, on 03/28/2014
at 06:36 PM, Bob Woodside ibm...@woodsway.com said:
Such as?
EXEC create entries on the stack, then goes away. The TMP uses I/O
service routines, e.g., GETLINE, to read lines from the stack, and the
service routines interpret the clist code in
In 53369a68.4060...@t-online.de, on 03/29/2014
at 11:03 AM, Bernd Oppolzer bernd.oppol...@t-online.de said:
PL/1, BTW, does other strange things using descriptors,
FSVO strange. PL/I supports call by reference, and the
locator/descriptor is simply the mechanism used by current
Am 30.03.2014 00:41, schrieb Shmuel Metz (Seymour J.):
In 53369a68.4060...@t-online.de, on 03/29/2014
at 11:03 AM, Bernd Oppolzer bernd.oppol...@t-online.de said:
PL/1, BTW, does other strange things using descriptors,
FSVO strange. PL/I supports call by reference, and the
A very good sort article with comments.
http://arstechnica.com/information-technology/2014/03/information-overload-i-know-too-much-to-program-quickly-what-can-i-do/
Basically the author is saying that he has a problem. He knows so much now,
especially trying to anticipate problems, that his
13 matches
Mail list logo
