|
A late reply--- There's an option in the CRTCMD options that lets you specify the sequence that the parameter appears in the command when prompted. This allows IBM (I think some restrictions apply to user commands) to use an old program with a new sequence of parameters by renumbering things. There's an example of a program that fakes out the validity checking process on the NEWS/400 web site database; search for CHGJOB or RUNPTY; I don't have the exact issue. The example was to allow checking parameters on the CHGJOB command to prevent users from changing their run priority to 1. The gist of the validity checking program is that in CL you can just list all of the parameters as *CHAR 1 position fields. CL evidently doesn't care about the length of the parameter since only a pointer to the data is being passed anyway; you just have to have enough parameters! Attempt to use the parameter variable (ie CHGVAR &TESTVAR &PARMVAR) and monitor for that icky "Attempt to reference something that isn't pointed to" message. This is your clue that the variable wasn't passed to your command checking program and you can't do anything with that data; it doesn't exist. --Paul E Musselman PaulMmn@ix.netcom.nospam.com >Content-Type: text/plain; x-avg-checked=avg-ok-21D6CFA; >charset=us-ascii; format=flowed >Content-Transfer-Encoding: 8bit > >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 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.