Re: Saving job output
RGEN in SDSF has some useful templates. I've built a few useful utilities using RGEN as a base. I'll take alook at Lionel's utilities too. Looks great. My latest (most useful to our shop) is using REXX/SDSF to find a writer ID from Tivoli Workload Scheduler output collector and write it out to a meaningful job name for our support staff to quickly find output from Windows tasks. I also use REXX/SDSF to cancel long running batch jobs that our training course students submit and forget about. Robs session at Share/Phoenix was very helpful. On Fri, Oct 11, 2019 at 4:42 AM Mike Stramba wrote: > On 10/10/19, Rob Scott wrote: > > The most recent link : https://www.share.org/d/do/17301 > > > > You *might* need a Share login. > > > > Got it, thank, no login req ;) > > >Depending on the level of z/OS you are at, in SDSF there is a REXX > Tutorial. > > Thanks Lizette. > > Mike > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- Wayne V. Bickerdike -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Saving job output
On 10/10/19, Rob Scott wrote: > The most recent link : https://www.share.org/d/do/17301 > > You *might* need a Share login. > Got it, thank, no login req ;) >Depending on the level of z/OS you are at, in SDSF there is a REXX Tutorial. Thanks Lizette. Mike -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Saving job output
On Thu, 10 Oct 2019 11:12:33 +, Rob Scott wrote: > >You can accomplish what you want very easily using the SDSF REXX interface, >you even have two options of how : > >(1) Use ISFACT and the "SA" action to allocate a DDName to each different >spool dataset and then use EXECIO to put the records wherever you want (1a) Use IEBGENER to unload the data set, avoiding the storage constraint. (EXECIO could read the data set piecewise, also.) (More sent privately.) >(2) Use ISFBROWSE to process data at the "cursor" position. > >Option (1) is probably easier conceptually, however because it reads the data >into stems it could have storage constraints for large spool datasets. >Option (2) uses a logical cursor so will be a better general purpose solution. > >See Share session 24671 "Learn to use SDSF Rexx" that I gave in Phoenix -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Saving job output
You should take a look at MacKinney Systems JSF product...just be sure to go after the most current version. Thanks, Ron McCabe Manager of Mainframe/Midrange Systems Mutual of Enumclaw -Original Message- From: IBM Mainframe Discussion List On Behalf Of John McKown Sent: Thursday, October 10, 2019 7:57 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Saving job output On Thu, Oct 10, 2019 at 5:56 AM Gadi Ben-Avi wrote: > Hi, > Every now and again, I have to send the output from a job or started > task to support. > Saving all of the output is simple using SDSF's XDC command, but that > saves all of the output to one file. > It's much easier to deal with the individual spool files. > > Does anyone have a utility that can split the output according to the > different spool files? > > Gadi > I have a REXX program which uses the SDSF REXX API to copy job output to disk. At present, it puts everything into a single data set (or UNIX file), but I think it can be modified to put each individual SPOOL files into a separate DSN. Would you like me to send it to you off-line? -- I find television very educational. The minute somebody turns it on, I go into the library and read a good book -- Groucho Marx Maranatha! <>< John McKown -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN Confidentiality Notice: This e- mail and all attachments may contain CONFIDENTIAL information and are meant solely for the intended recipient. It may contain controlled, privileged, or proprietary information that is protected under applicable law and shall not be disclosed to any unauthorized third party. If you are not the intended recipient, you are hereby notified that any unauthorized review, action, disclosure, distribution, or reproduction of any information contained in this e- mail and any attachments is strictly PROHIBITED. If you received this e- mail in error, please reply to the sender immediately stating that this transmission was misdirected, and delete or destroy all electronic and paper copies of this e-mail and attachments without disclosing the contents. This e- mail does not grant or assign rights of ownership in the proprietary subject matter herein, nor shall it be construed as a joint venture, partnership, teaming agreement, or any other formal business relationship. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Saving job output
On Thu, Oct 10, 2019 at 5:56 AM Gadi Ben-Avi wrote: > Hi, > Every now and again, I have to send the output from a job or started task > to support. > Saving all of the output is simple using SDSF's XDC command, but that > saves all of the output to one file. > It's much easier to deal with the individual spool files. > > Does anyone have a utility that can split the output according to the > different spool files? > > Gadi > I have a REXX program which uses the SDSF REXX API to copy job output to disk. At present, it puts everything into a single data set (or UNIX file), but I think it can be modified to put each individual SPOOL files into a separate DSN. Would you like me to send it to you off-line? -- I find television very educational. The minute somebody turns it on, I go into the library and read a good book -- Groucho Marx Maranatha! <>< John McKown -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Saving job output
Depending on the level of z/OS you are at, in SDSF there is a REXX Tutorial. In SDSF - enter PF1 (HELP) On this panel you would select TOC Then on that panel you should see REXX Tutorial entry. If you go through those pages, there are examples, explanations and other cool functions using SDSF REXX Lizette > -Original Message- > From: IBM Mainframe Discussion List On Behalf Of > Gadi Ben-Avi > Sent: Thursday, October 10, 2019 3:55 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Saving job output > > Hi, > Every now and again, I have to send the output from a job or started task to > support. > Saving all of the output is simple using SDSF's XDC command, but that saves > all of the output to one file. > It's much easier to deal with the individual spool files. > > Does anyone have a utility that can split the output according to the > different spool files? > > Gadi > > > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, send email to > lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Saving job output
The most recent link : https://www.share.org/d/do/17301 You *might* need a Share login. If you have trouble downloading, let me know and I can send you the pdf privately. Rob Scott Rocket Software -Original Message- From: IBM Mainframe Discussion List On Behalf Of Mike Stramba Sent: Thursday, October 10, 2019 1:16 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Saving job output Rob, On 10/10/19, Rob Scott wrote: > See Share session 24671 "Learn to use SDSF Rexx" that I gave in > Phoenix Do you have a link ? google is not finding anything. Mike -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN Rocket Software, Inc. and subsidiaries ■ 77 Fourth Avenue, Waltham MA 02451 ■ Main Office Toll Free Number: +1 855.577.4323 Contact Customer Support: https://my.rocketsoftware.com/RocketCommunity/RCEmailSupport Unsubscribe from Marketing Messages/Manage Your Subscription Preferences - http://www.rocketsoftware.com/manage-your-email-preferences Privacy Policy - http://www.rocketsoftware.com/company/legal/privacy-policy This communication and any attachments may contain confidential information of Rocket Software, Inc. All unauthorized use, disclosure or distribution is prohibited. If you are not the intended recipient, please notify Rocket Software immediately and destroy all copies of this communication. Thank you. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Saving job output
That's almost what I am looking for. I would like each DD to be in a separate output file. Gadi -Original Message- From: IBM Mainframe Discussion List On Behalf Of Lionel B Dyck Sent: Thursday, October 10, 2019 3:37 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Saving job output More info on SDSFEXT: Syntax:%sdsfext jobname ddname outdd jobnum (options Where: jobname is the name of the job to extract or * for the current jobname if * then active is set on support wild cards (% and *) in jobname ddname is the ddname to be extracted or (ddname1 ddname2 ...) or * for all ddnames ddname may be coded as stepname.ddname where stepname is the jcl stepname not the step found in a proc. or stepname.procstep.ddname outdd is the ddname where the extracted data is to be directed jobnum is the job number for the desired job ( is required if any options are specified options currently supported are: ACTIVE - only process jobs that are currently executing. - set on if jobname is * DEBUG- will echo the generated SDSF cmds INPUT- will allow selection of input data Example: %sdsfext smtp logfile report This will extract the ddname LOGFILE for each occurrence of the job SMTP in the spool with the output going to preallocated DD REPORT. Lionel B. Dyck < Website: http://www.lbdsoftware.com "Worry more about your character than your reputation. Character is what you are, reputation merely what others think you are." - John Wooden -Original Message- From: IBM Mainframe Discussion List On Behalf Of Gadi Ben-Avi Sent: Thursday, October 10, 2019 7:22 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Saving job output Thanks Lionel. Can the jobname include wildcards? What happens if there is more than one job with the same jobname? Gadi -Original Message- From: IBM Mainframe Discussion List On Behalf Of Lionel B Dyck Sent: Thursday, October 10, 2019 2:56 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Saving job output See my generalized routine SDSFEXT at http://lbdsoftware.com/sdsfext120.zip or in file 313 at cbttape.org: A generalized SDSF extraction process that will extract a specific ddname for all matching jobs that are in the JES2 SPOOL. The extraction is performed to a preallocated data set referenced by a DD statement in the batch terminal monitor program. %sdsfext jobname ddname outdd jobnum (options Lionel B. Dyck < Website: http://www.lbdsoftware.com "Worry more about your character than your reputation. Character is what you are, reputation merely what others think you are." - John Wooden -Original Message- From: IBM Mainframe Discussion List On Behalf Of Gadi Ben-Avi Sent: Thursday, October 10, 2019 5:55 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Saving job output Hi, Every now and again, I have to send the output from a job or started task to support. Saving all of the output is simple using SDSF's XDC command, but that saves all of the output to one file. It's much easier to deal with the individual spool files. Does anyone have a utility that can split the output according to the different spool files? Gadi -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listse
Re: Saving job output
More info on SDSFEXT: Syntax:%sdsfext jobname ddname outdd jobnum (options Where: jobname is the name of the job to extract or * for the current jobname if * then active is set on support wild cards (% and *) in jobname ddname is the ddname to be extracted or (ddname1 ddname2 ...) or * for all ddnames ddname may be coded as stepname.ddname where stepname is the jcl stepname not the step found in a proc. or stepname.procstep.ddname outdd is the ddname where the extracted data is to be directed jobnum is the job number for the desired job ( is required if any options are specified options currently supported are: ACTIVE - only process jobs that are currently executing. - set on if jobname is * DEBUG- will echo the generated SDSF cmds INPUT- will allow selection of input data Example: %sdsfext smtp logfile report This will extract the ddname LOGFILE for each occurrence of the job SMTP in the spool with the output going to preallocated DD REPORT. Lionel B. Dyck < Website: http://www.lbdsoftware.com "Worry more about your character than your reputation. Character is what you are, reputation merely what others think you are." - John Wooden -Original Message- From: IBM Mainframe Discussion List On Behalf Of Gadi Ben-Avi Sent: Thursday, October 10, 2019 7:22 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Saving job output Thanks Lionel. Can the jobname include wildcards? What happens if there is more than one job with the same jobname? Gadi -Original Message- From: IBM Mainframe Discussion List On Behalf Of Lionel B Dyck Sent: Thursday, October 10, 2019 2:56 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Saving job output See my generalized routine SDSFEXT at http://lbdsoftware.com/sdsfext120.zip or in file 313 at cbttape.org: A generalized SDSF extraction process that will extract a specific ddname for all matching jobs that are in the JES2 SPOOL. The extraction is performed to a preallocated data set referenced by a DD statement in the batch terminal monitor program. %sdsfext jobname ddname outdd jobnum (options Lionel B. Dyck < Website: http://www.lbdsoftware.com "Worry more about your character than your reputation. Character is what you are, reputation merely what others think you are." - John Wooden -Original Message- From: IBM Mainframe Discussion List On Behalf Of Gadi Ben-Avi Sent: Thursday, October 10, 2019 5:55 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Saving job output Hi, Every now and again, I have to send the output from a job or started task to support. Saving all of the output is simple using SDSF's XDC command, but that saves all of the output to one file. It's much easier to deal with the individual spool files. Does anyone have a utility that can split the output according to the different spool files? Gadi -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN Email secured by Check Point ---
Re: Saving job output
Thanks Lionel. Can the jobname include wildcards? What happens if there is more than one job with the same jobname? Gadi -Original Message- From: IBM Mainframe Discussion List On Behalf Of Lionel B Dyck Sent: Thursday, October 10, 2019 2:56 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Saving job output See my generalized routine SDSFEXT at http://lbdsoftware.com/sdsfext120.zip or in file 313 at cbttape.org: A generalized SDSF extraction process that will extract a specific ddname for all matching jobs that are in the JES2 SPOOL. The extraction is performed to a preallocated data set referenced by a DD statement in the batch terminal monitor program. %sdsfext jobname ddname outdd jobnum (options Lionel B. Dyck < Website: http://www.lbdsoftware.com "Worry more about your character than your reputation. Character is what you are, reputation merely what others think you are." - John Wooden -Original Message- From: IBM Mainframe Discussion List On Behalf Of Gadi Ben-Avi Sent: Thursday, October 10, 2019 5:55 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Saving job output Hi, Every now and again, I have to send the output from a job or started task to support. Saving all of the output is simple using SDSF's XDC command, but that saves all of the output to one file. It's much easier to deal with the individual spool files. Does anyone have a utility that can split the output according to the different spool files? Gadi -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN Email secured by Check Point -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Saving job output
Rob, On 10/10/19, Rob Scott wrote: > See Share session 24671 "Learn to use SDSF Rexx" that I gave in Phoenix Do you have a link ? google is not finding anything. Mike -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Saving job output
See my generalized routine SDSFEXT at http://lbdsoftware.com/sdsfext120.zip or in file 313 at cbttape.org: A generalized SDSF extraction process that will extract a specific ddname for all matching jobs that are in the JES2 SPOOL. The extraction is performed to a preallocated data set referenced by a DD statement in the batch terminal monitor program. %sdsfext jobname ddname outdd jobnum (options Lionel B. Dyck < Website: http://www.lbdsoftware.com "Worry more about your character than your reputation. Character is what you are, reputation merely what others think you are." - John Wooden -Original Message- From: IBM Mainframe Discussion List On Behalf Of Gadi Ben-Avi Sent: Thursday, October 10, 2019 5:55 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Saving job output Hi, Every now and again, I have to send the output from a job or started task to support. Saving all of the output is simple using SDSF's XDC command, but that saves all of the output to one file. It's much easier to deal with the individual spool files. Does anyone have a utility that can split the output according to the different spool files? Gadi -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Saving job output
Not much heavy lifting required - here is some sample ISFACT code that just
performs a "say" operation for a specified "unique job" , but the basic
framework is there.
Lastrc = isfcalls('ON')
ISFPREFIX=“ROBUNIQ1”
address SDSF “ISFEXEC ST”
address SDSF “ISFACT ST TOKEN(‘”token.1”’) PARM(NP SA)”
do ddindex = 1 to ISFDDNAME.0
say “Now reading : “ISFDSNAME.ddindex
address TSO “EXECIO * DISKR “ISFDDNAME.ddindex “ (STEM line. FINIS”
say “Lines read : “line.0
do lineindex = 1 to line.0
say substr(line.lineindex,1,72)
end
end
lastrc = isfcalls('OFF')
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Gadi Ben-Avi
Sent: Thursday, October 10, 2019 12:17 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Saving job output
Thanks Rob,
I was asking if someone had already done the heavy lifting.
Gadi
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of Rob
Scott
Sent: Thursday, October 10, 2019 2:13 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Saving job output
Gadi,
You can accomplish what you want very easily using the SDSF REXX interface, you
even have two options of how :
(1) Use ISFACT and the "SA" action to allocate a DDName to each different spool
dataset and then use EXECIO to put the records wherever you want
(2) Use ISFBROWSE to process data at the "cursor" position.
Option (1) is probably easier conceptually, however because it reads the data
into stems it could have storage constraints for large spool datasets.
Option (2) uses a logical cursor so will be a better general purpose solution.
See Share session 24671 "Learn to use SDSF Rexx" that I gave in Phoenix
Rob Scott
Rocket Software
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Gadi Ben-Avi
Sent: Thursday, October 10, 2019 11:55 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Saving job output
Hi,
Every now and again, I have to send the output from a job or started task to
support.
Saving all of the output is simple using SDSF's XDC command, but that saves all
of the output to one file.
It's much easier to deal with the individual spool files.
Does anyone have a utility that can split the output according to the different
spool files?
Gadi
--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to
lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Rocket Software, Inc. and subsidiaries ■ 77
Fourth Avenue, Waltham MA 02451 ■ Main Office Toll Free Number: +1 855.577.4323
Contact Customer Support:
https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmy.rocketsoftware.com%2FRocketCommunity%2FRCEmailSupport&data=02%7C01%7C%7C87872526f0384d55ee6b08d74d736926%7C79544c1eed224879a082b67a9a672aae%7C0%7C0%7C637063030407422035&sdata=3iIRsOnxWxhdFrpcQMiloDOIZcnePiLIDqrqhltFyAs%3D&reserved=0
Unsubscribe from Marketing Messages/Manage Your Subscription Preferences -
https://nam01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.rocketsoftware.com%2Fmanage-your-email-preferences&data=02%7C01%7C%7C87872526f0384d55ee6b08d74d736926%7C79544c1eed224879a082b67a9a672aae%7C0%7C0%7C637063030407432030&sdata=PVrXZGBCvgR9FDfPr4%2FD9ZO6dgtwtbp1wnQYbl7FBYM%3D&reserved=0
Privacy Policy -
https://nam01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.rocketsoftware.com%2Fcompany%2Flegal%2Fprivacy-policy&data=02%7C01%7C%7C87872526f0384d55ee6b08d74d736926%7C79544c1eed224879a082b67a9a672aae%7C0%7C0%7C637063030407432030&sdata=NcnGE2I0VYjsEfn6IsMhj2Hz%2FmDE2VQ%2BF2FvSXV8oWM%3D&reserved=0
This communication and any attachments may contain confidential information of
Rocket Software, Inc. All unauthorized use, disclosure or distribution is
prohibited. If you are not the intended recipient, please notify Rocket
Software immediately and destroy all copies of this communication. Thank you.
--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to
lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Email secured by Check Point
--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to
lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Rocket Software, Inc. and subsidiaries ■ 77 Fourth Avenue, Waltham MA 02451 ■
Main Office Toll Free Number: +1 855.577.4323
Contact Customer Support:
https://my.rocketsoftware.com/RocketCommunity/RCEmailSupport
Unsubscribe from Marketing Messages/Manage Your Subscription Preferences -
http://www.rocketsoftware.com/manage-your-email-preferences
Privacy Policy - http://www.rocketsoftware.com/company/legal/privacy-policy
=
Re: Saving job output
Yeah, I wasn't sure that was what you needed, but I thought it should be mentioned. I use it quite a bit. sas On Thu, Oct 10, 2019 at 7:43 AM Gadi Ben-Avi wrote: > I know that, > But if you have a job with many output files, or you want the output of > many jobs, this becomes tedious. You can also make mistakes. > Gadi > > -Original Message- > From: IBM Mainframe Discussion List On Behalf > Of Steve Smith > Sent: Thursday, October 10, 2019 2:41 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: Saving job output > > You can XDC each individual spool file. Just use the ? line command to > view them. > > sas > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, send email > to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > Email secured by Check Point > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- sas -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Saving job output
I know that, But if you have a job with many output files, or you want the output of many jobs, this becomes tedious. You can also make mistakes. Gadi -Original Message- From: IBM Mainframe Discussion List On Behalf Of Steve Smith Sent: Thursday, October 10, 2019 2:41 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Saving job output You can XDC each individual spool file. Just use the ? line command to view them. sas -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN Email secured by Check Point -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Saving job output
You can XDC each individual spool file. Just use the ? line command to view them. sas -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Saving job output
Thanks Rob, I was asking if someone had already done the heavy lifting. Gadi -Original Message- From: IBM Mainframe Discussion List On Behalf Of Rob Scott Sent: Thursday, October 10, 2019 2:13 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Saving job output Gadi, You can accomplish what you want very easily using the SDSF REXX interface, you even have two options of how : (1) Use ISFACT and the "SA" action to allocate a DDName to each different spool dataset and then use EXECIO to put the records wherever you want (2) Use ISFBROWSE to process data at the "cursor" position. Option (1) is probably easier conceptually, however because it reads the data into stems it could have storage constraints for large spool datasets. Option (2) uses a logical cursor so will be a better general purpose solution. See Share session 24671 "Learn to use SDSF Rexx" that I gave in Phoenix Rob Scott Rocket Software -Original Message- From: IBM Mainframe Discussion List On Behalf Of Gadi Ben-Avi Sent: Thursday, October 10, 2019 11:55 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Saving job output Hi, Every now and again, I have to send the output from a job or started task to support. Saving all of the output is simple using SDSF's XDC command, but that saves all of the output to one file. It's much easier to deal with the individual spool files. Does anyone have a utility that can split the output according to the different spool files? Gadi -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN Rocket Software, Inc. and subsidiaries ■ 77 Fourth Avenue, Waltham MA 02451 ■ Main Office Toll Free Number: +1 855.577.4323 Contact Customer Support: https://my.rocketsoftware.com/RocketCommunity/RCEmailSupport Unsubscribe from Marketing Messages/Manage Your Subscription Preferences - http://www.rocketsoftware.com/manage-your-email-preferences Privacy Policy - http://www.rocketsoftware.com/company/legal/privacy-policy This communication and any attachments may contain confidential information of Rocket Software, Inc. All unauthorized use, disclosure or distribution is prohibited. If you are not the intended recipient, please notify Rocket Software immediately and destroy all copies of this communication. Thank you. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN Email secured by Check Point -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Saving job output
Gadi, You can accomplish what you want very easily using the SDSF REXX interface, you even have two options of how : (1) Use ISFACT and the "SA" action to allocate a DDName to each different spool dataset and then use EXECIO to put the records wherever you want (2) Use ISFBROWSE to process data at the "cursor" position. Option (1) is probably easier conceptually, however because it reads the data into stems it could have storage constraints for large spool datasets. Option (2) uses a logical cursor so will be a better general purpose solution. See Share session 24671 "Learn to use SDSF Rexx" that I gave in Phoenix Rob Scott Rocket Software -Original Message- From: IBM Mainframe Discussion List On Behalf Of Gadi Ben-Avi Sent: Thursday, October 10, 2019 11:55 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Saving job output Hi, Every now and again, I have to send the output from a job or started task to support. Saving all of the output is simple using SDSF's XDC command, but that saves all of the output to one file. It's much easier to deal with the individual spool files. Does anyone have a utility that can split the output according to the different spool files? Gadi -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN Rocket Software, Inc. and subsidiaries ■ 77 Fourth Avenue, Waltham MA 02451 ■ Main Office Toll Free Number: +1 855.577.4323 Contact Customer Support: https://my.rocketsoftware.com/RocketCommunity/RCEmailSupport Unsubscribe from Marketing Messages/Manage Your Subscription Preferences - http://www.rocketsoftware.com/manage-your-email-preferences Privacy Policy - http://www.rocketsoftware.com/company/legal/privacy-policy This communication and any attachments may contain confidential information of Rocket Software, Inc. All unauthorized use, disclosure or distribution is prohibited. If you are not the intended recipient, please notify Rocket Software immediately and destroy all copies of this communication. Thank you. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: SAVING JOB OUTPUT IN A PDSE FROM SDSF
Thanks for the suggestion. I tried it out as a test and it worked. The only drawback is that I will have to include the output of the job after the //SYSUT1 DD * As a test I tried inserting the dsn as in the SYSUT1 DD * however it did not work. I got the folowing : DATA SET UTILITY - GENERATE IEB311I CONFLICTING DCB PARAMETERS Here is the jcl I used: /* //STEP EXEC PGM=IEBGENER //SYSUT2 DD DSN=SYS2.CNTL.SHR(XF),DISP=(MOD,CATLG), // UNIT=SYSALLDA,SPACE=(500,(500,,5)) //SYSUT1 DD DSN=SYS2.XF,DISP=SHR //SYSPRINT DD SYSOUT=(,) //SYSPRINT DD SYSOUT=* //SYSIN DD * /* On Fri, 4/29/16, R.S. wrote: Subject: Re: SAVING JOB OUTPUT IN A PDSE FROM SDSF To: IBM-MAIN@LISTSERV.UA.EDU Received: Friday, April 29, 2016, 5:06 PM W dniu 2016-04-29 o 22:30, Paul Gilmartin pisze: > On 2016-04-29, at 09:58, R.S. wrote: >>>> That deserves an SR. Works in JCL; works everywhere else. The statement is >>>> patently false. >>> No, it isn't. MOD is not allowed for *member* od PDS or PDSE. >>> MOD is allowed for PO dataset, i.e. for IEFBR14 MOD,DELETE >>> >>> Try IEBGENER //SYSUT2 DD DSN=HLQ.SOME.PO(MEMBER),DISP=(MOD,CATLG) >>> > My test job step: > //STEP EXEC PGM=IEBGENER > //SYSUT2 DD DSN=&SYSUID..SOME.PO(MEMBER),DISP=(MOD,CATLG), > // UNIT=SYSALLDA,SPACE=(500,(500,,5)) > //SYSUT1 DD * > Test Data > //SYSPRINT DD SYSOUT=(,) > //SYSIN DD * > //* > > And log output: > > 14.10.00 JOB00158 - -TIMINGS (MINS.)-- -PAGING COUNTS > 14.10.00 JOB00158 -STEPNAME PROCSTEP RC EXCP CONN TCB SRB CLOCK SERV WORKLOAD PAGE SWAP VIO SWAPS > 14.10.00 JOB00158 -STEP 00 47 22 .00 .00 .0 116 BATCH 0 0 0 0 > 14.10.00 JOB00158 IEF404I PDSMOD - ENDED - TIME=14.10.00 > 14.10.00 JOB00158 -PDSMOD ENDED. NAME-Paul Gilmartin TOTAL TCB CPU TIME= .00 TOTAL ELAPSED TIME= .0 > 14.10.00 JOB00158 $HASP395 PDSMOD ENDED - RC= > > Works for me. You are right. Please rerun the job. I bet you'll get SB214 abend. My description was innacurate (I'm sorry for that!), however I meant MOD as appending existing memebr. It is not possible. BTW: simple JCL workaound is to copy member to a PS, append it and then overwrite the member (overwrite is possible, despite of PDS vs PDSE internal processing, I mean what enduser see). Regarding SDSF, the forbiden DISP and DSORG combination can be result of SDSF dialog logic, not the access method restriction. Unfortunately, it is possible to overwrite a member by mistake using the dialog Regards -- Radoslaw Skorupka Lodz, Poland -- Tre tej wiadomoci moe zawiera informacje prawnie chronione Banku przeznaczone wycznie do uytku subowego adresata. Odbiorc moe by jedynie jej adresat z wyczeniem dostpu osób trzecich. Jeeli nie jeste adresatem niniejszej wiadomoci lub pracownikiem upowanionym do jej przekazania adresatowi, informujemy, e jej rozpowszechnianie, kopiowanie, rozprowadzanie lub inne dziaanie o podobnym charakterze jest prawnie zabronione i moe by karalne. Jeeli otrzymae t wiadomo omykowo, prosimy niezwocznie zawiadomi nadawc wysyajc odpowied oraz trwale usun t wiadomo wczajc w to wszelkie jej kopie wydrukowane lub zapisane na dysku. This e-mail may contain legally privileged information of the Bank and is intended solely for business use of the addressee. This e-mail may only be received by the addressee and may not be disclosed to any third parties. If you are not the intended addressee of this e-mail or the employee authorized to forward it to the addressee, be advised that any dissemination, copying, distribution or any other similar activity is legally prohibited and may be punishable. If you received this e-mail by mistake please advise the sender immediately by using the reply facility in your e-mail software and delete permanently this e-mail including any copies of it either printed or saved to hard drive. mBank S.A. z siedzib w Warszawie, ul. Senatorska 18, 00-950 Warszawa, www.mBank.pl, e-mail: kont...@mbank.pl Sd Rejonowy dla m. st. Warszawy XII Wydzia Gospodarczy Krajowego Rejestru Sdowego, nr rejestru przedsibiorców KRS 025237, NIP: 526-021-50-88. Wedug stanu na dzie 01.01.2016 r. kapita zakadowy mBanku S.A. (w caoci wpacony) wynosi 168.955.696 zotych.
Re: SAVING JOB OUTPUT IN A PDSE FROM SDSF
Robert, I tried out your recommendation but the member gets overriden. Below is the display of the dsn" Data set name ===> 'SYS2.BATCH.JOBS.OUTPUT' Member to use ===> JOB03070 Disposition===> SHR(OLD, NEW, SHR, MOD) Management class ===> (Blank for default management class) Storage class===> (Blank for default storage class) Volume serial ===> (Blank for authorized default volume) Device type===> (Generic unit or device address) Data class ===> (Blank for default data class) Space units===> CYLS (BLKS, TRKS, CYLS, BY, KB, or MB) Primary quantity ===> 1 (In above units) Secondary quantity ===> 5 (In above units) Directory blocks ===> (Zero for sequential data set) Record format ===> VBA Record length ===> 240 Block size ===> 3120 Data set name type ===> LIBRARY (LIBRARY, blank, ... See Help for more) Extended attributes ===> (NO, OPT, or blank) -------- On Mon, 5/2/16, Richards, Robert B. wrote: Subject: Re: SAVING JOB OUTPUT IN A PDSE FROM SDSF To: IBM-MAIN@LISTSERV.UA.EDU Received: Monday, May 2, 2016, 5:31 AM Willie, According to the HELP, the dataset name type defaults to the characteristics above. You did not specify directory blocks, so it assumes physical sequential (PS). Member names are invalid for PS datasets. Either add directory blocks or specify LIBRARY as the dataset name type. Bob -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of willie bunter Sent: Friday, April 29, 2016 1:24 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: SAVING JOB OUTPUT IN A PDSE FROM SDSF This is what I have. In the Data set name type ===> it is blank as shown below. Data set name ===> ''SYS2.BATCH.JOBS.OUTPUT' Member to use ===> JOB06703 Disposition ===> SHR (OLD, NEW, SHR, MOD) Management class ===> (Blank for default management class) Storage class ===> (Blank for default storage class) Volume serial ===> (Blank for authorized default volume) Device type ===> (Generic unit or device address) Data class ===> (Blank for default data class) Space units ===> CYLS (BLKS, TRKS, CYLS, BY, KB, or MB) Primary quantity ===> 1 (In above units) Secondary quantity ===> 5 (In above units) Directory blocks ===> (Zero for sequential data set) Record format ===> VBA Record length ===> 240 Block size ===> 3120 Data set name type ===> (LIBRARY, blank, ... See Help for more) Extended attributes ===> (NO, OPT, or blank) On Fri, 4/29/16, Richards, Robert B. wrote: Subject: Re: SAVING JOB OUTPUT IN A PDSE FROM SDSF To: IBM-MAIN@LISTSERV.UA.EDU Received: Friday, April 29, 2016, 7:50 AM Data set name ===> 'ABCDE.FGHIJK.LMNOP' Member to use ===> QRSTUV Disposition ===> NEW (OLD, NEW, SHR, MOD) Management class ===> (Blank for default management class) Storage class ===> (Blank for default storage class) Volume serial ===> (Blank for authorized default volume) Device type ===> (Generic unit or device address) Data class ===> (Blank for default data class) Space units ===> CYLS (BLKS, TRKS, CYLS, BY, KB, or MB) Primary quantity ===> 25 (In above units) Secondary quantity ===> 5 (In above units) Directory blocks ===> 45 (Zero for sequential data set) <= Did you specify directory blanks???
Re: SAVING JOB OUTPUT IN A PDSE FROM SDSF
Maybe put Year in DSN, member name would include Month 1-9,A,B,C, Day 01-31, Time -2359, or Day of Year 001-366, Time -2359. On Mon, May 2, 2016 at 11:21 AM, Pedro Vera wrote: >>> Is there something I could do to prevent this from happening? > > I think JES2 can be customized to use seven digit numbers for the job number. > On my site, the jobs numbers look like J1234567. That is, you cannot > prevent the collision in job numbers, but you can lessen the frequency. > > If I were doing this exercise, I would replace the first character with an > alphabetic sequence value. Instead of saving the job as member J1234567, > save it as A1234567. When there is a collision, use a member name of > B1234567, etc... Or perhaps do not worry about the member name, but archive > the entire data set when the numeric sequence number rolls over. > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- Mike A Schwab, Springfield IL USA Where do Forest Rangers go to get away from it all? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: SAVING JOB OUTPUT IN A PDSE FROM SDSF
>> Is there something I could do to prevent this from happening? I think JES2 can be customized to use seven digit numbers for the job number. On my site, the jobs numbers look like J1234567. That is, you cannot prevent the collision in job numbers, but you can lessen the frequency. If I were doing this exercise, I would replace the first character with an alphabetic sequence value. Instead of saving the job as member J1234567, save it as A1234567. When there is a collision, use a member name of B1234567, etc... Or perhaps do not worry about the member name, but archive the entire data set when the numeric sequence number rolls over. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: SAVING JOB OUTPUT IN A PDSE FROM SDSF
Willie, According to the HELP, the dataset name type defaults to the characteristics above. You did not specify directory blocks, so it assumes physical sequential (PS). Member names are invalid for PS datasets. Either add directory blocks or specify LIBRARY as the dataset name type. Bob -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of willie bunter Sent: Friday, April 29, 2016 1:24 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: SAVING JOB OUTPUT IN A PDSE FROM SDSF This is what I have. In the Data set name type ===> it is blank as shown below. Data set name ===> ''SYS2.BATCH.JOBS.OUTPUT' Member to use ===> JOB06703 Disposition ===> SHR (OLD, NEW, SHR, MOD) Management class ===> (Blank for default management class) Storage class ===> (Blank for default storage class) Volume serial ===> (Blank for authorized default volume) Device type ===> (Generic unit or device address) Data class ===> (Blank for default data class) Space units ===> CYLS (BLKS, TRKS, CYLS, BY, KB, or MB) Primary quantity ===> 1 (In above units) Secondary quantity ===> 5 (In above units) Directory blocks ===> (Zero for sequential data set) Record format ===> VBA Record length ===> 240 Block size ===> 3120 Data set name type ===> (LIBRARY, blank, ... See Help for more) Extended attributes ===> (NO, OPT, or blank) -------- On Fri, 4/29/16, Richards, Robert B. wrote: Subject: Re: SAVING JOB OUTPUT IN A PDSE FROM SDSF To: IBM-MAIN@LISTSERV.UA.EDU Received: Friday, April 29, 2016, 7:50 AM Data set name ===> 'ABCDE.FGHIJK.LMNOP' Member to use ===> QRSTUV Disposition ===> NEW (OLD, NEW, SHR, MOD) Management class ===> (Blank for default management class) Storage class ===> (Blank for default storage class) Volume serial ===> (Blank for authorized default volume) Device type ===> (Generic unit or device address) Data class ===> (Blank for default data class) Space units ===> CYLS (BLKS, TRKS, CYLS, BY, KB, or MB) Primary quantity ===> 25 (In above units) Secondary quantity ===> 5 (In above units) Directory blocks ===> 45 (Zero for sequential data set) <= Did you specify directory blanks??? Record format ===> FBA Record length ===> 133 Block size ===> Data set name type ===> <=== Do you have this value specified??? Extended attributes ===> (NO, OPT, or blank) -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of willie bunter Sent: Friday, April 29, 2016 7:45 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: SAVING JOB OUTPUT IN A PDSE FROM SDSF Lizette, I tried your suggestion using NEW but it doesn't work. I get the message MEMBER NAME NOT ALLOWED I hit the PF1 option but it wasn't much help. On Thu, 4/28/16, Lizette Koehler wrote: Subject: Re: SAVING JOB OUTPUT IN A PDSE FROM SDSF To: IBM-MAIN@LISTSERV.UA.EDU Received: Thursday, April 28, 2016, 7:08 PM When you use XDC and NEW it will indicate if the member already exists. You should try this and see if it works. I find trying SHR, OLD and NEW on a PDS that will not matter if it is over written a good thing to try to understand how things work. Also, you could press PF1 (HELP) and see what the HELP panel states. Lizette > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of willie bunter > Sent: Thursday, April 28, 2016 4:00 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: SAVING JOB OUTPUT IN A PDSE FROM SDSF > > Hallo All, > > I need your suggestions. I am savings job output in a PDSE using SDSF. The > member name I use is the job number e.g. > Member to use ===&
Re: SAVING JOB OUTPUT IN A PDSE FROM SDSF
On 2016-04-29, at 15:06, R.S. wrote: >> >> Works for me. > You are right. Please rerun the job. I bet you'll get SB214 abend. > I know that well. I assumed that since the OP's requirement was to avoid overwriting an existing member, SB214 would meet his need. I had considered the alternative of ISPEXEC LMCOPY with no REPLACE option. Alas, LMINIT won't accept a DDNAME generated by ISPF API (another silly restriction.) > My description was innacurate (I'm sorry for that!), however I meant MOD as > appending existing memebr. It is not possible. > BTW: simple JCL workaound is to copy member to a PS, append it and then > overwrite the member (overwrite is possible, despite of PDS vs PDSE internal > processing, I mean what enduser see). > Or, copy to a temporary PDS member using JCL DD concatenation; delete, and rename. Very slightly less I/O. I understand the structure of a PDS well enough to know that appending to an existing member is nearly impossible. Since I don't know PDSE internals but I suspect that a member isn't necessarily stored contiguously, I'm unable to infer a reason for prohibiting appending to a PDSE member. Or, use UNIX files, which impose no such silly restriction on appending. > Regarding SDSF, the forbiden DISP and DSORG combination can be result of SDSF > dialog logic, not the access method restriction. > I suspect likewise. > Unfortunately, it is possible to overwrite a member by mistake using the > dialog > So the designers, for unknown reasons, introduced an idiosyncratic syntactic restriction that precludes a conventional means of prudently avoiding overwriting. -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: SAVING JOB OUTPUT IN A PDSE FROM SDSF
W dniu 2016-04-29 o 22:30, Paul Gilmartin pisze: On 2016-04-29, at 09:58, R.S. wrote: That deserves an SR. Works in JCL; works everywhere else. The statement is patently false. No, it isn't. MOD is not allowed for *member* od PDS or PDSE. MOD is allowed for PO dataset, i.e. for IEFBR14 MOD,DELETE Try IEBGENER //SYSUT2 DD DSN=HLQ.SOME.PO(MEMBER),DISP=(MOD,CATLG) My test job step: //STEP EXEC PGM=IEBGENER //SYSUT2 DD DSN=&SYSUID..SOME.PO(MEMBER),DISP=(MOD,CATLG), // UNIT=SYSALLDA,SPACE=(500,(500,,5)) //SYSUT1 DD * Test Data //SYSPRINT DD SYSOUT=(,) //SYSIN DD * //* And log output: 14.10.00 JOB00158 - -TIMINGS (MINS.)-- -PAGING COUNTS 14.10.00 JOB00158 -STEPNAME PROCSTEPRC EXCP CONN TCB SRB CLOCK SERV WORKLOAD PAGE SWAP VIO SWAPS 14.10.00 JOB00158 -STEP 00 47 22 .00 .00 .0 116 BATCH0 0 0 0 14.10.00 JOB00158 IEF404I PDSMOD - ENDED - TIME=14.10.00 14.10.00 JOB00158 -PDSMOD ENDED. NAME-Paul Gilmartin TOTAL TCB CPU TIME= .00 TOTAL ELAPSED TIME=.0 14.10.00 JOB00158 $HASP395 PDSMOD ENDED - RC= Works for me. You are right. Please rerun the job. I bet you'll get SB214 abend. My description was innacurate (I'm sorry for that!), however I meant MOD as appending existing memebr. It is not possible. BTW: simple JCL workaound is to copy member to a PS, append it and then overwrite the member (overwrite is possible, despite of PDS vs PDSE internal processing, I mean what enduser see). Regarding SDSF, the forbiden DISP and DSORG combination can be result of SDSF dialog logic, not the access method restriction. Unfortunately, it is possible to overwrite a member by mistake using the dialog Regards -- Radoslaw Skorupka Lodz, Poland -- Tre tej wiadomoci moe zawiera informacje prawnie chronione Banku przeznaczone wycznie do uytku subowego adresata. Odbiorc moe by jedynie jej adresat z wyczeniem dostpu osób trzecich. Jeeli nie jeste adresatem niniejszej wiadomoci lub pracownikiem upowanionym do jej przekazania adresatowi, informujemy, e jej rozpowszechnianie, kopiowanie, rozprowadzanie lub inne dziaanie o podobnym charakterze jest prawnie zabronione i moe by karalne. Jeeli otrzymae t wiadomo omykowo, prosimy niezwocznie zawiadomi nadawc wysyajc odpowied oraz trwale usun t wiadomo wczajc w to wszelkie jej kopie wydrukowane lub zapisane na dysku. This e-mail may contain legally privileged information of the Bank and is intended solely for business use of the addressee. This e-mail may only be received by the addressee and may not be disclosed to any third parties. If you are not the intended addressee of this e-mail or the employee authorized to forward it to the addressee, be advised that any dissemination, copying, distribution or any other similar activity is legally prohibited and may be punishable. If you received this e-mail by mistake please advise the sender immediately by using the reply facility in your e-mail software and delete permanently this e-mail including any copies of it either printed or saved to hard drive. mBank S.A. z siedzib w Warszawie, ul. Senatorska 18, 00-950 Warszawa, www.mBank.pl, e-mail: kont...@mbank.pl Sd Rejonowy dla m. st. Warszawy XII Wydzia Gospodarczy Krajowego Rejestru Sdowego, nr rejestru przedsibiorców KRS 025237, NIP: 526-021-50-88. Wedug stanu na dzie 01.01.2016 r. kapita zakadowy mBanku S.A. (w caoci wpacony) wynosi 168.955.696 zotych. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: SAVING JOB OUTPUT IN A PDSE FROM SDSF
On 2016-04-29, at 09:58, R.S. wrote: >>> >>> That deserves an SR. Works in JCL; works everywhere else. The statement is >>> patently false. >> No, it isn't. MOD is not allowed for *member* od PDS or PDSE. >> MOD is allowed for PO dataset, i.e. for IEFBR14 MOD,DELETE >> >> Try IEBGENER //SYSUT2 DD DSN=HLQ.SOME.PO(MEMBER),DISP=(MOD,CATLG) >> My test job step: //STEP EXEC PGM=IEBGENER //SYSUT2 DD DSN=&SYSUID..SOME.PO(MEMBER),DISP=(MOD,CATLG), // UNIT=SYSALLDA,SPACE=(500,(500,,5)) //SYSUT1 DD * Test Data //SYSPRINT DD SYSOUT=(,) //SYSIN DD * //* And log output: 14.10.00 JOB00158 - -TIMINGS (MINS.)-- -PAGING COUNTS 14.10.00 JOB00158 -STEPNAME PROCSTEPRC EXCP CONN TCB SRB CLOCK SERV WORKLOAD PAGE SWAP VIO SWAPS 14.10.00 JOB00158 -STEP 00 47 22 .00 .00 .0 116 BATCH0 0 0 0 14.10.00 JOB00158 IEF404I PDSMOD - ENDED - TIME=14.10.00 14.10.00 JOB00158 -PDSMOD ENDED. NAME-Paul Gilmartin TOTAL TCB CPU TIME= .00 TOTAL ELAPSED TIME=.0 14.10.00 JOB00158 $HASP395 PDSMOD ENDED - RC= Works for me. -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: SAVING JOB OUTPUT IN A PDSE FROM SDSF
This is what I have. In the Data set name type ===> it is blank as shown below. Data set name ===> ''SYS2.BATCH.JOBS.OUTPUT' Member to use ===> JOB06703 Disposition ===> SHR (OLD, NEW, SHR, MOD) Management class ===> (Blank for default management class) Storage class ===> (Blank for default storage class) Volume serial ===> (Blank for authorized default volume) Device type ===> (Generic unit or device address) Data class ===> (Blank for default data class) Space units ===> CYLS (BLKS, TRKS, CYLS, BY, KB, or MB) Primary quantity ===> 1 (In above units) Secondary quantity ===> 5 (In above units) Directory blocks ===> (Zero for sequential data set) Record format ===> VBA Record length ===> 240 Block size ===> 3120 Data set name type ===> (LIBRARY, blank, ... See Help for more) Extended attributes ===> (NO, OPT, or blank) -------- On Fri, 4/29/16, Richards, Robert B. wrote: Subject: Re: SAVING JOB OUTPUT IN A PDSE FROM SDSF To: IBM-MAIN@LISTSERV.UA.EDU Received: Friday, April 29, 2016, 7:50 AM Data set name ===> 'ABCDE.FGHIJK.LMNOP' Member to use ===> QRSTUV Disposition ===> NEW (OLD, NEW, SHR, MOD) Management class ===> (Blank for default management class) Storage class ===> (Blank for default storage class) Volume serial ===> (Blank for authorized default volume) Device type ===> (Generic unit or device address) Data class ===> (Blank for default data class) Space units ===> CYLS (BLKS, TRKS, CYLS, BY, KB, or MB) Primary quantity ===> 25 (In above units) Secondary quantity ===> 5 (In above units) Directory blocks ===> 45 (Zero for sequential data set) <= Did you specify directory blanks??? Record format ===> FBA Record length ===> 133 Block size ===> Data set name type ===> <=== Do you have this value specified??? Extended attributes ===> (NO, OPT, or blank) -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of willie bunter Sent: Friday, April 29, 2016 7:45 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: SAVING JOB OUTPUT IN A PDSE FROM SDSF Lizette, I tried your suggestion using NEW but it doesn't work. I get the message MEMBER NAME NOT ALLOWED I hit the PF1 option but it wasn't much help. On Thu, 4/28/16, Lizette Koehler wrote: Subject: Re: SAVING JOB OUTPUT IN A PDSE FROM SDSF To: IBM-MAIN@LISTSERV.UA.EDU Received: Thursday, April 28, 2016, 7:08 PM When you use XDC and NEW it will indicate if the member already exists. You should try this and see if it works. I find trying SHR, OLD and NEW on a PDS that will not matter if it is over written a good thing to try to understand how things work. Also, you could press PF1 (HELP) and see what the HELP panel states. Lizette > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of willie bunter > Sent: Thursday, April 28, 2016 4:00 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: SAVING JOB OUTPUT IN A PDSE FROM SDSF > > Hallo All, > > I need your suggestions. I am savings job output in a PDSE using SDSF. The > member name I use is the job number e.g. > Member to use ===> JOB067XX > > I am afraid that some where down the line I could overwrite a member because > the job n
Re: SAVING JOB OUTPUT IN A PDSE FROM SDSF
(resend, please be patient if got two copies) W dniu 2016-04-29 o 17:37, R.S. pisze: W dniu 2016-04-29 o 17:31, Paul Gilmartin pisze: On Fri, 29 Apr 2016 11:49:57 +, willie bunter wrote: Paul. I tried out your suggestion using disp=mod however it doesn't work : MOD NOT ALLOWED FOR PDS ??? That deserves an SR. Works in JCL; works everywhere else. The statement is patently false. No, it isn't. MOD is not allowed for *member* od PDS or PDSE. MOD is allowed for PO dataset, i.e. for IEFBR14 MOD,DELETE Try IEBGENER //SYSUT2 DD DSN=HLQ.SOME.PO(MEMBER),DISP=(MOD,CATLG) -- Radoslaw Skorupka Lodz, Poland -- Treść tej wiadomości może zawierać informacje prawnie chronione Banku przeznaczone wyłącznie do użytku służbowego adresata. Odbiorcą może być jedynie jej adresat z wyłączeniem dostępu osób trzecich. Jeżeli nie jesteś adresatem niniejszej wiadomości lub pracownikiem upoważnionym do jej przekazania adresatowi, informujemy, że jej rozpowszechnianie, kopiowanie, rozprowadzanie lub inne działanie o podobnym charakterze jest prawnie zabronione i może być karalne. Jeżeli otrzymałeś tę wiadomość omyłkowo, prosimy niezwłocznie zawiadomić nadawcę wysyłając odpowiedź oraz trwale usunąć tę wiadomość włączając w to wszelkie jej kopie wydrukowane lub zapisane na dysku. This e-mail may contain legally privileged information of the Bank and is intended solely for business use of the addressee. This e-mail may only be received by the addressee and may not be disclosed to any third parties. If you are not the intended addressee of this e-mail or the employee authorized to forward it to the addressee, be advised that any dissemination, copying, distribution or any other similar activity is legally prohibited and may be punishable. If you received this e-mail by mistake please advise the sender immediately by using the reply facility in your e-mail software and delete permanently this e-mail including any copies of it either printed or saved to hard drive. mBank S.A. z siedzibą w Warszawie, ul. Senatorska 18, 00-950 Warszawa, www.mBank.pl, e-mail: kont...@mbank.pl Sąd Rejonowy dla m. st. Warszawy XII Wydział Gospodarczy Krajowego Rejestru Sądowego, nr rejestru przedsiębiorców KRS 025237, NIP: 526-021-50-88. Według stanu na dzień 01.01.2016 r. kapitał zakładowy mBanku S.A. (w całości wpłacony) wynosi 168.955.696 złotych. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: SAVING JOB OUTPUT IN A PDSE FROM SDSF
On Fri, 29 Apr 2016 11:49:57 +, willie bunter wrote: >Paul. > >I tried out your suggestion using disp=mod however it doesn't work : MOD NOT >ALLOWED FOR PDS > ??? That deserves an SR. Works in JCL; works everywhere else. The statement is patently false. -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: SAVING JOB OUTPUT IN A PDSE FROM SDSF
Paul. I tried out your suggestion using disp=mod however it doesn't work : MOD NOT ALLOWED FOR PDS On Thu, 4/28/16, Paul Gilmartin <000433f07816-dmarc-requ...@listserv.ua.edu> wrote: Subject: Re: SAVING JOB OUTPUT IN A PDSE FROM SDSF To: IBM-MAIN@LISTSERV.UA.EDU Received: Thursday, April 28, 2016, 7:12 PM On Thu, 28 Apr 2016 22:59:45 +, willie bunter wrote: > >I need your suggestions. I am savings job output in a PDSE using SDSF. The member name I use is the job number e.g. >Member to use ===> JOB067XX > >I am afraid that some where down the line I could overwrite a member because the job number could be the same. Is there something I could do to prevent this from happening? > If you allocate the PDS with DISP=MOD rather than DISP=OLD, the process will fail rather than overwriting. Recovery is left as an exercise for the student. -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: SAVING JOB OUTPUT IN A PDSE FROM SDSF
Data set name ===> 'ABCDE.FGHIJK.LMNOP' Member to use ===> QRSTUV Disposition===> NEW(OLD, NEW, SHR, MOD) Management class ===> (Blank for default management class) Storage class ===>(Blank for default storage class) Volume serial ===> (Blank for authorized default volume) Device type ===> (Generic unit or device address) Data class ===> (Blank for default data class) Space units ===> CYLS (BLKS, TRKS, CYLS, BY, KB, or MB) Primary quantity ===> 25(In above units) Secondary quantity ===> 5 (In above units) Directory blocks ===> 45(Zero for sequential data set) <= Did you specify directory blanks??? Record format ===> FBA Record length===> 133 Block size ===> Data set name type ===> <=== Do you have this value specified??? Extended attributes ===> (NO, OPT, or blank) -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of willie bunter Sent: Friday, April 29, 2016 7:45 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: SAVING JOB OUTPUT IN A PDSE FROM SDSF Lizette, I tried your suggestion using NEW but it doesn't work. I get the message MEMBER NAME NOT ALLOWED I hit the PF1 option but it wasn't much help. ---------------- On Thu, 4/28/16, Lizette Koehler wrote: Subject: Re: SAVING JOB OUTPUT IN A PDSE FROM SDSF To: IBM-MAIN@LISTSERV.UA.EDU Received: Thursday, April 28, 2016, 7:08 PM When you use XDC and NEW it will indicate if the member already exists. You should try this and see if it works. I find trying SHR, OLD and NEW on a PDS that will not matter if it is over written a good thing to try to understand how things work. Also, you could press PF1 (HELP) and see what the HELP panel states. Lizette > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of willie bunter > Sent: Thursday, April 28, 2016 4:00 PM > To: IBM-MAIN@LISTSERV.UA.EDU > > Subject: SAVING JOB OUTPUT IN A PDSE FROM SDSF > > Hallo All, > > I > need your suggestions. I am savings job output in a PDSE using SDSF. The > > member name I use is the job number e.g. > Member to use ===> JOB067XX > > I am afraid that some where down the line I could overwrite a member because > the job number could be the same. Is there something I could do to prevent > this from happening? > > Below is an example of the screen when I type XDC beside the job: > > Data set name ===> 'SYS2.BATCH.JOBS.OUTPUT > Member to use ===> JOB06703 > Disposition ===> SHR (OLD, NEW, SHR, MOD) > > Thanks in advance. > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: SAVING JOB OUTPUT IN A PDSE FROM SDSF
Lizette, I tried your suggestion using NEW but it doesn't work. I get the message MEMBER NAME NOT ALLOWED I hit the PF1 option but it wasn't much help. On Thu, 4/28/16, Lizette Koehler wrote: Subject: Re: SAVING JOB OUTPUT IN A PDSE FROM SDSF To: IBM-MAIN@LISTSERV.UA.EDU Received: Thursday, April 28, 2016, 7:08 PM When you use XDC and NEW it will indicate if the member already exists. You should try this and see if it works. I find trying SHR, OLD and NEW on a PDS that will not matter if it is over written a good thing to try to understand how things work. Also, you could press PF1 (HELP) and see what the HELP panel states. Lizette > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of willie bunter > Sent: Thursday, April 28, 2016 4:00 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: SAVING JOB OUTPUT IN A PDSE FROM SDSF > > Hallo All, > > I need your suggestions. I am savings job output in a PDSE using SDSF. The > member name I use is the job number e.g. > Member to use ===> JOB067XX > > I am afraid that some where down the line I could overwrite a member because > the job number could be the same. Is there something I could do to prevent > this from happening? > > Below is an example of the screen when I type XDC beside the job: > > Data set name ===> 'SYS2.BATCH.JOBS.OUTPUT > Member to use ===> JOB06703 > Disposition ===> SHR (OLD, NEW, SHR, MOD) > > Thanks in advance. > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: SAVING JOB OUTPUT IN A PDSE FROM SDSF
No, you cannot prevent it. Been there... -- Radoslaw Skorupka Lodz, Poland W dniu 2016-04-29 o 00:59, willie bunter pisze: Hallo All, I need your suggestions. I am savings job output in a PDSE using SDSF. The member name I use is the job number e.g. Member to use ===> JOB067XX I am afraid that some where down the line I could overwrite a member because the job number could be the same. Is there something I could do to prevent this from happening? Below is an example of the screen when I type XDC beside the job: Data set name ===> 'SYS2.BATCH.JOBS.OUTPUT Member to use ===> JOB06703 Disposition===> SHR(OLD, NEW, SHR, MOD) Thanks in advance. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- Treść tej wiadomości może zawierać informacje prawnie chronione Banku przeznaczone wyłącznie do użytku służbowego adresata. Odbiorcą może być jedynie jej adresat z wyłączeniem dostępu osób trzecich. Jeżeli nie jesteś adresatem niniejszej wiadomości lub pracownikiem upoważnionym do jej przekazania adresatowi, informujemy, że jej rozpowszechnianie, kopiowanie, rozprowadzanie lub inne działanie o podobnym charakterze jest prawnie zabronione i może być karalne. Jeżeli otrzymałeś tę wiadomość omyłkowo, prosimy niezwłocznie zawiadomić nadawcę wysyłając odpowiedź oraz trwale usunąć tę wiadomość włączając w to wszelkie jej kopie wydrukowane lub zapisane na dysku. This e-mail may contain legally privileged information of the Bank and is intended solely for business use of the addressee. This e-mail may only be received by the addressee and may not be disclosed to any third parties. If you are not the intended addressee of this e-mail or the employee authorized to forward it to the addressee, be advised that any dissemination, copying, distribution or any other similar activity is legally prohibited and may be punishable. If you received this e-mail by mistake please advise the sender immediately by using the reply facility in your e-mail software and delete permanently this e-mail including any copies of it either printed or saved to hard drive. mBank S.A. z siedzibą w Warszawie, ul. Senatorska 18, 00-950 Warszawa, www.mBank.pl, e-mail: kont...@mbank.pl Sąd Rejonowy dla m. st. Warszawy XII Wydział Gospodarczy Krajowego Rejestru Sądowego, nr rejestru przedsiębiorców KRS 025237, NIP: 526-021-50-88. Według stanu na dzień 01.01.2016 r. kapitał zakładowy mBanku S.A. (w całości wpłacony) wynosi 168.955.696 złotych. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: SAVING JOB OUTPUT IN A PDSE FROM SDSF
On Thu, 28 Apr 2016 22:59:45 +, willie bunter wrote: > >I need your suggestions. I am savings job output in a PDSE using SDSF. The >member name I use is the job number e.g. >Member to use ===> JOB067XX > >I am afraid that some where down the line I could overwrite a member because >the job number could be the same. Is there something I could do to prevent >this from happening? > If you allocate the PDS with DISP=MOD rather than DISP=OLD, the process will fail rather than overwriting. Recovery is left as an exercise for the student. -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: SAVING JOB OUTPUT IN A PDSE FROM SDSF
When you use XDC and NEW it will indicate if the member already exists. You should try this and see if it works. I find trying SHR, OLD and NEW on a PDS that will not matter if it is over written a good thing to try to understand how things work. Also, you could press PF1 (HELP) and see what the HELP panel states. Lizette > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of willie bunter > Sent: Thursday, April 28, 2016 4:00 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: SAVING JOB OUTPUT IN A PDSE FROM SDSF > > Hallo All, > > I need your suggestions. I am savings job output in a PDSE using SDSF. The > member name I use is the job number e.g. > Member to use ===> JOB067XX > > I am afraid that some where down the line I could overwrite a member because > the job number could be the same. Is there something I could do to prevent > this from happening? > > Below is an example of the screen when I type XDC beside the job: > > Data set name ===> 'SYS2.BATCH.JOBS.OUTPUT > Member to use ===> JOB06703 > Disposition===> SHR(OLD, NEW, SHR, MOD) > > Thanks in advance. > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
