RE: Problems Editing an Include mbr.. (VisualAge C..)

Jeff,

For you problem, you could copy the QSYSINC header to your own source 
file and then #include it instead of IBM's.

Attitude::SetGripeMode(true);           

I remember that the install of VAC++ was pretty nasty.  Anytime the 
install instructions come in a Book instead of a page or 2, there is 
something wrong.

Heck, it was a major challenge to even Order it!  And of course, after 
you finally work thru that, you find you must have a copy of VisualAge 
C++ for Windows!  Never mind the cost, the only way you can get that 
is via IBM Direct.

And after all that, you find even though all other V3R7 languages will 
target V3R1, VA C++ will not.

Several dollars poorer and shaking my head.....

Attitude::SetGripeMode(false);

Bob

-----Original Message-----
From:   Jeffrey Silberberg [SMTP:jsilberberg@mindspring.com]
Sent:   Monday, March 08, 1999 9:48 AM
To:     MIDRANGE-L@midrange.com
Subject:        Re: Problems Editing an Include mbr.. (VisualAge C..)

Bob,

Well, the more I get into this the more I find. When coding on any 
other
platform, the developer always has the opportunity to shoot oneself in 
the
foot by changing any of the system include files as "necessary". 
  With the
AS/400 V4R3 the QSYSINC/H *PF is created with the ALWxxx bits set to 
NO, so
I can not fix the issue.  Which by the way is that  "   typedef 
volatile
struct _LU_Work_Area_T {.........} _LU_Work_Area_T ; "
is not valid.

I am going to look at working around this today.

With regards V3R6, yes the C++ Users Guide on page 42 tells me "The 
compiler
can target the following AS/400 run-time environments:
        *  OS/400 V3R7
        * OS/400  V3R6
        * OS/400  V3R2   "

One interesting note since the compiler is still at "V3R7" there are 
no
specific references to building for V4Rx anything in the manuals, and 
at
this point I have not tried to build for anything but my current 
release
V4R3 and a V3R2 target system.

 Lastly, the install for this product is not developer friendly, never 
mind
user.  Be vary careful and feel free to contact me off list for some 
of my
more colorful how not to install information.

    JMS....

-----Original Message-----
From: Bob Crothers <bob@cstoneindy.com>
To: MIDRANGE-L@midrange.com <MIDRANGE-L@midrange.com>
Date: Sunday, March 07, 1999 9:38 AM
Subject: Re: Problems Editing an Include mbr..


>Jeff,
>
>Not sure about VisualAge, but for ILE/C (no ++), the system includes
>are all in source file H in library QSYSINC on your AS/400.  Many of
>these includes are stubs that just include another source member so 
you
>might have to follow the chain.
>
>Re VA C++, I had installed it but had to drop it as soon as I
>discovered it would not target V3R1 (a requirement of our product).
>This was a disappointment as I would MUCH rather work in C++ than 
plain
>C. But IBM wasn't going to change for one small ISV.
>
>My hope is that with Y2K and V3R1 not being Y2K compliant, we will be
>able to raise the bar to V3R2 & V3R6.  BTW, will VA C++ target V3R6?
>
>Bob
>
>-----Original Message-----
>From: Jeffrey Silberberg <jsilberberg@mindspring.com>
>To: MIDRANGE-L@midrange.com <MIDRANGE-L@midrange.com>
>Date: Friday, March 05, 1999 10:03 PM
>Subject: Problems Editing an Include mbr..
>
>
>>HELP,
>>
>>        I am trying to build some code with the VisualAge C++ for
>AS/400 LPP
>>targeted to V3R2.  To say that I have had a few minor issues would 
be
>very
>>polite, but I have it working about 80% on my NT 4.0 With SP 3.
>>
>>        The problem is that one of the AS/400 system include files
>>I:\QIBM\INCLUDE\milib.h has a bad typedef in it. Now I know what is
>broken
>>but I am not sure how to fix it as I can not edit it with the EDITOR
>from
>>VAge or the DOS EDIT.exe or any other method.  Now I am using 
QSECOFR,
>(It's
>>my 170 V4R3) even for the CA connect user and I just get errors back
>when I
>>try and save the updated .h file.
>>
>>        So, anyone know what step I am missing to edit these files 
??
>>Anyone else working with this product (5716-CX5) and want to compare
>the
>>gory details.
>>
>>        Thanks,
>>        JMS....
>>
>>+---
>>| This is the Midrange System Mailing List!
>>| To submit a new message, send your mail to 
MIDRANGE-L@midrange.com.
>>| To subscribe to this list send email to 
MIDRANGE-L-SUB@midrange.com.
>>| To unsubscribe from this list send email to
>MIDRANGE-L-UNSUB@midrange.com.
>>| Questions should be directed to the list owner/operator:
>david@midrange.com
>>+---
>>
>
>+---
>| This is the Midrange System Mailing List!
>| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
>| To subscribe to this list send email to 
MIDRANGE-L-SUB@midrange.com.
>| To unsubscribe from this list send email to
MIDRANGE-L-UNSUB@midrange.com.
>| Questions should be directed to the list owner/operator:
david@midrange.com
>+---

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to 
MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: 
david@midrange.com
+---

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---