Re: Problem Compiling for a V3R2M0 Build in CRTCMOD command.

["Jeffrey Silberberg" <jsilberberg@xxxxxxxxxxxxxx>]

Barbara,

            Thanks, I figured the problem out, in that when the system was
upgraded to V4R4 the Visual Age C++ licenses had installed but not the CX2
for ILE C. This meant that when I went looking for the CRTCMOD command I
only found the previous version and as you pointed out, it was not designed
to work in the
environment.

            Once I installed the missing LPP everything worked fine..

Jeffrey M. Silberberg
Independent Consultant
CompuDesigns, Inc.
Atlanta, GA.

AS SOON AS I KNOW THE ANSWERS
THEY CHANGE THE QUESTIONS

----- Original Message -----
From: <bmorris@ca.ibm.com>
To: <midrange-l@midrange.com>
Sent: Tuesday, September 25, 2001 12:24 PM
Subject: Re: Problem Compiling for a V3R2M0 Build in CRTCMOD command.


>
> >From: "Jeffrey Silberberg" <jsilberberg@mindspring.com>
> >Date: Tue, 25 Sep 2001 11:32:55 -0400
> >
> >        I have a CL build program to recreate a bunch of V3R2M0 modules
> >written in C.  The CLP uses the command  QSYSV3R2M0/CRTCMOD MODULE
> (........
> >TGTRLS(*CURRENT) SYSINC(*YES).
> >
> >        When I compile the CLP on V4R4M0 system I get the following error
> >message;
> >* CPF0885 30  System command CRTCMOD in library QSYSV3R2M0 is for
> >TGTRLS(V3R2M0).
>
> The QSYSVxRxMx commands aren't meant to be actually used.  They're
> meant for CL programs compiled with TGTRLS(non-*CURRENT) to be able
> to use an old version of the command for the specified release;
> for instance, to prevent you from creating a CL program that uses
> command parameters that aren't available on the specified target release.
>
> To get your programs to build correctly, just use CRTCMOD TGTRLS(V3R2M0).
>
> Barbara Morris
>
> _______________________________________________
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
> To post a message email: MIDRANGE-L@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
> or email: MIDRANGE-L-request@midrange.com
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>