Re: C++ compiler message CCN5802 The character literal %1$s contains more than one character.

2010-12-30 Thread Robert A. Rosenberg
At 17:34 -0500 on 12/30/2010, Farley, Peter x23353 wrote about Re: C++ compiler message CCN5802 The character literal %1$s: > I'm not positive, but to be strictly accurate, isn't a quotation mark > symbol this:", while this:' is an apostrophe? Well, yes, except here I used the 40-years-ago p

Re: Could I issue '-SETXCF COUPLE,ACOUPLE=PLEXBDZ3.OMVS' in a monoplex configuration

2010-12-30 Thread ibmnew
Dear Bill You are right. I have other two questions: 1.Could you tell me why the records associated with the SYSPLEX couple data set weren't in the incoming CDS ? Because of monplex configuration? 2. How to report on the contents of the BPXMCDS data? Thanks a lot! Best Regards, Jason

Re: C++ compiler message CCN5802 The character literal %1$s contains more than one character.

2010-12-30 Thread Bill Godfrey
On Thu, 30 Dec 2010 21:37:50 -0600, Bill Godfrey wrote: Using SUPP(CCN5802) in the PARM options might also work. Bill >Try this: > >#pragma report (disable, "CCN5802") > >Note the added quotes around the message number. The Language Reference >says: "You must use quotation marks with message num

Re: C++ compiler message CCN5802 The character literal %1$s contains more than one character.

2010-12-30 Thread Bill Godfrey
Try this: #pragma report (disable, "CCN5802") Note the added quotes around the message number. The Language Reference says: "You must use quotation marks with message number as in the preceding example". Hope that helps. Bill On Thu, 30 Dec 2010 13:09:28 -0800, Charles Mills wrote: >I poste

Re: C++ compiler message CCN5802 The character literal %1$s contains more than one character.

2010-12-30 Thread Charles Mills
I don't WANT a string literal. I WANT a character literal. I know darned well that they are two different things. One more time -- it is compiling correctly; it's the warning that is the problem. To be perfectly clear, in coding 'ABCD' I want the compiler to create an integer equal to 0xc1c2c3c4 (

Re: C++ compiler message CCN5802 The character literal %1$s contains more than one character.

2010-12-30 Thread Bill Godfrey
Change the single quotation marks to double quotation marks (these are terms used in the Language Reference). That should fix the problem. What you have is most likely a string literal, not a multicharacter literal. They are two different things. String literals are discussed in the very next se

Re: BCPii code

2010-12-30 Thread Jack Schudel
When I tried to follow the directions in the sample code for running a script to compile, assemble, and linkedit the program, I am getting stumped by the following line: /usr/bin/linkedit -d -V -wRENT,REUS,MAP,AMODE=31,AC=1 -l //XXX.XXX.XXX -i //sys1.csslib -o hwixmcs1 ./hwixmcs

Re: C++ compiler message CCN5802 The character literal %1$s contains more than one character.

2010-12-30 Thread Charles Mills
> Sounds to me like you may have to raise an issue with IBM. I was hoping to resolve the problem in a timeframe of hours or days, not weeks or months. Charles -Original Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of Farley, Peter x23353 Sent: Thur

Re: C++ compiler message CCN5802 The character literal %1$s contains more than one character.

2010-12-30 Thread Charles Mills
Why are listserves so good at answering every question but the one that was asked? >From the LR: A character literal contains a sequence of characters or escape sequences enclosed in single quotation mark symbols, for example 'c'. Anyone have any ideas on why my #pragma is not working to suppress

Re: C++ compiler message CCN5802 The character literal %1$s contains more than one character.

2010-12-30 Thread Farley, Peter x23353
That's a new one on me, but then I have seldom actually read the LR except when I needed to look up some syntax or other. Sounds to me like you may have to raise an issue with IBM. Seems like your problem description and the LR reference point in two different directions, so either the LR desc

OPENSSL calls from Mainframe C

2010-12-30 Thread Bernd Oppolzer
Hello all, I need to compile a ANSI C program on the mainframe, which does calls to the OPENSSL library. The OPENSSL library is located in the z/OS Unix filesystem, and the header files for the compile, too. I've not much experience with z/OS Unix. Our compile jobs deal with classical MVS datase

Re: C++ compiler message CCN5802 The character literal %1$s contains more than one character.

2010-12-30 Thread Farley, Peter x23353
> -Original Message- > From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On > Behalf Of Scott Rowe > Sent: Thursday, December 30, 2010 5:16 PM > To: IBM-MAIN@bama.ua.edu > Subject: Re: C++ compiler message CCN5802 The character literal %1$s > contains more than one character

Re: C++ compiler message CCN5802 The character literal %1$s contains more than one character.

2010-12-30 Thread Scott Rowe
I'm not positive, but to be strictly accurate, isn't a quotation mark symbol this:", while this:' is an apostrophe? On Thu, Dec 30, 2010 at 4:49 PM, Charles Mills wrote: > Single quotes. From the LR: > > A character literal contains a sequence of characters or escape sequences > enclosed in sing

Re: Antwort: Re: tar limitation preventing SAS install

2010-12-30 Thread Ted MacNEIL
>Yes, I only meant that it was a mix of PL/I and Fortran. Yes, I know you did. But, C was required to go multi-platform. And, arrogance still reigns! (Has since at least 1981 -- they still don't get it!) - Ted MacNEIL eamacn...@yahoo.ca --

Re: C++ compiler message CCN5802 The character literal %1$s contains more than one character.

2010-12-30 Thread Charles Mills
Single quotes. From the LR: A character literal contains a sequence of characters or escape sequences enclosed in single quotation mark symbols ... An ordinary character literal that contains more than one character or escape sequence ... is a multicharacter literal. ... C++ ... The type of a mult

Re: Antwort: Re: tar limitation preventing SAS install

2010-12-30 Thread Scott Rowe
Yes, I only meant that it was a mix of PL/I and Fortran. On Thu, Dec 30, 2010 at 4:41 PM, Ted MacNEIL wrote: > >Actually, SAS had a bunch of Fortran in it way back when, you could tell > from the DDNAMEs. > > Yes. I'd forgotten. > Log: FT11F001 > List: FT12F001 > > But, I'd discussed this with m

Re: Antwort: Re: tar limitation preventing SAS install

2010-12-30 Thread Ted MacNEIL
>Actually, SAS had a bunch of Fortran in it way back when, you could tell from >the DDNAMEs. Yes. I'd forgotten. Log: FT11F001 List: FT12F001 But, I'd discussed this with many SAS'rs in the early 1980's. And, PL/1 was most of the code. Had to have PLINK (and the other -- PLBASE?) in LPA, LNK, o

Re: Antwort: Re: tar limitation preventing SAS install

2010-12-30 Thread Scott Rowe
Actually, SAS had a bunch of Fortran in it way back when, you could tell from the DDNAMEs. But yes, I would be more inclined to go to WPS now, even if cost wasn't a factor. Their install was never very good, and now it sounds like a major nightmare. On Thu, Dec 30, 2010 at 3:33 PM, Ted MacNEIL

Re: C++ compiler message CCN5802 The character literal %1$s contains more than one character.

2010-12-30 Thread Farley, Peter x23353
Are you using single quotes or double quotes? AFAIK, only double-quoted literals ("strings" in C language terms) are allowed to be multi-character, but single-quoted literals are limited by language definition to one "character", which might be a multi-byte "character", depending on the locale'

C++ compiler message CCN5802 The character literal %1$s contains more than one character.

2010-12-30 Thread Charles Mills
I posted this to MVS-OE but they are down today so thought I would try here also. I'm getting the subject message on a character literal in a C++ compile. The assertion that the literal contains more than one character is true but it seems to me that the message explanation is wrong: Explanation:

Re: Antwort: Re: tar limitation preventing SAS install

2010-12-30 Thread Ted MacNEIL
>I could be wrong, but SAS Institute appears to be another "arrogant" vendor. >They have an excellent product with a large share of their market. >Therefore "we are the best and you need to conform to our ideas". >Probably started when their codebase went to C. I believe that your last comment is

Re: Antwort: Re: tar limitation preventing SAS install

2010-12-30 Thread McKown, John
> -Original Message- > From: IBM Mainframe Discussion List > [mailto:ibm-m...@bama.ua.edu] On Behalf Of Scott Rowe > Sent: Thursday, December 30, 2010 2:03 PM > To: IBM-MAIN@bama.ua.edu > Subject: Re: Antwort: Re: tar limitation preventing SAS install > > What I want to know is who at SAS

Re: Antwort: Re: tar limitation preventing SAS install

2010-12-30 Thread Scott Rowe
What I want to know is who at SAS thought it this was an installation process that was anywhere near acceptable? On Thu, Dec 30, 2010 at 2:37 PM, Paul Gilmartin wrote: > On Thu, 30 Dec 2010 13:31:49 -0500, Shmuel Metz (Seymour J.) wrote: > > >In <20101228145843.14b468f...@panix3.panix.com>, on 12

Re: tar limitation preventing SAS install

2010-12-30 Thread McKown, John
> -Original Message- > From: IBM Mainframe Discussion List > [mailto:ibm-m...@bama.ua.edu] On Behalf Of Mike Schwab > Sent: Thursday, December 30, 2010 1:36 PM > To: IBM-MAIN@bama.ua.edu > Subject: Re: tar limitation preventing SAS install > > On Thu, Dec 30, 2010 at 8:52 AM, Tom Marchant

Re: Antwort: Re: tar limitation preventing SAS install

2010-12-30 Thread Paul Gilmartin
On Thu, 30 Dec 2010 13:31:49 -0500, Shmuel Metz (Seymour J.) wrote: >In <20101228145843.14b468f...@panix3.panix.com>, on 12/28/2010 > at 09:58 AM, Don Poitras said: > >>While I am fully comfortable using the newer unix facilities on z/OS >>(including X11), > >X11 itself is pretty long in the too

Re: tar limitation preventing SAS install

2010-12-30 Thread Mike Schwab
On Thu, Dec 30, 2010 at 8:52 AM, Tom Marchant wrote: > On Thu, 30 Dec 2010 04:51:00 -0600, Mike Schwab wrote: >> >>The mainframe itself never has had a built in display and required a >>terminal while a person is entering data or reviewing status or >>output. > > Of course it has.  The mainframe h

Re: tar limitation preventing SAS install

2010-12-30 Thread Ed Finnell
In a message dated 12/29/2010 10:56:45 P.M. Central Standard Time, mike.a.sch...@gmail.com writes: Maybe we should refurbish IBM 3278s instead of PC with 3270E Emulators? >> IBM pretty much dropped the nuggets when they tried to prop up the cash cows. We had to replace a 20Mb hard drive i

Re: Authorized Rexx Assembler Function

2010-12-30 Thread Shmuel Metz (Seymour J.)
In <985915eee6984740ae93f8495c624c6c21cf025...@jscpcwexmaa1.bsg.ad.adp.com>, on 12/28/2010 at 05:27 PM, "Farley, Peter x23353" said: >If you have the REXX compiler and you use the compiler to create a >REXX load module and you authorize that load module and store it in >an APF-authorized libra

Re: Authorized Rexx Assembler Function

2010-12-30 Thread Shmuel Metz (Seymour J.)
In , on 12/29/2010 at 06:46 AM, Walt Farrell said: >(1) Normal Rexx environments (as extablished by TSO or by IRXEXEC in >batch) do not themselves run authorized. I'm confused. The question did not concern the EXEC command, it concerned a user written command that was AC(1), in an authorized

Re: Antwort: Re: tar limitation preventing SAS install

2010-12-30 Thread Shmuel Metz (Seymour J.)
In <20101228145843.14b468f...@panix3.panix.com>, on 12/28/2010 at 09:58 AM, Don Poitras said: >While I am fully comfortable using the newer unix facilities on z/OS >(including X11), X11 itself is pretty long in the tooth. The problem is not that it's new, the problem is that many companies ha

Re: tar limitation preventing SAS install

2010-12-30 Thread Arthur Gutowski
On Wed, 29 Dec 2010 14:28:16 -0800, Schwarz, Barry A wrote: >Actually, you have to use their installation application to produce a 9GB tree which you then must transfer to OMVS. >What PC utility did you use to ftp the entire tree and preserve its structure and long path names? We don't use N

Re: IBM MLC discount policies

2010-12-30 Thread Itschak Mugzach
Tx Bob, I will ask at IBM, but I want to be prepared. ITschak On Thu, Dec 30, 2010 at 5:47 PM, Richards, Robert B. < robert.richa...@opm.gov> wrote: > Itschak, > > I am not a contract lawyer! :-) > > Without elaboration and strictly my opinion: > > "NO" to all your questions. IBM publishes, for

Re: tar limitation preventing SAS install

2010-12-30 Thread J R
> >The mainframe itself never has had a built in display ... > > Of course it has. The mainframe has always come with a console. > Some have been display consoles and others have been printer consoles. Not to mention "das blinkenlights". > Date: Thu, 30 Dec 2010 08:52:48 -0600 > From: m4

Re: IBM MLC discount policies

2010-12-30 Thread Richards, Robert B.
Itschak, I am not a contract lawyer! :-) Without elaboration and strictly my opinion: "NO" to all your questions. IBM publishes, for all the world to see (on the web, on contracts, etc.) its pricing metrics and Terms and Conditions (T&C) for those metrics that usually apply to all. As a rule,

Re: tar limitation preventing SAS install

2010-12-30 Thread McKown, John
Ah, I "fondly" remember the 370/145's builtin console. But the one on the 168 was really neat - it was actually a vector-based 3270 as opposed to raster based. Strange looking font. John McKown Systems Engineer IV IT Administrative Services Group HealthMarkets(r) 9151 Boulevard 26

Re: tar limitation preventing SAS install

2010-12-30 Thread Tom Marchant
On Wed, 29 Dec 2010 23:54:08 -0500, Don Poitras wrote: >In article Gil wrote: >> On Wed, 29 Dec 2010 22:52:26 -0500, Don Poitras wrote: > >> > >> >On the higher-level versions of Windows 7 (above Home Premium) you can >> >also download SUA (Subsystem for UNIX-based Applications.) This is >> >the

Re: scope=common data space

2010-12-30 Thread Peter Relson
I have suggested to the owners of the IBMRSM,RSM_MAXCADS health check that they display the CADS names and owners when VERBOSE=YES is asked for (regardless of whether the check produces an exception). If nothing else, that is part of the information appropriate for diagnosing the problem (if th

Re: tar limitation preventing SAS install

2010-12-30 Thread Tom Marchant
On Thu, 30 Dec 2010 04:51:00 -0600, Mike Schwab wrote: > >The mainframe itself never has had a built in display and required a >terminal while a person is entering data or reviewing status or >output. Of course it has. The mainframe has always come with a console. Some have been display consoles

Re: tar limitation preventing SAS install

2010-12-30 Thread Steve Dover
We installed SAS 9.1.3 (recommended version by SAS tech support) this summer. We tried the install via the download method and were not successful, but only while waiting on SAS to deliver Base SAS on a 3490 cartridge. So yes, there is tape delivery for z/OS. On Thu, 30 Dec 2010 20:22:18 +110

Re: IBM MLC discount policies

2010-12-30 Thread Itschak Mugzach
Thanks to those who replied. My question is more about the limitation IBM took or put on IBM on pricing. For example. is this possible that one customer will pay for a product (not a OTC product) and the other will not? is this legal from IBM procedures point view? What I am trying to understand i

Re: IBM MLC discount policies

2010-12-30 Thread Richards, Robert B.
Excellent list, Timothy! One other "minor" point that may not be valid anymore (it has been 13 years since I was last a s/390 Client Rep): If you happen to be negotiating with IBM in late 4th quarter, you may be able to get them to be a little more accommodating if they are trying to hit certai

Re: IBM MLC discount policies

2010-12-30 Thread Timothy Sipples
I'll run through the list, in no particular order: 1. An IBM Enterprise License Agreement (ELA), and other IBM agreements which incorporate ELA terms and conditions, is/are a way to get some additional value from your MLC. In very simple terms, if you can reasonably forecast your MLC and make a fi

Re: tar limitation preventing SAS install

2010-12-30 Thread Mike Schwab
On Wed, Dec 29, 2010 at 11:28 PM, Paul Gilmartin wrote: > On Wed, 29 Dec 2010 22:43:18 -0600, Mike Schwab wrote: > >>On Wed, Dec 29, 2010 at 10:17 PM, Paul Gilmartin wrote: >> >>> In the longer view, I'd be dismayed that Windows, a fortiori >>> a particular level of a particular version of Windows

Re: tar limitation preventing SAS install

2010-12-30 Thread Paul Gillis
It is a physical 3590 cart not a 3592 cart which is incompatible with our old 3590 drives as is the 3590 cart on 3592 drives (tried it). The cart is still in our ATL. If you only have 3592 drives, ask SAS for delivery on 3592 media, hopefully they can write 3592 media. I did go through the pain of