Re: User state UNDEL2 utility available

[vhamberg@xxxxxxxxxxx]

At V5R1 there is the QCDRCMDD API, which should have no problems with system 
state, as it comes from IBM:

========================
The Retrieve Command Definition (QCDRCMDD) API retrieves the command definition 
source for a given command in XML tag language format. The source is returned 
in the destination provided in UTF-8 (CCSID 1208). See the Document Type 
Definition (DTD) in /QIBM/XML/DTD/QcdCLCmd.dtd for details of the XML tag 
language returned by this API.
========================

At V5R1 it did not return information about hidden parameters (defined with 
CONSTANT). At V5R3 a second format for the return variable was added that gives 
you everything.

There is a style sheet at IT Jungle - you could search there - that is a start 
at giving you the true command. It has a couple errors and is missing several 
things, but it is a start. The DTD is located at /QIBM/XML/DTD/QcdCLCmd.dtd. No 
need for MI anything here.

This API returns current defaults (CHGCMDDFT results), not the originals as set 
by IBM or a vendor.

HTH
Vern

-------------- Original message -------------- 
From: Keith Carpenter <carpcon@xxxxxxx> 

> Rob, 
> 
> Another great tool. 
> 
> RTVCMDSRC does not require system state or program patching as did 
> UNDEL. You still need a MI compiler which I think has been posted in 
> MI400 a few times. IBM also documents a simple one in API manuals. 
> 
> If you mean a non MI program version, it should be doable in RPG. The 
> MI program direct accesses the command definition space obj, but you can 
> avoid some security issues (domain violations) by going the DMPOBJ route 
> instead. The code to do the DMPOBJ is already in RTVCMDSRC. 
> 
> 
> Keith 
> 
> 
> rob@xxxxxxxxx wrote: 
> > What about RTVCMDSRC? 
> > 
> > Rob Berendt 
> -- 
> 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. 
>