|
I've never understood why IBM won't publish the complete parameter definition list for every command, just like they do the Escape messages. You should be able to hit F1 and see both.... Why is it such a secret? Users have been given the ability to write validity checking programs but IBM makes it really hard to do so! I just don't get it...
Al ... You should get on their case about this! <smile>
Kenneth -- ******************************** Kenneth E. Graap IBM Certified Specialist AS/400 Professional System Administrator NW Natural - Information Services System Services Phone 503 226 4211 X5537 FAX 603 849 0591 keg@xxxxxxxxxxxxx ********************************
-----Original Message----- From: Buck [mailto:buck.calabro@xxxxxxxxxxxx] Sent: Wednesday, July 23, 2003 2:22 PM To: midrange-l@xxxxxxxxxxxx Subject: Re: Question on Validity Checking
> am trying to write one for the WRKUSRJOB > command and keep getting errors that the > parameters do not match those in my > program.
There is a program called RTVCMDSRC floating round somewhere; try Google? Failing that, write a CL program, declare a hundred parameters and inspect each one via DMPCLPGM. By putting unique data into each element on the command, you should be able to tell something about the results. Of course, you'll go through it all over again at V5R3?...
Better is to write your own command, put it in a library above QSYS and do your processing there. When done, call the genuine command.
You can also look into the command exit points, but I haven't had a reason to dabble there yet. --buck
_______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
_______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
Pete Hall pbhall@xxxxxxxxxxxxx http://www.pbhall.us/
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.