Re: Does ROUND dataset allocation mean cylinder boundary?
Cylinder allocation (and therefore ROUND used with average block or average record) allows faster input/output of sequential data sets than does track allocation. Unfortunately, since ECKD was introduced, this statement is inaccurate. If the I/O is within a defined extent, then track/cylinder boundaries are irrelevent. Prior to ECKD, the allocation method mattered because the C/U had to check at the boundary (track or cylinder) to see whether the I/O was allowed. So, cylinder allocation was more efficient. With defined extents, either allocation is acceptable. I simplified the above explanation. IBM had an 'orange book' that explained this in great detail, when ECKD was first introduced. I managed to obtain a copy before IBM withdrew it from public distribution, because it told the PCM's too much. - Ted MacNEIL eamacn...@yahoo.ca -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Remote printers are Drained
Hi, We have got many remote printers are configured to mainframe via TCPIP address. Fort the past 2 weeks we are getting lot of cases that these printers are becoming DRAINED after printing the reports instead of becoming INACTIVE. So we need manually restart the printers each time. Please let me know what could have gone wrong. Regards, Thangavelu Please do not print this email unless it is absolutely necessary. The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Does R OUND datas et allocat ion mean c ylinder bo undary?
Like old soldiers this topic never dies. It does not even fade away monotonically. Consult the archives. The last time we went round (and round) about it o ROUND, while innocuous, no longer improved the performance of sequential datasets; but o ROUND did still measurably improve the performance of PDSs, though not of PDSEs. At that time there was a sort of commitment on the part of one of the senior IBM posters here that he would, when he found the time, remedy this situation, removing the exception for PDSs; and if he has done so I am sure he will chime in to say that he has. The hardware issue, when DASD did indeed spin, was that allocations in TRK units set the device mask foir an interrupt at each end-of-track, for a run through a long block of code IOCS to ensure that the next track was a part of in the data set being processed, while allocations in CYL units set the device mask for this interrupt only at each end-of-cylinder, i.e., for much less frequent runs throug this code. Old men and women in this business thus found themselves repeating the litany comma, comma, comma, round over and over again to the young, who had unwonted difficulty with positional parameters and vacuous-comma coding. It would be nice to know that this issue has now been resolved definitively, but in this OCO era only IBM can tell us that it has been. John Gilmore Ashland, MA 01721-1817 USA -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Does R OUND datas et allocat ion mean c ylinder bo undary?
On Wed, 2011-02-02 at 08:31 -0500, john gilmore wrote: Old men and women in this business thus found themselves repeating the litany comma, comma, comma, round over and over again to the young Um... comma, comma, contig, comma, round? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Ñ(X'69') character and SYSLOG display
On Tue, 1 Feb 2011 15:50:40 -0500, Shmuel Metz (Seymour J.) shmuel+ibm- m...@patriot.net wrote: I believe that he is running into a restriction in console processing. -- Correct. WTOs, WTORs and WTLs have always been restricted to a subset of code- page 037 character set 697. Specifically, the following characters: A through Z 0 through 9 characters + * / , . ( ) ' - = : % ? ; and blank Some additional code-points are not translated to blanks. Here is the complete translate table: x0 x1 x2 x3 x4 x5 x6 x7 x8 x9 xA xB xC xD xE xF - 0x | 40 40 40 40 40 40 40 40 40 40 40 40 40 40 4C 6E .. 1x | 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 2x | 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 3x | 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 4x | 40 40 40 40 40 40 40 40 40 40 4A 4B 4C 4D 4E 4F ..¢.(+| 5x | 50 40 40 40 40 40 40 40 40 40 5A 5B 5C 5D 5E 5F .!$*);^ 6x | 60 61 40 40 40 40 40 40 40 40 40 6B 6C 6D 6E 6F -/.,%_? 7x | 40 40 40 40 40 40 40 40 40 40 7A 7B 7C 7D 7E 7F ..:#@'= 8x | 40 81 82 83 84 85 86 87 88 89 40 40 40 40 40 40 .abcdefghi.. 9x | 40 91 92 93 94 95 96 97 98 99 40 40 40 40 40 40 .jklmnopqr.. Ax | 40 40 A2 A3 A4 A5 A6 A7 A8 A9 40 40 40 40 40 40 ..stuvwxyz.. Bx | 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 40 Cx | 40 C1 C2 C3 C4 C5 C6 C7 C8 C9 40 40 40 40 40 40 .ABCDEFGHI.. Dx | 40 D1 D2 D3 D4 D5 D6 D7 D8 D9 40 40 40 40 40 40 .JKLMNOPQR.. Ex | 40 40 E2 E3 E4 E5 E6 E7 E8 E9 40 40 40 40 40 40 ..STUVWXYZ.. Fx | F0 F1 F2 F3 F4 F5 F6 F7 F8 F9 40 40 40 40 40 40 0123456789.. The restriction is largely historical and due to shortcomings in early print and display hardware. - Early printers (1403) did not support lower-case and other code-points due to the impact printing technology in use at the time. Supporting lower-case and additional codepoints significantly reduced printing speed, even when those codepoints were not being used. At the time, SYSLOG went directly to a printer, not a data set, so the system could be constrained to operate at printer speed. - Early display devices (2260, early 3270) did not support lower-case or other code-points due to the additional circuitry that was required to store the additional character images. Fast read-only memory was very expensive at the time. - Lower-case (and other) English code-points collided with the codepoints used by the Japanese Katakana phonetic alphabet. The first two restrictions have been dealt with by non-impact printing technology and increases in circuit density and are no longer an issue. The third restriction has been handled by incorporating the Katakana character set into the double-byte Kanji character set. Katakana-only display devices have ceased to exist. While we have eased the restriction on the use of lower-case a through z characters in messages, we have not removed the restriction on the use of other code-points, although we have had a proposal to do so. The proposal died due to a lack of formal customer requirements that we fix the problem. W. Kevin Kelley -- IBM POK Lab -- z/OS Core Technical Development -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Ñ(X'69') character and SYSLOG display
On 2/2/2011 6:50 AM, W. Kevin Kelley wrote: While we have eased the restriction on the use of lower-case a through z characters in messages, we have not removed the restriction on the use of other code-points, although we have had a proposal to do so. The proposal died due to a lack of formal customer requirements that we fix the problem. This restriction must be for consoles only. I see those other characters in the log. +1+2+3+4+5+6+7+ N 0001000 MVS602011032 08:00:40.32 0090 SEÑORITA D4FFF4DEEFFFFF4FF7FF7FF4FF4444EC6DDCEC 51452602011032008A00A40B32900025969931 -- -- Edward E Jaffe Phoenix Software International, Inc 831 Parkview Drive North El Segundo, CA 90245 310-338-0400 x318 edja...@phoenixsoftware.com http://www.phoenixsoftware.com/ -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Ends an ISPF session.
Good morning. Once you have set the defaults for log/list (or your user has) key =x;; (2 semi-colons) This will bypass this panel and take them to the TSO ready prompt. Robbie -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Ends an ISPF session.
Helio, All of the previous responses referenced the user manually changing their personal settings and that must be done on every instance of your ISPF Profile dataset. For a single system environment, you are doing this only one time. For large environments(Multi-LPAR,Multi-PLEX) you would have to perform this manual step for each system that you sign on to. The Systems Programmer responsible for ISPF can set the Log and List dataset defaults by using the ISPF Dialog ISPCCONF. This is documented in the Planning and Customization guide. The key variables are LOG_DATA_SET_DISPOSITION LOG_PAGES_PRIMARY_QUANTITY LOG_PAGES_SECONDARY_QUANTITY If the installation decides to default to No Log Dataset then LOG_DATA_SET_DISPOSITION should be coded to default Delete and LOG_PAGES_PRIMARY_QUANTITY coded for 0 (Zero) Pages. For consistency sake, I also code LOG_PAGES_SECONDARY_QUANTITY as zero also. The defaults are used when a fresh Profile dataset is used(i.e. first time signon or delete/reallocate User's Profile Dataset). Gene -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Ends an ISPF session.
Gene, Also consider shared ISPF profiles for a multisystem environment. That's what we have done. Once profile dataset for all systems in the plex. For SDSF we added code prior to calling SDSf and afterwards that restores/saves your system commands on a per system basis to your ispf profile _ Dave Jousma Assistant Vice President, Mainframe Services david.jou...@53.com 1830 East Paris, Grand Rapids, MI 49546 MD RSCB1G p 616.653.8429 f 616.653.8497 -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Gene Soo Sent: Wednesday, February 02, 2011 10:41 AM To: IBM-MAIN@bama.ua.edu Subject: Re: Ends an ISPF session. Helio, All of the previous responses referenced the user manually changing their personal settings and that must be done on every instance of your ISPF Profile dataset. For a single system environment, you are doing this only one time. For large environments(Multi-LPAR,Multi-PLEX) you would have to perform this manual step for each system that you sign on to. The Systems Programmer responsible for ISPF can set the Log and List dataset defaults by using the ISPF Dialog ISPCCONF. This is documented in the Planning and Customization guide. The key variables are LOG_DATA_SET_DISPOSITION LOG_PAGES_PRIMARY_QUANTITY LOG_PAGES_SECONDARY_QUANTITY If the installation decides to default to No Log Dataset then LOG_DATA_SET_DISPOSITION should be coded to default Delete and LOG_PAGES_PRIMARY_QUANTITY coded for 0 (Zero) Pages. For consistency sake, I also code LOG_PAGES_SECONDARY_QUANTITY as zero also. The defaults are used when a fresh Profile dataset is used(i.e. first time signon or delete/reallocate User's Profile Dataset). Gene -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html 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...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Does ROUND dataset allocation mean cylinder boundary?
You're quite, Ron. It dates back to the days of SLEDs. Rick --- Ron Hawkins wrote: While it may be in the manual, I don't think this statement has been true for several decades. Cylinder allocation (and therefore ROUND used with average block or average record) allows faster input/output of sequential data sets than does track allocation. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Ñ(X'69') character and SYSLOG display
On Wed, 2 Feb 2011 07:25:23 -0800, Edward Jaffe edja...@phoenixsoftware.com wrote: On 2/2/2011 6:50 AM, W. Kevin Kelley wrote: While we have eased the restriction on the use of lower-case a through z characters in messages, we have not removed the restriction on the use of other code-points, although we have had a proposal to do so. The proposal died due to a lack of formal customer requirements that we fix the problem. This restriction must be for consoles only. I see those other characters in the log. Was your WTO issued by a program in supervisor state or key zero? The restriction might not apply to such programs. +1+2+3+4+5+6+- N 0001000 MVS602011032 08:00:40.32 0090 SEÑORITA D4FFF4DEEFFFFF4FF7FF7FF4FF4444EC6DDC EC 51452602011032008A00A40B329000259699 31 - -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Ends an ISPF session.
Many people have responded and maybe this solution has already been given. In general the LOG dataset is created when certain functions are done all along in the ISPF session. Only twice in my career did I care. So setting the OPTION to 2 to delete it when I am done seemed wasteful. WHY CREATE IT IN THE FIRST PLACE Go to Option 0, select LOG Defaults (1) and you will see a panel to complete. You can put 2 as the option but below you will see Primary Pages and Secondary Pages. These somehow equate to a space allocation for the LOG File. Change these to 0 (zero) and in the future when it goes to allocate the log, ISPF sees no space is to be allocated: a. It does not allocate the file. b. It will not write to the file along the way c. There is no need to delete the file at the end of the session. d. If for any reason, you need it, change the settings to values and use it. My customer at the time (wife who was my paying customer) complained about when she got into ISPF it always seemed like it went off for 4-5 seconds first thing and then was fine as far as response. I surmised it was the dynamic allocation for the file. In the 1990s we even had STK and Memorex 3380s and it was noticeable. She made the changes and no more delays to get started. I never figured out what the constant logging was doing as I was working. But the best I/O delay is the one you never make happen. I still spread the word today only because of all the SPFLOGn files left out on DASD and then our Storage Person has routines to sweep them away after a while. jim -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Does R OUND datas et allocat ion mean c ylinder bo undary?
Like old soldiers this topic never dies. It does not even fade away monotonically. Consult the archives. The last time we went round (and round) about it o ROUND, while innocuous, no longer improved the performance of sequential datasets; but o ROUND did still measurably improve the performance of PDSs, though not of PDSEs. At that time there was a sort of commitment on the part of one of the senior IBM posters here that he would, when he found the time, remedy this situation, removing the exception for PDSs; and if he has done so I am sure he will chime in to say that he has. The hardware issue, when DASD did indeed spin, was that allocations in TRK units set the device mask foir an interrupt at each end-of- track, for a run through a long block of code IOCS to ensure that the next track was a part of in the data set being processed, while allocations in CYL units set the device mask for this interrupt only at each end-of-cylinder, i.e., for much less frequent runs throug this code. Old men and women in this business thus found themselves repeating the litany comma, comma, comma, round over and over again to the young, who had unwonted difficulty with positional parameters and vacuous-comma coding. It would be nice to know that this issue has now been resolved definitively, but in this OCO era only IBM can tell us that it has been. Greg Dyck changed IEWFETCH to use ECKD in z/OS 1.7, which remedied the situation for fetching load modules from PDSes. He moved to DB2 Development several years ago, so I doubt that he follows IBM-MAIN any more. Jim Mulder z/OS System Test IBM Corp. Poughkeepsie, NY -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Does R OUND datas et allocat ion mean c ylinder bo undary?
Greg Dyck changed IEWFETCH to use ECKD in z/OS 1.7, which remedied the situation for fetching load modules from PDSes. He moved to DB2 Development several years ago, so I doubt that he follows IBM-MAIN any more. Pity. He is a really good guy to work with. Our loss, DB2's gain. Bob Shannon Rocket Software -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Does R OUND datas et allocat ion mean c ylinder bo undary?
I thought I heard that Greg was going to work on multi-tasking for DB2. I agree. Greg was a wonderful contributor for IBM-Main. Rob -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Does R OUND datas et allocat ion mean c ylinder bo undary?
On 2/2/2011 9:34 AM, Bob Shannon wrote: Greg Dyck changed IEWFETCH to use ECKD in z/OS 1.7, which remedied the situation forfetching load modules from PDSes. He moved to DB2 Development several years ago, so I doubtthat he follows IBM-MAIN any more. Pity. He is a really good guy to work with. Our loss, DB2's gain. Greg would rather live in central California than in the mid-Hudson valley. :-X -- Edward E Jaffe Phoenix Software International, Inc 831 Parkview Drive North El Segundo, CA 90245 310-338-0400 x318 edja...@phoenixsoftware.com http://www.phoenixsoftware.com/ -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Does ROUND dataset allocation mean cylinder boundary?
David Andrews wrote: | Um... comma, comma, contig, round which appears to be a polite attempted correction of the litany I provided. If it is, it is a misconceived one. The two requirements--those of contiguity and rounding to a cylinder boundary--are/were independent ones. John Gilmore Ashland, MA 01721-1817 USA -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
STGADMIN.ADR.DUMP.TOLERATE.ENQF
STGADMIN.ADR.DUMP.TOLERATE.ENQF is required for a user to use TOLERATE(ENQF) on a DSS dump. What is the security issue this is protecting against? Or is it just more of a data integrity issue? -- Frank Swarbrick Applications Architect - Mainframe Applications Development FirstBank Data Corporation - Lakewood, CO USA P: 303-235-1403 The information contained in this electronic communication and any document attached hereto or transmitted herewith is confidential and intended for the exclusive use of the individual or entity named above. If the reader of this message is not the intended recipient or the employee or agent responsible for delivering it to the intended recipient, you are hereby notified that any examination, use, dissemination, distribution or copying of this communication or any part thereof is strictly prohibited. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy this communication. Thank you. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Ends an ISPF session.
The Return command (PF4) does the same thing. I used that for many years until I found the Bye command that does the same thing as Return plus it will log out of TSO. Return is an ISPF command. Bye looks like it was setup in house, but I'm not sure. Thank you and have a Terrific day! Jonathan Goossen Tape Specialist ACT Mainframe Storage Group 651-361-4541 IBM Mainframe Discussion List IBM-MAIN@bama.ua.edu wrote on 02/02/2011 09:40:23 AM: From: Robbie McCoy ramc...@srpnet.com To: IBM-MAIN@bama.ua.edu Date: 02/02/2011 09:41 AM Subject: Re: Ends an ISPF session. Sent by: IBM Mainframe Discussion List IBM-MAIN@bama.ua.edu Good morning. Once you have set the defaults for log/list (or your user has) key =x;; (2 semi-colons) This will bypass this panel and take them to the TSO ready prompt. Robbie -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html This e-mail message and all attachments transmitted with it may contain legally privileged and/or confidential information intended solely for the use of the addressee(s). If the reader of this message is not the intended recipient, you are hereby notified that any reading, dissemination, distribution, copying, forwarding or other use of this message or its attachments is strictly prohibited. If you have received this message in error, please notify the sender immediately and delete this message and all copies and backups thereof. Thank you. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: STGADMIN.ADR.DUMP.TOLERATE.ENQF
It's just data integrity, as far as I know, preventing those that don't know better from shooting themselves in the foot ;-) On Wed, Feb 2, 2011 at 1:15 PM, Frank Swarbrick frank.swarbr...@efirstbank.com wrote: STGADMIN.ADR.DUMP.TOLERATE.ENQF is required for a user to use TOLERATE(ENQF) on a DSS dump. What is the security issue this is protecting against? Or is it just more of a data integrity issue? -- Frank Swarbrick Applications Architect - Mainframe Applications Development FirstBank Data Corporation - Lakewood, CO USA P: 303-235-1403 The information contained in this electronic communication and any document attached hereto or transmitted herewith is confidential and intended for the exclusive use of the individual or entity named above. If the reader of this message is not the intended recipient or the employee or agent responsible for delivering it to the intended recipient, you are hereby notified that any examination, use, dissemination, distribution or copying of this communication or any part thereof is strictly prohibited. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy this communication. Thank you. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html CONFIDENTIALITY/EMAIL NOTICE: The material in this transmission contains confidential and privileged information intended only for the addressee. If you are not the intended recipient, please be advised that you have received this material in error and that any forwarding, copying, printing, distribution, use or disclosure of the material is strictly prohibited. If you have received this material in error, please (i) do not read it, (ii) reply to the sender that you received the message in error, and (iii) erase or destroy the material. Emails are not secure and can be intercepted, amended, lost or destroyed, or contain viruses. You are deemed to have accepted these risks if you communicate with us by email. Thank you. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Ends an ISPF session.
On 2/2/2011 11:34 AM, Jonathan Goossen wrote: The Return command (PF4) does the same thing. I used that for many years until I found the Bye command that does the same thing as Return plus it will log out of TSO. Return is an ISPF command. Bye looks like it was setup in house, but I'm not sure. Thank you and have a Terrific day! Jonathan Goossen Tape Specialist ACT Mainframe Storage Group 651-361-4541 Yes, it is not a standard command. My colleague, Hunter Cobb, set up a command for us called 'byebye'; this command is issued from Ready prompt and checks to see if there are any other users on our z/OS system; if there are, it just exits, but if there are no other users it puts the z/OS system to sleep (we run under z/VM) so as not to use any more resources. -- Kind regards, -Steve Comstock The Trainer's Friend, Inc. 303-393-8716 http://www.trainersfriend.com * To get a good Return on your Investment, first make an investment! + Training your people is an excellent investment * Try our new tool for calculating your Return On Investment for training dollars at http://www.trainersfriend.com/ROI/roi.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Remote printers are Drained
Hi Thangavelu, What software are you using to send the output to the printers? Have you seen any error messages? Have any changes been made? Does the problem affect all of your printers or just one or two? If you can give us more information, we can probably help. Regards, Linda - Original Message - From: Chokalingam Thangavelu thangavelu.chokalin...@wipro.com To: IBM-MAIN@bama.ua.edu Sent: Wednesday, February 2, 2011 12:55:06 AM Subject: Remote printers are Drained Hi, We have got many remote printers are configured to mainframe via TCPIP address. Fort the past 2 weeks we are getting lot of cases that these printers are becoming DRAINED after printing the reports instead of becoming INACTIVE. So we need manually restart the printers each time. Please let me know what could have gone wrong. Regards, Thangavelu Please do not print this email unless it is absolutely necessary. The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Does ROUND dataset allocation mean cylinder boundary?
Ric, Ted got it right. It changed while we were still on SLEDs. Ron -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Rick Fochtman Sent: Wednesday, February 02, 2011 9:44 AM To: IBM-MAIN@bama.ua.edu Subject: Re: [IBM-MAIN] Does ROUND dataset allocation mean cylinder boundary? You're quite, Ron. It dates back to the days of SLEDs. Rick --- Ron Hawkins wrote: While it may be in the manual, I don't think this statement has been true for several decades. Cylinder allocation (and therefore ROUND used with average block or average record) allows faster input/output of sequential data sets than does track allocation. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: STGADMIN.ADR.DUMP.TOLERATE.ENQF
Scott, But allowing us who DO know better to still shoot ourselves in the foot. :-) Rex -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Does ROUND dataset allocation mean cylinder boundary?
On Wed, 2011-02-02 at 13:20 -0500, john gilmore wrote: | Um... comma, comma, contig, round which appears to be a polite attempted correction of the litany I provided. No, you simply reminded me of a relic of the past that I can *still* find in my proclibs. As you say, it is another problem. (I would not lightly dare to correct you.) -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Does ROUND dataset allocation mean cylinder boundary?
I'm not disagreeing with or correcting anybody. I wanted to point out that I was just helping out the hobbit with some explicit references to cylinder allocation via use of the ROUND option. As much as anything else, I was indicating that one should always read both JCL volumes, the Reference and the User's Guide. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: STGADMIN.ADR.DUMP.TOLERATE.ENQF
Of course! ;-) On Wed, Feb 2, 2011 at 2:39 PM, Rex Pommier rex.pomm...@cnasurety.comwrote: Scott, But allowing us who DO know better to still shoot ourselves in the foot. :-) Rex -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html CONFIDENTIALITY/EMAIL NOTICE: The material in this transmission contains confidential and privileged information intended only for the addressee. If you are not the intended recipient, please be advised that you have received this material in error and that any forwarding, copying, printing, distribution, use or disclosure of the material is strictly prohibited. If you have received this material in error, please (i) do not read it, (ii) reply to the sender that you received the message in error, and (iii) erase or destroy the material. Emails are not secure and can be intercepted, amended, lost or destroyed, or contain viruses. You are deemed to have accepted these risks if you communicate with us by email. Thank you. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
STCK vs TIMUSED
Using STCK as Wall time and TIMEUSED as CPU time without any Parms (TIMEUSED) defaults to TOD Format I am finding TIMEUSED STCK. I have before and after pair for each Sent from my iPhone -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: STCK vs TIMUSED
On 2/2/2011 2:35 PM, Micheal Butz wrote: Using STCK as Wall time and TIMEUSED as CPU time without any Parms (TIMEUSED) defaults to TOD Format I am finding TIMEUSED STCK. I have before and after pair for each TIMEUSED cannot be greater than current TOD returned by STCK. Think about it. TOD clock (STCK) has been counting since Jan 1, 1900 at 0 AM. TIMEUSED has been counting only since your unit of work started. -- Edward E Jaffe Phoenix Software International, Inc 831 Parkview Drive North El Segundo, CA 90245 310-338-0400 x318 edja...@phoenixsoftware.com http://www.phoenixsoftware.com/ -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: STCK vs TIMUSED
I think what the OP meant was that TIMEUSED was giving back a value greater than the end-time STCK minus start-time STCK recorded in his code. I would guess this might be possible in a multi-CPU environment where more than one unit of work in the address space is running on more than one CPU, simultaneously. (yucky phrasing) But I could be wrong about that interpretation of his original message, of course. On Wed, 2011-02-02 at 14:46 -0800, Edward Jaffe wrote: On 2/2/2011 2:35 PM, Micheal Butz wrote: Using STCK as Wall time and TIMEUSED as CPU time without any Parms (TIMEUSED) defaults to TOD Format I am finding TIMEUSED STCK. I have before and after pair for each TIMEUSED cannot be greater than current TOD returned by STCK. Think about it. TOD clock (STCK) has been counting since Jan 1, 1900 at 0 AM. TIMEUSED has been counting only since your unit of work started. -- John McKown Maranatha! -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: STCK vs TIMUSED
I am just subtracting the before and after microseconds portion ignoring date and time Sent from my iPhone On Feb 2, 2011, at 5:46 PM, Edward Jaffe edja...@phoenixsoftware.com wrote: On 2/2/2011 2:35 PM, Micheal Butz wrote: Using STCK as Wall time and TIMEUSED as CPU time without any Parms (TIMEUSED) defaults to TOD Format I am finding TIMEUSED STCK. I have before and after pair for each TIMEUSED cannot be greater than current TOD returned by STCK. Think about it. TOD clock (STCK) has been counting since Jan 1, 1900 at 0 AM. TIMEUSED has been counting only since your unit of work started. -- Edward E Jaffe Phoenix Software International, Inc 831 Parkview Drive North El Segundo, CA 90245 310-338-0400 x318 edja...@phoenixsoftware.com http://www.phoenixsoftware.com/ -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Does ROUND dataset allocation mean cylinder boundary?
I'm not disagreeing with or correcting anybody. I wanted to point out that I was just helping out the hobbit with some explicit references to cylinder allocation via use of the ROUND option. As much as anything else, I was indicating that one should always read both JCL volumes, the Reference and the User's Guide. Unfortunately, the statements about cylinder allocation and performance are way out of date. Reading the pertaining to that will misinform you. - Ted MacNEIL eamacn...@yahoo.ca -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: STCK vs TIMUSED
Sent from my iPhone... again?? = I am just subtracting the before and after microseconds portion = ignoring date and time = = Sent from my iPhone = = On Feb 2, 2011, at 5:46 PM, Edward Jaffe edja...@phoenixsoftware.com = wrote: = = On 2/2/2011 2:35 PM, Micheal Butz wrote: = Using STCK as Wall time and TIMEUSED as CPU time without any Parms = (TIMEUSED) defaults to TOD = Format I am finding TIMEUSED STCK. I have before and after = pair for each = = TIMEUSED cannot be greater than current TOD returned by STCK. Think = about it. TOD clock (STCK) has been counting since Jan 1, 1900 at 0 = AM. TIMEUSED has been counting only since your unit of work started. = = -- = Edward E Jaffe = Phoenix Software International, Inc = 831 Parkview Drive North = El Segundo, CA 90245 = 310-338-0400 x318 = edja...@phoenixsoftware.com = http://www.phoenixsoftware.com/ = = -- = For IBM-MAIN subscribe / signoff / archive access instructions, = send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO = Search the archives at http://bama.ua.edu/archives/ibm-main.html = = -- = For IBM-MAIN subscribe / signoff / archive access instructions, = send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO = Search the archives at http://bama.ua.edu/archives/ibm-main.html = John Cassidy (Dipl.-Ingr.) EU -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: STGADMIN.ADR.DUMP.TOLERATE.ENQF
Frank Swarbrick pisze: STGADMIN.ADR.DUMP.TOLERATE.ENQF is required for a user to use TOLERATE(ENQF) on a DSS dump. What is the security issue this is protecting against? Or is it just more of a data integrity issue? No. An access to the resource STGADMIN.ADR.DUMP.TOLERATE.ENQF is NOT required to use TOL(ENQF). All the STGADMIN.ADR.everything-but-second-STGADMIN resources are used to *optionally* deny access. In other words: STGADMIN.ADR.non-STGADMIN - no profile means access for everyone. STGADMIN.ADR.STGADMIN.** - no profile means no access. That's big difference. Dangerous functions are denied by default, while other functions CAN be denied (controlled) if you wish so. IMHO it's state of the art usage of RACF profiles. -- Radoslaw Skorupka Lodz, Poland -- BRE Bank SA ul. Senatorska 18 00-950 Warszawa www.brebank.pl Sd Rejonowy dla m. st. Warszawy XII Wydzia Gospodarczy Krajowego Rejestru Sdowego, nr rejestru przedsibiorców KRS 025237 NIP: 526-021-50-88 Wedug stanu na dzie 16.07.2010 r. kapita zakadowy BRE Banku SA (w caoci wpacony) wynosi 168.248.328 zotych. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Remote printers are Drained
Chokalingam Thangavelu wrote: We have got many remote printers are configured to mainframe via TCPIP address. With what? Are you using a output writer scraping data from JES2/3 or is it something which accepts output from STCs? How are those printers connected via TCP/IP to your system? Via a pool of IP addreses or assigned LUs? Fort the past 2 weeks we are getting lot of cases that these printers are becoming DRAINED after printing the reports instead of becoming INACTIVE. All of them? Some of them? Only after certain jobs/output? How do you see the status of those printers? Did you do an upgrade or change somewhere? What level of z/OS and TCP/IP are you using? Please let me know what could have gone wrong. A lot, all the way from the output generators, through the data carriers up to the printers themselves, but then you gave too few information. See also Linda's response too. Groete / Greetings Elardus Engelbrecht -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
