How to Purge Multiple Started Tasks from Output Q
I have a started task that kept failing. It actually used all the available job numbers up. I need to purge all of the output from this job, but keep getting error messages. Here is one of the commands I use: $P S'OSNMPD',OUTPUT,ALL $HASP003 RC=(78),P S'OSNMPD' - MULTIPLE JOBS FOUND I basically want to purge all of the OSNMPD started task output from the output Q. What command will do that? Thanks -- Eric Bielefeld Systems Programmer -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: How to Purge Multiple Started Tasks from Output Q
Since I rarely want the output from STCs, I just do a $PS1-99 and be done with it. If I do need the output, then I don't use a started task, but a started job. That way, I can code the JOB card and use the MSGCLASS=x in order to direct the output to our sysout archive software. -- John McKown Systems Engineer IV IT Administrative Services Group HealthMarkets(r) 9151 Boulevard 26 * N. Richland Hills * TX 76010 817) 255-3225 phone * john.mck...@healthmarkets.com * www.HealthMarkets.com Confidentiality Notice: This e-mail message may contain confidential or proprietary information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. HealthMarkets(r) is the brand name for products underwritten and issued by the insurance subsidiaries of HealthMarkets, Inc. -The Chesapeake Life Insurance Company(r), Mid-West National Life Insurance Company of TennesseeSM and The MEGA Life and Health Insurance Company.SM -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Eric Bielefeld Sent: Thursday, April 12, 2012 11:37 AM To: IBM-MAIN@bama.ua.edu Subject: How to Purge Multiple Started Tasks from Output Q I have a started task that kept failing. It actually used all the available job numbers up. I need to purge all of the output from this job, but keep getting error messages. Here is one of the commands I use: $P S'OSNMPD',OUTPUT,ALL $HASP003 RC=(78),P S'OSNMPD' - MULTIPLE JOBS FOUND I basically want to purge all of the OSNMPD started task output from the output Q. What command will do that? Thanks -- Eric Bielefeld Systems Programmer -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: How to Purge Multiple Started Tasks from Output Q
John - Thanks. It wasn't exactly what I was looking for, but it worked a lot better than putting a P in front of everything in SDSF. I didn't want to purge everything, but I was able to purge large groups at a time, so it didn't take too long. I don't know why I didn't think of that myself. I thought there was a command that you could give a jobname or STC name and purge multiple jobs or STCs. -- Eric Bielefeld Systems Programmer McKown wrote: Since I rarely want the output from STCs, I just do a $PS1-99 and be done with it. If I do need the output, then I don't use a started task, but a started job. That way, I can code the JOB card and use the MSGCLASS=x in order to direct the output to our sysout archive software. -- John McKown Systems Engineer IV IT Administrative Services Group HealthMarkets(r) 9151 Boulevard 26 * N. Richland Hills * TX 76010 817) 255-3225 phone * john.mck...@healthmarkets.com * www.HealthMarkets.com -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Eric Bielefeld Sent: Thursday, April 12, 2012 11:37 AM To: IBM-MAIN@bama.ua.edu Subject: How to Purge Multiple Started Tasks from Output Q I have a started task that kept failing. It actually used all the available job numbers up. I need to purge all of the output from this job, but keep getting error messages. Here is one of the commands I use: $P S'OSNMPD',OUTPUT,ALL $HASP003 RC=(78),P S'OSNMPD' - MULTIPLE JOBS FOUND I basically want to purge all of the OSNMPD started task output from the output Q. What command will do that? For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: How to Purge Multiple Started Tasks from Output Q
You can use a block command to affect a large number of sysouts in SDSF. On the NP column, you put a // and then the desired action on the first job and then page down to the last job and put in a // and press enter. And it will look something like this in SDSF: //p job001 // job999 Thanks, Hervey -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Eric Bielefeld Sent: Thursday, April 12, 2012 2:40 PM To: IBM-MAIN@bama.ua.edu Subject: Re: How to Purge Multiple Started Tasks from Output Q John - Thanks. It wasn't exactly what I was looking for, but it worked a lot better than putting a P in front of everything in SDSF. I didn't want to purge everything, but I was able to purge large groups at a time, so it didn't take too long. I don't know why I didn't think of that myself. I thought there was a command that you could give a jobname or STC name and purge multiple jobs or STCs. -- Eric Bielefeld Systems Programmer McKown wrote: Since I rarely want the output from STCs, I just do a $PS1-99 and be done with it. If I do need the output, then I don't use a started task, but a started job. That way, I can code the JOB card and use the MSGCLASS=x in order to direct the output to our sysout archive software. -- John McKown Systems Engineer IV IT Administrative Services Group HealthMarkets(r) 9151 Boulevard 26 * N. Richland Hills * TX 76010 817) 255-3225 phone * john.mck...@healthmarkets.com * www.HealthMarkets.com -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Eric Bielefeld Sent: Thursday, April 12, 2012 11:37 AM To: IBM-MAIN@bama.ua.edu Subject: How to Purge Multiple Started Tasks from Output Q I have a started task that kept failing. It actually used all the available job numbers up. I need to purge all of the output from this job, but keep getting error messages. Here is one of the commands I use: $P S'OSNMPD',OUTPUT,ALL $HASP003 RC=(78),P S'OSNMPD' - MULTIPLE JOBS FOUND I basically want to purge all of the OSNMPD started task output from the output Q. What command will do that? For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: How to Purge Multiple Started Tasks from Output Q
Try something like this: $P O Sx-x,JM=yourSTCname -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Eric Bielefeld Sent: Thursday, April 12, 2012 2:40 PM To: IBM-MAIN@bama.ua.edu Subject: Re: How to Purge Multiple Started Tasks from Output Q John - Thanks. It wasn't exactly what I was looking for, but it worked a lot better than putting a P in front of everything in SDSF. I didn't want to purge everything, but I was able to purge large groups at a time, so it didn't take too long. I don't know why I didn't think of that myself. I thought there was a command that you could give a jobname or STC name and purge multiple jobs or STCs. -- Eric Bielefeld Systems Programmer McKown wrote: Since I rarely want the output from STCs, I just do a $PS1-99 and be done with it. If I do need the output, then I don't use a started task, but a started job. That way, I can code the JOB card and use the MSGCLASS=x in order to direct the output to our sysout archive software. -- John McKown Systems Engineer IV IT Administrative Services Group HealthMarkets(r) 9151 Boulevard 26 * N. Richland Hills * TX 76010 817) 255-3225 phone * john.mck...@healthmarkets.com * www.HealthMarkets.com -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Eric Bielefeld Sent: Thursday, April 12, 2012 11:37 AM To: IBM-MAIN@bama.ua.edu Subject: How to Purge Multiple Started Tasks from Output Q I have a started task that kept failing. It actually used all the available job numbers up. I need to purge all of the output from this job, but keep getting error messages. Here is one of the commands I use: $P S'OSNMPD',OUTPUT,ALL $HASP003 RC=(78),P S'OSNMPD' - MULTIPLE JOBS FOUND I basically want to purge all of the OSNMPD started task output from the output Q. What command will do that? For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN This e-mail may contain confidential or privileged information. If you think you have received this e-mail in error, please advise the sender by reply e-mail and then delete this e-mail immediately. Thank you. Aetna -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
Re: DISPLAY command for non-IBM started tasks
On Sun, 15 Aug 2010 01:44:09 -0400 Jim Mulder d10j...@us.ibm.com wrote: :IBM Mainframe Discussion List IBM-MAIN@bama.ua.edu wrote on 08/14/2010 :07:31:36 AM: : Does anyone know the significance of CIBVERB = CIBSTCOM, documented as : COMMAND CODE FOR STC COMMUNICATION? : START command processing builds a separate CIB for each :STC Communication Keyword. The STC Communication Keywords :are SUB= and JOBNAME=. Is the SUB= CIB new? I do not recall receiving anything other than the START CIB even when using SUB=. -- Binyamin Dissen bdis...@dissensoftware.com http://www.dissensoftware.com Director, Dissen Software, Bar Grill - Israel Should you use the mailblocks package and expect a response from me, you should preauthorize the dissensoftware.com domain. I very rarely bother responding to challenge/response systems, especially those from irresponsible companies. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: DISPLAY command for non-IBM started tasks
On Sun, 15 Aug 2010 01:44:09 -0400 Jim Mulder d10j...@us.ibm.com wrote: :IBM Mainframe Discussion List IBM-MAIN@bama.ua.edu wrote on 08/14/2010 :07:31:36 AM: : Does anyone know the significance of CIBVERB = CIBSTCOM, documented as : COMMAND CODE FOR STC COMMUNICATION? : START command processing builds a separate CIB for each :STC Communication Keyword. The STC Communication Keywords :are SUB= and JOBNAME=. Is the SUB= CIB new? I do not recall receiving anything other than the START CIB even when using SUB=. The change flags on the SUB= CIB code are old-style format - I think from MVS/XA SP2.1.0. The SUB= CIB is used by STC Job Scheduling to select the requested subsystem, and is deleted at that point. So it is gone by the time your code would get control. JOBNAME= was introduced in SP5.1.0. I don't see any references to CIBSTCOM in a z/OS BCP XREF other than START command processing and STC Job Scheduling, so maybe the JOBNAME= CIB persists. Jim Mulder z/OS System Test IBM Corp. Poughkeepsie, NY -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: DISPLAY command for non-IBM started tasks
In 062101cb3ba4$423fbda0$c6bf38...@org, on 08/14/2010 at 07:31 AM, Charles Mills charl...@mcn.org said: I know how to process MODIFY and STOP (and the operands of START) commands in a non-IBM-written started task (using EXTRACT, CIB, and QEDIT). There is no documented interface for extending, e.g., DISPLAY (D), HALT (Z) or VARY (V). If you want to process them then you'll have to do as Rob suggested and parse them yourself. Just out of curiosity, if it's not possible, does anyone know why it is not? Because the destinations of D, V and Z are hard-wired. -- Shmuel (Seymour J.) Metz, SysProg and JOAT ISO position; see http://patriot.net/~shmuel/resume/brief.html We don't care. We don't have to care, we're Congress. (S877: The Shut up and Eat Your spam act of 2003) -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
DISPLAY command for non-IBM started tasks
I know how to process MODIFY and STOP (and the operands of START) commands in a non-IBM-written started task (using EXTRACT, CIB, and QEDIT). Is it possible to use some roughly similar interface to accept DISPLAY commands? How? Just out of curiosity, if it's not possible, does anyone know why it is not? You can shoehorn any function into MODIFY, but sometimes it's not a great fit. Does anyone know the significance of CIBVERB = CIBSTCOM, documented as COMMAND CODE FOR STC COMMUNICATION? Charles Mills -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: DISPLAY command for non-IBM started tasks
Charles As far as I am aware, there is no *easy* way for you to get your software to respond to just D FOO,BAR You would have to have a subsystem and process the broadcast function code 10 (system commands). You could then intercept the command string that you seek and queue it up for your server code to handle. However, the normal way that software does this is to register a command prefix so that clashes are avoided with other software products and subsystems - so in the end you will end up with something like ( being your command prefix) : D FOO,BAR It is subjective if that is preferable to F server,D FOO,BAR Rob Scott Lead Developer Rocket Software 275 Grove Street * Newton, MA 02466-2272 * USA Tel: +1.617.614.2305 Email: rsc...@rs.com Web: www.rocketsoftware.com -Original Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of Charles Mills Sent: 14 August 2010 13:32 To: IBM-MAIN@bama.ua.edu Subject: DISPLAY command for non-IBM started tasks I know how to process MODIFY and STOP (and the operands of START) commands in a non-IBM-written started task (using EXTRACT, CIB, and QEDIT). Is it possible to use some roughly similar interface to accept DISPLAY commands? How? Just out of curiosity, if it's not possible, does anyone know why it is not? You can shoehorn any function into MODIFY, but sometimes it's not a great fit. Does anyone know the significance of CIBVERB = CIBSTCOM, documented as COMMAND CODE FOR STC COMMUNICATION? Charles Mills -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: DISPLAY command for non-IBM started tasks
Hmmm. Thanks. I guess I'll stick with F server,STATS Charles -Original Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of Rob Scott Sent: Saturday, August 14, 2010 10:14 AM To: IBM-MAIN@bama.ua.edu Subject: Re: DISPLAY command for non-IBM started tasks Charles As far as I am aware, there is no *easy* way for you to get your software to respond to just D FOO,BAR You would have to have a subsystem and process the broadcast function code 10 (system commands). You could then intercept the command string that you seek and queue it up for your server code to handle. However, the normal way that software does this is to register a command prefix so that clashes are avoided with other software products and subsystems - so in the end you will end up with something like ( being your command prefix) : D FOO,BAR It is subjective if that is preferable to F server,D FOO,BAR -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: DISPLAY command for non-IBM started tasks
IBM Mainframe Discussion List IBM-MAIN@bama.ua.edu wrote on 08/14/2010 07:31:36 AM: Does anyone know the significance of CIBVERB = CIBSTCOM, documented as COMMAND CODE FOR STC COMMUNICATION? START command processing builds a separate CIB for each STC Communication Keyword. The STC Communication Keywords are SUB= and JOBNAME=. Jim Mulder z/OS System Test IBM Corp. Poughkeepsie, NY -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Started Tasks
In [EMAIL PROTECTED], on 08/03/2006 at 06:12 PM, Rob Weiss [EMAIL PROTECTED] said: All Started Tasks (STC) are started through Master JCL to the internal reader. No. Those that run under MASTER do not go through the primary JES. The default is SYS1.PROCLIB on the system where the task was started. Most shops that I've seen update the Master JCL and the JES parms to provide other libraries. -- Shmuel (Seymour J.) Metz, SysProg and JOAT ISO position; see http://patriot.net/~shmuel/resume/brief.html We don't care. We don't have to care, we're Congress. (S877: The Shut up and Eat Your spam act of 2003) -- 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
Re: Started Tasks
All Started Tasks (STC) are started through Master JCL to the internal reader. No. Those that run under MASTER do not go through the primary JES. He said Master JCL, which I believe is correct. He did not say MSTR subsystem as in SUB=MSTR. Bob Shannon -- 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
Started Tasks
We are z/OS V1R4. I have a question about CA's started tasks. CAS9 CAL7 (CA-ELEVEN) will not start unless they are in SYS1.PROCLIB. These procs reside in a proclib that is in the concatenation of JES2, but are not in the proclib concatenation of MSTRJCL00. My question is how do these proc's know the difference of which library they are started from. Is CAS9 forcing these to come from SYS1.PROCLIB or forcing them to come from the MSTRJCLxx concatenation? Any help would be appreciated. Thank You -- 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
Re: Started Tasks
If they are started 'SUB-MSTR' then they must be in the MSTJCL concatination. JES doesn't get involved in processing for 'SUB=MSTR'. Jon L. Veilleux [EMAIL PROTECTED] (860) 636-2683 -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Mark Steely Sent: Thursday, August 03, 2006 3:21 PM To: IBM-MAIN@BAMA.UA.EDU Subject: Started Tasks We are z/OS V1R4. I have a question about CA's started tasks. CAS9 CAL7 (CA-ELEVEN) will not start unless they are in SYS1.PROCLIB. These procs reside in a proclib that is in the concatenation of JES2, but are not in the proclib concatenation of MSTRJCL00. My question is how do these proc's know the difference of which library they are started from. Is CAS9 forcing these to come from SYS1.PROCLIB or forcing them to come from the MSTRJCLxx concatenation? Any help would be appreciated. Thank You -- 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 - This e-mail may contain confidential or privileged information. If you think you have received this e-mail in error, please advise the sender by reply e-mail and then delete this e-mail immediately. Thank you. Aetna -- 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
Re: Started Tasks
-Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Mark Steely Sent: Thursday, August 03, 2006 2:21 PM To: IBM-MAIN@BAMA.UA.EDU Subject: Started Tasks We are z/OS V1R4. I have a question about CA's started tasks. CAS9 CAL7 (CA-ELEVEN) will not start unless they are in SYS1.PROCLIB. These procs reside in a proclib that is in the concatenation of JES2, but are not in the proclib concatenation of MSTRJCL00. My question is how do these proc's know the difference of which library they are started from. Is CAS9 forcing these to come from SYS1.PROCLIB or forcing them to come from the MSTRJCLxx concatenation? Any help would be appreciated. Thank You The problem is that CAS9 and CAL7 are defined as sub systems, like JES2. When a START command is issued, the command processor compares the name of the started task with the names of the subsystems. If the name being started matches a subsystem name, then the command processor implicitly adds a ,SUB=MSTR to start the JCL under the master subsystem. You can get around this by issuing the commands as follows: S CAS9,SUB=JES2 S CAL7,SUB=JES2 to force the command processor to give the START command to JES2 instead of MSTR. -- John McKown Senior Systems Programmer HealthMarkets Keeping the Promise of Affordable Coverage Administrative Services Group Information Technology This message (including any attachments) contains confidential information intended for a specific individual and purpose, and its content is protected by law. If you are not the intended recipient, you should delete this message and are hereby notified that any disclosure, copying, or distribution of this transmission, or taking any action based on it, is strictly prohibited. -- 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
