-----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Charles Mills Sent: Tuesday, February 23, 2010 7:09 PM To: [email protected] Subject: Re: Determining if DUMMY allocation
I wasn't picking on JES3 specifically or any one aspect of things. My point was just that when you are a product vendor you never know what darned environment your product is going to run in, and it can be *very* difficult shooting a problem that only happens on a customer machine *without* ticking off the customer. So I try to choose interfaces -- when they're not GUPI interfaces -- that in my imperfect judgment (guess?) will be least likely to cause unpleasant consequences at a customer site. I was just riffing on that general concept -- not making a real fine judgment -- when I mentioned the particular bits in question and JES3. As a smaller vendor you have a particular challenge. I imagine CA does regression testing on their JES3 box as a regular part of product release. <SNIPPAGE> When I worked at CA, I don't remember a JES3 system... I have worked with JES3 systems, even when I was the last of the ACS/WYLBUR developers. I just did not have to do internals, except for an exit that we had. And I rarely had to do anything with it, because we use the "SSI" interface to get spool for JES3. For JES2, I overhauled the "JES2 SRB" interface and became more familiar with JES2 internals than I ever wanted to be. The biggest headaches you have as an ISV are other ISVs (and sometimes home grown systems) that intercept OPEN, STOW, BLDL, VSAM (for caching), and the like, when you do serious I/O routines. Regards, Steve Thompson -- Opinions expressed by this poster may not reflect poster's employer's opinions -- ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
