Retrieve Command Information

[bvining@xxxxxxxxxxxx]

Retrieve Command Definition (QCDRCMDD), with format DEST0100, does
allow the destination to be a receiver variable rather than a file.

Another command related enhancement (though only available with V4R5)
are the new command analyzer exit points that allow an exit program to
be called prior to executing a given command.  These exits will
hopefully allow users to not have to front end application and/or system
commands with their own (which was one of the historical reasons for
wanting access to command definitions).

Bruce

>
>Hello:
>
>Some of you may have used MI or even a DMPSYSOBJ to generate the source for
>a *CMD object. Well, there is a new QCDRCMDD API (V4R4M0-SF62574) that will
>retrieve the command definition in XML tag language format. It must output
>to the IFS but it is a simple matter to input the string and then fgenerate
>the command source in AS/400 compatible format.
>
>This means that you can recover your command object and fix it if the source
>is lost. It also allows you to correct release incompatibilities that may
>have creeped up...
>
>Steve Glanstein
>mic@aloha.com
>


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