RE: QUSRSPLA and operating system upgrade

[vhamberg@xxxxxxxxx]

Yeah, I think it's almost impossible to get ALL the
changes to be handled automatically when using CL. But
Simon's response may still apply, if you don't need the
new stuff. Ofssets may change, but where the offsets are
listed should be in the same places relative to the
start of the various structures.

You can still get bit. I know someone using the job log
APIs that got garbage. But when he went to soft-coding
the offsets and sizes, it was better. This was in C,
however.
> Forgot to mention that I'm using it in a CL program.
>
> Dave
>
> -----Original Message-----
> From: vhamberg@attbi.com [mailto:vhamberg@attbi.com]
> Sent: Tuesday, July 16, 2002 3:57 PM
> To: midrange-l@midrange.com
> Subject: Re: QUSRSPLA and operating system upgrade
>
>
> Which programming language? In C/C++, declare a struct
> with the one from the QSYSINC as the first element, than
> add the variable-length items at the end. This is
> instead of completely copying the includes/copy members
> into your code and having to do it again after an
> upgrade. Of course, the analogous use of /COPY may not
> work in RPG(LE), since you can't use a data type the
> same way, right? Or has this changed?
>
> In C/C++
>
> struct
> {
>      IBM_struct   element1;
>      datatype     your_element1;
>      ..
>      ..
> } struct_name;
>
> I think.
> > Does anyone have a good example of using QUSRSPLA - one that works even
> > after OS upgrades.  We just upgraded to V5R1 and have a few programs that
> > call QUSRSPLA and they bombed because the length of the variable being
> > passed was not long enough now.  It was easy to fix them and the error
> > message even told us what the new length should be but there should be a
> way
> > to automatically determine the length needed and dynamically allocate the
> > variable.  I'm not seeing anything in the manuals that helps.
> > Suggestions/examples?
> >
> > Thanks,
> > Dave
> _______________________________________________
> 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.
> _______________________________________________
> 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.
>