how to lose a sysplex in 30 seconds
Hi all, We had a small incident here last week and I wanted to hear your take about it... We have 2 LPARs in a sysplex, running on 2 different machines in 2 different sites. What happened was we lost connectivity between our 2 sites for a few seconds. As a result, MVSB (running in site B) lost its connectivity to the primary SYSPELX couple data set residing on dasd in site A, and issued the following message: IXC253I PRIMARY COUPLE DATA SET 953 XCF.COUPLE01 FOR SYSPLEX IS BEING REMOVED BECAUSE OF AN I/O ERROR DETECTED BY SYSTEM MVSB ERROR CASE: PERMANENT ERROR The above message was then issued by MVSA as well. Sadly enough, our alternate SYSPLEX couple data set resides on dasd in site B. So MVSA had no connectivity to it, which led to a Disabled Wait 0A2 RC 20 in MVSA. After that, MVSB issued the following message: IXC256A REMOVAL OF PRIMARY COUPLE DATA SET 463 XCF.COUPLE01 FOR SYSPLEX CANNOT COMPLETE UNTIL THE FOLLOWING SYSTEM(S) ACKNOWLEDGE THE REMOVAL: MVSA Of course, MVSA could never acknowledge since it was in a disabled wait. IXC256A rolled off the MVSB console (which was in DEL=R mode), so by the time I got to the console I couldnt see it and didnt know it was issued. At MVSB's console, I issued a D R,R and didnt see anything. After I saw why MVSA entered the wait, I issued D XCF,C at MVSB's console and never got a response. Eventually we IPLed both MVSB and MVSA because it seemed like MVSB was hung... I realize there were many mistakes done along the way here, my question is, how could I know that IXC256A was issued if it rolled off the console (TSO/E was hung too)?? If i knew it was issued, i would issue a V XCF,MVSA,OFFLINE,FORCE and let MVSB complete its couple data set switch... Also, I dont understand the logic here. MVSA had access to the primary, but not to the alternate. MVSB had access to the alternate, but not to the primary. Still, MVSA disabled wait and MVSB stayed up, hung until MVSA cleanup... The same exact thing happened on our 2nd sysplex. The 2nd sysplex consists of 4 LPARs, 2 in site A and 2 in site B. On this sysplex the 2 systems on site A entered a disabed wait 0A2 and the other 2 on site B stayed hung waiting for their cleanup... In either case, I ended up with half a sysplex in a disabled wait and half hung. Which got me thinking... what if there were 7 systems on site A and only 1 system on site B?? would z/OS logic still be to enter 7 systems into a disabled wait instead of only the 1 system that lost access to the primary??? Basically you can say we learned the true value of SFM. Had we been using it, it would probably prevent the hang in MVSB, because it would clean up the mess left by MVSA after it entered the disabled wait. Would SFM also help in the 7-1 case?? Thanks, Gil. -- 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
PSP information
Hi, I am trying to get to the PSP site. My serverpac installation guide tells me to go to https://techsupport.services.ibm.com/server/390.psp390, but this site doesn't seem to work. Does anyone know what the 'new' PSP site is? TIA Gadi -- 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: PSP information
Gadi, When you copy and paste to your browser just remove the comma that unfortunately got added to the URL. I'm sure in the original context it was the correct grammar but it got incorporated into the URL. The correct URL is https://techsupport.services.ibm.com/server/390.psp390 and this sentence only has a full stop - or should that be period? - only because I added some more text and didn't add it immediately after the URL. Chris Mason If John Giltner is reading this I'm trying this post after having removed the IBM-MAIN text. Let's see if it works. - Original Message - From: גדי בן אבי [EMAIL PROTECTED] Newsgroups: bit.listserv.ibm-main To: IBM-MAIN@BAMA.UA.EDU Sent: Sunday, 27 November, 2005 2:16 PM Subject: PSP information Hi, I am trying to get to the PSP site. My serverpac installation guide tells me to go to https://techsupport.services.ibm.com/server/390.psp390, but this site doesn't seem to work. Does anyone know what the 'new' PSP site is? TIA Gadi -- 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: sftp interactive under uss shell?
In [EMAIL PROTECTED], on 11/23/2005 at 11:33 AM, Joel Ivey [EMAIL PROTECTED] said: For those who use sftp on zOS, do you enter this interactive mode using the uss shell? What are you trying to ask? You can get into a Unix (*not* USS, which is something unrelated) from TSO or by logging on directly, e.g., via Telnet. If you log on via ssh, you get the same shell, but in a more secure fashion. Are you saying that sftp behaves differently for two of those three environments? Or is otelnet the only way to establish the interactive mode? I doubt it. -- 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: Policy for CPU and OS upgrade
Mohamed Juma wrote: Good day every one, I want to get the experience of other in two issues: 1. How you put your policy to upgrade the CPU or to go to new bigger processor, is it just when you suffer from 100% CPU usage or what are the criteria used for that? 2. Regarding the operating system: when you decide to go to higher version? and what is your maintenance policy?, are you puting maintenance every 6 months as example or you do maintenance only if you are forced because of a problem you faced? Best regards, Mohamed Juma 1) We normally only do CPU upgrades after our users/customers start telling us that their work is not getting through and then wait a month or two. We do have SDP, but I am not sure what it is today. I started off at avg. 70% CPU utilization for production work over a one month period. However the 1st time we hit that they raised it to 75%, then 80%, and then 85%. I think we are up to 90% or 95% for two consecutive months now. Before we had the SDP, we just waited until our customers started screaming. We still have the privilege of having a 8 hour outage window every Sunday. One time we ran the box at 100% all of the time, except for during this 8 hour window, or 3 months, before we were allowed to upgrade. 2) We put on new releases of the OS normally about 3 months after they have been released GA and after we have received conformation from all software vendor that they will run on the new OS. We apply regular maintenance about every 3-4 months. -- 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: Early Release of JES2 SPOOL space for spin-off data sets
I am not entirely sure on this, but functionality for all JES2 SYSOUTs seems to have changed with our latest upgrade to z/OS 1.6 IIRC, it was around ESA 4.0. -teD Me? A skeptic? I trust you have proof! -- 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: Early Release of JES2 SPOOL space for spin-off data sets
Hate to reply to myself, but I was wrong and it appears that the space is truly only freed when a SYSOUT is coded as FREE=CLOSE. Sorry, but even though it separates the output to another entry, the space is not freed when purging or printing the output of a non-FREE=CLOSE SYSOUT. NOT true. It is freed after the JOE is printed, now. I remember that ops used to depend on the fact that it wasn't and they could check certain maintenance jobs, even if the output was printed. Then the 'functionality' disappeared. -teD Me? A skeptic? I trust you have proof! -- 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: Using symbolic in JCL
In [EMAIL PROTECTED], on 11/24/2005 at 10:50 AM, Ted MacNEIL [EMAIL PROTECTED] said: Not true, in batch (a file with SYSNAME in it, and the file exists): IEFC627I INCORRECT USE OF AMPERSAND IN THE DSN FIELD Batch is not STC. Batch is not TSU. What you quoted was correct. -- 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: EXEC PARM bug or feature?
I can double up on the trailing Forward Slash as a work around to get what I need in the COBOL program, but I'm surprised by this behavior. Should I be? Slashes are special delimeters in LE/370. This is how you separate the runtime options from the programme options. -teD Me? A skeptic? I trust you have proof! -- 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: how to lose a sysplex in 30 seconds
Wow. I think there's a way to make the message non-rollable and high lighted. Also I think the wait state should be DEADBEEF. -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Gil Peleg Sent: Sunday, November 27, 2005 7:30 AM To: IBM-MAIN@BAMA.UA.EDU Subject: how to lose a sysplex in 30 seconds Hi all, We had a small incident here last week and I wanted to hear your take about it... We have 2 LPARs in a sysplex, running on 2 different machines in 2 different sites. What happened was we lost connectivity between our 2 sites for a few seconds. As a result, MVSB (running in site B) lost its connectivity to the primary SYSPELX couple data set residing on dasd in site A, and issued the following message: IXC253I PRIMARY COUPLE DATA SET 953 XCF.COUPLE01 FOR SYSPLEX IS BEING REMOVED BECAUSE OF AN I/O ERROR DETECTED BY SYSTEM MVSB ERROR CASE: PERMANENT ERROR The above message was then issued by MVSA as well. Sadly enough, our alternate SYSPLEX couple data set resides on dasd in site B. So MVSA had no connectivity to it, which led to a Disabled Wait 0A2 RC 20 in MVSA. After that, MVSB issued the following message: IXC256A REMOVAL OF PRIMARY COUPLE DATA SET 463 XCF.COUPLE01 FOR SYSPLEX CANNOT COMPLETE UNTIL THE FOLLOWING SYSTEM(S) ACKNOWLEDGE THE REMOVAL: MVSA Of course, MVSA could never acknowledge since it was in a disabled wait. IXC256A rolled off the MVSB console (which was in DEL=R mode), so by the time I got to the console I couldnt see it and didnt know it was issued. At MVSB's console, I issued a D R,R and didnt see anything. After I saw why MVSA entered the wait, I issued D XCF,C at MVSB's console and never got a response. Eventually we IPLed both MVSB and MVSA because it seemed like MVSB was hung... I realize there were many mistakes done along the way here, my question is, how could I know that IXC256A was issued if it rolled off the console (TSO/E was hung too)?? If i knew it was issued, i would issue a V XCF,MVSA,OFFLINE,FORCE and let MVSB complete its couple data set switch... Also, I dont understand the logic here. MVSA had access to the primary, but not to the alternate. MVSB had access to the alternate, but not to the primary. Still, MVSA disabled wait and MVSB stayed up, hung until MVSA cleanup... The same exact thing happened on our 2nd sysplex. The 2nd sysplex consists of 4 LPARs, 2 in site A and 2 in site B. On this sysplex the 2 systems on site A entered a disabed wait 0A2 and the other 2 on site B stayed hung waiting for their cleanup... In either case, I ended up with half a sysplex in a disabled wait and half hung. Which got me thinking... what if there were 7 systems on site A and only 1 system on site B?? would z/OS logic still be to enter 7 systems into a disabled wait instead of only the 1 system that lost access to the primary??? Basically you can say we learned the true value of SFM. Had we been using it, it would probably prevent the hang in MVSB, because it would clean up the mess left by MVSA after it entered the disabled wait. Would SFM also help in the 7-1 case?? Thanks, Gil. -- 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: EXEC PARM bug or feature?
For all but COBOL, i.e., for C, FORTRAN, HLASM, and PL/I, the historical LE parm-string sequence was and is (first ordering) PARM='LE environmental options/program data' Initially, COBOL got it backwards, as (second ordering) PARM='program data/LE environmental options' This second ordering is called the COBOL-options convention. Specifying CBLOPTS(OFF) at LE installation time selects the first ordering, making COBOL behave like the other languages. Specifying CBLOPTS(ON) instead yields the second ordering. Thus for CBLOPTS(OFF) and LE environmental options equal to a null string (missing), PARM=' /program data' is required; and for CBLOPTS(ON) and LE environmental options missing PARM='program data/' is required instead. The z/OS Language Environment Programming Reference, SA22-7562, dscusses these matters at length. John Gilmore Ashland, MA 01721-1817 USA _ Express yourself instantly with MSN Messenger! Download today - it's FREE! http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/ -- 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: Early Release of JES2 SPOOL space for spin-off data sets
In [EMAIL PROTECTED], on 11/25/2005 at 03:10 PM, Bruno Sugliani [EMAIL PROTECTED] said: It cannot be freed because what you purge is a JOE ( Job Output Element ) Unfortunately JOE belongs to JQE ( Job Queue Element ) and the allocation (the number of trackgroups used by the JOE's) is written in the JQE . No. What controls it is the IOT. If two SYSOUT data sets are in the same IOT, then JES2 can't purge the space until it has purged every JOE for both data sets. A data set with its own IOT will still pertain to the job's JQE. -- 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: EXEC PARM bug or feature?
In [EMAIL PROTECTED], on 11/26/2005 at 03:20 PM, Gerry Palmer [EMAIL PROTECTED] said: I've run into an oddity when passing an EXEC PARM to a COBOL program. I don't see anything in the JCL reference Nor should you; it belongs in the COBOL and LE documentation. Basically, it seems that if the last character of the EXEC PARM string is a forward slash, that character is stripped from the PARM value before the parameter string is passed to my COBOL program. LE treats a slash as a separator between the application's parameters and the runtime's parameters. The installation can control which comes first[1]. [1] At least for PL/I; I'm not sure about COBOL. -- 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: Policy for CPU and OS upgrade
In [EMAIL PROTECTED], on 11/26/2005 at 08:58 PM, Mohamed Juma [EMAIL PROTECTED] said: 1. How you put your policy to upgrade the CPU or to go to new bigger processor, is it just when you suffer from 100% CPU usage or what are the criteria used for that? Is the work getting done in accordance with your SLA? Do you project that the work will continue getting done for the forseeable future? If yes, you don't need a new CPU, even if you see long periods of 100% CPU use. If it looks the the work won't get done in accordance with your SLA next quarter, then you need to upgrade even if you never see 100% CPU utilization. What's your lead time for an upgrade? You need to order it early enough so that it's there, installed and in production before the balloon goes up. Planning. What's the cost of not meeting your SLA? 2. Regarding the operating system: when you decide to go to higher version? Well before the old one goes out of service; much earlier if you need new functionality. How disruptive is an IPL. Have you taken regression checking into account? are you puting maintenance every 6 months as example I used to do it much more often, but let service age for 90 days. You need to decide what balance of PUT, RSU and HIPER service makes sense for your installation. -- 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: EXEC PARM bug or feature?
In article [EMAIL PROTECTED] you wrote: At 03:43 PM 11/26/2005, you wrote: The LE runtime is interpreting the slash as the way to pass LE execution parameters. Dave, Thanks. I needed someone to jog me memory. I've seen and used that convention before to pass LE parms, but it slipped my mind when this happened and I kept thinking of it as strictly a JCL issue. At some level of LE, they came up with parm string redirection. e.g. PARM='ENVAR(_CEE_ENVFILE=DD:ENVVAR)/' //ENVVAR DD * LIBPATH=/usr/lpp/ocsf/lib /* -- Don Poitras - SAS Development - SAS Institute Inc. - SAS Campus Drive [EMAIL PROTECTED] (919) 531-5637Cary, NC 27513 -- 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: EXEC PARM bug or feature?
The whole slash business in COBOL goes back to the OS/VS COBOL days, before LE was even a blip on the PL/I radar (yes, that's where the LE stuff originated, and why COBOL had to adapt to LE). I remember setting COBOL runtime options after the slash back in the early 1980's. PL/I X (and probably Checkout, too) had the run time before the slash. Minor nit; if you have CBLOPTS(ON), the trailing slash is _not_ required for indicating lack of specification of runtime options. Later, Ray on 2005.11.27 09:51 john gilmore said the following: For all but COBOL, i.e., for C, FORTRAN, HLASM, and PL/I, the historical LE parm-string sequence was and is (first ordering) PARM='LE environmental options/program data' Initially, COBOL got it backwards, as (second ordering) PARM='program data/LE environmental options' This second ordering is called the COBOL-options convention. Specifying CBLOPTS(OFF) at LE installation time selects the first ordering, making COBOL behave like the other languages. Specifying CBLOPTS(ON) instead yields the second ordering. Thus for CBLOPTS(OFF) and LE environmental options equal to a null string (missing), PARM=' /program data' is required; and for CBLOPTS(ON) and LE environmental options missing PARM='program data/' is required instead. The z/OS Language Environment Programming Reference, SA22-7562, dscusses these matters at length. -- 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: Using symbolic in JCL
In [EMAIL PROTECTED], on 11/25/2005 at 08:01 AM, Paul Gilmartin [EMAIL PROTECTED] said: No joy. Dammit, how many things can IBM do wrong in the JCL parser? Which JCL parser? JES2 and JES3 parse their respective control statements before the C/I ever sees them. It's that simple! No it's not :-( -- 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: WELLS FARGO QUESTION
In [EMAIL PROTECTED], on 11/25/2005 at 03:47 PM, [EMAIL PROTECTED] [EMAIL PROTECTED] said: (1) Certificates of Deposit: Certificates in my family's name were, without authorization, put in someone else's name, and ours replaced. The bank attributes this to a computer error, without explanation. Possible but not likely. My experience over decades has been that 99.44% of computer errors in accounts are either human errors or fraud[1][2]. (2) Home Mortgage: Wells Fargo changed my home mortgage account, without consent, so that I was bumped from primary customer to additional customer, and the same stranger who appeared on the CD accounts became the primary customer. See above. (3) Home Equity Line of Credit: Wells Fargo says the same computer error caused the change in ownership by replacing my spouse s name with that of the person who appeared on the other accounts. See above. Never attribute to malice what can be explained by incompetence. (Al Miller) My guess is that somebody made a systemic error. The fact that they are relying on customers to catch problems is a red flag, and I would be worried about the problems that nobody has noticed yet. In your place I'd be writing the Fed and the local regulator agencies and suggesting that an intensive audit is long overdue. Somebody was asleep at the switch. [1] But a well run bank would have trip-wires in place to catch embezzlement attempts, so it still gets back to incompetence or an unprecedented stream of bad luck. [2] Some of the places using that excuse in the old days didn't even have a computer ;-) -- 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: PSP information
Chris Mason wrote: Gadi, When you copy and paste to your browser just remove the comma that unfortunately got added to the URL. I'm sure in the original context it was the correct grammar but it got incorporated into the URL. The correct URL is https://techsupport.services.ibm.com/server/390.psp390 and this sentence only has a full stop - or should that be period? - only because I added some more text and didn't add it immediately after the URL. Chris Mason If John Giltner is reading this I'm trying this post after having removed the IBM-MAIN text. Let's see if it works. - Original Message - From: גדי בן אבי [EMAIL PROTECTED] Newsgroups: bit.listserv.ibm-main To: IBM-MAIN@BAMA.UA.EDU Sent: Sunday, 27 November, 2005 2:16 PM Subject: PSP information Hi, I am trying to get to the PSP site. My serverpac installation guide tells me to go to https://techsupport.services.ibm.com/server/390.psp390, but this site doesn't seem to work. Does anyone know what the 'new' PSP site is? TIA Gadi Reading and it looks like it worked. -- 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: Introducing delay in a assembler.
-Thanks to all , Now I am getting it right. Regards, Jerry -- 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: PSP information
Hi, Thanx to everyone who answered. It looks like there is something in our firewall that is blocking this address. Gadi -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of John S. Giltner, Jr. Sent: Monday, November 28, 2005 6:00 AM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: PSP information Chris Mason wrote: Gadi, When you copy and paste to your browser just remove the comma that unfortunately got added to the URL. I'm sure in the original context it was the correct grammar but it got incorporated into the URL. The correct URL is https://techsupport.services.ibm.com/server/390.psp390 and this sentence only has a full stop - or should that be period? - only because I added some more text and didn't add it immediately after the URL. Chris Mason If John Giltner is reading this I'm trying this post after having removed the IBM-MAIN text. Let's see if it works. - Original Message - From: גדי בן אבי [EMAIL PROTECTED] Newsgroups: bit.listserv.ibm-main To: IBM-MAIN@BAMA.UA.EDU Sent: Sunday, 27 November, 2005 2:16 PM Subject: PSP information Hi, I am trying to get to the PSP site. My serverpac installation guide tells me to go to https://techsupport.services.ibm.com/server/390.psp390, but this site doesn't seem to work. Does anyone know what the 'new' PSP site is? TIA Gadi Reading and it looks like it worked. -- 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
slash in PARM strings
M. Ray Mullins [EMAIL PROTECTED] wrote: The whole slash business in COBOL goes back to the OS/VS COBOL days, before LE was even a blip on the PL/I radar (yes, that's where the LE stuff originated, and why COBOL had to adapt to LE). Well, the slash PARM separator goes at least back to the OS/360 loader which has its own parms separate from those of the program it is loading and executing. -- glen -- 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
MAXCC=2000
Hi all, I am right now in the phase of testing my application. One of my testcase involves uninterrupted start and shutdown of my application. I find no problem with my application for atleast 40 minutes but after some time the JOB ends with the following message in the log- SE '22.44.52 JOB09909 $HASP165 VCM60 ENDED AT N1 MAXCC=2000',LOGON, USER=(NAXZY) I am also getting a CEEDUMP after this message. Please help me in knowing what the error actually means. I am worried whether there is anything to do with the configuration of the system. Thanks in advance, Jerry. -- 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: Early Release of JES2 SPOOL space for spin-off data sets
We're talking real spin-off data sets here, right? The way I do it is with a started job (in other words: Give the STC a jobcard) and putting JESLOG=(SPIN,'00:00') in the job card. It looks a little strange via SDSF DA and ? and gives me a JESYSMSG and JESMSGLG per day. Comes in mighty handy for STCs that have a lot of system WTOs, though. Regards, Barbara Nitz -- Lust, ein paar Euro nebenbei zu verdienen? Ohne Kosten, ohne Risiko! Satte Provisionen für GMX Partner: http://www.gmx.net/de/go/partner -- 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: how to lose a sysplex in 30 seconds
As a result, MVSB (running in site B) lost its connectivity to the primary SYSPELX couple data set residing on dasd in site A, and issued the following message: IXC253I The above message was then issued by MVSA as well. Sadly enough, our alternate SYSPLEX couple data set resides on dasd in site B. So MVSA had no connectivity to it, which led to a Disabled Wait 0A2 RC 20 in MVSA. When you loose the primary sysplex CDS, MVS indepently of each other will attempt the switch to the alternate sysplex CDS. MVSB could connect since the alternate was in site B, MVSA could not and entered the wait state without further ado to keep data integrity. After that, MVSB issued the following message: IXC256A REMOVAL OF PRIMARY COUPLE DATA SET XCF.COUPLE01 FOR SYSPLEX CANNOT COMPLETE UNTIL THE FOLLOWING SYSTEM(S) ACKNOWLEDGE THE REMOVAL: MVSA Of course, MVSA could never acknowledge since it was in a disabled wait. And they could not communicate with each other. Does 'lost communication' also mean that all (signalling) CTCs and all signalling structures were lost? Answering my own question: Probably yes, since otherwise MVSB would have known that MVSA had wait stated itself. IXC256A rolled off the MVSB console (which was in DEL=R mode), so by the time I got to the console I couldnt see it and didnt know it was issued. At MVSB's console, I issued a D R,R and didnt see anything. Since this is not a reply, you wouldn't. Do you use AMRF? This is a CE message and if AMRF is used, it would have been retained. After I saw why MVSA entered the wait, I issued D XCF,C at MVSB's console and never got a response. Strange. I think you should have seen that the system was in the middle of the CDS switch. Eventually we IPLed both MVSB and MVSA because it seemed like MVSB was hung... Yes, it would. All XCF requests get delayed. And you wouldn't believe what needs XCF these days. I realize there were many mistakes done along the way here, my question is, how could I know that IXC256A was issued if it rolled off the console TSO/E was hung too)?? If i knew it was issued, i would issue a V XCF,MVSA,OFFLINE,FORCE and let MVSB complete its couple data set switch... Have automation in place that on IXC256a will do the following: 1. Set all consoles to DEL=RD 2. Re-issue the message in red Also, I dont understand the logic here. MVSA had access to the primary, but not to the alternate. MVSB had access to the alternate, but not to the primary. Still, MVSA disabled wait and MVSB stayed up, hung until MVSA cleanup... Integrity requires that all members of the sysplex have to have the same primary CDS. Without seeing the actual messages, it is unclear to me if maybe MVSA issued the IXC253I for the alternate CDS as it couldn't get to it. That would mean that there was sysplex communication still going on via CF or CTC, so MVSA had seen MVSB's request to switch to the alternate (that would get communicated across the sysplex) but due to later loss of communication couldn't tell MVSB that it would wait state itself. In either case, I ended up with half a sysplex in a disabled wait and half hung. Which got me thinking... what if there were 7 systems on site A and only 1 system on site B?? would z/OS logic still be to enter 7 systems into a disabled wait instead of only the 1 system that lost access to the primary??? I believe that without SFM, yes that would be the logic on the premise that all systems have to have the same primary and alternate CDS. But I can be wrong on this. Basically you can say we learned the true value of SFM. Had we been using it, it would probably prevent the hang in MVSB, because it would clean up the mess left by MVSA after it entered the disabled wait. Would SFM also help in the 7-1 case?? SFM would have helped only in the sense that it would have detected that MVSA was not updating its status anymore (since it was wait stated). Depending on policy, you would have either gotten IXC402D or an automatic removal from the sysplex. I don't think that the 7-1 issue would be addressed by SFM at all, as SFM weights are for 'status update missing' conditions, not for loss of connectivity to the sysplex CDS due to I/O error. Best regards, Barbara Nitz -- 10 GB Mailbox, 100 FreeSMS/Monat http://www.gmx.net/de/go/topmail +++ GMX - die erste Adresse für Mail, Message, More +++ -- 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: CA-1 to RMM Conversion
Hi James, I have sent you an Email with several documents including a project plan, so this should get you going. Major observations: 1) Garbage In = Garbage Out Cleaning up all TMC volume (VOL) and data set (DSNB) chaining errors is mandatory, but also perform a housekeeping exercise to identify and delete any other obsolete or erroneous TMC resources (E.g. Locations, Volumes, et al). 2) DFSMSrmm runs in parallel (Warning Mode) with any other TMS Use this feature wisely. Perform the actual conversion as many times as you need to, but run in parallel for at least a week, ideally a month, anything longer might be overkill. This allows all personnel (E.g. Operations, Storage Administration, et al) an opportunity to acclimatise. There will be differences in the way that DFSMSrmm performs expiration (E.g. Scratch via EXPROC) and vaulting (E.g. Move via DSTORE). 3) Decide on your reporting strategy CA-1 has its own built in reports and we have probably used these for years and take them for granted. DFSMSrmm has a plethora of reporting options but doesnt have a Generalised Report Writer (E.g. TMSGRW) and so your options are numerous (E.g. DFSMSrmm House-Keeping Reports, Sort, Rexx, SAS, et al). You just need to decide which methodology is best for your installation. Generally I would recommend creating a flat file from the DFSMSrmm CDS via the EDGHSKP REPTEXT function and this file has numerous mapping macros (E.g. MXG, ASM DESCT, et al) and so the world is your oyster so to speak Regards, UK Mikey. PS. I have performed nn DFSMSrmm conversions since the early 1990s and if I can do them, it should be a walk in the park for you! On Mon, 28 Nov 2005 10:50:43 +0800, James Smith [EMAIL PROTECTED] wrote: Folks Does anyone out there have a CA-1 to RMM conversion plan that they would be willing to share? Lots of great information in the conversion Redbook but it would be nice to see a 'real, live' plan. Jim S -- 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: MAXCC=2000
The job step is ending with return code 2000. You'll need to lookup the meaning of return code in your application doc. The SE message you see in the log is due to a NOTIFY=NAXYZ on the job statement. It is simply sending a job termination message to user NAXYZ's TSO session and is not related to whether the job ends normally or in error. Peter Hunkeler Credit Suisse - Information Technology -- 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
