If you've ever reported an error in DMSPIPE, you would have noticed that service is quick to ask you to download the module from Marist and see whether that fixes the problem. ymmv.
On 28 February 2010 21:36, Paul Gilmartin <[email protected]> wrote: > On Feb 27, 2010, at 23:56, John P. Hartmann wrote: > > > May I politely suggest that you take the question of how to avoid using > CMS > > Pipelines to another list? > > > One of us misunderstands -- I believe there's a version of CMS > Pipelines which is included in the base CMS product, and supported > in the base IBM service contract (am I wrong?). I expect no one > to have any objection to that. The distribution available from > Marist is another matter -- while the support is timely and the > response is excellent, some corporate officers and IT managers > may object to its informality. Is the charter of this list > only the version available from Marist, not the one supplied > by IBM? > > > > On 27 February 2010 17:14, Paul Gilmartin <[email protected]> wrote: > > > >> On Feb 27, 2010, at 09:05, Richard Troth wrote: > >>> > >>> > >>> So ... VMFPLC is great, and TAR is interoperable with non-CMS. Both > >>> are envelope thingies. Both can be neatly wrapped into plumbing. > >>> > >> And, because we must take into account customers who may balk at > >> installing anything for which they can't purchase a service > >> contract, and at purchasing a service contract they don't already > >> have, which of these are incorporated in the base VM? > >> > >> (Our own systems programmer refuses to install/support the > >> Pipelines RTL; customers may feel likewise.) > > I've coded a REXX which uses the DIGEST stage available only > in the Library Distribution. I'll try to make checksums > available to customers to verify with whatever techniques > are acceptable. > > Thanks, > gil >
