I gave up looking at the IBM supplied pipeline documentation years ago. PIPE AHELP is the only way to go. This is not an isolated phenomenon. Formerly IBM internal-only things that end up in the product line generally evolve along different paths and for many different reasons (although in my experience, the ability to provide full support going forward is often a significant driver). -- bc
On Fri, Feb 26, 2016 at 1:08 PM, Rob van der Heij <[email protected]> wrote: > > John P. Hartmann wrote: > > > From day one, some things were deliberately not described in the > > > official pipeline books from Glendale lab. > > > > Were they hoping to dispense with the un-described features? Or just > lazy in the docs department? > > Who knows, and who cares to find out after all those years... > > If I were you, I would make myself familiar with the style of the Author's > Edition Book. If you have to write against the old plumbing, be aware of > the > revision codes in the book and double check. Or maybe try, when in doubt. > You could pick up the PIPELINE HELPLIB and use PIPE AHELP online as well. > > There will be help from myself and others on the list when you run into any > issues with the Runtime Library level of CMS Pipelines. > > Sir Rob the Plumber > z/VM Development - CMS Pipelines >
