I agree with John McKown's comments. I would only add one note... Since our server-side JavaScript engine runs on the zIIP (and inside of CICS), our customers write integration services that are zIIP enabled. Are these "applications"? Not in the traditional sense. However, customers are doing some pretty interesting things in terms of: (a) data transformation, and (b) automating interactions with existing applications. Note that whenever we pass control to non-JavaScript customer code (e.g., LINKing to a CICS COBOL program), we flip that work over to a CICS Open TCB. That keeps us compliant with the ISV license agreement, but also avoids a whole array of technical issues that would result otherwise.
Russ Teubner - HostBridge -----Original Message----- From: IBM Mainframe Assembler List [mailto:[email protected]] On Behalf Of John McKown Sent: Friday, May 08, 2015 2:04 PM To: [email protected] Subject: Re: ASSEMBLER-LIST Digest - 5 May 2015 to 6 May 2015 (#2015-52) On Fri, May 8, 2015 at 1:14 PM, John Walker < [email protected]> wrote: > What are the gains in doing the ziip thing? I am aware of it, as a > mainframe guy, but don't know the details. It might be helpful to > learn in any case. > There are two mains ones that I know of: (1) If you run zIIP enabled code on a zIIP, then that CPU is not part of your MSU for software billing purposes; (2) A zIIP engine always run "full speed", even if the normal CPs are "knee capped". However, you also need to be aware that you cannot run just anything on a zIIP. Not all system services are available to code running zIIP enabled. Also, getting the information on how to write zIIP enabled code is IBM proprietary. You cannot use then information except as allowed by IBM. You cannot disclose the information to others because requires signing an NDA. You cannot reveal the source to others, again due to the NDA. zIIP enabled code is really only for vendors. Now, you _can_ use a zIIP engine for application code _IF_ you enable zAAP on zIIP processing. But you can only write zAAP enabled code in Java. So it could be used for things like WAS transactions, CICS transactions (I think), or even batch programs. But again, only for Java language. And don't try to use JNI to slide some COBOL or HLASM in there because the JNI interface will turn off the zAAP eligibility while the JNI code is running. -- If someone tell you that nothing is impossible: Ask him to dribble a football. He's about as useful as a wax frying pan. 10 to the 12th power microphones = 1 Megaphone Maranatha! <>< John McKown
