• Subject: Re: 250 libraries. a solution?
  • From: "M. Lazarus" <mlazarus@xxxxxxxx>
  • Date: Thu, 31 May 2001 21:21:09 -0400

Steve,

At 5/30/01 01:18 AM -0400, you wrote:
>If the ibm v5r1 rtvjoba will rtn the <=25 library libl into the char 275 var
>w/o error and will signal an excp ONLY if the rtvd libl will not fit in the
>rtn var, then imo the ibm solution is the correct one.

  There is a major difference between this change and others.  Other 
changes were self contained, so if you messed up by coding a return 
variable that's too long and stomped on some other area in memory, it's 
your fault.  Existing code, that was coded following the rules should not 
break.

  In this case, the *LIBL may be added to by other applications.  The 
effects are cumulative, meaning that as you enter and exit independent 
applications your *LIBL may continue to grow.  In the past the attempt 
would fail immediately, so your application would not continue and you 
could rectify the problem up front.  Now, you would not know that you are 
"over the limit" until existing code bombs.

  This is NOT good.  I agree w/ Al that this implementation is poor and it 
could easily have been avoided.

  One suggestion is to add an additional parm: LIBLFORMAT( *SHORT | *LONG 
), with short being the default, of course.  Since IBM can have variable 
length return variables, this should have been a "no brainer."

  -mark

+---
| 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
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.