> > Previously, when using other batch launchers, we noticed significant > general purpose CPU usage. I profiled the behavior using IBM APA, and the > histogram showed that 90 percent of the time was spent in pause element > pause and resume. I assume this reflects frequent context switching between > a zIIP and a general purpose processor.
Interesting. Makes sense I guess. I wouldn't expect much unless there was a lot of output being redirected. I'm not sure how BPXBATCH handles it, but in COZBATCH we use pipes for stdin/stdout and a select loop. So that costs nothing unless there is data being passed. I do know that z/OS Unix pipes are not very CPU efficient in some cases. > > > BTW: The JZOS Console support is not actually part of the JZOS Batch > > Launcher. There is a com.ibm.jzos.MvsConsole class in the JZOS Toolkit. > > If you invoke the startMvsCommandListener() static method, you can have > > console support in any z/OS Java application. The JZOS Batch launcher > > just starts this after initializing the JVM, although that can be disabled > > with an environment variable. The MvsConsole class also allows you to > > customize a callback so that you can have whatever command language you > > want. > > > > That is interesting. When I run a batch Java program using COZBATCH that > listens for events with com.ibm.jzos.MvsConsole, and I issue a STOP > command, I get the message IEE341I <jobname> NOT ACTIVE. I must be missing > something or doing it wrong? Hmm. I would first check to see that java ran in the original batch address space. _BPX_SHAREAS=YES ? Otherwise, your "P jobname" would be going to the wrong address space. If you find multiple jobs with the same jobname, you can target one by using ",A=asid" on the STOP command ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
