Re: how to handle handlers *update

["Crispin Bates" <cbates@xxxxxxxxxxx>]

Rory,

RPG OA uses the existing code, and just passes info to the handler as 
parameters. No changes required to the rest of the source, so I can't see 
why any additional conditioning would be required...

----- Original Message ----- 
From: "Rory Hewitt" <rory.hewitt@xxxxxxxxx>
To: "RPG programming on the IBM i / System i" <rpg400-l@xxxxxxxxxxxx>
Sent: Tuesday, March 15, 2011 11:00 AM
Subject: Re: how to handle handlers *update


Nice solution, Tom. Do you also need to use this method anywhere else (when
specifying record format names for Write, Read etc.)?
On Mar 15, 2011 5:19 AM, "Tom Deskevich" <thomas.l.deskevich@xxxxxxxxxxxxx>
wrote:
> I came up with this getting ready for work. It is true that the bathroom
is the thinking room.
> This example that I created does NOT raise a syntax error since you use a
/COPY with the HANDLER.
> FCEN106D CF E WORKSTN
> /copy cenhnd
>
> (will not raise the syntax error, because SEU does not know I am using a
handler)
> Source member CENHND
>
> /if defined(USE_HANDLER)
> F Handler('ASNAWINGS')
> /endif
>
> (get the syntax error here, but you only touch this once)
>
>
> We are keeping two object libraries, one for the handler RPG objects and
one NOT.
> The 5250 programmers compile like they normally do, and DO NOT get the
syntax error when they go into the source.
> We compile with CRTBNDRPG define(‘use_handler’)
> If we accidently compile it to the wrong place, they just need to
re-compile without the parm to make it work.
> Tom Deskevich
> INFOCON
> 814-472-6066
> Fax 814-472-5019
> --
> This is the RPG programming on the IBM i / System i (RPG400-L) mailing
list
> To post a message email: RPG400-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
> or email: RPG400-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/rpg400-l.