Re: Is there a way to retrieve the source for a custom WSCST file?

On 30-Jan-2012 17:56 , Kirk Goins wrote:

On Mon, Jan 30, 2012 at 5:54 PM, Kirk Goins wrote:

<<SNIP>> RTVWSCST only works on the IBM predefined objects.
I opened a PMR with IBM and here was the 'trick' they said to use.
#1 Create a DUPOBJ of and existing IBM WSCST object ( like
QWPDEFAULT ) with a new name.
#2 Delete the Original Qxxxxx WSCST
#3 Put your existing WSCST that doesn't have the source in QSYS
using the name of the IBM object

#4 RTVWSCST using the IBM name
Now you have the source for your WSCST
#5 Reverse the changes you made so the IBM WSCST object you used

Worked pretty slick

I do not think those are the best possible instructions. I would go as far as suggesting they are very /bad/ instructions. With very rare exceptions, instructions from IBM should *not* suggest to delete an object shipped with the OS :-(

I wonder if followed as written, those steps might cause the OS to be in error; i.e. if the request to CHKPRDOPT PRDID(*OPSYS) RLS(*OPSYS) OPTION(*BASE) LODID(5050) DETAIL(*FULL) is run after performing those steps, might the OS become marked *ERROR because the original object which belongs to the OS has gone missing? Irrespective of potential for a missing OS object [as diagnosed by the OS], those instructions do not ensure to effect proper\matching ownership nor authority to the original OS object :-(

If interested, I could script a much safer and IMO better means; though I have no idea what "using the IBM name" means for RTVWSCST since I see nothing in the syntax diagram to correlate. Seems rather daft that they do not just have a WSCST parameter for the command, if the feature can support that effect generically.?

Regards, Chuck