Re: WDSC vs SEU

["Wilt, Charles" <WiltC@xxxxxxxxxx>]

Bill,

Assuming the defaults haven't been changed, if you convert RPG III to RPG IV using CVTRPGSRC, convert
CLP to CLLE and continue to use CRTBNDxxx (PDM option 14-Compile).

Then both the CLLE and the RPGLE programs will be created with DFTACTGRP(*YES) and will continue to
work like OPM programs.

These conversions are indeed trivial.

Things become not trivial, once you specify DFTACTGRP(*NO) in any of the programs in the job stream.
Before doing so, you need to understand activation groups.

While OVRSCOPE(*JOB) may fix problems, it is IMHO not usually the "correct" answer.  OVRSCOPE(*JOB) is
sometimes needed, but more often it is used as a brute force fix by those who don't understand
activation groups.

Charles

> -----Original Message-----
> From: wdsci-l-bounces@xxxxxxxxxxxx 
> [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Bill Reed
> Sent: Thursday, October 25, 2007 8:55 AM
> To: Websphere Development Studio Client for iSeries
> Subject: Re: [WDSCI-L] WDSC vs SEU
>
> Be careful.  Changing from CL to CLLE may not be trivial. Be 
> sure that the CL's and the programs they call are running in 
> the proper activation group.  QILE is the default for CLLE's, 
> but your RPG's, etc, could be in others depending on your 
> program specs and compile options.  
>
> The impact of running in the wrong group is most noticeable 
> with overrides.  The safest way to ensure that your overrides 
> are in effect is to specify both OVRSCOPE(*JOB) and 
> OPNSCOPE(*JOB) in any OVR* commands.
>
> The first time we tried changing from CL to CLLE, a long time 
> ago, we did it wrong, and had a situation where we overrode 
> to a specific member in a multi-member file, then ran a 
> program which deleted a bunch of records.  Wrong override, 
> wrong member.  Ouch.
>
> Bill Reed
> Rock of Ages Corp.
>
>
>
> -----Original Message-----
> From: wdsci-l-bounces@xxxxxxxxxxxx 
> [mailto:wdsci-l-bounces@xxxxxxxxxxxx]
> On Behalf Of Vernon Hamberg
> Sent: Thursday, October 25, 2007 8:28 AM
> To: Websphere Development Studio Client for iSeries
> Subject: Re: [WDSCI-L] WDSC vs SEU
>
> I add my vote to changing CLP to CLLE - there is a 
> performance gain, and the only commands to worry about, 
> mostly, are RCLRSC, which behaves differently, and TFRCTL, 
> which can't be used in ILE CL. This link has an excerpt from 
> the ILE App Dev manual that explains more -
>
> http://www.systeminetwork.com/isnetforums/showthread.php?t=20479
>
> Also, see the help text for RCLRSC for some clues as to its 
> new behavior.
>
> HTH
> Vern
>
> At 06:35 AM 10/25/2007, you wrote:
>
> > > 5. Debug is magic, but I cannot use it for old OPM programs.
> > >    So I have converted the RPG source to RPGLE and this was not a 
> > > trivial
> > >    exercise. The CLs I have not converted to CLLE as I do 
> not have a 
> > > clear
> > >    concept of the implications of doing so.
> >
> > I debug OPM RPG programs all the time in WDSC.
> >
> > You can't use Service Entry Points, but you can still debug them.
> >
> > Converting from CL to CLLE is trivial.  If you've already converted 
> > from RPG to RPGLE, then I'd go ahead and convert from CL to 
> CLLE also.
> > Charles
>
> --
> This is the Websphere Development Studio Client for iSeries  
> (WDSCI-L) mailing list To post a message email: 
> WDSCI-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change 
> list options,
> visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
> or email: WDSCI-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives 
> at http://archive.midrange.com/wdsci-l.
>
> --
> This is the Websphere Development Studio Client for iSeries  
> (WDSCI-L) mailing list To post a message email: 
> WDSCI-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change 
> list options,
> visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
> or email: WDSCI-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives 
> at http://archive.midrange.com/wdsci-l.

This e-mail transmission contains information that is intended to be confidential and privileged.  If you receive this e-mail and you are not a named addressee you are hereby notified that you are not authorized to read, print, retain, copy or disseminate this communication without the consent of the sender and that doing so is prohibited and may be unlawful.  Please reply to the message immediately by informing the sender that the message was misdirected.  After replying, please delete and otherwise erase it and any attachments from your computer system.  Your assistance in correcting this error is appreciated.