Re: About dispatching process
So to answer the questions, once disabled the system has no way to interrupt you and you can starve everyone else out. But if you're *not* running disabled, which is the normal case, your program will get interrupted sooner or later. There will be other routines starting an I/O every now and then. If your program is executing on the very CPU that is in charge of handling I/O interrupts, your code will be interrupted as soon as that other program's I/O has finished. Just to name a single case out of the various reasons and kinds of interrupts that constantly happen. -- Peter Hunkeler Credit Suisse -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Healthcheck (IBMCSV,CSV_APF_EXISTS)
Was Barbara saying that other mechanisms than HSM were used to migrate data sets? If so, then we can consider some sort of rules parameter. I was talking about the time when our ISV data sets in APFlist were not SMS-managed. My RACFadmin used to complain a lot about apf datasets being migrated (command migration). This year we have converted to SMS, so this behaviour has stopped (more or less). I just did the same test the others did and got (predictably) the same ARC rc/rsn everyone else had *except* in the case where an APF-auth SMS dataset was only APF-auth'd on one system in the sysplex, not the other. From the other system the command migration went through without a hitch. Given that HC doesn't have XCF communication, but HSM definitely does - I thing in a sysplex HSM should prevent migration by first making sure the dataset in not in APF on *any* system in the sysplex. Now the second case of not using SMS but a volser works as far as APF is concerned but DFSMShsm does not recognize it and WILL migrate it. As you indicated, the APF-EXISTS health check recognizes this (had a lengthy discussion with a colleague who used volser on an SMS-managed dataset and was muttering about the HC). In this case, I think that CSV should not allow an SMS-managed dataset into APF when it is specified via volser (given that HC recognizes this as a bad practise!) The question is: *Can* CSV recognize that the data set is SMS managed when it does the IPL progxx-members? Best regards, Barbara -- Ist Ihr Browser Vista-kompatibel? Jetzt die neuesten Browser-Versionen downloaden: http://www.gmx.net/de/go/browser -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Healthcheck ((IBMCSV,CSV_APF_EXISTS)
Knutson, Sam wrote: CHECK(IBMCSV,CSV_APF_EXISTS) START TIME: 10/23/2007 20:03:57.740282 CHECK DATE: 20050720 CHECK SEVERITY: LOW A problem was found with each APF list entry displayed. VOLUME DSNAME ERROR G10078 U06T03.LOAD.TEST.APFMIG DS is SMS-managed DS is SMS-managed The data set is SMS-managed, but the APF list entry specified a volume. If the APF list entry represents a SMS-managed data set but has specified the volume parameter, the data set would not be authorized if it were moved to a different volume. In order for DFSMShsm to verify APF-authorization properly, the APF list entry must indicate that the data set is SMS-managed. I think you could make a good case for DFSMShsm not functioning correctly. It should refuse to migrate both since using SMS is recommended by not required by APF. The check's documentation states that, In order for [HSM] to verify APF-authorization properly, the APF list entry must indicate that the data set is SMS-managed. And, that's exactly what you've demonstrated here. HSM is unable to verify the APF property when an SMS-managed data set is improperly defined as non-SMS-managed in the APF list. So, the data set gets migrated in that case. In summary, HSM will allow migration when the APF list entry is erroneously defined: |Data Set is APF Entry Indicates Erroneous Can Be |SMS Managed SMS-Managed Definition Migrated? |--- --- -- - |YES YES NO NO |NO NO NO Not if matching volume |YES NO YES YES |NO YES YES YES So, the CSV_APF_EXISTS check is doing its job! Right? -- Edward E Jaffe Phoenix Software International, Inc 5200 W Century Blvd, Suite 800 Los Angeles, CA 90045 310-338-0400 x318 [EMAIL PROTECTED] http://www.phoenixsoftware.com/ -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: About dispatching process
However, if my program is also running disabled for external interrupts and it uses CPU cycles heavily , how will the system 'pre-empt' my TCB? Or it cannot and just let my TCB starve other users? So to answer the questions, once disabled the system has no way to interrupt you and you can starve everyone else out. Hate to, but I beg to differ :-) Disabling oneself for interrupts (if done correctly) means holding a spin lock. So sooner or later (if you have at least two processors in that lpar) excessive spin recovery will kick in and if set up correctly issue the restart interrupt. That usually takes care of the 'easier' forms of bugs. Won't work on a uni lpar, that one will just become unresponsive and you have to *know* that it may be a spin loop and you have to use the right icon on the HMC to interrupt that one. The spin loops that are caused by unexpected circular chains (SRM, RSM, dispatcher itself) are resolved by that excessive spin setup, too, but the spin will occur again right away on another processor because the code will run into the same circular chain. (The dispatcher protects itself against that by going into recovery and preventing every other processor from executing dispatcher code. On the one processor it will attempt to sort things out.) Getting rights to be authorized means you can then do just about anything you want, and you had better be careful I heartily agree. That's what my caveats above are meant to address. I believe once you're authorized you can go and do an LPSW with a predefined disabled psw *without* holding the proper locks. You're violating the architecture then. I had seen a spin loop sadump where a sysprog wanted to 'test' the SIGP instruction. He didn't know the first thing about the architecture around that SIGP instruction (I don't think it is externally documented), so obviously could not use it, but he brought down 'that' system. Regards, Barbara Nitz -- GMX FreeMail: 1 GB Postfach, 5 E-Mail-Adressen, 10 Free SMS. Alle Infos und kostenlose Anmeldung: http://www.gmx.net/de/go/freemail -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Outsmarting WLM (was: Re: Are there tasks that don't play by WLM's rules)
I had the idea of getting automation to listen to IEF404I BPXAS - ENDED - TIME=00.31.51 $HASP395 BPXASENDED (one of the two), and whenever it happens do the forks under the assumption that that will not hinder the *actual* work that needs it. Wouldn't is be sufficient to run the keep BPXAS alive program periodically, say every 15 minutes? The new childs would use idle BPXASs and WLM would create new ones if the ovefrall system load permits this. Two important things to consider no matter what method you choose: - Make sure you can stop the mechanism when sutting down z/OS for IPL. Part of the shutdown process is to stop all BPXASs to allow JES to come down. If you trigger by the BPXAS has ended message you might never get to the point where JES is dormant. - As I have never played with this, I cannot tell from experience, so you'd need to do some experiments. It is my understanding, that WLM decides if the system can cope with another BPXAS, and that WLM might refuse to start another one. I do not know the measures WLM uses to make that decision. fork() can return an error, saying that no child has been created. I don't know how fork() will behave when WLM decides not to allow another BPXAS. Will the kernel keep the reques outstanding until a BPXAS becomes available (unlikely) or will fork() return EAGAIN (likely) which tells the parent to try again. The possible problem I can see with the design of the keep BPXAS alive program is it might deadlock: To make sure it is using yx BPXASs it needs to create xy-1 children, which in turn need to wait for a terminate signal from the parent. The parent does not send the terminate signal before it could start all xy-1 children but further fork()s are failing due to WLM not allowing more BPXASs... Maybe its time to ask IBM to implement a way to tell WLM how many BPXASs shall be kept ready at all time. -- Peter Hunkeler Credit Suisse -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Outsmarting WLM (was: Re: Are there tasks that don't play by WLM's rules)
Barbara Nitz [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED]... First of all, my apologies to the original poster that I had appropriated his thread! I am finally changing the name I have checked with our resident unix people - a little program to do fork() will be easy to write. The trick will be to pick the point when to kick it off - I had the idea of getting automation to listen to Be careful: it was some time ago when I had my USS course, but I remember that there are fork()'s that can remain within the same address space and fork()'s that require a new (BPXAS) address space. Kees. ** For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch Airlines) is registered in Amstelveen, The Netherlands, with registered number 33014286 ** -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Outsmarting WLM (was: Re: Are there tasks that don't play by WLM's rules)
Be careful: it was some time ago when I had my USS course, but I remember that there are fork()'s that can remain within the same address space and fork()'s that require a new (BPXAS) address space. There are *processes* that can share an address space. If a new process is create with fork() it will run in a separate address space by definition. If it is created with spawn(), it may run in the same address space as the parent or it may run in a separete AS. (To complete the list: There is also the non-UNIX attach_mvs asm service which starts a new process in the parents AS. attach_mvs predates spawn()) -- Peter Hunkeler Credit Suisse -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Outsmarting WLM (was: Re: Are there tasks that don't play by WLM's rules)
Hunkeler Peter , KIUK 3 [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED]. ... Be careful: it was some time ago when I had my USS course, but I remember that there are fork()'s that can remain within the same address space and fork()'s that require a new (BPXAS) address space. There are *processes* that can share an address space. If a new process is create with fork() it will run in a separate address space by definition. If it is created with spawn(), it may run in the same address space as the parent or it may run in a separete AS. (To complete the list: There is also the non-UNIX attach_mvs asm service which starts a new process in the parents AS. attach_mvs predates spawn()) -- Peter Hunkeler Credit Suisse Thanks for the clarification. I remembered there was something, so I thought it useful to mention, expecting that someone would come up with the correct details. Kees. ** For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch Airlines) is registered in Amstelveen, The Netherlands, with registered number 33014286 ** -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: tso racf
George Fogg wrote: BTW, does the ISPF exits run authorized? I read the manual but not quite sure if they do. No. AC=00 by default. These exits must be re-usable, preferably reentrant, because they are loaded once during logon. AMODE=31, RMODE=ANY. HTH! Groete / Greetings Elardus Engelbrecht -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: JES2 / JES3 in same plex
Jerry, You're right, it can be done in a lab. I've seen it done in a lab. From my short experience in such a configuration, you should be aware of at least these basic issues: - You will need an additional program on top of SDSF to be able to view JES3's spool. I know (E)JES supports JES3 and JES2 as well. I seem to recall they had a usermod that changed (E)JES's behavior to ask you against which subsystem you wish to work before invoking (E)JES for real. - If your two JES3 images are not at the same JES3 level, you might need to keep two copies of the (E)JES libraries (or some other program you use for viewing the spool). I remember that (E)JES's ENV mod uses JES3's macro library, which changes from one JES3 level to the other. - They also changed TSO/E to ask you using which JES subsystem to logon. I think this code was published in an old Redbook, but sadly I can't find it now on the Redbooks web site. Hope this helps, Gil. On 10/23/07, J Ellis [EMAIL PROTECTED] wrote: does anyone have any experience with running JES2 and JES3 images within the same plex ? It can be done in the lab, I'm curious if anyone has tried it in production. I may need to merge two JES3 images into an exsiting JES2 plex. TIA and you can reply directly so as to not clutter up the list. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: About dispatching process
Chris, Thanks for your confirmation. Peter, Yes, I overlooked the situation you mentioned :) On 10/24/07, Hunkeler Peter (KIUK 3) [EMAIL PROTECTED] wrote: So to answer the questions, once disabled the system has no way to interrupt you and you can starve everyone else out. But if you're *not* running disabled, which is the normal case, your program will get interrupted sooner or later. There will be other routines starting an I/O every now and then. If your program is executing on the very CPU that is in charge of handling I/O interrupts, your code will be interrupted as soon as that other program's I/O has finished. Just to name a single case out of the various reasons and kinds of interrupts that constantly happen. -- Peter Hunkeler Credit Suisse -- Best Regards, Johnny Luo -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: About dispatching process
Barbara, Just after I sent my question to the list, I searched the bookshelves using the keyword 'loop' and surprisingly to find some useful information in a diagnostic book. I think what the manual says is the same as what you said. In a MP system, a disabled loop is observed as a spin loop by other processors. However, if you have only one processor, a disabled loop can bring a system outage. I must say it's very interesting. Suppose in a single-processor system, I write some codes which cause a disabled loop. How to handle it? Press 'restart' key like what we usually react in a windows system? :) On 10/24/07, Barbara Nitz [EMAIL PROTECTED] wrote: Disabling oneself for interrupts (if done correctly) means holding a spin lock. So sooner or later (if you have at least two processors in that lpar) excessive spin recovery will kick in and if set up correctly issue the restart interrupt. That usually takes care of the 'easier' forms of bugs. Won't work on a uni lpar, that one will just become unresponsive and you have to *know* that it may be a spin loop and you have to use the right icon on the HMC to interrupt that one. The spin loops that are caused by unexpected circular chains (SRM, RSM, dispatcher itself) are resolved by that excessive spin setup, too, but the spin will occur again right away on another processor because the code will run into the same circular chain. (The dispatcher protects itself against that by going into recovery and preventing every other processor from executing dispatcher code. On the one processor it will attempt to sort things out.) -- Best Regards, Johnny Luo -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: About dispatching process
Johnny Luo [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED]... Barbara, Just after I sent my question to the list, I searched the bookshelves using the keyword 'loop' and surprisingly to find some useful information in a diagnostic book. I think what the manual says is the same as what you said. In a MP system, a disabled loop is observed as a spin loop by other processors. This is not exactly true: A disabled loop by itsself will not generate a problem. However, other processors will regularly want to talk to the disabled processor, via the SIGP instruction. The calling processor will spin (in a disabled loop, therefor spin loop) waiting for an answer. The disabled called processor will of course not answer and the calling processor will detect this and generate an excessive spinloop time out condition. So the spinloop is a normal, short duration, situation; an excisive spinloop timeout is a condition detected by an active processor, where an other processor does not answer. This can be for many reasons, being disabled, hardware problems etc. etc. Have a look at Initialization and Tuning Reference, member EXCPATxx, for more information on spinloops. However, if you have only one processor, a disabled loop can bring a system outage. I must say it's very interesting. Suppose in a single-processor system, I write some codes which cause a disabled loop. How to handle it? Press 'restart' key like what we usually react in a windows system? :) Exactly. Kees. ** For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch Airlines) is registered in Amstelveen, The Netherlands, with registered number 33014286 ** -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: About dispatching process
I must say it's very interesting. Suppose in a single-processor system, I write some codes which cause a disabled loop. How to handle it? Press 'restart' key like what we usually react in a windows system? :) The difference being that you, the operator, get in control after pressing the restart key. You can then choose to abend the looping task. The system will continue to run thereafter. -- Peter Hunkeler Credit Suisse -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: About dispatching process
Peter, I checked POO and yes, RESTART interruption cannot be disabled so at least we have a final choice under such a situation. Never had the chance to use HMC (I guess the restart key must be there), do you mean after pressing it we will be prompted to select the action to take? On 10/24/07, Hunkeler Peter (KIUK 3) [EMAIL PROTECTED] wrote: I must say it's very interesting. Suppose in a single-processor system, I write some codes which cause a disabled loop. How to handle it? Press 'restart' key like what we usually react in a windows system? :) The difference being that you, the operator, get in control after pressing the restart key. You can then choose to abend the looping task. The system will continue to run thereafter. -- Peter Hunkeler Credit Suisse -- Best Regards, Johnny Luo -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: About dispatching process
Never had the chance to use HMC (I guess the restart key must be there), do you mean after pressing it we will be prompted to select the action to take? It used to be a physical button on a real console's keyboard. Since consoles are mostly plain PCs with 3270 emulators nowadays, that key is no longer available from the console. Its an HMC action. Yes, once the restart interrupt is generated, you'll see a bunch of messages at the master console (or is it the system console). Similar appearance to the messages you see after V XCF,...,OFFLINE when the system is in the wait state. The restart messages tell you a bit about the job/task running on the interrupted processor and then give you the choice of (relying on my failing memory here): - ABEND the interrupted task - Giving control back to the interrupted task (is it RETRY?) - Having the system scan and repair, if neccessary, its vital control blocks, then continue. It doesn't use nor depend on CONSOLE communication. The restart interrupt handler communicates directly with the operator via disabled console communication. You need to alway reply with R 00, It's always worth a try before you decide to IPL a dead system. Could save you an IPL and doesn't waste a lot of time if it doesn't help. -- Peter Hunkeler Credit Suisse -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: About dispatching process
Johnny Luo [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED]... Peter, I checked POO and yes, RESTART interruption cannot be disabled so at least we have a final choice under such a situation. Never had the chance to use HMC (I guess the restart key must be there), Yes, it used to be a button or you a HCM command, now it will probably be a panel option. do you mean after pressing it we will be prompted to select the action to take? No, it is different from windows: First of all, you send an External Interrupt to a specific processor, in your case the one with the disabled loop. The task on this processor will be pulled through RTM (Recovery and Termination Manager), more or less as if an error had occurred on the task. The assumption then is, that RTM will abort the looping task, clean up and recover it, so that the disabled part has been terminated. So, Peter, as far as I know, the operator does not (directly) get control after a Restart Interrupt. Kees. On 10/24/07, Hunkeler Peter (KIUK 3) [EMAIL PROTECTED] wrote: I must say it's very interesting. Suppose in a single-processor system, I write some codes which cause a disabled loop. How to handle it? Press 'restart' key like what we usually react in a windows system? :) The difference being that you, the operator, get in control after pressing the restart key. You can then choose to abend the looping task. The system will continue to run thereafter. -- Peter Hunkeler Credit Suisse ** For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch Airlines) is registered in Amstelveen, The Netherlands, with registered number 33014286 ** -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: About dispatching process
So, Peter, as far as I know, the operator does not (directly) get control after a Restart Interrupt. Yes, you do. I've been playing with this, just don't remember the exact messages and options you get. The system gives you the option to ABEND or RESUME the interrupted task. After all, it might be doing the right thing but the operator was just impatient (or inadvertantly hit the RESTART key). If the system would just ABEND the task it might kill the wrong task. -- Peter Hunkeler Credit Suisse -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Healthcheck ((IBMCSV,CSV_APF_EXISTS)
Hi, I agree the CSV_APF_EXISTS check is working correctly. I think DFSMShsm certainly can and should determine a data set is APF regardless of weather it was defined in the recommended way using SMS or incorrectly using a volume serial. SCP honors a volser specified for an SMS managed data for APF till that changes everyone else should too. I don't know if HSM uses CSVAPF for each data set that it has selected to migrate. If so then it probably is invoking it with VOLTYPE=SMS for an SMS managed library and so no match. This is a lot of guessing but if that is the case just using VOLTYPE=ANY would get correct results. If HSM has some sort of RYO code to inspect a list retrieved once from CSVAPF at the beginning of migration then that code would need to change. HSM should not care if you have defined a data set to APF using the correct style. IMHO the CSV_APF_EXISTS is useful and is working correctly telling me what I should do. HSM should honor the APF processing as it is warts and all. Extending HSM to do this protection HSMPlex wide would be an enhancement but I think the case discussed of migration of an SMS managed library APF by volser is defect. The HSM team may not agree I have not reported this. CSVAPF ,VOLTYPE=SMS ,VOLTYPE=ANY,VOLUME=volume Specifies the status of the library specified on the DSNAME parameter, which is one of the following: SMS The library is managed by the storage management subsystem (SMS). ANY The library may or may not be SMS-managed. The library is located on volume volume, which specifies the address of a 6-character volume serial number; for an ADD request, you can also specify ** (six asterisks) to indicate the current sysres volume, or *MCAT* to indicate the volume on which the master catalog resides. If volume is all zeros, the system assumes that the library is SMS-managed. Note: The return code on a Query is determined by whether the match is exact or inexact. A return code of 0 indicates an exact match which could be: o You coded DSNAME=d and VOLTYPE=ANY and VOLUME=v and there is an entry in the APF list that matches both the data set and the volser. o You coded DSNAME=d and an indication of SMS-managed (VOLTYPE=SMS) and there is an entry in the APF list that matches the data set and indicates SMS-managed. A return code of 4 with a reason code = 0401 indicates an inexact match which is: o You coded DSNAME=d and VOLTYPE=ANY and VOLUME=v and there is no exact match, but there is an entry in the APF list that matches the data set and indicates SMS-managed. Best Regards, Sam Knutson, GEICO System z Performance and Availability Management mailto:[EMAIL PROTECTED] (office) 301.986.3574 Think big, act bold, start simple, grow fast... -Original Message- Knutson, Sam wrote: I think you could make a good case for DFSMShsm not functioning correctly. It should refuse to migrate both since using SMS is recommended by not required by APF. The check's documentation states that, In order for [HSM] to verify APF-authorization properly, the APF list entry must indicate that the data set is SMS-managed. And, that's exactly what you've demonstrated here. HSM is unable to verify the APF property when an SMS-managed data set is improperly defined as non-SMS-managed in the APF list. So, the data set gets migrated in that case. In summary, HSM will allow migration when the APF list entry is erroneously defined: |Data Set is APF Entry Indicates Erroneous Can Be |SMS Managed SMS-Managed Definition Migrated? |--- --- -- - |YES YES NO NO |NO NO NO Not if matching volume |YES NO YES YES |NO YES YES YES So, the CSV_APF_EXISTS check is doing its job! Right? -- Edward E Jaffe Phoenix Software International, Inc 5200 W Century Blvd, Suite 800 Los Angeles, CA 90045 310-338-0400 x318 [EMAIL PROTECTED] http://www.phoenixsoftware.com/ This email/fax message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution of this email/fax is prohibited. If you are not the intended recipient, please destroy all paper and electronic copies of the original message. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET
Re: Healthcheck ((IBMCSV,CSV_APF_EXISTS)
I want to thank everyone for trying out these scenarios and letting us know the results. Now I have some evidence with which to pursue this with the HSM folks. I will report back if I find anything out Perhaps Rob Scott and Allan Staller could confirm if Sam Knutson's and Ed Jaffe's (and others) thoughts are correct, with respect to the actual APF list entry. The key pieces of data are: -- is the data set SMS-managed or not that you are trying to HMIGrate? -- is the APF list entry by volume or *SMS*? So the 4 cases are -- data set is SMS-managed, APF list entry is *SMS* -- data set is SMS-managed, APF list entry is by volume -- data set is not SMS-managed, APF list entry is *SMS* -- data set is not SMS-managed, APF list entry is by volume Obviously the 3rd case is not what you would want, but I included it for completeness... Peter Relson z/OS Core Technology Design -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Healthcheck ((IBMCSV,CSV_APF_EXISTS)
Peter, APF list entry in PROGxx is : APF ADD DSNAME(some.dataset) SMS some.dataset is SMS managed, and is migrated to ML2. It is likely that at some point in the past on this system (or one of the other systems in the sysplex) that this dataset was migrated whilst NOT in the APF list. Rob Scott Rocket Software, Inc 275 Grove Street Newton, MA 02466 617-614-2305 [EMAIL PROTECTED] -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Peter Relson Sent: 24 October 2007 12:56 To: IBM-MAIN@BAMA.UA.EDU Subject: Re: Healthcheck ((IBMCSV,CSV_APF_EXISTS) I want to thank everyone for trying out these scenarios and letting us know the results. Now I have some evidence with which to pursue this with the HSM folks. I will report back if I find anything out Perhaps Rob Scott and Allan Staller could confirm if Sam Knutson's and Ed Jaffe's (and others) thoughts are correct, with respect to the actual APF list entry. The key pieces of data are: -- is the data set SMS-managed or not that you are trying to HMIGrate? -- is the APF list entry by volume or *SMS*? So the 4 cases are -- data set is SMS-managed, APF list entry is *SMS* -- data set is SMS-managed, APF list entry is by volume -- data set is not SMS-managed, APF list entry is *SMS* -- data set is not SMS-managed, APF list entry is by volume Obviously the 3rd case is not what you would want, but I included it for completeness... Peter Relson z/OS Core Technology Design -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: JES2 / JES3 in same plex
Thanks to all who have responded. per request from others, please respond to the list so all can see, I didn't think many folks would be interested in this topic. the JES3 side is currently using a product called OMC-Flash for the jes3/sdsf type of things. for those that have done this, any GRS,WLM,XCF issues that you ran across ? Thanks Again -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Outsmarting WLM
Wouldn't is be sufficient to run the keep BPXAS alive program periodically, say every 15 minutes? The new childs would use idle BPXASs and WLM would create new ones if the ovefrall system load permits this. Well, I don't want to unnecessarily create new BPXASs when the system is already busy handling a spike in 'real workload' and that spike happens to coincide with expiration of a 15-minute interval (or however long that interval is). - Make sure you can stop the mechanism when sutting down z/OS for IPL. Part of the shutdown process is to stop all BPXASs to allow JES to come down. If you trigger by the BPXAS has ended message you might never get to the point where JES is dormant. Good point and do I know what you're talking about! When I finally lost patience with the jes2 is stuck messages I implemented the following: f bpxoinit,shutdown=forkinit as one of the very first thing - I think that disables new bpxas's from being created. And before I even attempt to $Pjes2, there is an unconditional F bpxoinit,shutdown=forks. That usually gets the last of the stragglers down. If not, next pass checks which OMVS processes are still around and except for the two allowed ones every one of those processes get a kill command. Only *then* do I even attempt to terminate jes2 :-) The points you mentioned regarding WLMs behaviour and how many bpxas's can be started, that would need to be subject to intense testing before we ever go into production with that. And it will need to be a concerted effort of more than just me on my own But I really appreciate the input... Best regards, Barbara -- GMX FreeMail: 1 GB Postfach, 5 E-Mail-Adressen, 10 Free SMS. Alle Infos und kostenlose Anmeldung: http://www.gmx.net/de/go/freemail -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: SMS Question - Rename STORAGE CLASS
What is the real problem you are trying to solve? -Original Message- From: John Dawes [mailto:snip] Sent: Monday, October 22, 2007 3:47 AM To: IBM-MAIN@BAMA.UA.EDU Subject: SMS Question - Rename STORAGE CLASS I am in a bind, can I rename a storage class? I am hesitant to try it out because I don't have a test system. If it is possible, could there be problems? I assume that I will need to do the translate, validate and activate. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: tso racf
-Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Ted MacNEIL Sent: Tuesday, October 23, 2007 5:26 PM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: tso racf That way you know the user was safely tucked into ISPF. Why do we care? What problem are we solving by restricting access to the READY prompt? I've already asked this question; received no response. - Why? IT is here to serve! We aren't here to ask questions such as why?. That's management's job. And given some managers that I've had the misfortune to work with, the answer is most likely because I said so, damn it! sysprog type=frustrated/ -- John McKown Senior Systems Programmer HealthMarkets Keeping the Promise of Affordable Coverage Administrative Services Group Information Technology The information contained in this e-mail message may be privileged and/or confidential. It is for intended addressee(s) only. If you are not the intended recipient, you are hereby notified that any disclosure, reproduction, distribution or other use of this communication is strictly prohibited and could, in certain circumstances, be a criminal offense. If you have received this e-mail in error, please notify the sender by reply and delete this message without copying or disclosing it. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Another squirrel strike
ISTR one of their number taking hte list down a while back ... http://www.theregister.co.uk/2007/10/24/kamikaze_squirrel/ -- Phil Payne http://www.isham-research.co.uk +44 7833 654 800 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: tso racf
i never said i liked the approach i was asked to do. as a matter of fact i dont. but, i kind of like to eat.etc... so , i am trying to do what my boss has asked me to do. we all have little quirks, so this isnt no big deal. i really do appreciate all of your comments and suggjestions. i will put a 'logoff' command at the end of the logon clist. Thank you Bill Carroll -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of McKown, John Sent: Wednesday, October 24, 2007 9:05 AM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: tso racf -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Ted MacNEIL Sent: Tuesday, October 23, 2007 5:26 PM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: tso racf That way you know the user was safely tucked into ISPF. Why do we care? What problem are we solving by restricting access to the READY prompt? I've already asked this question; received no response. - Why? IT is here to serve! We aren't here to ask questions such as why?. That's management's job. And given some managers that I've had the misfortune to work with, the answer is most likely because I said so, damn it! sysprog type=frustrated/ -- John McKown Senior Systems Programmer HealthMarkets Keeping the Promise of Affordable Coverage Administrative Services Group Information Technology The information contained in this e-mail message may be privileged and/or confidential. It is for intended addressee(s) only. If you are not the intended recipient, you are hereby notified that any disclosure, reproduction, distribution or other use of this communication is strictly prohibited and could, in certain circumstances, be a criminal offense. If you have received this e-mail in error, please notify the sender by reply and delete this message without copying or disclosing it. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html EMAIL DISCLAIMER: The information contained in this message may be privileged or confidential and is protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Outsmarting WLM
-Original Message- From: IBM Mainframe Discussion List On Behalf Of Barbara Nitz [ snip ] - Make sure you can stop the mechanism when sutting down z/OS for IPL. Part of the shutdown process is to stop all BPXASs to allow JES to come down. If you trigger by the BPXAS has ended message you might never get to the point where JES is dormant. Good point and do I know what you're talking about! When I finally lost patience with the jes2 is stuck messages I implemented the following: f bpxoinit,shutdown=forkinit as one of the very first thing - I think that disables new bpxas's from being created. And before I even attempt to $Pjes2, there is an unconditional F bpxoinit,shutdown=forks. That usually gets the last of the stragglers down. If not, next pass checks which OMVS processes are still around and except for the two allowed ones every one of those processes get a kill command. Only *then* do I even attempt to terminate jes2 :-) When preparing to re-IPL, we just issue F OMVS,SHUTDOWN as the last command before $PJES2. So far, that has always caused OMVS to pack up, clock out and go home, and allow JES2 to do likewise. z/OS 1.7... -jc- -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
New memory technology
Not from or about IBM, per se. But I hope that general computing information might be of interest to most of us. http://www.tgdaily.com/content/view/34506/113/ This is about resistor based memory. What is neat is that it is supposed to be non-volitale, faster than DRAM, take less power than DRAM, and be able to code multiple bits in a single cell. -- John McKown Senior Systems Programmer HealthMarkets Keeping the Promise of Affordable Coverage Administrative Services Group Information Technology The information contained in this e-mail message may be privileged and/or confidential. It is for intended addressee(s) only. If you are not the intended recipient, you are hereby notified that any disclosure, reproduction, distribution or other use of this communication is strictly prohibited and could, in certain circumstances, be a criminal offense. If you have received this e-mail in error, please notify the sender by reply and delete this message without copying or disclosing it. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
FW: Can CICS/ESA 4.1 using APPC/LU6.2 Run on a z9 BC?
If you will be installing a z9 BC, and you are running CICS/ESA 4.1 and you are using APPC, you may want to ask IBM about AN5718I, at least that was the name on the usermod they sent. Initial testing seems to indicate that this corrected both the APPC and CICS Windows problems we had when running on the z9. We'll find out for sure when we can get a window to move our production LPAR back to the z9 again. Tom Chicklon -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Outsmarting WLM
Wouldn't is be sufficient to run the keep BPXAS alive program periodically, say every 15 minutes? The new childs would use idle BPXASs and WLM would create new ones if the overall system load permits this. Well, I don't want to unnecessarily create new BPXASs when the system is already busy handling a spike in 'real workload' and that spike happens to coincide with expiration of a 15-minute interval (or however long that interval is). But when that spike is using all but one BPXAS and this last one times out, the BPXAS has ended mechanism would trigger as well and create a bunch of new ones, wouldn't it? You'd need to count the number of idle BPXASs and decide then if and how many to create. Idle ones are those which show up as BPXAS in a D A,BPXAS. Haven't thought about how to get that information in the keep-alive program, I admit. -- Peter Hunkeler Credit Suisse -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: tso racf
-Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Ted MacNEIL Sent: Tuesday, October 23, 2007 5:26 PM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: tso racf That way you know the user was safely tucked into ISPF. Why do we care? What problem are we solving by restricting access to the READY prompt? I've already asked this question; received no response. SNIP PHB Syndrome -- Opinions are my own -- -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Another squirrel strike
From the article Phil linked to: As a rather poignant footnote, the Jersey Journal notes that the Millars' house is fully decked out in anticipation of Halloween, complete with a tiny plastic tombstone on their front lawn. Tony Millar said the family will consider dedicating the tombstone to the squirrel. We had a squirrel take down the data center once, maybe twenty or so years ago. Jon snip ISTR one of their number taking hte list down a while back ... http://www.theregister.co.uk/2007/10/24/kamikaze_squirrel/ /snip -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Another squirrel strike
Actually it took half the campus down! Darren On Wed, 24 Oct 2007, Phil Payne wrote: ISTR one of their number taking hte list down a while back ... http://www.theregister.co.uk/2007/10/24/kamikaze_squirrel/ -- Phil Payne http://www.isham-research.co.uk +44 7833 654 800 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: tso racf
Ted MacNEIL wrote: That way you know the user was safely tucked into ISPF. Why do we care? What problem are we solving by restricting access to the READY prompt? I've already asked this question; received no response. Perhaps the users targeted for this behavior don't know how to type LOGOFF at the READY prompt. -- Edward E Jaffe Phoenix Software International, Inc 5200 W Century Blvd, Suite 800 Los Angeles, CA 90045 310-338-0400 x318 [EMAIL PROTECTED] http://www.phoenixsoftware.com/ -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
different TSO logon proc, depending on system. Restricting who can logon to a specific system
I just had a minor flash of insight which I thought might be of interest to people. Suppose you have multiple z/OS systems. Also suppose that you share the RACF database. And suppose you want to have a __different__ logon proc for people, depending on which system they log on to. Now, RACF only supports remembering a single logon proc name in the database. So either the user has to change the logon proc in the logon screen, depending on the system [s]he was logging on to, or you had to have a different TSO proclib, with the same proc names, for each system. I just had an epiphany on this. Instead, use the // INCLUDE MEMBER= to dynamically create the name of the JCL library member to be included, based on the SYSNAME. For an example, suppose your standard TSO proc name was STDTSO. You would have a proc with that name in the shared TSO proclib. It would look something like: //STDTSO PROC //INCLUDE MEMBER=TSOPSYSNAME Then, in the same proclib, you'd have a number of TSOP members, one for each system. If there are a number of shared statements for all procs, then include those statements in the STDTSO proc and only include the system unique statements in the TSOP member. Extending this slightly, suppose that you have a restricted system that you only want certain users to log on to. In the TSOPSYSNAME for that system, simply have a DD statement similar to: //RESTRICT DD DISP=SHR,DSN=HLQ.SYSSYSNAME.SYSUID Replace HLQ is some reasonable high level qualifier. Now, on that system, for each valid user, create the appropriate dataset. If the dataset does not exist, then when the user attempts to log on, they get a JCL error and the LOGON fails. Or am I just insane? -- John McKown Senior Systems Programmer HealthMarkets Keeping the Promise of Affordable Coverage Administrative Services Group Information Technology The information contained in this e-mail message may be privileged and/or confidential. It is for intended addressee(s) only. If you are not the intended recipient, you are hereby notified that any disclosure, reproduction, distribution or other use of this communication is strictly prohibited and could, in certain circumstances, be a criminal offense. If you have received this e-mail in error, please notify the sender by reply and delete this message without copying or disclosing it. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Healthcheck ((IBMCSV,CSV_APF_EXISTS)
Peter, et. al. My results: APF List Attribute Dataset Attribute Migration Result SMS managed SMS managedSuccessful SMS managed Non-SMS managedSuccessful Non-SMS managed Non-SMS managedFailed Non-SMS managed SMS managedSuccessful This was done with a ordinary dataset and dynamic APF commands on a z/OS 1.7 monopolex. All migration attempts were with the command HMIG dataset snip Perhaps Rob Scott and Allan Staller could confirm if Sam Knutson's and Ed Jaffe's (and others) thoughts are correct, with respect to the actual APF list entry. The key pieces of data are: -- is the data set SMS-managed or not that you are trying to HMIGrate? -- is the APF list entry by volume or *SMS*? So the 4 cases are -- data set is SMS-managed, APF list entry is *SMS* -- data set is SMS-managed, APF list entry is by volume -- data set is not SMS-managed, APF list entry is *SMS* -- data set is not SMS-managed, APF list entry is by volume /snip -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Outsmarting WLM
When I finally lost patience with the jes2 is stuck messages I implemented the following: f bpxoinit,shutdown=forkinit as one of the very first thing - I think that disables new bpxas's from being created. No, this command only asks *idle* BPXASs to terminate immediately. You can happily start new ones thereafter (via fork() or spawn()). F bpxoinit,shutdown=forks. This command denies further process creation. In the case of fork() and non-local-spawn() this imples that no new BPXASs will be started. (It also inhibits local-spawn()s to create new processes.) Not sure if it also lets idle BPXAS terminate immediately. -- Peter Hunkeler Credit Suisse -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Dynamic ISPF panels?
Cloink wrote: My company is soon to move away from something called Roscoe which has a programming facility similar to ISPF/CLIST/REXX in TSO. In Roscoe, 'on the fly'/dynamic panel definitions can be created to display output and/or accept user input; these are especially useful when accommodating either a 24x80, 27x132 or 43x80 screen size (or even some other size if the screen is split). Though I would like to use dynamic panels for more advanced reasons too - i.e., I realise I could have 3 different fixed panel definitions, and choose one or other based on screen size, but I don't want to do that. I have read ISPF/CLIST/REXX documentation regarding panel definitions but can't find any mention of dynamically-created ones. My only remaining supposition is that it would be necessary to write a definition to a PDS, and tell the rexx to look in that PDS for the definition. Does anyone know how best to create dynamic panel definitions? Take a look at SYS1.SBLSPNL0 members BLSPDISD and BLSPDISP, the panel definitions behind two of the key screens that you see when you use the browse option (option 1) of the IPCS dialog. They're set up to use a tiny portion of the screen face in a fixed manner and allow the program behind the panels to fill in the dynamic area as desired. Even the fixed portion of the panel flexes to fill the width of the screen. I haven't used the comparable Roscoe facility to determine how easy it might be to migrate code using one to the other, but a great deal of flexibility is there in ISPF. Bob Wright - MVS Service Aids -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Outsmarting WLM
-Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Hunkeler Peter (KIUK 3) Sent: Wednesday, October 24, 2007 8:44 AM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: Outsmarting WLM Wouldn't is be sufficient to run the keep BPXAS alive program periodically, say every 15 minutes? The new childs would use idle BPXASs and WLM would create new ones if the overall system load permits this. Well, I don't want to unnecessarily create new BPXASs when the system is already busy handling a spike in 'real workload' and that spike happens to coincide with expiration of a 15-minute interval (or however long that interval is). But when that spike is using all but one BPXAS and this last one times out, the BPXAS has ended mechanism would trigger as well and create a bunch of new ones, wouldn't it? You'd need to count the number of idle BPXASs and decide then if and how many to create. Idle ones are those which show up as BPXAS in a D A,BPXAS. Haven't thought about how to get that information in the keep-alive program, I admit. -- Peter Hunkeler If you are using CA-OPS/MVS, then you might be able to do something like: )MSG $HASP395 )PROC IF WORD(MSG.TEXT,2) = 'BPXAS' THEN DO RUNNING=OPSTATUS(A,A,BPXAS) IF RUNNING 10 THEN DO ADDRESS OPER F KEEPUP,10-RUNNING END END RETURN The keep alive STC is called KEEPUP. It allows operator modify commands. The MODIFY command's argument is simply the number of times to fork() a child. The 10 in the rule is arbitrary. Of course, the above does have the possibility of issuing multiple MODIFY command quickly, possibly resulting in more than 10 fork()'s. But this can be minimized by having the code ignore and purge any queued MODIFY commands before waiting on the CIB again. -- John McKown Senior Systems Programmer HealthMarkets Keeping the Promise of Affordable Coverage Administrative Services Group Information Technology The information contained in this e-mail message may be privileged and/or confidential. It is for intended addressee(s) only. If you are not the intended recipient, you are hereby notified that any disclosure, reproduction, distribution or other use of this communication is strictly prohibited and could, in certain circumstances, be a criminal offense. If you have received this e-mail in error, please notify the sender by reply and delete this message without copying or disclosing it. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Healthcheck ((IBMCSV,CSV_APF_EXISTS)
Staller, Allan wrote: APF List Attribute Dataset Attribute Migration Result SMS managed SMS managedSuccessful ===!!! SMS managed Non-SMS managedSuccessful Non-SMS managed Non-SMS managedFailed Non-SMS managed SMS managedSuccessful The above entry denoted with ===!!! is wrong. Whatever the cause in your environment, I assume it's APARable. -- Edward E Jaffe Phoenix Software International, Inc 5200 W Century Blvd, Suite 800 Los Angeles, CA 90045 310-338-0400 x318 [EMAIL PROTECTED] http://www.phoenixsoftware.com/ -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: different TSO logon proc, depending on system. Restricting who can logon to a specific system
Excellent idea, we use the JCL include to set up the joblibs and job variables that are global to every job of our applications. Sounds like just a different application of the same principle. Darren -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of McKown, John Sent: Wednesday, October 24, 2007 9:55 AM To: IBM-MAIN@BAMA.UA.EDU Subject: different TSO logon proc, depending on system. Restricting who can logon to a specific system I just had a minor flash of insight which I thought might be of interest to people. Suppose you have multiple z/OS systems. Also suppose that you share the RACF database. And suppose you want to have a __different__ logon proc for people, depending on which system they log on to. Now, RACF only supports remembering a single logon proc name in the database. So either the user has to change the logon proc in the logon screen, depending on the system [s]he was logging on to, or you had to have a different TSO proclib, with the same proc names, for each system. I just had an epiphany on this. Instead, use the // INCLUDE MEMBER= to dynamically create the name of the JCL library member to be included, based on the SYSNAME. For an example, suppose your standard TSO proc name was STDTSO. You would have a proc with that name in the shared TSO proclib. It would look something like: //STDTSO PROC //INCLUDE MEMBER=TSOPSYSNAME Then, in the same proclib, you'd have a number of TSOP members, one for each system. If there are a number of shared statements for all procs, then include those statements in the STDTSO proc and only include the system unique statements in the TSOP member. Extending this slightly, suppose that you have a restricted system that you only want certain users to log on to. In the TSOPSYSNAME for that system, simply have a DD statement similar to: //RESTRICT DD DISP=SHR,DSN=HLQ.SYSSYSNAME.SYSUID Replace HLQ is some reasonable high level qualifier. Now, on that system, for each valid user, create the appropriate dataset. If the dataset does not exist, then when the user attempts to log on, they get a JCL error and the LOGON fails. Or am I just insane? -- John McKown Senior Systems Programmer HealthMarkets Keeping the Promise of Affordable Coverage Administrative Services Group Information Technology The information contained in this e-mail message may be privileged and/or confidential. It is for intended addressee(s) only. If you are not the intended recipient, you are hereby notified that any disclosure, reproduction, distribution or other use of this communication is strictly prohibited and could, in certain circumstances, be a criminal offense. If you have received this e-mail in error, please notify the sender by reply and delete this message without copying or disclosing it. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: VARY too many devices offline
-Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Ed Gould Sent: Tuesday, October 23, 2007 6:29 PM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: VARY too many devices offline On Oct 23, 2007, at 3:17 AM, Zaromil Tisler wrote: On Tue, 23 Oct 2007 08:54:31 +0100, Kenny Fogarty wrote: I agree, but, if the wrong date, or IPL parm, or whatever is entered, then the chances are you're going to have to re-IPL to rectify the situation. As you said above, if RACF doesn't start, you can go back to see why, and take steps to fix the issue. I wish the person this had happened to would pipe up, but to set the record more precisely because of a bad date RACF (This is hear say) did something to the (RACF) database that essentially rendered the system not operatrional. Just by IPLing (again) with the correct date was too late as the RACF database unusable. I do not know if they had backups or any specifics. I heard they were down for a day or so. Luckily this was a weekend. SNIP During Y2K testing, a future date was picked. Since all RACF IDs were beyond the revoke dates... So IPL with the correct date left them with having to do an OPERATOR override and allow a SPECIAL/AUDITOR ID (similar to IBMUSER, or it was IBMUSER) to logon even though it was revoked. Then it is a long laborious process to re-activate every revoked account. It was my understanding that this happened during a required Y2K test at a Nuclear plant. I'm told it got real interesting when all the access badges went dead as they hadn't been used for over 2 years as far as the security system was concerned. Regards, Steve Thompson -- Opinions expressed are my own. -- -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: VARY too many devices offline
-snip--- I had a problem with IPLing I think a year behind the current date. This was running under VM. VM was IPL'd with the wrong date, passing the date along to each guest. We had 5 DOS guests, one MVS guest, and one VS1 guest at the time. This was our first conversion of one of the DOS guests to MVS. I don't think there were any problems while running a year back, but something led me to check the date, and I discovered we had the wrong one. We shut everything down, and reIPL'd VM with the correct date, and brought everything back up. The only problem after coming back up was that anyone who had logged on TSO while the date was 1 year behind couldn't log on. That was me, and a few of the programmers and the operator. This led to my getting my 2nd TSO id, which I wanted in the beginning, but a girl who worked there for a while didn't want anyone to have 2 TSO ids. It so happened that she wasn't home, so I kind of sat there and couldn't even log on for about an hour, until she finally got home and called me. Then I logged on with her password and ID and reset my own ID. Needless to say, it didn't take much convincing to get a 2nd TSO id after that. -unsnip- RACF has the capability of disallowing a user to logon if he's been inactive for a certain number of days. We got stung by this at Clearing long ago, when even STC wasn't allowed to logon. We installed an exit to bypass that difficulty. I believe now that RACF has been altered such that started tasks aren't limited in that fashion. We also had a proc that could be started from the console to restore certain critical ID's so we could recover from a similar disaster in the future. When we first got stung, we were down for an entire CBOT trading session and the repercussions were VERY MESSY, to say the least. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: different TSO logon proc, depending on system. Restricting who can logon to a specific system
On Wed, 24 Oct 2007 11:54:35 -0500, McKown, John [EMAIL PROTECTED] wrote: I just had a minor flash of insight which I thought might be of interest to people. Suppose you have multiple z/OS systems. Also suppose that you share the RACF database. And suppose you want to have a __different__ logon proc for people, depending on which system they log on to. Now, RACF only supports remembering a single logon proc name in the database. So either the user has to change the logon proc in the logon screen, depending on the system [s]he was logging on to, or you had to have a different TSO proclib, with the same proc names, for each system. I just had an epiphany on this. Instead, use the // INCLUDE MEMBER= to dynamically create the name of the JCL library member to be included, based on the SYSNAME. For an example, suppose your standard TSO proc name was STDTSO. You would have a proc with that name in the shared TSO proclib. It would look something like: //STDTSO PROC //INCLUDE MEMBER=TSOPSYSNAME Then, in the same proclib, you'd have a number of TSOP members, one for each system. If there are a number of shared statements for all procs, then include those statements in the STDTSO proc and only include the system unique statements in the TSOP member. Extending this slightly, suppose that you have a restricted system that you only want certain users to log on to. In the TSOPSYSNAME for that system, simply have a DD statement similar to: //RESTRICT DD DISP=SHR,DSN=HLQ.SYSSYSNAME.SYSUID Replace HLQ is some reasonable high level qualifier. Now, on that system, for each valid user, create the appropriate dataset. If the dataset does not exist, then when the user attempts to log on, they get a JCL error and the LOGON fails. Or am I just insane? -- Not insane, but sort of Rube Goldberg-ish. 1) If you already have system specific proclibs (we do), is it any more work to have 1 member in 8 proclibs vs. 8 members in 1 proclib to maintain? Yes... I read where you suggested multiple include members so common ones can be shared. By the time I drew the roadmap to figure it all out, it could have updated the different logon PROCs separately anyway. 2) Your logon PROCs should be vanilla to being with and do your processing in the LOGON CLIST / exec. In there you can be a lot more flexible with processing based on userid, system or whatever. Vanilla being TSO/ISPF only. This also reduces the risk of a logon failure. 3) Dynamic ISPF - Tom should be jumping in any moment. Mark -- Mark Zelden Sr. Software and Systems Architect - z/OS Team Lead Zurich North America / Farmers Insurance Group - ZFUS G-ITO mailto:[EMAIL PROTECTED] z/OS Systems Programming expert at http://expertanswercenter.techtarget.com/ Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: ServerPac master catalog flag
In [EMAIL PROTECTED], on 10/21/2007 at 05:07 AM, Mark Zelden [EMAIL PROTECTED] said: CH MCAT N Interesting: according to the documentation that shouldn't work, although it did. Thanks. -- Shmuel (Seymour J.) Metz, SysProg and JOAT ISO position; see http://patriot.net/~shmuel/resume/brief.html We don't care. We don't have to care, we're Congress. (S877: The Shut up and Eat Your spam act of 2003) -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: different TSO logon proc, depending on system. Restricting whocanlogon to a specific system
One easy way that I've used over the years that two different very large sites is a generic logon proc that invokes a startup exec. The startup exec can do lots of things like testing which lpar you're on and customizing the libraries allocated based on that. Then to further customize things the startup exec can optionally call a user startup exec (after first testing to determine if it exists) - this allows the users to define their own set of libraries to allocate. For an example of the user tailoring for ispf see my PREISPF tool at http://www.lbdsoftware.com/ispftools.html Lionel B. Dyck, Consultant/Specialist Enterprise Platform Services, Mainframe Engineering KP-IT Enterprise Engineering 925-926-5332 (8-473-5332) | E-Mail: [EMAIL PROTECTED] AIM: lbdyck | Yahoo IM: lbdyck Kaiser Service Credo: Our cause is health. Our passion is service. We?re here to make lives better.? Worry more about your character than your reputation. Character is what you are, reputation merely what others think you are. - John Wooden NOTICE TO RECIPIENT: If you are not the intended recipient of this e-mail, you are prohibited from sharing, copying, or otherwise using or disclosing its contents. If you have received this e-mail in error, please notify the sender immediately by reply e-mail and permanently delete this e-mail and any attachments without reading, forwarding or saving them. Thank you. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Healthcheck ((IBMCSV,CSV_APF_EXISTS)
For me it works I get the expected RC=99 RSN=14 for a HMIG. However I still believe such a condition (SMS-Managed, APF with SMS and migrated) shouldn't throw an expection for this healthcheck Roland -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Staller, Allan Sent: Wednesday, October 24, 2007 3:52 PM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: Healthcheck ((IBMCSV,CSV_APF_EXISTS) Peter, et. al. My results: APF List Attribute Dataset Attribute Migration Result SMS managed SMS managedSuccessful SMS managed Non-SMS managedSuccessful Non-SMS managed Non-SMS managedFailed Non-SMS managed SMS managedSuccessful This was done with a ordinary dataset and dynamic APF commands on a z/OS 1.7 monopolex. All migration attempts were with the command HMIG dataset -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: About dispatching process
I think the default exspin order is spin-abend-term generating abend071 rsn10, 30, 20. Second pass through exspin recovery is allowed to retry, third pass through not. That usually takes care of all spin loops, unless they were caused by something that makes the component that is *validly* spinning spin again immediately due to other errors. Restart interrupts from the HMC cause reason codes C and less, and the unit of work is aleays terminated (according to the book). I was not talking about spin-loop recovery but about the RESTART interrupt in general. I was pretty sure I am correct but your and Kees' responses made me start doubting, so I searched my archives. I knew I tried this once and I had documented it. Here are my findings from a while ago (but I assume this has not changed): - I ran a little looping program, basically a LM followed by a Branch back to the LM. I named it PHUNLOOP. - I then initiated the RESTART interrrupt. Since my program was *not* running disabled, I had to try more than once to catch my program. I caught *MASTER*, TCP/IP and others before I finally caught PHUNLOOP. - Here is what appeared on the master console: IEE107I THE FOLLOWING MESSAGE IS ISSUED BY SYNCHRONOUS WTO/R SERVICE *00 BLW004A RESTART INTERRUPT DURING PHUNLOOP PHUNLOOP ASID=0023 MODE=TASK PSW=078D 91900FA8 SYSTEM NON-DISPATCHABILITY INDICATOR IS OFF REPLY ABEND TO ABEND INTERRUPTED PROGRAM, RESUME TO RESUME INTERRUPTED PROGRAM, REPAIR TO PERFORM REPAIR ACTIONS. - Replying with RESUME lets the program continue to waste CPU cycles :-) - Replying with ABEND abends the program with a S071 Reason= - Not responding in time (the WTOR times out) leads to the same abend. -- Peter Hunkeler Credit Suisse -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: tso racf
On Wed, 2007-10-24 at 09:55 -0700, Edward Jaffe wrote: Perhaps the users targeted for this behavior don't know how to type LOGOFF at the READY prompt. Harumph. MY users generally just click the little 'X' on the top right corner of the emulator screen and let LOSTERM sort it out. Makes me nuts. -- David Andrews A. Duda and Sons, Inc. [EMAIL PROTECTED] -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: ServerPac master catalog flag
Shmuel Metz , Seymour J. wrote: In [EMAIL PROTECTED], on 10/21/2007 at 05:07 AM, Mark Zelden [EMAIL PROTECTED] said: CH MCAT N Interesting: according to the documentation that shouldn't work, although it did. Thanks. What documentation are you looking at? I think Appendix A.7 in ServerPac: Using the Installation Dialog (the command reference part of the book) pretty clearly says that CH MCAT N exists and is intended for exactly this use: To override the master catalog requirement for data sets in your configuration, do the following: * Use the dialog's View and Change Facility to display data sets with a Master Catalog attribute of 'Yes'. * From the list of master catalog data sets, enter the CHANGE MCAT command as follows: CH MCAT N * Exclude any data sets that you do not want to change (through line command X) and press Enter. * Press Enter or End to refresh the display. The overridden data sets are removed from the list. Does some other part of the book conflict with this? Note: Like all CHange commands, you can issue this from *any* data set list in View and Change. So if there are several operations you want to carry out for all data sets (MCAT flag - N, add primary and secondary space, etc.), you can pick any attribute in View and Change and select a list based on all its values to get a list of all data sets, and then fire away. (e.g., you could pick Required in Master Catalog and then select both Yes and No.) There is no need to generate one list for MCAT, another for SPACE, a third for RENAME, etc. You can override all three from the same list. Also: The dialog being what it is, in my opinion it pays to at least skim the whole book. It's not that long, and the time spent reading is likely to pay you back several times over. -- John Eells z/OS Technical Marketing IBM Poughkeepsie [EMAIL PROTECTED] -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: About dispatching process
Since DISABLED applies to only I/O and External interrupts, if you dont want to used Restart interrupt(for whatever mysterious reason), I am curious If I can induce a Machine check without actually messing with the pysical machine..:) Also more thoughts on Dispatcher.. In the old 360 days, the disptacher used to run thru a TCB(RB) chain looking for a RB Wait Count Field(WCF) =0. If it was 0 then the it would load the Registers and then do a load PSW, to disptach the TCB.If it was not =0, then it would go to the next TCB in the chain. If it doesnt find a single TCB with an RBWCF=0 and it reaches the last TCB, you a have a WAIT STATE(waiting for more work). Now I think Dispatcher runs of what is called a WEB(Work element block), although I suspect it is still looks at WCF to determine if it wants to dipstach the TCB. I am curious when was the last time they changed the Dispatcher code!!! Regards, Santosh. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: About dispatching process
-Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Santosh Kandi Sent: Wednesday, October 24, 2007 1:52 PM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: About dispatching process Since DISABLED applies to only I/O and External interrupts, if you dont want to used Restart interrupt(for whatever mysterious reason), I am curious If I can induce a Machine check without actually messing with the pysical machine..:) SNIP Repressible or Exigent? Do you have VM or Flex-Es? Otherwise, it will be rather hard to force a real machine (or LPAR) to take/recognize an Exigent machine check. Regards, Steve Thompson -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: New memory technology
On Wed, 24 Oct 2007 11:40:31 -0500, McKown, John [EMAIL PROTECTED] wrote: ... http://www.tgdaily.com/content/view/34506/113/ This is about resistor based memory. What is neat is that it is supposed to be non-volitale, faster than DRAM, take less power than DRAM, and be able to code multiple bits in a single cell. ... I'm going to assume that the device actually developed and the technology as described in the article are somewhat different. They start by saying this is Ferroelectric RAM but then mention nothing about ferroelectric properties at all. The go on to say that these semiconductor switches can be switched between high resistance and low resistance. (Gee. A transistor. As I recall, Transistor originally came from transfer resistor - a resistor with electronically controlled resistance.) But it uses mobile ions instead electrons or holes as in usual semiconductors. (Gee. A very slow transistor! Hopefully, the author of the article just didn't get it, but that some fast, low power ferroelectric memory has actually been developed. Pat O'Keefe -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Fw: Dynamic ISPF panels?
- Original Message - From: Cloink [EMAIL PROTECTED] Newsgroups: bit.listserv.ibm-main Sent: Wednesday, October 24, 2007 7:24 AM Subject: Dynamic ISPF panels? My company is soon to move away from something called Roscoe which has a programming facility similar to ISPF/CLIST/REXX in TSO. In Roscoe, 'on the fly'/dynamic panel definitions can be created to display output and/or accept user input; these are especially useful when accommodating either a 24x80, 27x132 or 43x80 screen size (or even some other size if the screen is split). Though I would like to use dynamic panels for more advanced reasons too - i.e., I realise I could have 3 different fixed panel definitions, and choose one or other based on screen size, but I don't want to do that. I have read ISPF/CLIST/REXX documentation regarding panel definitions but can't find any mention of dynamically-created ones. My only remaining supposition is that it would be necessary to write a definition to a PDS, and tell the rexx to look in that PDS for the definition. Does anyone know how best to create dynamic panel definitions? Two ideas. Scrollable menus, or dynamic areas. Regards, Tom Conley -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: ServerPac master catalog flag
On Wed, 24 Oct 2007 14:45:53 -0400, John Eells [EMAIL PROTECTED] wrote: * Exclude any data sets that you do not want to change (through line command X) and press Enter. When I posted my response I wrote: To get the list down to just the CPAC dsns... list by LVOLUME I forgot you do the exclude after your change command. That aspect of the change command is a** backwards from normal ISPF use. My excuse is I hadn't done a ServerPac prior to 1.8 for a few releases since we try to take turns. Even if I did every release... it's only once a year and the modify system layout is just a small part of the process. Mark -- Mark Zelden Sr. Software and Systems Architect - z/OS Team Lead Zurich North America / Farmers Insurance Group - ZFUS G-ITO mailto:[EMAIL PROTECTED] z/OS Systems Programming expert at http://expertanswercenter.techtarget.com/ Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
OT: TJX Update
* Scope of TJX data breach doubles: 94M cards now said to be affected http://cwflyris.computerworld.com/t/2246270/20890881/84579/2/ -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: SMS Data class for 3494
Hi George, On Sat, 20 Oct 2007 08:29:03 -0500, George Dranes [EMAIL PROTECTED] wrote: We have a 3494 ATL with 3590 drives. When we initially set this up, the Magstar Redbook I used said to leave the volume count for the data class as 1 since it is not used for tape. Yet I see IBM documentation apars for the JCL manual ( OA10660) which add volume count to attributes that apply to tape datasets. Which is it??? If true I guess I've never went over 1 tape for a single dataset. Also if were a stacked tape and a dataset was split over 2 volumes, would this pertain? What do others use for this value? Thanks for any help! I wasn't sure what year you set up 3494 or which Redbook (and whether that one happened to have a mistake), so looking at current doc.: z/OS 1.9 DFSMS Storage Admin Ref (that's the 18 MB with 1,580 pages, you're right, Tom), SC26-7402-08: Defining Record and Space Attributes for Data Class ... Volume Count specifies the maximum number of SMS-managed DASD or mountable volumes a data set can span, with the following exceptions. Valid values are 1 through 59. ... For managed mountable volumes, this value can be overridden by the volume count specified in JCL up to a maximum of 255. Dynamic volume count has no affect to tape data sets. Volume count is ignored for data sets to which no storage class is assigned. The default is 1. Note: In JES3 systems, volume count is also ignored for managed mountable data sets. ... Dynamic Volume Count Dynamic Volume Count is used during allocation processing to determine the maximum number of volumes a data set can span. The number can be in the range 1 through 59. The default value is 1. 59 is the z/OS volume limit. Also, from IBM TotalStorage 3494 Tape Library: A Practical Guide to Tape Drives and Tape Automation, SG24-4632-07: Defining Data Classes A Data Class provides the tape device selection information or tape datasets. The attributes that you can specify are: ... - The maximum volume count that your dataset can span ... Volume Count: Specify the maximum number of cartridges that you expect to use to store a dataset in this Data Class. Note: Coding a small value in the volume count parameter can cause job abends. This is especially true if you migrate from a native 3590 or 3592 environment to a VTS/TS7700 solution without changing your JCL. This occurs because the cartridge capacity is significantly different between a 3590 or a 3592 and a 3490E. So I think the answer is something like: If someone said *dynamic* volume count, that does not apply; If volume count, then it does apply to SMS- managed tape, except for JES3 and data sets to which no storage class is assigned. And bear in mind that it can be overridden by the volume count specified in JCL. HTH, Mike Baldwin Cartagena Software Ltd. http://www.cartagena.com +1 905-887-0755 1-888-USE-TAPE -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Dynamic ISPF panels?
Does anyone know how best to create dynamic panel definitions?Two ideas. Scrollable menus, or dynamic areas. Or scrollable dynamic areas.:-) To see an example, click the link below. Dave SaltSee the new SimpList(tm) rollover image at:http://www.mackinney.com/products/SIM/simplist.htm _ Express yourself with free Messenger emoticons. Get them today! http://www.freemessengeremoticons.ca/?icid=EMENCA122 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: ServerPac master catalog flag
On Wed, 24 Oct 2007 09:06:56 -0300, Shmuel Metz (Seymour J.) [EMAIL PROTECTED] wrote: In [EMAIL PROTECTED], on 10/21/2007 at 05:07 AM, Mark Zelden [EMAIL PROTECTED] said: CH MCAT N Interesting: according to the documentation that shouldn't work, although it did. Thanks. Which documentation? ServerPac manual or ISPF help screens? Mark -- Mark Zelden Sr. Software and Systems Architect - z/OS Team Lead Zurich North America / Farmers Insurance Group - ZFUS G-ITO mailto:[EMAIL PROTECTED] z/OS Systems Programming expert at http://expertanswercenter.techtarget.com/ Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: IBM System/3 3277-1
The following message is a courtesy copy of an article that has been posted to comp.sys.ibm.sys3x.misc,alt.folklore.computers,bit.listserv.ibm-main as well. [EMAIL PROTECTED] writes: I could read ASCII from a paper tape. Took me a while. :-) previous post in this thread: http://www.garlic.com/~lynn/2007q.html#48 IBM System/3 3277-1 i eventually learned to read 12-2-9 (i.e. card punch holes for hex 02) txt text deck cards ... as part of multi-punch/duplicate cards and punching patches ... i had a 2000 card assembler program and it was frequently faster to multi-punch fixes (into duplicate/new card) than to reassemble program (which could take 30-60 minutes elapsed time ... this was on 360/30 under os/360 release 6 ... i had dedicated university machine room on weekends for 48hrs stretch). basically had to not only be able to read storage dumps and equivalence between hexcode and things like instructions and/or addresses ... but the similar information on cards in punch hole representation. field/col definition for 12-2-9 TXT card: col 1 12-2-9 / x'02' 2-4 TXT 5 blank 6-8 relative address of first instruction on record 9-10blank 11-12 byte count ... number of bytes in information field 15-16 ESDID 17-72 56-byte information field 73-80 deck id, sequence number, or both cols. 2-4 and 73-80 were character ... the other fields were hex. qd converstion of gcard ios3270 to html http://www.garlic.com/~lynn/gcard.html but it lacks card punch hole equivalence for hex (on real green card) here is actual scan of a 360 green card ... front back (11mb) http://weblog.ceicher.com/archives/IBM360greencard.pdf from: http://weblog.ceicher.com/archives/2006/12/ibm_system360_green_card.html the following table is from http://www.cs.uiowa.edu/~jones/cards/codes.html giving equivalence between card punch codes, hexidemal value, and ebcdic 00 10 20 30 40 50 60 70 80 90 A0 B0 C0 D0 E0 F0 ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ 0|NUL| |DS | |SP | | - | | | | | | | | | 0 |0 |__1|___|__2|___|__3|__4|__5|___|___|___|___|___|___|___|___|___| 1| | |SOS| | | | / | | a | j | | | A | J | | 1 |1 |___|___|___|___|___|___|___|___|___|___|___|___|___|___|___|___| 2| | |FS | | | | | | b | k | s | | B | K | S | 2 |2 |___|___|___|___|___|___|___|___|___|___|___|___|___|___|___|___| 3| |TM | | | | | | | c | l | t | | C | L | T | 3 |3 |___|___|___|___|___|___|___|___|___|___|___|___|___|___|___|___| 4|PF |RES|BYP|PN | | | | | d | m | u | | D | M | U | 4 |4 |___|___|___|___|___|___|___|___|___|___|___|___|___|___|___|___| 5|HT |NL |LF |RS | | | | | e | n | v | | E | N | V | 5 |5 |___|___|___|___|___|___|___|___|___|___|___|___|___|___|___|___| 6|LC |BS |EOB|UC | | | | | f | o | w | | F | O | W | 6 |6 |___|___|___|___|___|___|___|___|___|___|___|___|___|___|___|___| 7|DEL|IL |PRE|EOT| | | | | g | p | x | | G | P | X | 7 |7 |___|___|___|___|___|___|___|___|___|___|___|___|___|___|___|___| 8| | | | | | | | | h | q | y | | H | Q | Y | 8 |8 |___|___|___|___|___|___|___|___|___|___|___|___|___|___|___|___| 9| | | | | | | | | i | r | z | | I | R | Z | 9 |9 |___|___|___|___|___|___|___|___|___|___|___|___|___|___|___|___| A| | | | | ¢ | ! | | : | | | | | | | | |2-8 |___|___|___|___|___|___|___|___|___|___|___|___|___|___|___|___| B| | | | | . | $ | , | # | | | | | | | | |3-8 |___|___|___|___|___|___|___|___|___|___|___|___|___|___|___|___| C| | | | | | * | % | @ | | | | | | | | |4-8 |___|___|___|___|___|___|___|___|___|___|___|___|___|___|___|___| D| | | | | ( | ) | _ | ' | | | | | | | | |5-8 |___|___|___|___|___|___|___|___|___|___|___|___|___|___|___|___| E| | | | | + | ; | | = | | | | | | | | |6-8 |___|___|___|___|___|___|___|___|___|___|___|___|___|___|___|___| F| | | | | | | ¬ | ? | | | | | | | | | |7-8 |___|___|___|___|___|___|___|___|___|___|___|___|___|___|___|___| 12 11 10 12 11 10 12 11 10 12 11 10 9 9 9 10 12 11 i.e. hex values down the left and across the top, punch holes dorwn the right adn across the bottom. and card punch format ... card rows are number 12, 11, 0-9 from the top. /-0123456789ABCDEFGHIJKLMNOPQR/STUVWXYZb#@'V?.¤[§!$*];^±,%v\¶ 12 / O OOO 11| O O OO 0|O O OO 1| OOOO 2| OOOO O O O O 3| OOOO O O O O 4|OO
Re: tso racf
On Tue, 23 Oct 2007 17:04:56 -0700, George Fogg wrote: BTW, does the ISPF exits run authorized? I read the manual but not quite sure if they do. George, It doesn't matter (much) whether the exits are authorized or not if all you do is issue a WTO to alert your automation package that it is safe (but not necessarily required) to issue the STOP command to the source TSO address space now. -- Tom Schmidt Madison, WI (The difference between authorized or not is whether or not the + prefixes the WTO in the display; you'll learn which right after the 1st WTO.) -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: tso racf
On Tue, 23 Oct 2007 20:11:33 -0500 Tom Schmidt [EMAIL PROTECTED] wrote: :I well understood what PCF's goal was, but my point was that it was FAR too :easy to circumvent the command 'control' portion. As long as you (or a friend) :had program access to ANY library that you could execute from (without using :TSO TEST) you could install your own command processor (same name, :different purpose) that could then trivially circumvent PCF. There were other :means of bypassing PCF, too, but I usually used that, my favorite mechanism. :(Dance with the one that brought you.) What PCF did well was protect APF authorized CPs. You could not circumvent PCF unless you had the ability to write into an APF library, which if you can - you can do whatever you want anyway. -- Binyamin Dissen [EMAIL PROTECTED] http://www.dissensoftware.com Director, Dissen Software, Bar Grill - Israel Should you use the mailblocks package and expect a response from me, you should preauthorize the dissensoftware.com domain. I very rarely bother responding to challenge/response systems, especially those from irresponsible companies. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
ASTE, Linkage Table Origin, and PC's
This one has me totally stumped. The POPs manual in chapter 5 explains the mechanism used for PC number translation. I've got a z/os 1.6 system with DB2 V8 up. On my machine, bit 44 of control reg 0 is off, so I believe the PC translation process is the same as it has always been. I use the address in control reg 5 to get to the Primary ASTE. POPS says this is real address, and at byte 24 into this is the Linkage table origin. The LTO uses bits 25 - 31 to indicate how many 128 byte linkage table entries there are. This value is 1 less than, so add one. When I do the math, on my system, it comes up with a max LX value of C0. I don't know if this is new with DB2 V8, but when I use call attach to execute some sql, I first see a PC with a LX value of 1D. PC nbr is actually 01D05 on my system. This is a non-apce switch PC that moves from DSNACAF in private area to a module loaded in ECSA. The space switch PC that actually takes the path into the DBM1 address space is executed in this ECSA module, but here's the kicker. It has an LX value of 0D0. The actual PC is 0D001. My question. How is it possible to run with an LX value that is not defined in the PCAUTH linkage table? POPS manual states the linkage table length is compared to the LX value used to determine if the index used is within the linkage table. --Dave Day -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: tso racf
On Tue, 23 Oct 2007 17:04:56 -0700, George Fogg wrote: BTW, does the ISPF exits run authorized? I read the manual but not quite sure if they do. George, It doesn't matter (much) whether the exits are authorized or not if all you do is issue a WTO to alert your automation package that it is safe (but not necessarily required) to issue the STOP command to the source TSO address space now. Tom: I was thiking I would let the ISPF exit deal with the P userid command so I would build a trusted token and pass that in the MGCRE call, which of course, requires authorization of some type to do these calls. The trusted token would bypass the authorization check to issue the P userid command. That is, if I want to do such a thing. George Fogg -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Full DASD Volume Copy
But one possible cautionary note that I would want to check on before saying the VTOCIX and VVDS names are immaterial: If you do a DFDSS COPY with DUMPCONDITIONING to another online DASD volume (which preserves the volser of the target so it can stay online and then be source of a DUMP), with the intent of being able to later use a dump of the COPY target to RESTORE the original volume, the original volser appears to be derived in some way from either the VTOCIX or the VVDS (we found at one DR test that if both are missing from the volume, the correct volser definitely isn't restored!). I don't know if the restore is driven from the names of these datasets or in some way from their contents. If from the names, having those out of sync with the actual volser could be a potential problem down the road. At the time we encountered the DFDSS RESTORE VTOCIX/VVDS/volser dependency, it was undocumented; so my understanding is based on empirical evidence. We ended up having to put a VTOCIX on our 1-file, non-SMS, JES spool volumes to avoid ending up with incorrect volsers at DR recovery. I always assumed it was the highly-visible volser in the VTOCIX name that did the trick, but maybe it was something in the VTOCIX contents. Ted MacNEIL wrote: datasets for the indexed VTOC and VVDS reflect the name of the volume That has never been a problem. Since they're not catalogued, the names are meaningless. They are found (through the VTOC) by TTR, not by name. ... -- Joel C. Ewing, Fort Smith, AR[EMAIL PROTECTED] -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: tso racf
On Wed, 24 Oct 2007 22:38:03 -0400, Binyamin Dissen wrote: What PCF did well was protect APF authorized CPs. You could not circumvent PCF unless you had the ability to write into an APF library, which if you can - you can do whatever you want anyway. Oh yes I could (and did)! I could run any APF or non-APF command processor on the system where I had no write access to their APF libraries. That's why it was a joke. -- Tom Schmidt Madison, WI -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: About dispatching process
Now I think Dispatcher runs of what is called a WEB(Work element block), although I suspect it is still looks at WCF to determine if it wants to dipstach the TCB. I am curious when was the last time they changed the Dispatcher code!!! The last major change was done with MVS/ESA V5, but I'm sure there have been other changes thereafter. Since MVS/ESA V5, the dispatcher doesn't have to scan TCB queues for ready work. The WUQ (work unit queue) only has elements for ready work units, and they are in priority order. It can pick the top element and dispatch it on the free CPU. When a ready work unit (TCB or SRB) is taken from the CPU, it is put on the WUQ. When a work unit is going to wait for an asynchroneous event, it is not put on the WUQ while waiting. When it later becomes ready again it is put back on the WUQ. -- Peter Hunkeler Credit Suisse -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
