Fyi: (if this has any relevance) We have MAXPROCUSER set to 100, which is the number of concurrent processes for each UID. I think that the default was 25 - maybe you need more.
I still do not understand why the BPXP024I message appears for some tasks and not mine. BPXP024I BPXAS INITIATOR STARTED ON BEHALF OF JOB XSYSCERT RUNNING IN ASID 00B5 -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Barkow, Eileen Sent: Thursday, March 20, 2014 11:33 AM To: [email protected] Subject: Re: Java -Xdump:tool option on z/OS Fyi: I do not get the BPXP024I message when my IEFBR14 job starts, although I see the BPXP024I for other tasks. I think that initiators can get reused so maybe BPX is just reusing an existing initator for this function. I am running z/os 1.13 $ java -version java version "1.7.0" Java(TM) SE Runtime Environment (build pmz3170sr5-20130619_01(SR5)) IBM J9 VM (build 2.6, JRE 1.7.0 z/OS s390-31 20130617_152572 (JIT enabled, AOT e nabled) J9VM - R26_Java726_SR5_20130617_1436_B152572 JIT - r11.b04_20130528_38954ifx1 GC - R26_Java726_SR5_20130617_1436_B152572 J9CL - 20130617_152572) JCL - 20130616_01 based on Oracle 7u25-b12 $ -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of John McKown Sent: Thursday, March 20, 2014 11:16 AM To: [email protected] Subject: Re: Java -Xdump:tool option on z/OS If you're in the mood to experiment, you might also try: -Xdump:tool:events=vmstart,exec="submit //sa.jcl\(apfauth\)" The above definitely says that the DSN is 'SA.JCL', not prefixed with your RACF/TSO id. The \ escape the ( and ) which have meaning to the shell. I am not sure if they are needed or not in this case. I don't know why the tso and tsocmd commands are not working for you when then do for Eileen. What release of Java and z/OS? On Thu, Mar 20, 2014 at 9:55 AM, Steve Austin <[email protected]>wrote: > Thanks for that I'll keep trying. However, it would be nice if the > process that that is not submitting the job could be persuaded to say > something. > > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] > On Behalf Of Barkow, Eileen > Sent: 20 March 2014 14:28 > To: [email protected] > Subject: Re: Java -Xdump:tool option on z/OS > > The xdump command worked for me - started up IEFBR14 job. > > BPXM023I (ACSCEXB) 938 > JVMDUMP039I Processing dump event "vmstart", detail "" at 2014/03/20 > 10:22:38 - please wait. > > $HASP100 IEFBR14 ON INTRDR 10CICMLJ FROM TSU04969 > ACSCEXB > IRR010I USERID ACSCEXB IS ASSIGNED TO THIS JOB. > ICH70001I ACSCEXB LAST ACCESS AT 09:26:53 ON THURSDAY, MARCH 20, 2014 > $HASP373 IEFBR14 STARTED - INIT 1 - CLASS S - SYS MVSZ > - --TIMINGS (MINS.)-- > ----PAGING COUNTS--- > > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] > On Behalf Of Steve Austin > Sent: Thursday, March 20, 2014 9:49 AM > To: [email protected] > Subject: Java -Xdump:tool option on z/OS > > I'm attempting to use this option to issue a command at JVM start; > > -Xdump:tool:events=vmstart,exec="tso submit 'sa.jcl(apfauth)'" > > I can see the BPXAS address space being started on my behalf; > > JOB07776 00000090 BPXM023I (SA) 786 > 786 00000090 JVMDUMP039I Processing dump event "vmstart", detail "" > at 2014/03/20 > 786 00000090 13:06:26 - please wait. > 786 00000090 > STC07777 00080281 £HASP100 BPXAS ON STCINRDR > STC07777 00080290 £HASP373 BPXAS STARTED > STC07777 00000090 IEF403I BPXAS - STARTED - TIME=13.06.26 > STC07777 00000290 BPXP024I BPXAS INITIATOR STARTED ON BEHALF OF JOB > SAJNIJVM RUNNING IN ASID 001A > > STDERR contains; > > JVMDUMP039I Processing dump event "vmstart", detail "" at 2014/03/20 > 13:06:26 - please wait. > JVMDUMP007I JVM Requesting Tool dump using '"tso submit 'sa.jcl(apfauth)'"' > JVMDUMP011I Tool dump created process 65649 JVMDUMP013I Processed dump > event "vmstart", detail "". > > > However the job in question is not submitted and the BPXAS address > space remains wonderfully inscrutable . Has anyone done this > successfully, or have any idea how to get diagnostics on why the command is > failing? > > Thanks > > > This e-mail message has been scanned and cleared by Postini / Google > Message Security and the UNICOM Global security systems. This message > is for the named person's use only. If you receive this message in > error, please delete it and notify the sender. > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, send > email to [email protected] with the message: INFO IBM-MAIN > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, send > email to [email protected] with the message: INFO IBM-MAIN This > e-mail message has been scanned and cleared by Postini / Google > Message Security and the UNICOM Global security systems. This message > is for the named person's use only. If you receive this message in > error, please delete it and notify the sender. > > > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, send > email to [email protected] with the message: INFO IBM-MAIN > -- There is nothing more pleasant than traveling and meeting new people! Genghis Khan Maranatha! <>< John McKown ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
