Re: 250 libraries. a solution?

["Steve Richter" <srichter@xxxxxxxxxxxxx>]

-----Original Message-----
From: M. Lazarus <mlazarus@ttec.com>
>  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.


hook the chglibl and addlible cmds.  in your version of the cmd send an
escape msg when the nbr of libs exceeds 25.


>  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."


hook the rtvjoba cmd. In your version, add this LiblFmt parameter.  If by
variable lgth rtn variables you mean Vary(*Yes) and PassAttr(*Yes), then a
user written cmd can have variable lgth rtn variables also.

-Steve



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