Re: Bindable APIs Vs Non-Bindable APIs -- MIDRANGE-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Subject: Re: Bindable APIs Vs Non-Bindable APIs
From: Barbara Morris <bmorris@xxxxxxxxxx>
Date: Wed, 18 Feb 2004 17:51:48 -0500
List-archive: <http://archive.midrange.com/midrange-l>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

Simon Coulter wrote:
> 
> On Thursday, February 19, 2004, at 02:46  AM, Barbara Morris wrote:
> 
> > (I don't think it's possible to omit parameters in CL.)
> 
> It is: CALLPRC api (parm1 parm2 *OMIT)
> 

Thanks, that's good to know.  I prompted on the PARM part of the CALLPRC
command, and didn't see *OMIT there.  Now I see that the help does
mention *OMIT.

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: Bindable APIs Vs Non-Bindable APIs , Simon Coulter

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.