Re: Useful little utility?
A quick FYI, SDSF has the "PARM" (2.1+) and "PROC" (2.2+) commands that display the PARMLIB and JES2 PROCLIB concatenations. You can search for a member name mask in the displayed list and then use NP actions to access the matching members. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of John McKown Sent: Monday, November 20, 2017 5:11 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Useful little utility? This is a small ISPF based utility. I call it SYSPARM because it brings up a ISPF option 3.4 like DSN list which contains the system PARMLIB concatenation. It might be a nice way to find out where a specific PARMLIB member is: e.g. Where is TSOKEY27?? It is 140 lines of HLASM code. I wrote in on z/OS 1.12 and tested it on a 2.3 system as well. Basically it uses IEFPRMLB REQUEST=ALLOCATE to allocate the system PARMLIB and then does an ISRDDN ONLY to display that allocation. ref: https://github.com/JohnArchieMckown/miscutil/blob/master/SYSPARM -- I have a theory that it's impossible to prove anything, but I can't prove it. Maranatha! <>< John McKown -- 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 877.328.2932 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: Useful little utility?
DDLIST (ISRDDN) has this capability out of the box Just type PARMLIB to add the logical parmlib concatenation to your display. You can then issue O(nly) PARMLIB command followed by M(ember) xxx. Andrew -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Useful little utility?
On Tue, Nov 21, 2017 at 5:41 AM, Andrew Metcalfe < 0149a256c9e8-dmarc-requ...@listserv.ua.edu> wrote: > DDLIST (ISRDDN) has this capability out of the box > Just type PARMLIB to add the logical parmlib concatenation to your display. > You can then issue O(nly) PARMLIB command followed by M(ember) xxx. > > Andrew > > Thanks. I knew about the LINKLIST command, but had never noticed the PARMLIB command. Oh, well, another one bites the dust. -- I have a theory that it's impossible to prove anything, but I can't prove it. 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: ECVTDUCU & "trap" condition in z/OS
There is no additional documentation and there are no other references because there is no particular need for there to be. If you are using the trap instructions then you know (or need to know) about the trap control block and that the trap instructions architecture requires you to provide information controlling the traps within the dispatchable unit control table (DUCT). This pointer (and the service behind it) was created so that individual trap exploiters would not code these updates themselves because they were more likely to get it wrong than z/OS development is and were more likely not to be in a position to react to architectural changes (such as happened when z/Architecture was introduced) than z/OS development is. Peter Relson z/OS Core Technology Design -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: ECVTDUCU & "trap" condition in z/OS
On Tue, Nov 21, 2017 at 6:55 AM, Peter Relson wrote: > There is no additional documentation and there are no other references > because there is no particular need for there to be. > > If you are using the trap instructions then you know (or need to know) > about the trap control block and that the trap instructions architecture > requires you to provide information controlling the traps within the > dispatchable unit control table (DUCT). This pointer (and the service > behind it) was created so that individual trap exploiters would not code > these updates themselves because they were more likely to get it wrong > than z/OS development is and were more likely not to be in a position to > react to architectural changes (such as happened when z/Architecture was > introduced) than z/OS development is. > > Peter Relson > z/OS Core Technology Design > So, it is GUPI. But it is not going to be documented in a manual such as "Authorized Assembler Services Guide". IOW, as the preacher said in "Blazing Saddles", "Son, you're on your own!" -- I have a theory that it's impossible to prove anything, but I can't prove it. 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: Useful little utility?
John, I wonder how many of us missed that little improvement. I use ISRDDN enough times per day that I created a command table entry for it so that I only have to type DDN from anywhere. I just checked the new PARM command in SDSF. If you are using SYSNAME *, it will search for a member (masking acceptable) in every parmlib dataset listed. I did not see the capability to search for a string from that display, unless I missed it in my quick read of the tutorial . Still, that member search can be very powerful in its own right, especially in shops with tons of lpars. Bob -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of John McKown Sent: Tuesday, November 21, 2017 7:30 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Useful little utility? On Tue, Nov 21, 2017 at 5:41 AM, Andrew Metcalfe < 0149a256c9e8-dmarc-requ...@listserv.ua.edu> wrote: > DDLIST (ISRDDN) has this capability out of the box Just type PARMLIB > to add the logical parmlib concatenation to your display. > You can then issue O(nly) PARMLIB command followed by M(ember) xxx. > > Andrew > > Thanks. I knew about the LINKLIST command, but had never noticed the PARMLIB command. Oh, well, another one bites the dust. -- I have a theory that it's impossible to prove anything, but I can't prove it. Maranatha! <>< John McKown -- 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
Small SMP utility for USS (was "Include FMID, PTFID and APARID as eye catcher in each LMOD")
I've written a little Unix command that uses the SMP/E query API to dig information out of the CSI. The output is not especially human-friendly; it's intended for processing by scripts. You can get it from github: https://github.com/zorts/smpapi -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Useful little utility?
My wish for ISRDDN would be to be able to toggle on/off sysplex-wide ENQ data for STAR mode GRS configuration. ISRDDN ENQ pulls up a TASID-like panel, but there is no way to make it display global enqueues that I can see. All I get is a LIMITED ENQ DATA in the upper right corner, and extended help says: This system is running with SETGRS MODE=STAR. ENQ information will not be collected from other systems. As a result, ENQ displays may not reflect all of the ENQs which are known to GRS. _ Dave Jousma Manager Mainframe Engineering, Assistant Vice President david.jou...@53.com 1830 East Paris, Grand Rapids, MI 49546 MD RSCB2H p 616.653.8429 f 616.653.2717 -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Richards, Robert B. Sent: Tuesday, November 21, 2017 8:27 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Useful little utility? **CAUTION EXTERNAL EMAIL** **DO NOT open attachments or click on links from unknown senders or unexpected emails** John, I wonder how many of us missed that little improvement. I use ISRDDN enough times per day that I created a command table entry for it so that I only have to type DDN from anywhere. I just checked the new PARM command in SDSF. If you are using SYSNAME *, it will search for a member (masking acceptable) in every parmlib dataset listed. I did not see the capability to search for a string from that display, unless I missed it in my quick read of the tutorial . Still, that member search can be very powerful in its own right, especially in shops with tons of lpars. Bob -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of John McKown Sent: Tuesday, November 21, 2017 7:30 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Useful little utility? On Tue, Nov 21, 2017 at 5:41 AM, Andrew Metcalfe < 0149a256c9e8-dmarc-requ...@listserv.ua.edu> wrote: > DDLIST (ISRDDN) has this capability out of the box Just type PARMLIB > to add the logical parmlib concatenation to your display. > You can then issue O(nly) PARMLIB command followed by M(ember) xxx. > > Andrew > > Thanks. I knew about the LINKLIST command, but had never noticed the PARMLIB command. Oh, well, another one bites the dust. -- I have a theory that it's impossible to prove anything, but I can't prove it. Maranatha! <>< John McKown -- 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 **CAUTION EXTERNAL EMAIL** **DO NOT open attachments or click on links from unknown senders or unexpected emails** This e-mail transmission contains information that is confidential and may be privileged. It is intended only for the addressee(s) named above. If you receive this e-mail in error, please do not read, copy or disseminate it in any manner. If you are not the intended recipient, any disclosure, copying, distribution or use of the contents of this information is prohibited. Please reply to the message immediately by informing the sender that the message was misdirected. After replying, please erase it from your computer system. Your assistance in correcting this error is appreciated. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Useful little utility?
Check out the new "ENQ" command in SDSF (2.1+) as it supports sysplex-wide ENQ information display. Note that you can also do an "N" action in the "NP" column on the DA panel to show enqueues for the ASID only. Rob Scott -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Jousma, David Sent: Tuesday, November 21, 2017 2:03 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Useful little utility? My wish for ISRDDN would be to be able to toggle on/off sysplex-wide ENQ data for STAR mode GRS configuration. ISRDDN ENQ pulls up a TASID-like panel, but there is no way to make it display global enqueues that I can see. All I get is a LIMITED ENQ DATA in the upper right corner, and extended help says: This system is running with SETGRS MODE=STAR. ENQ information will not be collected from other systems. As a result, ENQ displays may not reflect all of the ENQs which are known to GRS. _ Dave Jousma Manager Mainframe Engineering, Assistant Vice President david.jou...@53.com 1830 East Paris, Grand Rapids, MI 49546 MD RSCB2H p 616.653.8429 f 616.653.2717 -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Richards, Robert B. Sent: Tuesday, November 21, 2017 8:27 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Useful little utility? **CAUTION EXTERNAL EMAIL** **DO NOT open attachments or click on links from unknown senders or unexpected emails** John, I wonder how many of us missed that little improvement. I use ISRDDN enough times per day that I created a command table entry for it so that I only have to type DDN from anywhere. I just checked the new PARM command in SDSF. If you are using SYSNAME *, it will search for a member (masking acceptable) in every parmlib dataset listed. I did not see the capability to search for a string from that display, unless I missed it in my quick read of the tutorial . Still, that member search can be very powerful in its own right, especially in shops with tons of lpars. Bob -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of John McKown Sent: Tuesday, November 21, 2017 7:30 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Useful little utility? On Tue, Nov 21, 2017 at 5:41 AM, Andrew Metcalfe < 0149a256c9e8-dmarc-requ...@listserv.ua.edu> wrote: > DDLIST (ISRDDN) has this capability out of the box Just type PARMLIB > to add the logical parmlib concatenation to your display. > You can then issue O(nly) PARMLIB command followed by M(ember) xxx. > > Andrew > > Thanks. I knew about the LINKLIST command, but had never noticed the PARMLIB command. Oh, well, another one bites the dust. -- I have a theory that it's impossible to prove anything, but I can't prove it. Maranatha! <>< John McKown -- 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 **CAUTION EXTERNAL EMAIL** **DO NOT open attachments or click on links from unknown senders or unexpected emails** This e-mail transmission contains information that is confidential and may be privileged. It is intended only for the addressee(s) named above. If you receive this e-mail in error, please do not read, copy or disseminate it in any manner. If you are not the intended recipient, any disclosure, copying, distribution or use of the contents of this information is prohibited. Please reply to the message immediately by informing the sender that the message was misdirected. After replying, please erase it from your computer system. Your assistance in correcting this error is appreciated. -- 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 877.328.2932 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 Softwa
Re: Useful little utility?
For this, MXI ENQ is your friend. Thanks Rob! -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Jousma, David Sent: Tuesday, November 21, 2017 9:03 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Useful little utility? My wish for ISRDDN would be to be able to toggle on/off sysplex-wide ENQ data for STAR mode GRS configuration. ISRDDN ENQ pulls up a TASID-like panel, but there is no way to make it display global enqueues that I can see. All I get is a LIMITED ENQ DATA in the upper right corner, and extended help says: This system is running with SETGRS MODE=STAR. ENQ information will not be collected from other systems. As a result, ENQ displays may not reflect all of the ENQs which are known to GRS. _ Dave Jousma Manager Mainframe Engineering, Assistant Vice President david.jou...@53.com 1830 East Paris, Grand Rapids, MI 49546 MD RSCB2H p 616.653.8429 f 616.653.2717 -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Richards, Robert B. Sent: Tuesday, November 21, 2017 8:27 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Useful little utility? **CAUTION EXTERNAL EMAIL** **DO NOT open attachments or click on links from unknown senders or unexpected emails** John, I wonder how many of us missed that little improvement. I use ISRDDN enough times per day that I created a command table entry for it so that I only have to type DDN from anywhere. I just checked the new PARM command in SDSF. If you are using SYSNAME *, it will search for a member (masking acceptable) in every parmlib dataset listed. I did not see the capability to search for a string from that display, unless I missed it in my quick read of the tutorial . Still, that member search can be very powerful in its own right, especially in shops with tons of lpars. Bob -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of John McKown Sent: Tuesday, November 21, 2017 7:30 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Useful little utility? On Tue, Nov 21, 2017 at 5:41 AM, Andrew Metcalfe < 0149a256c9e8-dmarc-requ...@listserv.ua.edu> wrote: > DDLIST (ISRDDN) has this capability out of the box Just type PARMLIB > to add the logical parmlib concatenation to your display. > You can then issue O(nly) PARMLIB command followed by M(ember) xxx. > > Andrew > > Thanks. I knew about the LINKLIST command, but had never noticed the PARMLIB command. Oh, well, another one bites the dust. -- I have a theory that it's impossible to prove anything, but I can't prove it. Maranatha! <>< John McKown -- 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 **CAUTION EXTERNAL EMAIL** **DO NOT open attachments or click on links from unknown senders or unexpected emails** This e-mail transmission contains information that is confidential and may be privileged. It is intended only for the addressee(s) named above. If you receive this e-mail in error, please do not read, copy or disseminate it in any manner. If you are not the intended recipient, any disclosure, copying, distribution or use of the contents of this information is prohibited. Please reply to the message immediately by informing the sender that the message was misdirected. After replying, please erase it from your computer system. Your assistance in correcting this error is appreciated. -- 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: Useful little utility?
Rob, I've been playing with that too. ENQC is nice, shows plex-wide enq contention, ENQ not so much, kludgy IMO. By default ENQ is single system, and to enable all systems, you have to also specify major name. So ENQ SYSDSN * to get all systems in the plex. No way to pass any kind of filter on the major name, so you get (in my case, a list of 268K entries back) all data set names. Which you can then use a filter or find commands against, but why on earth no short cut? ENQC is easy enough that my operations staff can use it to see who is holding up a production batch job. However on occasion, they want to just "look up" a dataset to see if anyone is using it at that moment. I realize there are methods via ISPF 3.4, etc, or just issue the D GRS,RES=(SYSDSN,'DATA.SET.NAME') As for the "N", I've tried that too. I don’t know if something is wrong, but when I use that, it takes a good 15 seconds for the display to come back, and then its scope is only that single system. Once that list is produced, and you issue a "D" next to the dataset to display all enqueues, another 15 seconds, and even that display is single system. _ Dave Jousma Manager Mainframe Engineering, Assistant Vice President david.jou...@53.com 1830 East Paris, Grand Rapids, MI 49546 MD RSCB2H p 616.653.8429 f 616.653.2717 -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Rob Scott Sent: Tuesday, November 21, 2017 9:28 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Useful little utility? **CAUTION EXTERNAL EMAIL** **DO NOT open attachments or click on links from unknown senders or unexpected emails** Check out the new "ENQ" command in SDSF (2.1+) as it supports sysplex-wide ENQ information display. Note that you can also do an "N" action in the "NP" column on the DA panel to show enqueues for the ASID only. Rob Scott -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Jousma, David Sent: Tuesday, November 21, 2017 2:03 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Useful little utility? My wish for ISRDDN would be to be able to toggle on/off sysplex-wide ENQ data for STAR mode GRS configuration. ISRDDN ENQ pulls up a TASID-like panel, but there is no way to make it display global enqueues that I can see. All I get is a LIMITED ENQ DATA in the upper right corner, and extended help says: This system is running with SETGRS MODE=STAR. ENQ information will not be collected from other systems. As a result, ENQ displays may not reflect all of the ENQs which are known to GRS. _ Dave Jousma Manager Mainframe Engineering, Assistant Vice President david.jou...@53.com 1830 East Paris, Grand Rapids, MI 49546 MD RSCB2H p 616.653.8429 f 616.653.2717 -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Richards, Robert B. Sent: Tuesday, November 21, 2017 8:27 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Useful little utility? **CAUTION EXTERNAL EMAIL** **DO NOT open attachments or click on links from unknown senders or unexpected emails** John, I wonder how many of us missed that little improvement. I use ISRDDN enough times per day that I created a command table entry for it so that I only have to type DDN from anywhere. I just checked the new PARM command in SDSF. If you are using SYSNAME *, it will search for a member (masking acceptable) in every parmlib dataset listed. I did not see the capability to search for a string from that display, unless I missed it in my quick read of the tutorial . Still, that member search can be very powerful in its own right, especially in shops with tons of lpars. Bob -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of John McKown Sent: Tuesday, November 21, 2017 7:30 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Useful little utility? On Tue, Nov 21, 2017 at 5:41 AM, Andrew Metcalfe < 0149a256c9e8-dmarc-requ...@listserv.ua.edu> wrote: > DDLIST (ISRDDN) has this capability out of the box Just type PARMLIB > to add the logical parmlib concatenation to your display. > You can then issue O(nly) PARMLIB command followed by M(ember) xxx. > > Andrew > > Thanks. I knew about the LINKLIST command, but had never noticed the PARMLIB command. Oh, well, another one bites the dust. -- I have a theory that it's impossible to prove anything, but I can't prove it. Maranatha! <>< John McKown -- 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 /
Re: Useful little utility?
I like MXI, but in my shop shareware is not to be used outside of our own group. Same with TASID. _ Dave Jousma Manager Mainframe Engineering, Assistant Vice President david.jou...@53.com 1830 East Paris, Grand Rapids, MI 49546 MD RSCB2H p 616.653.8429 f 616.653.2717 -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Richards, Robert B. Sent: Tuesday, November 21, 2017 9:28 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Useful little utility? **CAUTION EXTERNAL EMAIL** **DO NOT open attachments or click on links from unknown senders or unexpected emails** For this, MXI ENQ is your friend. Thanks Rob! -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Jousma, David Sent: Tuesday, November 21, 2017 9:03 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Useful little utility? My wish for ISRDDN would be to be able to toggle on/off sysplex-wide ENQ data for STAR mode GRS configuration. ISRDDN ENQ pulls up a TASID-like panel, but there is no way to make it display global enqueues that I can see. All I get is a LIMITED ENQ DATA in the upper right corner, and extended help says: This system is running with SETGRS MODE=STAR. ENQ information will not be collected from other systems. As a result, ENQ displays may not reflect all of the ENQs which are known to GRS. _ Dave Jousma Manager Mainframe Engineering, Assistant Vice President david.jou...@53.com 1830 East Paris, Grand Rapids, MI 49546 MD RSCB2H p 616.653.8429 f 616.653.2717 -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Richards, Robert B. Sent: Tuesday, November 21, 2017 8:27 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Useful little utility? **CAUTION EXTERNAL EMAIL** **DO NOT open attachments or click on links from unknown senders or unexpected emails** John, I wonder how many of us missed that little improvement. I use ISRDDN enough times per day that I created a command table entry for it so that I only have to type DDN from anywhere. I just checked the new PARM command in SDSF. If you are using SYSNAME *, it will search for a member (masking acceptable) in every parmlib dataset listed. I did not see the capability to search for a string from that display, unless I missed it in my quick read of the tutorial . Still, that member search can be very powerful in its own right, especially in shops with tons of lpars. Bob -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of John McKown Sent: Tuesday, November 21, 2017 7:30 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Useful little utility? On Tue, Nov 21, 2017 at 5:41 AM, Andrew Metcalfe < 0149a256c9e8-dmarc-requ...@listserv.ua.edu> wrote: > DDLIST (ISRDDN) has this capability out of the box Just type PARMLIB > to add the logical parmlib concatenation to your display. > You can then issue O(nly) PARMLIB command followed by M(ember) xxx. > > Andrew > > Thanks. I knew about the LINKLIST command, but had never noticed the PARMLIB command. Oh, well, another one bites the dust. -- I have a theory that it's impossible to prove anything, but I can't prove it. Maranatha! <>< John McKown -- 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 **CAUTION EXTERNAL EMAIL** **DO NOT open attachments or click on links from unknown senders or unexpected emails** This e-mail transmission contains information that is confidential and may be privileged. It is intended only for the addressee(s) named above. If you receive this e-mail in error, please do not read, copy or disseminate it in any manner. If you are not the intended recipient, any disclosure, copying, distribution or use of the contents of this information is prohibited. Please reply to the message immediately by informing the sender that the message was misdirected. After replying, please erase it from your computer system. Your assistance in correcting this error is appreciated. -- 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...@li
Re: Useful little utility?
I am sure Rob would be willing to sell you the non-shareware version marketed by Rocket Software. :-) -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Jousma, David Sent: Tuesday, November 21, 2017 9:49 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Useful little utility? I like MXI, but in my shop shareware is not to be used outside of our own group. Same with TASID. _ Dave Jousma Manager Mainframe Engineering, Assistant Vice President david.jou...@53.com 1830 East Paris, Grand Rapids, MI 49546 MD RSCB2H p 616.653.8429 f 616.653.2717 -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Richards, Robert B. Sent: Tuesday, November 21, 2017 9:28 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Useful little utility? **CAUTION EXTERNAL EMAIL** **DO NOT open attachments or click on links from unknown senders or unexpected emails** For this, MXI ENQ is your friend. Thanks Rob! -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Jousma, David Sent: Tuesday, November 21, 2017 9:03 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Useful little utility? My wish for ISRDDN would be to be able to toggle on/off sysplex-wide ENQ data for STAR mode GRS configuration. ISRDDN ENQ pulls up a TASID-like panel, but there is no way to make it display global enqueues that I can see. All I get is a LIMITED ENQ DATA in the upper right corner, and extended help says: This system is running with SETGRS MODE=STAR. ENQ information will not be collected from other systems. As a result, ENQ displays may not reflect all of the ENQs which are known to GRS. _ Dave Jousma Manager Mainframe Engineering, Assistant Vice President david.jou...@53.com 1830 East Paris, Grand Rapids, MI 49546 MD RSCB2H p 616.653.8429 f 616.653.2717 -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Richards, Robert B. Sent: Tuesday, November 21, 2017 8:27 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Useful little utility? **CAUTION EXTERNAL EMAIL** **DO NOT open attachments or click on links from unknown senders or unexpected emails** John, I wonder how many of us missed that little improvement. I use ISRDDN enough times per day that I created a command table entry for it so that I only have to type DDN from anywhere. I just checked the new PARM command in SDSF. If you are using SYSNAME *, it will search for a member (masking acceptable) in every parmlib dataset listed. I did not see the capability to search for a string from that display, unless I missed it in my quick read of the tutorial . Still, that member search can be very powerful in its own right, especially in shops with tons of lpars. Bob -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of John McKown Sent: Tuesday, November 21, 2017 7:30 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Useful little utility? On Tue, Nov 21, 2017 at 5:41 AM, Andrew Metcalfe < 0149a256c9e8-dmarc-requ...@listserv.ua.edu> wrote: > DDLIST (ISRDDN) has this capability out of the box Just type PARMLIB > to add the logical parmlib concatenation to your display. > You can then issue O(nly) PARMLIB command followed by M(ember) xxx. > > Andrew > > Thanks. I knew about the LINKLIST command, but had never noticed the PARMLIB command. Oh, well, another one bites the dust. -- I have a theory that it's impossible to prove anything, but I can't prove it. Maranatha! <>< John McKown -- 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 **CAUTION EXTERNAL EMAIL** **DO NOT open attachments or click on links from unknown senders or unexpected emails** This e-mail transmission contains information that is confidential and may be privileged. It is intended only for the addressee(s) named above. If you receive this e-mail in error, please do not read, copy or disseminate it in any manner. If you are not the intended recipient, any disclosure, copying, distribution or use of the contents of this information is prohibited. Please reply to the message immediately by informing the sender that the message was misdirected. After replying, please erase it from your computer system. Your assistance in correcting this error is appreciated. -
Re: Useful little utility?
Well, there is that... :) _ Dave Jousma Manager Mainframe Engineering, Assistant Vice President david.jou...@53.com 1830 East Paris, Grand Rapids, MI 49546 MD RSCB2H p 616.653.8429 f 616.653.2717 -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Richards, Robert B. Sent: Tuesday, November 21, 2017 9:55 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Useful little utility? **CAUTION EXTERNAL EMAIL** **DO NOT open attachments or click on links from unknown senders or unexpected emails** I am sure Rob would be willing to sell you the non-shareware version marketed by Rocket Software. :-) -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Jousma, David Sent: Tuesday, November 21, 2017 9:49 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Useful little utility? I like MXI, but in my shop shareware is not to be used outside of our own group. Same with TASID. _ Dave Jousma Manager Mainframe Engineering, Assistant Vice President david.jou...@53.com 1830 East Paris, Grand Rapids, MI 49546 MD RSCB2H p 616.653.8429 f 616.653.2717 -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Richards, Robert B. Sent: Tuesday, November 21, 2017 9:28 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Useful little utility? **CAUTION EXTERNAL EMAIL** **DO NOT open attachments or click on links from unknown senders or unexpected emails** For this, MXI ENQ is your friend. Thanks Rob! -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Jousma, David Sent: Tuesday, November 21, 2017 9:03 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Useful little utility? My wish for ISRDDN would be to be able to toggle on/off sysplex-wide ENQ data for STAR mode GRS configuration. ISRDDN ENQ pulls up a TASID-like panel, but there is no way to make it display global enqueues that I can see. All I get is a LIMITED ENQ DATA in the upper right corner, and extended help says: This system is running with SETGRS MODE=STAR. ENQ information will not be collected from other systems. As a result, ENQ displays may not reflect all of the ENQs which are known to GRS. _ Dave Jousma Manager Mainframe Engineering, Assistant Vice President david.jou...@53.com 1830 East Paris, Grand Rapids, MI 49546 MD RSCB2H p 616.653.8429 f 616.653.2717 -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Richards, Robert B. Sent: Tuesday, November 21, 2017 8:27 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Useful little utility? **CAUTION EXTERNAL EMAIL** **DO NOT open attachments or click on links from unknown senders or unexpected emails** John, I wonder how many of us missed that little improvement. I use ISRDDN enough times per day that I created a command table entry for it so that I only have to type DDN from anywhere. I just checked the new PARM command in SDSF. If you are using SYSNAME *, it will search for a member (masking acceptable) in every parmlib dataset listed. I did not see the capability to search for a string from that display, unless I missed it in my quick read of the tutorial . Still, that member search can be very powerful in its own right, especially in shops with tons of lpars. Bob -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of John McKown Sent: Tuesday, November 21, 2017 7:30 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Useful little utility? On Tue, Nov 21, 2017 at 5:41 AM, Andrew Metcalfe < 0149a256c9e8-dmarc-requ...@listserv.ua.edu> wrote: > DDLIST (ISRDDN) has this capability out of the box Just type PARMLIB > to add the logical parmlib concatenation to your display. > You can then issue O(nly) PARMLIB command followed by M(ember) xxx. > > Andrew > > Thanks. I knew about the LINKLIST command, but had never noticed the PARMLIB command. Oh, well, another one bites the dust. -- I have a theory that it's impossible to prove anything, but I can't prove it. Maranatha! <>< John McKown -- 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 **CAUTION EXTERNAL EMAIL** **DO NOT open attachments or click on links from unknown senders or unexpected emails** This e-mail
Re: Useful little utility?
"Scotty, I need more power!" :-) On my zEC12 system with three logical CPs, observably less than a second. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Jousma, David Sent: Tuesday, November 21, 2017 9:47 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Useful little utility? Rob, I've been playing with that too. ENQC is nice, shows plex-wide enq contention, ENQ not so much, kludgy IMO. By default ENQ is single system, and to enable all systems, you have to also specify major name. So ENQ SYSDSN * to get all systems in the plex. No way to pass any kind of filter on the major name, so you get (in my case, a list of 268K entries back) all data set names. Which you can then use a filter or find commands against, but why on earth no short cut? ENQC is easy enough that my operations staff can use it to see who is holding up a production batch job. However on occasion, they want to just "look up" a dataset to see if anyone is using it at that moment. I realize there are methods via ISPF 3.4, etc, or just issue the D GRS,RES=(SYSDSN,'DATA.SET.NAME') As for the "N", I've tried that too. I don’t know if something is wrong, but when I use that, it takes a good 15 seconds for the display to come back, and then its scope is only that single system. Once that list is produced, and you issue a "D" next to the dataset to display all enqueues, another 15 seconds, and even that display is single system. _ Dave Jousma Manager Mainframe Engineering, Assistant Vice President david.jou...@53.com 1830 East Paris, Grand Rapids, MI 49546 MD RSCB2H p 616.653.8429 f 616.653.2717 -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Rob Scott Sent: Tuesday, November 21, 2017 9:28 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Useful little utility? **CAUTION EXTERNAL EMAIL** **DO NOT open attachments or click on links from unknown senders or unexpected emails** Check out the new "ENQ" command in SDSF (2.1+) as it supports sysplex-wide ENQ information display. Note that you can also do an "N" action in the "NP" column on the DA panel to show enqueues for the ASID only. Rob Scott -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Jousma, David Sent: Tuesday, November 21, 2017 2:03 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Useful little utility? My wish for ISRDDN would be to be able to toggle on/off sysplex-wide ENQ data for STAR mode GRS configuration. ISRDDN ENQ pulls up a TASID-like panel, but there is no way to make it display global enqueues that I can see. All I get is a LIMITED ENQ DATA in the upper right corner, and extended help says: This system is running with SETGRS MODE=STAR. ENQ information will not be collected from other systems. As a result, ENQ displays may not reflect all of the ENQs which are known to GRS. _ Dave Jousma Manager Mainframe Engineering, Assistant Vice President david.jou...@53.com 1830 East Paris, Grand Rapids, MI 49546 MD RSCB2H p 616.653.8429 f 616.653.2717 -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Richards, Robert B. Sent: Tuesday, November 21, 2017 8:27 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Useful little utility? **CAUTION EXTERNAL EMAIL** **DO NOT open attachments or click on links from unknown senders or unexpected emails** John, I wonder how many of us missed that little improvement. I use ISRDDN enough times per day that I created a command table entry for it so that I only have to type DDN from anywhere. I just checked the new PARM command in SDSF. If you are using SYSNAME *, it will search for a member (masking acceptable) in every parmlib dataset listed. I did not see the capability to search for a string from that display, unless I missed it in my quick read of the tutorial . Still, that member search can be very powerful in its own right, especially in shops with tons of lpars. Bob -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of John McKown Sent: Tuesday, November 21, 2017 7:30 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Useful little utility? On Tue, Nov 21, 2017 at 5:41 AM, Andrew Metcalfe < 0149a256c9e8-dmarc-requ...@listserv.ua.edu> wrote: > DDLIST (ISRDDN) has this capability out of the box Just type PARMLIB > to add the logical parmlib concatenation to your display. > You can then issue O(nly) PARMLIB command followed by M(ember) xxx. > > Andrew > > Thanks. I knew about the LINKLIST command, but had never noticed the PARMLIB command. Oh, well, another one bites the dust. -- I have a theory that it's impossible to prove anything, but I can't prove it.
Re: Useful little utility?
Dave, SDSF primary command syntax is a bit clunky as it has to support "the way it has always worked" and every parameter is positional rather than a more modern "keyword(value)" or "keyword=value" format. I have the ear of the current SDSF development team and perhaps they can provide something like a "ENQD dsname_pattern" command that would prime the major name with "SYSDSN", the SYSNAME with "*" and then filter the minor names by the specified pattern. Let me know if this sounds like something you would like. As for the response time of the "N" and "D" line commands, that very much sounds like something to do with your GRS configuration - perhaps raise a PMR with IBM to investigate if you believe that this is not a simple case of lack of CPU power? Rob Scott -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Jousma, David Sent: Tuesday, November 21, 2017 2:47 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Useful little utility? Rob, I've been playing with that too. ENQC is nice, shows plex-wide enq contention, ENQ not so much, kludgy IMO. By default ENQ is single system, and to enable all systems, you have to also specify major name. So ENQ SYSDSN * to get all systems in the plex. No way to pass any kind of filter on the major name, so you get (in my case, a list of 268K entries back) all data set names. Which you can then use a filter or find commands against, but why on earth no short cut? ENQC is easy enough that my operations staff can use it to see who is holding up a production batch job. However on occasion, they want to just "look up" a dataset to see if anyone is using it at that moment. I realize there are methods via ISPF 3.4, etc, or just issue the D GRS,RES=(SYSDSN,'DATA.SET.NAME') As for the "N", I've tried that too. I don’t know if something is wrong, but when I use that, it takes a good 15 seconds for the display to come back, and then its scope is only that single system. Once that list is produced, and you issue a "D" next to the dataset to display all enqueues, another 15 seconds, and even that display is single system. _ Dave Jousma Manager Mainframe Engineering, Assistant Vice President david.jou...@53.com 1830 East Paris, Grand Rapids, MI 49546 MD RSCB2H p 616.653.8429 f 616.653.2717 -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Rob Scott Sent: Tuesday, November 21, 2017 9:28 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Useful little utility? **CAUTION EXTERNAL EMAIL** **DO NOT open attachments or click on links from unknown senders or unexpected emails** Check out the new "ENQ" command in SDSF (2.1+) as it supports sysplex-wide ENQ information display. Note that you can also do an "N" action in the "NP" column on the DA panel to show enqueues for the ASID only. Rob Scott -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Jousma, David Sent: Tuesday, November 21, 2017 2:03 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Useful little utility? My wish for ISRDDN would be to be able to toggle on/off sysplex-wide ENQ data for STAR mode GRS configuration. ISRDDN ENQ pulls up a TASID-like panel, but there is no way to make it display global enqueues that I can see. All I get is a LIMITED ENQ DATA in the upper right corner, and extended help says: This system is running with SETGRS MODE=STAR. ENQ information will not be collected from other systems. As a result, ENQ displays may not reflect all of the ENQs which are known to GRS. _ Dave Jousma Manager Mainframe Engineering, Assistant Vice President david.jou...@53.com 1830 East Paris, Grand Rapids, MI 49546 MD RSCB2H p 616.653.8429 f 616.653.2717 -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Richards, Robert B. Sent: Tuesday, November 21, 2017 8:27 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Useful little utility? **CAUTION EXTERNAL EMAIL** **DO NOT open attachments or click on links from unknown senders or unexpected emails** John, I wonder how many of us missed that little improvement. I use ISRDDN enough times per day that I created a command table entry for it so that I only have to type DDN from anywhere. I just checked the new PARM command in SDSF. If you are using SYSNAME *, it will search for a member (masking acceptable) in every parmlib dataset listed. I did not see the capability to search for a string from that display, unless I missed it in my quick read of the tutorial . Still, that member search can be very powerful in its own right, especially in shops with tons of lpars. Bob -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
Re: ECVTDUCU & "trap" condition in z/OS
Peter, Thanks for the reply. But there is still the second question I asked - Can you say if there is any (near?) future possibility of a PC or SVC interface that would permit application-level code (problem state, non-zero-key) to use the TRAP facility? Such a facility would make many application-level assembler debugging tools (including and maybe especially the CBT collection) far more efficient and useful than is currently possible via ESTAEX or BAKR/PR methodologies. Peter -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Peter Relson Sent: Tuesday, November 21, 2017 7:55 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: ECVTDUCU & "trap" condition in z/OS EXTERNAL: This email originated from outside of Broadridge. Do not click any links or open any attachments unless you trust the sender and know the content is safe. There is no additional documentation and there are no other references because there is no particular need for there to be. If you are using the trap instructions then you know (or need to know) about the trap control block and that the trap instructions architecture requires you to provide information controlling the traps within the dispatchable unit control table (DUCT). This pointer (and the service behind it) was created so that individual trap exploiters would not code these updates themselves because they were more likely to get it wrong than z/OS development is and were more likely not to be in a position to react to architectural changes (such as happened when z/Architecture was introduced) than z/OS development is. Peter Relson z/OS Core Technology Design -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: IEBUPDTE question
In addition to IEBUPDTE-like utilities, StarTool (and I would hope its CBT predecessor) has a REPLACE function that can scan an entire PDS(E) and replace one string with another as long the result does not exceed line length. It allows such filters as WORD, PREFIX, and SUFFIX. You can make a trial run to examine the results without actually updating anything before doing it for real. Several other options are included as well. Something to keep in mind. . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-543-6132 Office ⇐=== NEW robin...@sce.com -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Tony Thigpen Sent: Monday, November 20, 2017 8:50 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: (External):Re: IEBUPDTE question Hundred+ members. As I mentioned (but it got lost in the what is midnight argument), I used a CBT program to perform the adds. I just modified it to pass-though the ./ INCLUDE cards as data cards. Tony Thigpen Wayne Bickerdike wrote on 11/20/2017 11:39 PM: > oops, > > Change all the unwanted ./ cards to ## or similar. After the IEBUPDTE, > change them back to ./ > > On Tue, Nov 21, 2017 at 3:32 PM, Wayne Bickerdike wrote: > >> Assuming the cards with a ./ don't have the correct syntax, why not >> do an EXCLUDE ALL, FIND ALL ./. >> >> EXCLUDE all the correct ./ cards and then do a DEL ALL NX >> >> >> >> On Mon, Nov 20, 2017 at 2:45 PM, Tony Thigpen wrote: >> >>> I need to catalog a bunch of jobs into a PDS during a conversion. >>> The source system utility creates an IEBUPDTE job for this purpose. >>> >>> Unfortunately, some of the data within these jobs steams contain a './' >>> at the start of the card record. IEBUPDTE thinks they are control >>> cards and cancels the catalog of the new member. >>> >>> At this point, the only thing I think should work is to individually >>> FTP these members and bypass IEBUPDTE, but that will be a real hassle. >>> >>> I am looking for suggestions on how to get these members cataloged. >>> >>> -- >>> Tony Thigpen >> -- >> 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: Useful little utility?
Even ardent GRS star advocates had a hard time buying this story some years ago. We had a single non-sharing system where a catalog management job ran many times longer than on any other system--even the feeble sysprog sandbox. In comparing systems, the only visible difference I could see was that this single system was still running GRS ring mode because hey, it was only a single system, why bother with star? On a pure guess, I converted this system to star mode even though it was not sharing with anyone else. From that moment onward, the catalog job ran there as well as anywhere else. Go figure. . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-543-6132 Office ⇐=== NEW robin...@sce.com -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Rob Scott Sent: Tuesday, November 21, 2017 8:07 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: (External):Re: Useful little utility? Dave, SDSF primary command syntax is a bit clunky as it has to support "the way it has always worked" and every parameter is positional rather than a more modern "keyword(value)" or "keyword=value" format. I have the ear of the current SDSF development team and perhaps they can provide something like a "ENQD dsname_pattern" command that would prime the major name with "SYSDSN", the SYSNAME with "*" and then filter the minor names by the specified pattern. Let me know if this sounds like something you would like. As for the response time of the "N" and "D" line commands, that very much sounds like something to do with your GRS configuration - perhaps raise a PMR with IBM to investigate if you believe that this is not a simple case of lack of CPU power? Rob Scott -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Jousma, David Sent: Tuesday, November 21, 2017 2:47 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Useful little utility? Rob, I've been playing with that too. ENQC is nice, shows plex-wide enq contention, ENQ not so much, kludgy IMO. By default ENQ is single system, and to enable all systems, you have to also specify major name. So ENQ SYSDSN * to get all systems in the plex. No way to pass any kind of filter on the major name, so you get (in my case, a list of 268K entries back) all data set names. Which you can then use a filter or find commands against, but why on earth no short cut? ENQC is easy enough that my operations staff can use it to see who is holding up a production batch job. However on occasion, they want to just "look up" a dataset to see if anyone is using it at that moment. I realize there are methods via ISPF 3.4, etc, or just issue the D GRS,RES=(SYSDSN,'DATA.SET.NAME') As for the "N", I've tried that too. I don’t know if something is wrong, but when I use that, it takes a good 15 seconds for the display to come back, and then its scope is only that single system. Once that list is produced, and you issue a "D" next to the dataset to display all enqueues, another 15 seconds, and even that display is single system. _ Dave Jousma Manager Mainframe Engineering, Assistant Vice President david.jou...@53.com 1830 East Paris, Grand Rapids, MI 49546 MD RSCB2H p 616.653.8429 f 616.653.2717 -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Rob Scott Sent: Tuesday, November 21, 2017 9:28 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Useful little utility? **CAUTION EXTERNAL EMAIL** **DO NOT open attachments or click on links from unknown senders or unexpected emails** Check out the new "ENQ" command in SDSF (2.1+) as it supports sysplex-wide ENQ information display. Note that you can also do an "N" action in the "NP" column on the DA panel to show enqueues for the ASID only. Rob Scott -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Jousma, David Sent: Tuesday, November 21, 2017 2:03 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Useful little utility? My wish for ISRDDN would be to be able to toggle on/off sysplex-wide ENQ data for STAR mode GRS configuration. ISRDDN ENQ pulls up a TASID-like panel, but there is no way to make it display global enqueues that I can see. All I get is a LIMITED ENQ DATA in the upper right corner, and extended help says: This system is running with SETGRS MODE=STAR. ENQ information will not be collected from other systems. As a result, ENQ displays may not reflect all of the ENQs which are known to GRS. _ Dave Jousma Manager Mainframe Engineering, Assistant Vice President david.jou...@53.com 1830 East Paris, Grand Rapids, MI 49546 MD RSCB2H p 616.653.8429 f 616.653.2717
Re: IEBUPDTE question
On Tue, 21 Nov 2017 15:32:37 +1100, Wayne Bickerdike wrote: >Assuming the cards with a ./ don't have the correct syntax, why not do an >EXCLUDE ALL, FIND ALL ./. > >EXCLUDE all the correct ./ cards and then do a DEL ALL NX > I asumed he wanted them preserved as data records, not deleted. -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: IEBUPDTE question
On Mon, 20 Nov 2017 23:15:14 -0600, Edward Gould wrote: > >> I suspect 1-8 was an intended accommodation to VB. And in another apparent >> accommodation, ISPF Edit until recently would not create an 8-character >> record >> but always padded it with an additional blank. > >I don’t think so as SPF wasn’t around when MVS first came out. I “think” it >was 5 or so years afterwards, so that wasn’t the reason. > Have you a more plausible conjecture? If not, I'm sticking with mine. And the chronology you assume fits with my explanation. >> In days of yore panel definitions for SPF (now known as ISPF) were VB. >> Abruptly >> they changed to FB. Disruptively -- it broke all my customized panels. >> Cognoscenti >> surmised this was an accommodation to SMP(/E) and IEBUPDTE. > >I will admit that I am leary of that explanation, ... >> Why? -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Useful little utility?
Thanks for the feedback Rob. I doubt its lack of horsepower. I'll have to dig into this further. _ Dave Jousma Manager Mainframe Engineering, Assistant Vice President david.jou...@53.com 1830 East Paris, Grand Rapids, MI 49546 MD RSCB2H p 616.653.8429 f 616.653.2717 -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Rob Scott Sent: Tuesday, November 21, 2017 11:07 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Useful little utility? **CAUTION EXTERNAL EMAIL** **DO NOT open attachments or click on links from unknown senders or unexpected emails** Dave, SDSF primary command syntax is a bit clunky as it has to support "the way it has always worked" and every parameter is positional rather than a more modern "keyword(value)" or "keyword=value" format. I have the ear of the current SDSF development team and perhaps they can provide something like a "ENQD dsname_pattern" command that would prime the major name with "SYSDSN", the SYSNAME with "*" and then filter the minor names by the specified pattern. Let me know if this sounds like something you would like. As for the response time of the "N" and "D" line commands, that very much sounds like something to do with your GRS configuration - perhaps raise a PMR with IBM to investigate if you believe that this is not a simple case of lack of CPU power? Rob Scott -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Jousma, David Sent: Tuesday, November 21, 2017 2:47 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Useful little utility? Rob, I've been playing with that too. ENQC is nice, shows plex-wide enq contention, ENQ not so much, kludgy IMO. By default ENQ is single system, and to enable all systems, you have to also specify major name. So ENQ SYSDSN * to get all systems in the plex. No way to pass any kind of filter on the major name, so you get (in my case, a list of 268K entries back) all data set names. Which you can then use a filter or find commands against, but why on earth no short cut? ENQC is easy enough that my operations staff can use it to see who is holding up a production batch job. However on occasion, they want to just "look up" a dataset to see if anyone is using it at that moment. I realize there are methods via ISPF 3.4, etc, or just issue the D GRS,RES=(SYSDSN,'DATA.SET.NAME') As for the "N", I've tried that too. I don’t know if something is wrong, but when I use that, it takes a good 15 seconds for the display to come back, and then its scope is only that single system. Once that list is produced, and you issue a "D" next to the dataset to display all enqueues, another 15 seconds, and even that display is single system. _ Dave Jousma Manager Mainframe Engineering, Assistant Vice President david.jou...@53.com 1830 East Paris, Grand Rapids, MI 49546 MD RSCB2H p 616.653.8429 f 616.653.2717 -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Rob Scott Sent: Tuesday, November 21, 2017 9:28 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Useful little utility? **CAUTION EXTERNAL EMAIL** **DO NOT open attachments or click on links from unknown senders or unexpected emails** Check out the new "ENQ" command in SDSF (2.1+) as it supports sysplex-wide ENQ information display. Note that you can also do an "N" action in the "NP" column on the DA panel to show enqueues for the ASID only. Rob Scott -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Jousma, David Sent: Tuesday, November 21, 2017 2:03 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Useful little utility? My wish for ISRDDN would be to be able to toggle on/off sysplex-wide ENQ data for STAR mode GRS configuration. ISRDDN ENQ pulls up a TASID-like panel, but there is no way to make it display global enqueues that I can see. All I get is a LIMITED ENQ DATA in the upper right corner, and extended help says: This system is running with SETGRS MODE=STAR. ENQ information will not be collected from other systems. As a result, ENQ displays may not reflect all of the ENQs which are known to GRS. _ Dave Jousma Manager Mainframe Engineering, Assistant Vice President david.jou...@53.com 1830 East Paris, Grand Rapids, MI 49546 MD RSCB2H p 616.653.8429 f 616.653.2717 -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Richards, Robert B. Sent: Tuesday, November 21, 2017 8:27 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Useful little utility? **CAUTION EXTERNAL EMAIL** **DO NOT open attachments or click on links from unknown senders or unexpected emails
Re: [TSO-REXX] Fwd: Pipelines in the z/OS base.
Martin wrote: > A DFSORT stage would/could/should allow all the myriad* DFSORT control statements. And be for heavy lifting. Those are the two reasons I suggested it. I was going to do some details research (my DFSORT knowledge is probably out of date, for which I take responsibility), but time is short, and I don't want the issue to get stale. I believe you are referring to INCLUDE/OMIT, INREC/OUTREC, etc. I hope this answers your point. I don't know if your statement is true, or will ever be implemented. I will say that Pipelines offers so many more options in record selection, formatting, conversion and field specification, that what you suggest probably will never need to be implemented. Here's why: - Of the 300+ Pipelines stages, many are selection stages. In this case, "many" is much more than myriad, AFAIK, by an order of magniture. There are simple selectors, but also complex ones that support conversions, logic, arithmetic, and reformatting. - Fields can be identified by character, word, or delimited field. Each of these can used as substring to an enclosing specification, to multiple levels. E.g., take the second slash delimited subfield in the seventh tab delimited field to get a numeric month value. And you are not limited to blanks as white space or tabs as delimiters. - The DFSORT program product control statements can only be used in connection with the sort process. Pipelines stages can be used even when you are not sorting. In other words, Pipelines skills, while being easy to learn (unlike my recollection of DFSORT control statement), they have a vastly broader range of applicable uses. - The DFSORT program product E15 and E35 internal sort exits can only be used once per sort. Pipelines stages bring this efficiency to each and every stage in a Pipeline. To press the point, unlike the need for record and field definitions in, say, a COBOL internal sort exit, the intermediate records don't have to be defined, and fields only have to be referenced if they are actually involved in the a particular stage. - Finally, you can process unselected records without having to reprocess the entire input file, as shown below. Business problem: You have an externally produced name and address file that has to be sorted by ZIP code to get a USPS discount rate. There are two types of records, business and residential. The fields are free format and tab delimited. The business records differ from residential records in that there are additional fields: Company after the name fields and an ATTN: field after the ZIP code. This would be trivial in pipes if the ZIP code were the last field, but we can't use that because of the ATTN: field. A pipes approach is as follows: Separate the records into streams and prefix each record with its ZIP code. Then sort by the ZIP in the first field, discard the prefix ZIP. It would look something like this in commented REXX. ( Visualizing someone else's multi-stream pipe is easier with a flow chart.) ... /**/ /* f200: f800: */ /* +-+ +-+ ++ +-+ +--+ ++ +-+ */ /* |<|-->|p|-->|spec|-->|f|-->|dfsort|-->|chop|-->|>| */ /* +-+ |i| ++ |a| +--+ ++ +-+ */ /* |c||n| */ /* |k| ++ |i| */ /* | |-->|spec|-->|n| */ /* +-+ ++ +-+ */ /**/ "pipe (listerr name ZIPSort.exec end ?", "|out.file */ "? f200: ", /* Business record come here. */ "| specsfield 9 1 1-* nextfield", /* ZIP pfx */ "| f800: ", /* Back to first stream. */ ... I hope this helps. Even if there are features new (to me) of DFSORT would make some of my statements incorrect, I'm quite sure that the remaining ones would still drive the point home easily. On Sat, Nov 18, 2017 at 3:01 AM, Martin Packer wrote: > A DFSORT stage would/could/should allow all the myriad* DFSORT control > statements. And be for heavy lifting. Those are the two reasons I suggested > it. > > And note a DFSORT stage could be tested outside of a pipeline. > > Also note Pipelines could orchestrate multiple DFSORT invocations in a > chain. > > Cheers, Martin > > * If you don’t think the word “myriad” is ap
Shocking Bug in Latest PCOMM Release
Just installed PCOMM 13.0. It was released November 9, 2017. The DEL key just beeps. Doesn't delete *any* characters! IBM's PCOMM developers must not have actual 3270 users participating in the their early testing. I hereby volunteer... -- Phoenix Software International Edward E. Jaffe 831 Parkview Drive North El Segundo, CA 90245 http://www.phoenixsoftware.com/ -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Finally joined Linkedin
I've been inactive since my Internet provider folded up with no advance notice. A lot has happened since then, most of which is off topic, but it seems reasonable to post here that I've finally oined LinkedIn from e-mail address sme...@gmu.edu. For those of you who are on LinkedIn and know me, feel free to connect. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Finally joined Linkedin
Here I am in a short week of work and trying to get z/OS 2.02 ready to go in on one of my LPARS a week from today and with a couple of regular problems being thrown my way, "Loopy" does not half describe my state, so take the following with solid grins, please: Do we have a new work in the English language, "oined"? :) (Yes, I know someone forgot to hit the "j", but like I said, I am LOOPY today!) Al Nims Systems Admin/Programmer 3 UFIT University of Florida (352) 273-1298 -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Seymour J Metz Sent: Tuesday, November 21, 2017 4:23 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Finally joined Linkedin I've been inactive since my Internet provider folded up with no advance notice. A lot has happened since then, most of which is off topic, but it seems reasonable to post here that I've finally oined LinkedIn from e-mail address sme...@gmu.edu. For those of you who are on LinkedIn and know me, feel free to connect. -- Shmuel (Seymour J.) Metz https://urldefense.proofpoint.com/v2/url?u=http-3A__mason.gmu.edu_-7Esmetz3&d=DwIFAw&c=pZJPUDQ3SB9JplYbifm4nt2lEVG5pWx2KikqINpWlZM&r=0Ef64GJS77DVfhr5GGKZeQ&m=2sKj_aOZbPd15a5BaYD6NzvZEyrfI4v4RUcrPE8vOuQ&s=twwQJ_Fi0A1v7fcrASgcq96YYO5tamdtQ9-kFzv6JlM&e= -- 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: [TSO-REXX] Fwd: Pipelines in the z/OS base.
Hi, Here is a sample DFSORT job that reads a pipe and does a sort while modifying the data using inrec(before sorting) Outrec(after sorting) and Outfil //PIPEDEMA JOB (DA26,001,098,J69),'KOLUSU', // CLASS=A, // MSGCLASS=H, // MSGLEVEL=(1,1), // NOTIFY=&SYSUID //* //** //* DELETE THE INPUT PIPE DATASET IF IT EXISTED ** //** //STEP0001 EXEC PGM=IEFBR14 //SYSPRINT DD SYSOUT=* //DD1 DD DSN=&SYSUID..PIPE.INPUT, //UNIT=SYSDA,SPACE=(TRK,0),DISP=(MOD,DELETE) //* //** //* CREATE THE INPUT TO SORT AND WRITE IT TO A PIPE ** //* WILL HAVE 60 RECORDS (20 RECORDS FOR EACH NAME) ** //** //PIPERCRE EXEC PGM=SORT //SYSOUT DD SYSOUT=* //SORTIN DD * PAUL MARTIN HOBART //SORTOUT DD DSN=&SYSUID..PIPE.INPUT, //SUBSYS=(BP01,'WAITOPEN=180'), //DCB=(LRECL=80,RECFM=FB,BLKSIZE=27920) //SYSINDD * OPTION COPY OUTFIL REPEAT=20,OVERLAY=(20:SEQNUM,3,ZD,RESTART=(1,10)) /* //PIPEDEMB JOB (DA26,001,098,J69),'KOLUSU', // CLASS=A, // MSGCLASS=H, // MSGLEVEL=(1,1), // NOTIFY=&SYSUID //* //** //* READ THE PIPE AND USING INREC MODIFY MARTIN RECORDS ** //* SORT THE DATA ON NAME AND SEQUENCE DESCENDING ** //* MODIFY PAUL RECORDS USING OUTREC ** //* MODIFY HOBART RECORDS USING OUTFIL** //** //PIPEREAD EXEC PGM=SORT //SYSOUT DD SYSOUT=* //SORTDIAG DD DUMMY //SORTIN DD DISP=SHR,DSN=&SYSUID..PIPE.INPUT, //SUBSYS=(BP01,'WAITOPEN=180'), //DCB=(LRECL=80,RECFM=FB,BLKSIZE=27920) //SORTOUT DD SYSOUT=* //SYSINDD * INREC IFTHEN=(WHEN=(01,10,CH,EQ,C'MARTIN',AND, 20,03,SS,EQ,C'005,010,015,020'), OVERLAY=(31:C'EVERY 5TH RECORD TAGGED USING INREC')) SORT FIELDS=(01,10,CH,A, $ SORT ON NAME ASC 21,03,ZD,D) $ SORT ON SEQ DESC OUTREC IFTHEN=(WHEN=(01,10,CH,EQ,C'PAUL',AND, 20,03,SS,EQ,C'006,012,018'), OVERLAY=(31:C'TAGGED EVERY 6TH RECORD USING OUTREC')) OUTFIL IFTHEN=(WHEN=(01,10,CH,EQ,C'HOBART',AND, 20,03,CH,EQ,C'020'), OVERLAY=(31:C'RECORD 20 IS TAGGED USING OUTFIL')) /* Further if you have any questions please let me know Thanks, Kolusu DFSORT Development IBM Corporation IBM Mainframe Discussion List wrote on 11/21/2017 01:05:40 PM: > From: Hobart Spitz > To: IBM-MAIN@LISTSERV.UA.EDU > Date: 11/21/2017 01:06 PM > Subject: Re: [TSO-REXX] Fwd: Pipelines in the z/OS base. > Sent by: IBM Mainframe Discussion List > > Martin wrote: > > A DFSORT stage would/could/should allow all the myriad* DFSORT control > statements. And be for heavy lifting. Those are the two reasons I suggested > it. > > I was going to do some details research (my DFSORT knowledge is probably > out of date, for which I take responsibility), but time is short, and I > don't want the issue to get stale. I believe you are referring to > INCLUDE/OMIT, INREC/OUTREC, etc. > > I hope this answers your point. I don't know if your statement is true, or > will ever be implemented. I will say that Pipelines offers so many more > options in record selection, formatting, conversion and field > specification, that what you suggest probably will never need to be > implemented. > > Here's why: > > - Of the 300+ Pipelines stages, many are selection stages. In this case, > "many" is much more than myriad, AFAIK, by an order of magniture. There > are simple selectors, but also complex ones that support conversions, > logic, arithmetic, and reformatting. > > - Fields can be identified by character, word, or delimited field. Each of > these can used as substring to an enclosing specification, to multiple > levels. E.g., take the second slash delimited subfield in the seventh tab > delimited field to get a numeric month value. And you are not limited to > blanks as white space or tabs as delimiters. > > - The DFSORT program product control statements can only be used in > connection with the sort process. Pipelines stages can be used even when > you are not sorting. In other words, Pipelines skills, while being easy to > learn (unlike my recollection of DFSORT control statement), they have a > vastly broader range of applicable uses. > > - The DFSORT program product E15 and E35 internal sort exits can only be > used once per sort. Pipelines stages bring this efficiency to each and > every stage in a Pipeline. To press the point, unlike the need for recor
Re: Finally joined Linkedin
Blame the keyboard; I'm not dyslexic. That's my story and I'm sticking to it. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM Mainframe Discussion List on behalf of Nims,Alva John (Al) Sent: Tuesday, November 21, 2017 4:48 PM To: IBM-MAIN@listserv.ua.edu Subject: Re: Finally joined Linkedin Here I am in a short week of work and trying to get z/OS 2.02 ready to go in on one of my LPARS a week from today and with a couple of regular problems being thrown my way, "Loopy" does not half describe my state, so take the following with solid grins, please: Do we have a new work in the English language, "oined"? :) (Yes, I know someone forgot to hit the "j", but like I said, I am LOOPY today!) Al Nims Systems Admin/Programmer 3 UFIT University of Florida (352) 273-1298 -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Seymour J Metz Sent: Tuesday, November 21, 2017 4:23 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Finally joined Linkedin I've been inactive since my Internet provider folded up with no advance notice. A lot has happened since then, most of which is off topic, but it seems reasonable to post here that I've finally oined LinkedIn from e-mail address sme...@gmu.edu. For those of you who are on LinkedIn and know me, feel free to connect. -- Shmuel (Seymour J.) Metz https://urldefense.proofpoint.com/v2/url?u=http-3A__mason.gmu.edu_-7Esmetz3&d=DwIFAw&c=pZJPUDQ3SB9JplYbifm4nt2lEVG5pWx2KikqINpWlZM&r=0Ef64GJS77DVfhr5GGKZeQ&m=2sKj_aOZbPd15a5BaYD6NzvZEyrfI4v4RUcrPE8vOuQ&s=twwQJ_Fi0A1v7fcrASgcq96YYO5tamdtQ9-kFzv6JlM&e= -- 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: Finally joined Linkedin
Yes, typical SysProg excuse, "That's a Hardware problem, I only do Software!" :) PS: My fingers have been know to miss a key or two, even the entire keyboard! :) Al Nims Systems Admin/Programmer 3 UFIT University of Florida (352) 273-1298 -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Seymour J Metz Sent: Tuesday, November 21, 2017 4:54 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Finally joined Linkedin Blame the keyboard; I'm not dyslexic. That's my story and I'm sticking to it. -- Shmuel (Seymour J.) Metz https://urldefense.proofpoint.com/v2/url?u=http-3A__mason.gmu.edu_-7Esmetz3&d=DwIFAw&c=pZJPUDQ3SB9JplYbifm4nt2lEVG5pWx2KikqINpWlZM&r=0Ef64GJS77DVfhr5GGKZeQ&m=ZSfhVw8U7TBJ98ix3llJrz2kxM5oEY6ptEoCCXGFVrE&s=1Yvb4pyRCY2CyzB2YhqvPPyCV0gBqOt2JfA5BC0nx90&e= From: IBM Mainframe Discussion List on behalf of Nims,Alva John (Al) Sent: Tuesday, November 21, 2017 4:48 PM To: IBM-MAIN@listserv.ua.edu Subject: Re: Finally joined Linkedin Here I am in a short week of work and trying to get z/OS 2.02 ready to go in on one of my LPARS a week from today and with a couple of regular problems being thrown my way, "Loopy" does not half describe my state, so take the following with solid grins, please: Do we have a new work in the English language, "oined"? :) (Yes, I know someone forgot to hit the "j", but like I said, I am LOOPY today!) Al Nims Systems Admin/Programmer 3 UFIT University of Florida (352) 273-1298 -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Seymour J Metz Sent: Tuesday, November 21, 2017 4:23 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Finally joined Linkedin I've been inactive since my Internet provider folded up with no advance notice. A lot has happened since then, most of which is off topic, but it seems reasonable to post here that I've finally oined LinkedIn from e-mail address sme...@gmu.edu. For those of you who are on LinkedIn and know me, feel free to connect. -- Shmuel (Seymour J.) Metz https://urldefense.proofpoint.com/v2/url?u=http-3A__mason.gmu.edu_-7Esmetz3&d=DwIFAw&c=pZJPUDQ3SB9JplYbifm4nt2lEVG5pWx2KikqINpWlZM&r=0Ef64GJS77DVfhr5GGKZeQ&m=2sKj_aOZbPd15a5BaYD6NzvZEyrfI4v4RUcrPE8vOuQ&s=twwQJ_Fi0A1v7fcrASgcq96YYO5tamdtQ9-kFzv6JlM&e= -- 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 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: [TSO-REXX] Fwd: Pipelines in the z/OS base.
I have never worked with pipes in a production batch environment. In a classic batch job, if a problem occurs somewhere in the middle, it's common to restart the job at some recoverable point after fixing the downstream problem. I cannot visualize how to restart a pipes job in such a case. Without intermediate files to resume with, how does all that in-memory data get recreated without starting back at the top? In a short or medium length job, starting over may not be such a big problem, but for a job that runs hours on a good day, I could envision some major production schedule glitches with pipes. . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-543-6132 Office ⇐=== NEW robin...@sce.com -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Sri h Kolusu Sent: Tuesday, November 21, 2017 1:54 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: (External):Re: [TSO-REXX] Fwd: Pipelines in the z/OS base. Hi, Here is a sample DFSORT job that reads a pipe and does a sort while modifying the data using inrec(before sorting) Outrec(after sorting) and Outfil //PIPEDEMA JOB (DA26,001,098,J69),'KOLUSU', // CLASS=A, // MSGCLASS=H, // MSGLEVEL=(1,1), // NOTIFY=&SYSUID //* //** //* DELETE THE INPUT PIPE DATASET IF IT EXISTED ** //** //STEP0001 EXEC PGM=IEFBR14 //SYSPRINT DD SYSOUT=* //DD1 DD DSN=&SYSUID..PIPE.INPUT, //UNIT=SYSDA,SPACE=(TRK,0),DISP=(MOD,DELETE) //* //** //* CREATE THE INPUT TO SORT AND WRITE IT TO A PIPE ** //* WILL HAVE 60 RECORDS (20 RECORDS FOR EACH NAME) ** //** //PIPERCRE EXEC PGM=SORT //SYSOUT DD SYSOUT=* //SORTIN DD * PAUL MARTIN HOBART //SORTOUT DD DSN=&SYSUID..PIPE.INPUT, //SUBSYS=(BP01,'WAITOPEN=180'), //DCB=(LRECL=80,RECFM=FB,BLKSIZE=27920) //SYSINDD * OPTION COPY OUTFIL REPEAT=20,OVERLAY=(20:SEQNUM,3,ZD,RESTART=(1,10)) /* //PIPEDEMB JOB (DA26,001,098,J69),'KOLUSU', // CLASS=A, // MSGCLASS=H, // MSGLEVEL=(1,1), // NOTIFY=&SYSUID //* //** //* READ THE PIPE AND USING INREC MODIFY MARTIN RECORDS ** //* SORT THE DATA ON NAME AND SEQUENCE DESCENDING ** //* MODIFY PAUL RECORDS USING OUTREC ** //* MODIFY HOBART RECORDS USING OUTFIL** //** //PIPEREAD EXEC PGM=SORT //SYSOUT DD SYSOUT=* //SORTDIAG DD DUMMY //SORTIN DD DISP=SHR,DSN=&SYSUID..PIPE.INPUT, //SUBSYS=(BP01,'WAITOPEN=180'), //DCB=(LRECL=80,RECFM=FB,BLKSIZE=27920) //SORTOUT DD SYSOUT=* //SYSINDD * INREC IFTHEN=(WHEN=(01,10,CH,EQ,C'MARTIN',AND, 20,03,SS,EQ,C'005,010,015,020'), OVERLAY=(31:C'EVERY 5TH RECORD TAGGED USING INREC')) SORT FIELDS=(01,10,CH,A, $ SORT ON NAME ASC 21,03,ZD,D) $ SORT ON SEQ DESC OUTREC IFTHEN=(WHEN=(01,10,CH,EQ,C'PAUL',AND, 20,03,SS,EQ,C'006,012,018'), OVERLAY=(31:C'TAGGED EVERY 6TH RECORD USING OUTREC')) OUTFIL IFTHEN=(WHEN=(01,10,CH,EQ,C'HOBART',AND, 20,03,CH,EQ,C'020'), OVERLAY=(31:C'RECORD 20 IS TAGGED USING OUTFIL')) /* Further if you have any questions please let me know Thanks, Kolusu DFSORT Development IBM Corporation IBM Mainframe Discussion List wrote on 11/21/2017 01:05:40 PM: > From: Hobart Spitz > To: IBM-MAIN@LISTSERV.UA.EDU > Date: 11/21/2017 01:06 PM > Subject: Re: [TSO-REXX] Fwd: Pipelines in the z/OS base. > Sent by: IBM Mainframe Discussion List > > Martin wrote: > > A DFSORT stage would/could/should allow all the myriad* DFSORT > > control > statements. And be for heavy lifting. Those are the two reasons I suggested > it. > > I was going to do some details research (my DFSORT knowledge is > probably out of date, for which I take responsibility), but time is > short, and I don't want the issue to get stale. I believe you are > referring to INCLUDE/OMIT, INREC/OUTREC, etc. > > I hope this answers your point. I don't know if your statement is > true, or > will ever be implemented. I will say that Pipelines offers so many > more options in record selection, formatting, conversion and field > specification, that what you suggest probably will never need to be > implemented. > > Here's why: > > - Of the 300+ Pipelines stages, many are selection stages. In this case, > "many" is much more than myriad, AFAIK, by an order of ma
Re: [TSO-REXX] Fwd: Pipelines in the z/OS base.
Jesse, If one end of the pipe fails for any reason, then both ends would have to be rerun. The redbook "Batch Modernization on z/OS" chapter 16 explains the use of Batch pipes. Martin Packer is one of the co-author. http://www.redbooks.ibm.com/abstracts/sg247779.html Thanks, Kolusu From: Jesse 1 Robinson To: IBM-MAIN@LISTSERV.UA.EDU Date: 11/21/2017 03:13 PM Subject:Re: [TSO-REXX] Fwd: Pipelines in the z/OS base. Sent by:IBM Mainframe Discussion List I have never worked with pipes in a production batch environment. In a classic batch job, if a problem occurs somewhere in the middle, it's common to restart the job at some recoverable point after fixing the downstream problem. I cannot visualize how to restart a pipes job in such a case. Without intermediate files to resume with, how does all that in-memory data get recreated without starting back at the top? In a short or medium length job, starting over may not be such a big problem, but for a job that runs hours on a good day, I could envision some major production schedule glitches with pipes. . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-543-6132 Office ⇐=== NEW robin...@sce.com -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Sri h Kolusu Sent: Tuesday, November 21, 2017 1:54 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: (External):Re: [TSO-REXX] Fwd: Pipelines in the z/OS base. Hi, Here is a sample DFSORT job that reads a pipe and does a sort while modifying the data using inrec(before sorting) Outrec(after sorting) and Outfil //PIPEDEMA JOB (DA26,001,098,J69),'KOLUSU', // CLASS=A, // MSGCLASS=H, // MSGLEVEL=(1,1), // NOTIFY=&SYSUID //* //** //* DELETE THE INPUT PIPE DATASET IF IT EXISTED ** //** //STEP0001 EXEC PGM=IEFBR14 //SYSPRINT DD SYSOUT=* //DD1 DD DSN=&SYSUID..PIPE.INPUT, //UNIT=SYSDA,SPACE=(TRK,0),DISP=(MOD,DELETE) //* //** //* CREATE THE INPUT TO SORT AND WRITE IT TO A PIPE ** //* WILL HAVE 60 RECORDS (20 RECORDS FOR EACH NAME) ** //** //PIPERCRE EXEC PGM=SORT //SYSOUT DD SYSOUT=* //SORTIN DD * PAUL MARTIN HOBART //SORTOUT DD DSN=&SYSUID..PIPE.INPUT, //SUBSYS=(BP01,'WAITOPEN=180'), //DCB=(LRECL=80,RECFM=FB,BLKSIZE=27920) //SYSINDD * OPTION COPY OUTFIL REPEAT=20,OVERLAY=(20:SEQNUM,3,ZD,RESTART=(1,10)) /* //PIPEDEMB JOB (DA26,001,098,J69),'KOLUSU', // CLASS=A, // MSGCLASS=H, // MSGLEVEL=(1,1), // NOTIFY=&SYSUID //* //** //* READ THE PIPE AND USING INREC MODIFY MARTIN RECORDS ** //* SORT THE DATA ON NAME AND SEQUENCE DESCENDING ** //* MODIFY PAUL RECORDS USING OUTREC ** //* MODIFY HOBART RECORDS USING OUTFIL** //** //PIPEREAD EXEC PGM=SORT //SYSOUT DD SYSOUT=* //SORTDIAG DD DUMMY //SORTIN DD DISP=SHR,DSN=&SYSUID..PIPE.INPUT, //SUBSYS=(BP01,'WAITOPEN=180'), //DCB=(LRECL=80,RECFM=FB,BLKSIZE=27920) //SORTOUT DD SYSOUT=* //SYSINDD * INREC IFTHEN=(WHEN=(01,10,CH,EQ,C'MARTIN',AND, 20,03,SS,EQ,C'005,010,015,020'), OVERLAY=(31:C'EVERY 5TH RECORD TAGGED USING INREC')) SORT FIELDS=(01,10,CH,A, $ SORT ON NAME ASC 21,03,ZD,D) $ SORT ON SEQ DESC OUTREC IFTHEN=(WHEN=(01,10,CH,EQ,C'PAUL',AND, 20,03,SS,EQ,C'006,012,018'), OVERLAY=(31:C'TAGGED EVERY 6TH RECORD USING OUTREC')) OUTFIL IFTHEN=(WHEN=(01,10,CH,EQ,C'HOBART',AND, 20,03,CH,EQ,C'020'), OVERLAY=(31:C'RECORD 20 IS TAGGED USING OUTFIL')) /* Further if you have any questions please let me know Thanks, Kolusu DFSORT Development IBM Corporation IBM Mainframe Discussion List wrote on 11/21/2017 01:05:40 PM: > From: Hobart Spitz > To: IBM-MAIN@LISTSERV.UA.EDU > Date: 11/21/2017 01:06 PM > Subject: Re: [TSO-REXX] Fwd: Pipelines in the z/OS base. > Sent by: IBM Mainframe Discussion List > > Martin wrote: > > A DFSORT stage would/could/should allow all the myriad* DFSORT > > control > statements. And be for heavy lifting. Those are the two reasons I suggested > it. > > I was going to do some details research (my DFSORT knowledge is > probably out of date, for which I take responsibility), but time is > short, and I don't want the issue to get stale. I believe you are > referring to IN
Re: Finally joined Linkedin
Welcome back! Charles -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Seymour J Metz Sent: Tuesday, November 21, 2017 1:54 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Finally joined Linkedin Blame the keyboard; I'm not dyslexic. That's my story and I'm sticking to it. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM Mainframe Discussion List on behalf of Nims,Alva John (Al) Sent: Tuesday, November 21, 2017 4:48 PM To: IBM-MAIN@listserv.ua.edu Subject: Re: Finally joined Linkedin Here I am in a short week of work and trying to get z/OS 2.02 ready to go in on one of my LPARS a week from today and with a couple of regular problems being thrown my way, "Loopy" does not half describe my state, so take the following with solid grins, please: Do we have a new work in the English language, "oined"? :) (Yes, I know someone forgot to hit the "j", but like I said, I am LOOPY today!) Al Nims Systems Admin/Programmer 3 UFIT University of Florida (352) 273-1298 -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Seymour J Metz Sent: Tuesday, November 21, 2017 4:23 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Finally joined Linkedin I've been inactive since my Internet provider folded up with no advance notice. A lot has happened since then, most of which is off topic, but it seems reasonable to post here that I've finally oined LinkedIn from e-mail address sme...@gmu.edu. For those of you who are on LinkedIn and know me, feel free to connect. -- Shmuel (Seymour J.) Metz https://urldefense.proofpoint.com/v2/url?u=http-3A__mason.gmu.edu_-7Esmetz3&; d=DwIFAw&c=pZJPUDQ3SB9JplYbifm4nt2lEVG5pWx2KikqINpWlZM&r=0Ef64GJS77DVfhr5GGK ZeQ&m=2sKj_aOZbPd15a5BaYD6NzvZEyrfI4v4RUcrPE8vOuQ&s=twwQJ_Fi0A1v7fcrASgcq96Y YO5tamdtQ9-kFzv6JlM&e= -- 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 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Finally joined Linkedin
Hear, hear! I was beginning to fear the worst. > On Nov 21, 2017, at 18:35, Charles Mills wrote: > > Welcome back! > > Charles > > --- > > > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of Seymour J Metz > Sent: Tuesday, November 21, 2017 4:23 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Finally joined Linkedin > > I've been inactive since my Internet provider folded up with no advance > notice. A lot has happened since then, most of which is off topic, but it > seems reasonable to post here that I've finally oined LinkedIn from e-mail > address sme...@gmu.edu. For those of you who are on LinkedIn and know me, > feel free to connect. > > > -- > Shmuel (Seymour J.) Metz > https://urldefense.proofpoint.com/v2/url?u=http-3A__mason.gmu.edu_-7Esmetz3&; > d=DwIFAw&c=pZJPUDQ3SB9JplYbifm4nt2lEVG5pWx2KikqINpWlZM&r=0Ef64GJS77DVfhr5GGK > ZeQ&m=2sKj_aOZbPd15a5BaYD6NzvZEyrfI4v4RUcrPE8vOuQ&s=twwQJ_Fi0A1v7fcrASgcq96Y > YO5tamdtQ9-kFzv6JlM&e= -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Finally joined Linkedin
> On Nov 21, 2017, at 3:23 PM, Seymour J Metz wrote: > > I've been inactive since my Internet provider folded up with no advance > notice. A lot has happened since then, most of which is off topic, but it > seems reasonable to post here that I've finally oined LinkedIn from e-mail > address sme...@gmu.edu. For those of you who are on LinkedIn and know me, > feel free to connect. > > > — Welcome Back!!, you have really been missed. Hope your ISP issue has been straightened out. Ed -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: IEBUPDTE question
> On Nov 21, 2017, at 12:27 PM, Paul Gilmartin > <000433f07816-dmarc-requ...@listserv.ua.edu> wrote: > > Have you a more plausible conjecture? If not, I'm sticking with mine. And > the chronology you assume fits with my explanation. > >>> In days of yore panel definitions for SPF (now known as ISPF) were VB. >>> Abruptly >>> they changed to FB. Disruptively -- it broke all my customized panels. >>> Cognoscenti >>> surmised this was an accommodation to SMP(/E) and IEBUPDTE. >> >> I will admit that I am leary of that explanation, ... >>> > Why? Way back then concatenation of VB and FB wasn’t available. Ed > > -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: [TSO-REXX] Fwd: Pipelines in the z/OS base.
On Tue, 21 Nov 2017 15:37:57 -0700, Sri h Kolusu wrote: > >If one end of the pipe fails for any reason, then both ends would have to >be rerun. The redbook "Batch Modernization on z/OS" chapter 16 >explains the use of Batch pipes. Martin Packer is one of the co-author. > >http://www.redbooks.ibm.com/abstracts/sg247779.html > SORT is a weak instructional tool for pipe concepts. As in: CMS Pipelines User’s Guide and Reference: sort—Order Records ... Record Delay: sort delays all records until end-of-file. I.e. SORT writes nothing until it has completely read its input. One might as well write to a temp file and sort that. A better example might be to use ICETOOL to do a minor reformtting, record-by-record, of its input. And generate that input with an EXEC that emits a record every few seconds. And use SDSF to track its output in real time. But beware: a Master Plumber is apt to jump in with SPECS stages that do the same thing, faster, better, cheaper. QSAM buffering will introduce some parasitic delay unless you use unbuffered RECFM. -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: IEBUPDTE question
On Tue, 21 Nov 2017 19:14:30 -0600, Edward Gould wrote: >> In days of yore panel definitions for SPF (now known as ISPF) were VB. Abruptly they changed to FB. Disruptively -- it broke all my customized panels. Cognoscenti surmised this was an accommodation to SMP(/E) and IEBUPDTE. >>> >>> I will admit that I am leary of that explanation, ... >> Why? > >Way back then concatenation of VB and FB wasn’t available. > But that's exactly what broke my customized panels when IBM changed their panels from VB to FB. Concatenating mine with theirs suddenly failed where it had worked as long as IBM's panels were VB. -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Finally joined Linkedin
Glad to see you back! On Tue, Nov 21, 2017 at 3:23 PM, Seymour J Metz wrote: > I've been inactive since my Internet provider folded up with no advance > notice. A lot has happened since then, most of which is off topic, but it > seems reasonable to post here that I've finally oined LinkedIn from e-mail > address sme...@gmu.edu. For those of you who are on LinkedIn and know me, > feel free to connect. > > > -- > Shmuel (Seymour J.) Metz > http://mason.gmu.edu/~smetz3 > > -- > 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: IEBUPDTE question
> On Nov 21, 2017, at 10:24 AM, Jesse 1 Robinson > wrote: > > In addition to IEBUPDTE-like utilities, StarTool (and I would hope its CBT > predecessor) has a REPLACE function that can scan an entire PDS(E) and > replace one string with another as long the result does not exceed line > length. It allows such filters as WORD, PREFIX, and SUFFIX. You can make a > trial run to examine the results without actually updating anything before > doing it for real. Several other options are included as well. Something to > keep in mind. > > . > . Skip: I never had the free tool, I always used the $$ version. I also will freely admit it has saved my ass many a time. Little story: Way back in the XA days, we had just put an enormous number of JES2 fixes on and I *DID* look at each hold on the 30-40 fixes. None of them mentioned the fact that JES2 would no longer accept a specific JECL parameter. About 0500 I had just let the production system go, so they started to run jobs. About 5 minutes later I get a call saying something is wrong and the JECL parameter is flagged as an error. I started to look at it and to me it seemed valid, so I headed for the manual and it agreed with what I was saying it was valid. I was sweating as I didn’t want to back out all the maintenance. I looked at other option and found one. I had no idea how many of these were in production. I did a quick scan of the library where production came out of and found 10 jobs. I said to myself go for it, so I did a scan/replace and it found the 10 jobs. I called back to production control and asked them too resubmit. Just about the time he submitted it, The VP walked into the office of the supervisor where I was at and asked if we should back out as we had until 6 AM of the stock markets would not open. I said wait one minute and I called back to production control and the job ran successfully. I turned around to the VP and said, no everything is fine. He looked at me and said he had been told there was a major issue and I said no sir, it was a minor issue which has been fixed. After that morning I went back through every JES2 fix that went on and there was NOT a single hold. I then went back and read the cover letters and found the blasted fix. I called in to the support center and bitched at the level 1 people and asked to be connected to level 2. I let level 2 know in no uncertain terms that a HOLD was mandatory for something like this. I didn’t get a lot of oops we are sorry, so at the next SHARE, I buttonholed one of the JES2 IBMers and raged on him. From then on JES2 was good at putting out holds on PTFS. Ed -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Finally joined Linkedin
Glad to see you are back. Missed your great comments. I remember an old friend who was a dyslexic, insomniac and an atheist. He stayed awake most of the night Wondering if there really was a DOG. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Charles Mills Sent: Tuesday, November 21, 2017 6:35 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Finally joined Linkedin Welcome back! Charles -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Seymour J Metz Sent: Tuesday, November 21, 2017 1:54 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Finally joined Linkedin Blame the keyboard; I'm not dyslexic. That's my story and I'm sticking to it. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM Mainframe Discussion List on behalf of Nims,Alva John (Al) Sent: Tuesday, November 21, 2017 4:48 PM To: IBM-MAIN@listserv.ua.edu Subject: Re: Finally joined Linkedin Here I am in a short week of work and trying to get z/OS 2.02 ready to go in on one of my LPARS a week from today and with a couple of regular problems being thrown my way, "Loopy" does not half describe my state, so take the following with solid grins, please: Do we have a new work in the English language, "oined"? :) (Yes, I know someone forgot to hit the "j", but like I said, I am LOOPY today!) Al Nims Systems Admin/Programmer 3 UFIT University of Florida (352) 273-1298 -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Seymour J Metz Sent: Tuesday, November 21, 2017 4:23 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Finally joined Linkedin I've been inactive since my Internet provider folded up with no advance notice. A lot has happened since then, most of which is off topic, but it seems reasonable to post here that I've finally oined LinkedIn from e-mail address sme...@gmu.edu. For those of you who are on LinkedIn and know me, feel free to connect. -- Shmuel (Seymour J.) Metz https://urldefense.proofpoint.com/v2/url?u=http-3A__mason.gmu.edu_-7 Esmetz3& d=DwIFAw&c=pZJPUDQ3SB9JplYbifm4nt2lEVG5pWx2KikqINpWlZM&r=0Ef64GJS77D Vfhr5GGK ZeQ&m=2sKj_aOZbPd15a5BaYD6NzvZEyrfI4v4RUcrPE8vOuQ&s=twwQJ_Fi0A1v7fcr ASgcq96Y YO5tamdtQ9-kFzv6JlM&e= -- 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 -- 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: Shocking Bug in Latest PCOMM Release
On 11/21/2017 4:28 PM, Ed Jaffe wrote: Just installed PCOMM 13.0. It was released November 9, 2017. The DEL key just beeps. Doesn't delete *any* characters! IBM's PCOMM developers must not have actual 3270 users participating in the their early testing. I hereby volunteer... LOL that you expect a reasonable default keyboard. WAKE UP, MAN! -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
CF REPORT
Hi all Below is our three CF reports at the same time. Report 1. CFSYS from RMF MONIII The Coupling Facility Systems (CF Systems) report (CFSYS) gives you information about the distribution of coupling facility requests among the systems and about the activities in the subchannels and paths attached to the coupling facilities in the sysplex CF Name System Subchannel -- Paths -- -- Sync --- --- Async --- Delay Busy Avail Delay Rate AvgRate Avg Chng Del % % % Serv Serv %% BPC3C1 NP1A 0.1 97.84 0.00.1497 26344 1187 49.6 50.3 Note1: The Subchannel Delay =0.1% Report 2 : SUBCHANNEL ACTIVITY from RMF Postprocessor C O U P L I N G F A C I L I T Y A C T I V I T Y PAGE 225 z/OS V2R2 SYSPLEX PLEXNP1 DATE 11/15/2017 INTERVAL 015.00.000 RPT VERSION V2R2 RMFTIME 23.45.00 CYCLE 01.000 SECONDS -- COUPLING FACILITY NAME = BPC3C1 -- SUBCHANNEL ACTIVITY -- # REQ --- REQUESTS --- -- DELAYED REQUESTS -- SYSTEM TOTAL -- CF LINKS -- PTH # -SERVICE TIME(MIC)- # % OF -- AVG TIME(MIC) -- NAME AVG/SEC TYPE GEN USE BUSYREQ AVGSTD_DEV REQREQ /DELSTD_DEV /ALL NP1A 18567K CS5 44 2 SYNC 4654K 10.7 18.7 LIST/CACHE 12M 62.8 1719 1954 1080 20630 SUBCH 64 32 ASYNC13757K 990.7 700.5 LOCK 0 0.00.00.0 0.0 CHANGED 11244K INCLUDED IN ASYNC TOTAL12M 62.8 note2: Subchannel DELAYED REQUESTS %=62.8 Report 3 :COUPLING FACILITY STRUCTURE ACTIVITY from RMF Postprocessor C O U P L I N G F A C I L I T Y A C T I V I T Y PAGE 121 z/OS V2R2 SYSPLEX PLEXNP1 DATE 11/15/2017 INTERVAL 015.00.000 RPT VERSION V2R2 RMFTIME 23.45.00 CYCLE 01.000 SECONDS -- COUPLING FACILITY NAME = BPC3C1 -- COUPLING FACILITY STRUCTURE ACTIVITY STRUCTURE NAME = DSNEP01_GBP16K1 TYPE = CACHE STATUS = ACTIVE # REQ-- REQUESTS - -- DELAYED REQUESTS - SYSTEMTOTAL # % OF -SERV TIME(MIC)-REASON# % OF AVG TIME(MIC) - NAME AVG/SEC REQALL AVG STD_DEVREQ REQ /DELSTD_DEV /ALL NP1A 7474K SYNC254K0.419.5 62.4 NO SCH 7012K 93.8 2463 1074 2311 8304ASYNC 7220K 11.6 1433.0569.2 PR WT 0 0.00.00.00.0 CHNGD 7098K 11.4 INCLUDED IN ASYNC PR CMP0 0.00.00.00.0 SUPPR 0 0.0 DUMP 0 0.00.00.00.0 note3 : Subchannel DELAYED REQUESTS %=93.8% Our question: 1 Why these three report is difference for Subchannel Delay? 2 Why The Subchannel Delay is just 0.1% in CFSYS ? Thanks a lot!Best Regards, Jason Cai -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Shocking Bug in Latest PCOMM Release
On 11/21/2017 6:57 PM, Tom Conley wrote: LOL that you expect a reasonable default keyboard. WAKE UP, MAN! This problem is not caused by a messed up keyboard map. Incredibly, the DEL key simply does not work any more! Believe it or not, as inconvenient as it is, it's actually a *less* serious bug than what I had been dealing with in PCOMM 12.02. (Buffer overruns i.e., input not accepted properly if one types too fast over a remote connection!) I was perfectly happy with PCOMM 6.x and never would have upgraded except that it didn't work with the Windows 10 Creators Update Edition. It seems that IBM's testing of this product has become shoddy at best. The developers are PC developers and not 3270 users. Clearly they don't "eat" their own "cooking." -- Phoenix Software International Edward E. Jaffe 831 Parkview Drive North El Segundo, CA 90245 http://www.phoenixsoftware.com/ -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Shocking Bug in Latest PCOMM Release
Tom Brennan Vista? Charles -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Ed Jaffe Sent: Tuesday, November 21, 2017 7:37 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Shocking Bug in Latest PCOMM Release On 11/21/2017 6:57 PM, Tom Conley wrote: > > LOL that you expect a reasonable default keyboard. WAKE UP, MAN! This problem is not caused by a messed up keyboard map. Incredibly, the DEL key simply does not work any more! Believe it or not, as inconvenient as it is, it's actually a *less* serious bug than what I had been dealing with in PCOMM 12.02. (Buffer overruns i.e., input not accepted properly if one types too fast over a remote connection!) I was perfectly happy with PCOMM 6.x and never would have upgraded except that it didn't work with the Windows 10 Creators Update Edition. It seems that IBM's testing of this product has become shoddy at best. The developers are PC developers and not 3270 users. Clearly they don't "eat" their own "cooking." -- Phoenix Software International Edward E. Jaffe 831 Parkview Drive North El Segundo, CA 90245 http://www.phoenixsoftware.com/ -- 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: Shocking Bug in Latest PCOMM Release
Two words. Vista TN3270. . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-543-6132 Office ⇐=== NEW robin...@sce.com -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Ed Jaffe Sent: Tuesday, November 21, 2017 7:37 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: (External):Re: Shocking Bug in Latest PCOMM Release On 11/21/2017 6:57 PM, Tom Conley wrote: > > LOL that you expect a reasonable default keyboard. WAKE UP, MAN! This problem is not caused by a messed up keyboard map. Incredibly, the DEL key simply does not work any more! Believe it or not, as inconvenient as it is, it's actually a *less* serious bug than what I had been dealing with in PCOMM 12.02. (Buffer overruns i.e., input not accepted properly if one types too fast over a remote connection!) I was perfectly happy with PCOMM 6.x and never would have upgraded except that it didn't work with the Windows 10 Creators Update Edition. It seems that IBM's testing of this product has become shoddy at best. The developers are PC developers and not 3270 users. Clearly they don't "eat" their own "cooking." -- Phoenix Software International Edward E. Jaffe 831 Parkview Drive North El Segundo, CA 90245 http://www.phoenixsoftware.com/ -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Shocking Bug in Latest PCOMM Release
On 11/21/2017 7:43 PM, Charles Mills wrote: Tom Brennan Vista? We use that too (an excellent product). We use most of the most well-known emulators: PCOMM, Extra!, BlueZone, Hummingbird, QWS3270, etc. even x3270 I know Tom "eats" his own "cooking," probably with a fork, knife, and spoon... -- Phoenix Software International Edward E. Jaffe 831 Parkview Drive North El Segundo, CA 90245 http://www.phoenixsoftware.com/ -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Shocking Bug in Latest PCOMM Release
I eat the same cooking. Have not used any other emulator since Tom moseyed by my desk one day eons ago and said, I'd like you to try this out. I was hooked. But I understand the need to keep one's feet wet in different emulators. Even Tom did that for several reasons. Ha! I was more of purist than Tom. ;-) . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-543-6132 Office ⇐=== NEW robin...@sce.com -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Ed Jaffe Sent: Tuesday, November 21, 2017 7:50 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: (External):Re: Shocking Bug in Latest PCOMM Release On 11/21/2017 7:43 PM, Charles Mills wrote: > Tom Brennan Vista? We use that too (an excellent product). We use most of the most well-known emulators: PCOMM, Extra!, BlueZone, Hummingbird, QWS3270, etc. even x3270 I know Tom "eats" his own "cooking," probably with a fork, knife, and spoon... -- Phoenix Software International Edward E. Jaffe 831 Parkview Drive North El Segundo, CA 90245 http://www.phoenixsoftware.com/ -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Shocking Bug in Latest PCOMM Release
On 22/11/2017 11:36 AM, Ed Jaffe wrote: LOL that you expect a reasonable default keyboard. WAKE UP, MAN! This problem is not caused by a messed up keyboard map. Incredibly, the DEL key simply does not work any more! Believe it or not, as inconvenient as it is, it's actually a *less* serious bug than what I had been dealing with in PCOMM 12.02. (Buffer overruns i.e., input not accepted properly if one types too fast over a remote connection!) I was perfectly happy with PCOMM 6.x and never would have upgraded except that it didn't work with the Windows 10 Creators Update Edition. It seems that IBM's testing of this product has become shoddy at best. The developers are PC developers and not 3270 users. Clearly they don't "eat" their own "cooking." It's disconcerting that IBM don't seem to have automated regressions tests for PCOMM! A broken delete key is an absolute howler. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Shocking Bug in Latest PCOMM Release
On 11/21/2017 8:44 PM, Jesse 1 Robinson wrote: Two words. Vista TN3270. One word: x3270 -- Jack J. Woehr # Science is more than a body of knowledge. It's a way of www.well.com/~jax # thinking, a way of skeptically interrogating the universe www.softwoehr.com # with a fine understanding of human fallibility. - Carl Sagan -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: doubt on catalog
is it possible to copy master catalog of sys A to SYST ? On Mon, Nov 20, 2017 at 6:33 PM, johnnydeep san wrote: > on RDZ ,SYSA lpar we mentioned script like this" 0A91 3390 > C:\**\***\ " , is non-sms volume i installed product > using smpe and place the all required data-set on > . Now we planned to use the same product on SYST , instead of > installing the product from scratch , we planed to go with volume transfer > . so we include the below > " 0A91 3390 C:\**\***\ " on SYST devmap. > > On Mon, Nov 20, 2017 at 5:36 AM, Elardus Engelbrecht < > elardus.engelbre...@sita.co.za> wrote: > >> johnnydeep san wrote: >> >> >>Is the dasd shared? Or did you transfer to new system? >> >DASD is not shared , i transferred to new system >> >> How did you transferred them to the new system? Perhaps you used >> incorrect settings or cataloging process. >> >> Please post the job and results of your transfer attempt. >> >> Groete / Greetings >> Elardus Engelbrecht >> >> -- >> 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: Shocking Bug in Latest PCOMM Release
On 22/11/2017 1:36 PM, Jack J. Woehr wrote: On 11/21/2017 8:44 PM, Jesse 1 Robinson wrote: Two words. Vista TN3270. One word: x3270 There's not much choice on Linux. x3270 is full of bugs and not well maintained. What we need is more cross-platform browser based 3270 emulators like the Mocha TN3270 chrome app. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Shocking Bug in Latest PCOMM Release
>It seems that IBM's testing of this product has become shoddy at best. The developers are PC developers and not 3270 users. Clearly they don't "eat" their own "cooking." Silly man: assuming that there's anybody left at IBM to test anything any more! Don't be daft. With fewer than 25K domestic employees, who's got time to test?! Just ship it. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Finally joined Linkedin
welcome back! ITschak On Tue, Nov 21, 2017 at 9:23 PM, Seymour J Metz wrote: > I've been inactive since my Internet provider folded up with no advance > notice. A lot has happened since then, most of which is off topic, but it > seems reasonable to post here that I've finally oined LinkedIn from e-mail > address sme...@gmu.edu. For those of you who are on LinkedIn and know me, > feel free to connect. > > > -- > Shmuel (Seymour J.) Metz > http://mason.gmu.edu/~smetz3 > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- ITschak Mugzach *|** IronSphere Platform* *|** Automatic ISCM** (Information Security Contiguous Monitoring) **| * -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN