× 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: Validity checking program parms
  • From: Carel Teijgeler <COTeijgeler@xxxxxxxxx>
  • Date: Mon, 06 Aug 2001 18:02:37 +0200

John,

As far as I can remember it receives the same parameters as the CPP in the 
same order. Because you want to place a VCP on a system command you need to 
retrieve the definition of that for hidden parameters. Others have put in 
suggestions for that.

Regards,

Carel Teijgeler.

At 15:18 6-8-01, you wrote:

>Does anyone know if there's a manual somewhere that tells how parms are
>supposed to be defined for a validity checking program written in CL for
>a specific command (in this case the dltsplf command)?  I know the parms
>are supposed to be received in the same order that they appear in the
>command prompt but I keep getting parameter error messages.  (A search
>of the online books and this mailing list didn't turn up anything.)
>
>- John
>
>+---
>| 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
>+---
>
>
>---
>Incoming mail is certified Virus Free.
>Checked by AVG anti-virus system (http://www.grisoft.com).
>Version: 6.0.265 / Virus Database: 137 - Release Date: 18-7-01

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.