Re: Tracing RACF?
On Fri, 27 Sep 2019 00:13:25 -0500, Bruce Hewson wrote: >SMS will catalog in the MASTER CATALOG. It does override the >access rules. It really is important that ALIAS entries are defined >for any GROUP or USER created. If the USER has access to create >the dataset then SMS will catalog that dataset. I have plenty of >evidence to this. I knew I'd seen situations where it did not, so I did a quick search. https://www.ibm.com/support/knowledgecenter/SSLTBW_2.3.0/com.ibm.zos.v2r3.adru000/r2109.htm SMS-managed data sets: Access to SMS-managed data sets gives you access to the user catalog for the data sets. However, for a RACF-protected master catalog, you also need UPDATE-access authority to add or delete an SMS-managed data set entry. -- Tom Marchant -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Who writes these things?
> I think you new my intent I have no interest in arguing with the willfully ignorant. I'm no more a telepath than you are, and if you are going to respond to your hallucinations about what is in my head instead of responding to what I wrote then I will allow you to wallow in your misinformation. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM Mainframe Discussion List on behalf of Jon Perryman Sent: Friday, September 27, 2019 12:32 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Who writes these things? On Thursday, September 26, 2019, 01:15:42 PM PDT, Seymour J Metz wrote: >> You are referring to XML parse tree. > Not even close. What are you smoking? After looking at Perl's HTML5 DOM which came out this year, I stand corrected. Apparently, people are willing to put a lot of effort and time into an obscure seldom used browser. It's DOM object appears to be compatible with JS. Sorry but I've ignored these obscure browser implementations >> Even Nodejs parses uses the XML parser instead of the HTML parser. > There is no "the XML parser" or "the HTML parser"; I actually meant AN instead of THE but I think you new my intent and you just wanted to add to your list. >> JavaScript OO was specifically designed around DOM. > What language features do you believe have anything to do with DOM? If you've used javascript, you will have noticed it doesn't have "CLASS". The functionality exists but not in a way OO programmers would expect. There are others but they are much harder to explain. >> This has caused a huge debate about JavaScript being OO. > No, what has cause a huge debate is that > JS doesn't satisfy the standard definitions of OO language. Either you don't fully understand JS or OO. Which OO criteria do you think JS is missing? Remember, you may not like the JS implementation but it does exist. >> JavaScript is part of HTML. > Repeating the claim doesn't make I true. Ok Mr Trump. I gave you justification for my claim. Apparently I need to take your word on faith. >> JavaScript could not exist outside of HTML until 2009 (nodejs). > I can get you a good price on a calendar for 1995, which, last I heard, is > earlier than 2009. Am I supposed to take everything you say as gospel? Does that calendar include the date and product? Does that product still exist? >> I never said that CSS is OO. However it does have scripting capabilities > How do you code, e.g., a sort, in CSS? Are you really this clueless about programming languages. You should google the definition of program. Or maybe it's scripting language you should google. Where does it say the code must provide specific capabilities (e.g. sort)? >> Only Netscape supported javascript for web sites. >> The rest of the world >> only accepted JavaScript as part of HTML. > I can get you a good price on a 1996 calendar. Apparently repeating absolutely useless information will make us believe your point. >> You missed my point which is the definition of "macro" which you said has >> not changed since 1950. > Whoosh! Which part of "first hit" don't you understand. > THE FIRST HIT MATCHED THE DEFINITION FROM THE 1950S. You really should catch up with the times. What meaning do you think "first hit" has in regards to Googles search engine AI? It did not turn up in my results as far as I was willing to look. To make matters worse, you say things like search google #def #if. #def is clearly misspelled and googles AI often corrects this to real words instead of special phrases (e.g. #define). >> What main stream languages prior to C (1970) used the word "macro" in the >> same way as C? > PL/I. Pretty much every mainframe assembler. > OTOH, I've never seen anybody but you refer to COPY or INCLUDE s macro > facilities. > When did "macro" go from "special purpose command language" to being "copy"? I used copy and include as an analogy. Clearly you haven't used C macro's much otherwise you would have understood the analogy, said #define instead of #def and known that #if is not valid in a C macro. PL1 and assembler clearly have a proper macro language. You said prior to 1970 there were languages with a macro language similar to the C implementation. What is that language. Jon. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Who writes these things?
JS has things called classes and objects, but their behaviors are not what the OO community means by object oriented. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM Mainframe Discussion List on behalf of David Crayford Sent: Friday, September 27, 2019 1:53 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Who writes these things? On 2019-09-27 12:32 PM, Jon Perryman wrote: >>> JavaScript OO was specifically designed around DOM. >> What language features do you believe have anything to do with DOM? > If you've used javascript, you will have noticed it doesn't have "CLASS". The > functionality exists but not in a way OO programmers would expect. There are > others but they are much harder to explain. ECMAScript 6 introduced classes in 2015 https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Classes. It's syntactic sugar wrapped over the prototype but everybody has started to use classes. Of course, you can easily create objects in JavaScript simply by using closures. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: casting with XL C\C++ compiler
POSIX(ON) is perfectly fine for new code. From an administration perspective, the user running a POSIX(ON) program needs a RACF OMVS Segment. That's really not that big a deal. Obviously, if you run in USS, you already have that set up. If you have existing code (say COBOL) that is running with POSIX(OFF) and you add a component (say Java) that requires POSIX(ON) there are subtle differences in the way signals are delivered. So you should probably do extra testing when first adding Java to a COBOL program that has been running for years. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: casting with XL C\C++ compiler
On Fri, 27 Sep 2019 18:47:42 +0100, Charles Mills wrote: >... >FWIW, POSIX(ON) is not a problem. "My" code all runs POSIX(ON). > What motivation is there for POSIX(OFF)? Compatibility with lost source code? >-Original Message- >From: Allan Kielstra >Sent: Friday, September 27, 2019 4:41 PM > >We are listening! >https://www-01.ibm.com/servers/resourcelink/svc00100.nsf/pages/xlCC++V231ForZOsV23?OpenDocument > >This is a web deliverable that co-exists (does not overwrite) the existing xlC >compiler. I have personally used it to develop C++ code with initializer >lists, emplacements in collections, lambdas, variadic template classes and >other more modern features. > >One thing I should point out. For any non-trivial program, the resulting >executable will require POSIX(ON). Also, you should compile an entire >application with the new compiler or the old one. (The object models are not >the same.) -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: casting with XL C\C++ compiler
I imagine it is quite a few steps ahead of z/OS Unix System Services keeping up with Unix / Linux commands. On Fri, Sep 27, 2019 at 12:48 PM Charles Mills wrote: > > Alan, thanks. We've spoken at the TDM. I hope I was not too hard on you > guys.. I'm aware of the product of which you speak and why IBM supports it. > (Can I say its name and the reason here or is that NDA?) > > I've semi-retired from full-time hard-core C++ development and product > architecting, so my opinion no longer matters a whole lot. But if I were > setting product direction I would be wanting to know what is the strategic > IBM C++ compiler? The "real" IBM product or the open source download? I would > not want to commit to a new and quite different C++ compiler only to find out > that no, IBM was now heading off in some other directions. > > I think -- and as I say, what I think does not really matter -- I think that > IBM needs to stand up and say unambiguously "this is our strategic compiler, > it supports C and C++, it supports 31- and 64-bit, it is our intent that it > will lag only a year or three behind the standards, and it will be our > strategic compiler for the foreseeable future." Otherwise frankly I wonder if > a developer today would be making a mistake to make the commitment I made 9 > years ago to C++ on Z. IBM has a strategic COBOL compiler; why not a > strategic C/C++ compiler? > > FWIW, POSIX(ON) is not a problem. "My" code all runs POSIX(ON). > > Charles > > > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of Allan Kielstra > Sent: Friday, September 27, 2019 4:41 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: casting with XL C\C++ compiler > > Hi Charles > > We are listening! > https://www-01.ibm.com/servers/resourcelink/svc00100.nsf/pages/xlCC++V231ForZOsV23?OpenDocument > > This is a web deliverable that co-exists (does not overwrite) the existing > xlC compiler. I have personally used it to develop C++ code with initializer > lists, emplacements in collections, lambdas, variadic template classes and > other more modern features. > > One thing I should point out. For any non-trivial program, the resulting > executable will require POSIX(ON). Also, you should compile an entire > application with the new compiler or the old one. (The object models are not > the same.) > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- Mike A Schwab, Springfield IL USA Where do Forest Rangers go to get away from it all? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: casting with XL C\C++ compiler
Alan, thanks. We've spoken at the TDM. I hope I was not too hard on you guys.. I'm aware of the product of which you speak and why IBM supports it. (Can I say its name and the reason here or is that NDA?) I've semi-retired from full-time hard-core C++ development and product architecting, so my opinion no longer matters a whole lot. But if I were setting product direction I would be wanting to know what is the strategic IBM C++ compiler? The "real" IBM product or the open source download? I would not want to commit to a new and quite different C++ compiler only to find out that no, IBM was now heading off in some other directions. I think -- and as I say, what I think does not really matter -- I think that IBM needs to stand up and say unambiguously "this is our strategic compiler, it supports C and C++, it supports 31- and 64-bit, it is our intent that it will lag only a year or three behind the standards, and it will be our strategic compiler for the foreseeable future." Otherwise frankly I wonder if a developer today would be making a mistake to make the commitment I made 9 years ago to C++ on Z. IBM has a strategic COBOL compiler; why not a strategic C/C++ compiler? FWIW, POSIX(ON) is not a problem. "My" code all runs POSIX(ON). Charles -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Allan Kielstra Sent: Friday, September 27, 2019 4:41 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: casting with XL C\C++ compiler Hi Charles We are listening! https://www-01.ibm.com/servers/resourcelink/svc00100.nsf/pages/xlCC++V231ForZOsV23?OpenDocument This is a web deliverable that co-exists (does not overwrite) the existing xlC compiler. I have personally used it to develop C++ code with initializer lists, emplacements in collections, lambdas, variadic template classes and other more modern features. One thing I should point out. For any non-trivial program, the resulting executable will require POSIX(ON). Also, you should compile an entire application with the new compiler or the old one. (The object models are not the same.) -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Softcopy Librarian and V2R3
On Wed, 25 Sep 2019 20:13:41 +, Gibney, Dave wrote: >I will give them a try :) > >But, I will again take this opportunity to plea for the return of Bookmanager >format :) > It's a hard business case to make to IBM when some documents have outgrown the capabilities of Bookie and some COTS PDF authoring tools may cost less than upgrading Bookie, and PDF readers are available to end users for a plethora of platforms at very attractive prices. But the PDF library could be better organized, perhaps into multiple directories with a README in each. And the index.html better designed -- I've already suggested putting the clickable link closer to the document title. And some documents which were split for perhaps no better reason than ring binder capacity could be coalesced so the ToCs could be merged. >> -Original Message- >> From: Susan Shumway >> Sent: Wednesday, September 25, 2019 12:34 PM >> >> ... That's the PDF collection with the snazzy Adobe Indexed search >> capability that users liken to BookManager. -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: casting with XL C\C++ compiler
> Anyway read the link and give the compiler a try! I have, and it works - very well! If you haven't tried this compiler, you should. There are some limitations, but if you like the 64-bit LE programming model, this compiler is a win. -- Jerry -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: casting with XL C\C++ compiler
64-bit only? Does this amount to a "stabilization" of support for 31-bit XLC/C++ compilers? BTW: I'm happy to move to 64-bit after IBM supports 64-bit storage for most of their OS services, in the mean time its a PITA with no real advantage for us. On Fri, Sep 27, 2019 at 10:41 AM Allan Kielstra wrote: > Hi Charles > > We are listening! > https://www-01.ibm.com/servers/resourcelink/svc00100.nsf/pages/xlCC++V231ForZOsV23?OpenDocument > > This is a web deliverable that co-exists (does not overwrite) the existing > xlC compiler. I have personally used it to develop C++ code with > initializer lists, emplacements in collections, lambdas, variadic template > classes and other more modern features. > > One thing I should point out. For any non-trivial program, the resulting > executable will require POSIX(ON). Also, you should compile an entire > application with the new compiler or the old one. (The object models are > not the same.) > > Anyway read the link and give the compiler a try! > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: casting with XL C\C++ compiler
Hi Charles We are listening! https://www-01.ibm.com/servers/resourcelink/svc00100.nsf/pages/xlCC++V231ForZOsV23?OpenDocument This is a web deliverable that co-exists (does not overwrite) the existing xlC compiler. I have personally used it to develop C++ code with initializer lists, emplacements in collections, lambdas, variadic template classes and other more modern features. One thing I should point out. For any non-trivial program, the resulting executable will require POSIX(ON). Also, you should compile an entire application with the new compiler or the old one. (The object models are not the same.) Anyway read the link and give the compiler a try! -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Trying to put three reports together with SORT
Billy, even simpler: //SORT01 EXEC PGM=SORT //SYSOUTDD SYSOUT=* //SORTIN DD * FRUIT ORANGES FLORIDA SKU#1 FRUIT ORANGES ARIZONA SKU#1 FRUIT ORANGES ARIZONA SKU#2 FRUIT GRAPESWISCONSIN SKU#3 FRUIT GRAPESIDAHO SKU#4 FRUIT GRAPESOREGONSKU#4 VEGETABLE CORN IOWA SKU#8 VEGETABLE CORN KANSASSKU#8 VEGETABLE CARROTS VERMONT SKU#9 /* //SORTK1 DD DSN=&,DISP=(,PASS),SPACE=(TRK,(1,1)) //SORTK2 DD DSN=&,DISP=(,PASS),SPACE=(TRK,(1,1)) //SORTK3 DD DSN=&,DISP=(,PASS),SPACE=(TRK,(1,1)) //SORTK4 DD DSN=&,DISP=(,PASS),SPACE=(TRK,(1,1)) //SORTK12 DD SYSOUT=* //SORTK22 DD SYSOUT=* //SORTK32 DD SYSOUT=* //SORTK42 DD SYSOUT=* //SYSIN DD * INREC FIELDS=(1,80,SEQNUM,5,ZD) SORT FIELDS=COPY OUTFIL FNAMES=SORTK1,NODETAIL,REMOVECC, SECTIONS=(1,10,HEADER3=(1,10,11,10,21,10,31,10,X,81,5,X,C'1')) OUTFIL FNAMES=SORTK2,NODETAIL,REMOVECC, SECTIONS=(11,10,HEADER3=(10X,11,10,21,10,31,10,X,81,5,X,C'2')) OUTFIL FNAMES=SORTK3,NODETAIL,REMOVECC, SECTIONS=(21,10,HEADER3=(20X,21,10,31,10,X,81,5,X,C'3')) OUTFIL FNAMES=SORTK4,NODETAIL,REMOVECC, SECTIONS=(31,10,HEADER3=(30X,31,10,X,81,5,X,C'4')) OUTFIL FNAMES=SORTK12,NODETAIL,REMOVECC, SECTIONS=(1,10,HEADER3=(1,10,11,10,21,10,31,10,X,81,5,X,C'1')) OUTFIL FNAMES=SORTK22,NODETAIL,REMOVECC, SECTIONS=(11,10,HEADER3=(10X,11,10,21,10,31,10,X,81,5,X,C'2')) OUTFIL FNAMES=SORTK32,NODETAIL,REMOVECC, SECTIONS=(21,10,HEADER3=(20X,21,10,31,10,X,81,5,X,C'3')) OUTFIL FNAMES=SORTK42,NODETAIL,REMOVECC, SECTIONS=(31,10,HEADER3=(30X,31,10,X,81,5,X,C'4')) /* //SORT02 EXEC PGM=SORT //SYSOUTDD SYSOUT=* //SORTIN DD DSN=&,DISP=(OLD,DELETE) // DD DSN=&,DISP=(OLD,DELETE) // DD DSN=&,DISP=(OLD,DELETE) // DD DSN=&,DISP=(OLD,DELETE) /* //SORTOUT DD SYSOUT=* //SYSIN DD * SORT FIELDS=(42,5,ZD,A),EQUALS SUM FIELDS=NONE /* Output is: FRUIT ORANGES FLORIDA SKU#1 1 1 ARIZONA SKU#1 2 3 SKU#2 3 4 GRAPESWISCONSIN SKU#3 4 2 IDAHO SKU#4 5 3 OREGONSKU#4 6 3 VEGETABLE CORN IOWA SKU#8 7 1 KANSASSKU#8 8 3 CARROTS VERMONT SKU#9 9 2 Same as before, duplicate DD to "see what happens" and RECNUM maybe small and dummy fields after RECNUM. Best regards. Max Il giorno gio 26 set 2019 alle ore 15:15 Massimo Biancucci < mad4...@gmail.com> ha scritto: > Billy, > > it was a bit challenging and I'm not 100% sure it's so generalized . > you've real file, try and let us know. > > Here a stream who (in theory) does the needed, I've left different useless > output but understanding the flow: > > //*--- > //SORT01 EXEC PGM=SORT > //SYSOUTDD SYSOUT=* > //SORTIN DD * > FRUIT ORANGES FLORIDA SKU#1 > FRUIT ORANGES ARIZONA SKU#1 > FRUIT ORANGES ARIZONA SKU#2 > FRUIT GRAPESWISCONSIN SKU#3 > FRUIT GRAPESIDAHO SKU#4 > FRUIT GRAPESOREGONSKU#4 > VEGETABLE CORN IOWA SKU#8 > VEGETABLE CORN KANSASSKU#8 > VEGETABLE CARROTS VERMONT SKU#9 > /* > //SORTOUT DD DSN=&,DISP=(,PASS),SPACE=(TRK,(1,1)) > //SORTOU2 DD SYSOUT=* > //SYSIN DD * > INREC FIELDS=(1,80,SEQNUM,5,ZD) > SORT FIELDS=COPY > *SORT FIELDS=(1,10,A,11,10,A,21,10,A,31,10,A),FORMAT=BI > OUTFIL FNAMES=SORTOUT,NODETAIL,REMOVECC, > SECTIONS=(1,10,HEADER3=(1,10,11,10,21,10,31,10,X,81,5,X,C'1'), > 11,10,HEADER3=(10X,11,10,21,10,31,10,X,81,5,X,C'2'), > 21,10,HEADER3=(20X,21,10,31,10,X,81,5,X,C'3'), > 31,10,HEADER3=(30X,31,10,X,81,5,X,C'4')) > OUTFIL FNAMES=SORTOU2,NODETAIL,REMOVECC, > SECTIONS=(1,10,HEADER3=(1,10,11,10,21,10,31,10,X,81,5,X,C'1'), > 11,10,HEADER3=(10X,11,10,21,10,31,10,X,81,5,X,C'2'), > 21,10,HEADER3=(20X,21,10,31,10,X,81,5,X,C'3'), > 31,10,HEADER3=(30X,31,10,X,81,5,X,C'4')) > /* > //*--- > //SORT02 EXEC PGM=SORT > //SYSOUTDD SYSOUT=* > //SORTIN DD DSN=&,DISP=(OLD,DELETE) > //SORTK12 DD SYSOUT=* > //SORTK22 DD SYSOUT=* > //SORTK32 DD SYSOUT=* > //SORTK42 DD SYSOUT=* > //SORTK1 DD DSN=&,DISP=(,PASS),SPACE=(TRK,(1,1)) > //SORTK2 DD DSN=&,DISP=(,PASS),SPACE=(TRK,(1,1)) > //SORTK3 DD DSN=&,DISP=(,PASS),SPACE=(TRK,(1,1)) > //SORTK4 DD DSN=&,DISP=(,PASS),SPACE=(TRK,(1,1)) > //SYSIN DD * > SORT FIELDS=COPY > OUTFIL FNAMES=SORTK1,INCLUDE=(1,10,CH,NE,C' ') > OUTFIL FNAMES=SORTK2,INCLUDE=(1,10,CH,EQ,C' ',AND, > 11,10,CH,NE,C' ') > OUTFIL FNAMES=SORTK3,INCLUDE=(1,10,CH,EQ,C' ',AND, > 11,10,CH,EQ,C' ',AND, > 21,10,CH,NE,C' ')
Re: DB2LUW forum?
The IDUG DB2 - L list serv forum covers Db2 LUW as well as z/OS Db2. https://www.idug.org/p/fo/si/topic=19 db...@lists.idug.org Chris Bowen Macro 4 Limited A Division of UNICOM Global -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: casting with XL C\C++ compiler
I know I'm a little late to the party but I think I am extremely qualified
to answer this question: for the past nine years I have used MSVS to edit,
syntax check, and in some cases alpha test thousands and thousands of lines
of C++ for a very successful z/OS product. Let me say
- Yes, casts always take a type name, not a variable name.
- Structs in C (but not C++) require the word struct on all declarations:
struct foo {int x; int y;};
foo bar;
is valid in C++ but C requires
struct foo bar;
- If you re-phrase your question as "I wrote some valid C code and it will
not compile with XLC" then you are alleging a defect -- never mind MSVS one
way or the other. I think a defect is unlikely, but as you saw with the
S0C4, certainly possible. You also saw that IBM responds well to allegations
of defects.
- In my nine years I was extremely happy with the compatibility between the
two compilers. Yes, there are of course things that are specific to z/OS.
Yes, there are some recent extensions that were implemented differently. The
worst problem for me seemed to be that MSVC "forgave" certain syntax and
similar errors that XLC did not. Seeing as how my use of MSVC was as a
syntax checker for XLC that was no favor. One example: if I recall correctly
MSVC allows one to take the address of a C++ static const int; the standard
does not, nor does XLC:
static const int foo = 1;
int *bar = // not valid C++ but accepted by MSVS
(For those of you that are not C++ geeks, a static const int is kind of like
an EQU in assembler: it has a value but occupies no storage, so taking its
address is irrational.)
Also the #pragma pack syntax is different on the two platforms: annoying but
once you figure it out it is easy to write a macro that bridges the gap.
Frankly one of the most annoying things was how far behind the standards XLC
lags. I used MSVS 2010. There was no point in upgrading to a more recent
version because MSVS 2010 is already more advanced with the standards than
XLC V2R3. That is kind of sad. IBM, are you listening?
Charles
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf Of Joseph Reichman
Sent: Thursday, September 26, 2019 4:40 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: casting with XL C\C++ compiler
Hi
Seems like a lot the casting I was able to do with the Visual Studio C\C++
compiler I am not able to do with XL C\C++ compiler
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
