× 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: Douglas Handy <dhandy1@xxxxxxxxxxxxx>
  • Date: Mon, 06 Aug 2001 08:41:40 -0400

John,

>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)?  

There is no such manual -- which explains why you can't find it. <g>

If you are on a release prior to V5R1, then the best thing to do is get a copy
of Dave McKenzie's excellent freeware RTVCMDSRC utility.  This will recreate the
command source for virtually any command -- IBM or user.  Armed with the command
source, you can tell the parameter structure the CPP is expecting and therefore
what a VCP will need as well.

RTVCMDSRC is available on the shareware/freeware section of the News/400 web
side ( www.as400network.com ) and possibly other places too.

In V5R1, new exit programs were added for dealing with commands, and are the
preferred method for modifing the behavior of IBM commands.

Doug

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