Re: JES NOTIFY EMAIL=
So, I wanted to circle back around on this topic. I just saw the Share presentation slides for session 25309 "What's new in z/OSMF in V2.4". I've got V2.4 Serverpac installed, just not IPLed anywhere yet, but looking at the slides I predict that IBM has hit this one out of the ball park! Besides all the new features, there is a Security Configuration Assistant that appears to really dissect the required security setup, as well as provide diagnostics process on what needs to be done. https://share.confex.com/share/133/webprogrameval/Session25309.html I look forward to taking a new look at this. _ Dave Jousma AVP | Manager, Systems Engineering Fifth Third Bank | 1830 East Paris Ave, SE | MD RSCB2H | Grand Rapids, MI 49546 616.653.8429 | fax: 616.653.2717 -Original Message- From: IBM Mainframe Discussion List On Behalf Of Carmen Vitullo Sent: Monday, November 11, 2019 8:44 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: JES NOTIFY EMAIL= **CAUTION EXTERNAL EMAIL** **DO NOT open attachments or click on links from unknown senders or unexpected emails** thanks for your insight Brian, I'll have to check my security once, more, I would hope IBM support would have seen the security issues back in August when I opened the PMR and received the first trace as I said before they assured my my security was setup correctly Carmen Vitullo - Original Message - From: "Brian Westerman" To: IBM-MAIN@LISTSERV.UA.EDU Sent: Saturday, November 9, 2019 4:27:48 PM Subject: Re: JES NOTIFY EMAIL= On Fri, 8 Nov 2019 09:35:43 -0600, Carmen Vitullo wrote: >David I feel your pain, we are also a TSS shop, CA (BROADCOM) has some good >doc on converting RACF to TSS, if you need I'll see if I can get the link to >you. > >my previous reply to Brian never was posted, > >agree, and what I do not understand, is the freebee software like JES2MAIL and >other paid products work well, access our SMTP passthru server with no issues, >this is not just a JES2EDS issue, but a normal notification issue from z/OSMF, >I can sent email's from OPS, from JCL batch, no issues, using the same >configuration, I'm trying to get ahead of the game and setup all the parts >pieces for z/OSMF, I suspect the notification, once we're are forced to us >this POC, will be very important. >another trace yesterday sent to level 2, SEV2 ticket still open since Aug 27th >:( > >-- >For IBM-MAIN subscribe / signoff / archive access instructions, >send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN Yes, the problem with the new JES mail option isn't getting CSSMTP to work with it, you will likely find that you missed one of the install steps or misinterpreted the results like I did (3 times). I ended up going through the entire install 4 times before I got it "right" thinking that everything was fine each time and it turned out that while the steps all seemed to have worked, checking the content of the issued messages themselves pointed to the problem I had with the izudflt.zosmf.notification.notify part. It turned out that no one (except zosmf itself) was authorized to send the email. :( But even when it was done and completely implemented, it wasn't even as nice as the stuff you can get off the freeware tapes. It is a particular pain to have to actually add the notify card to the jobs. I think there are several better ways that it could have been handled and it could have been much more comprehensively implemented. While it doesn't "suck" per se, it's not really worth the enormous effort for such a small "feature". If you already are running z/OSMF, then adding it is not going to really be a big deal, but I don't see any part of it which is worth the effort to implement (and actually run since z/OSMF is installed for you at serverpak now), all of z/OSMF just to get the notify part. I just keep falling back to the fact that if you don't make something simple and easy to use, that most people just won't bother to use it, at least not when it counts. We made SyzMPF/z and SyzMAIL/z so that normal installation is on the order of 10 minutes or less. I can't imagine what they were thinking when they decided to design the notify feature of z/OSMF but I'm thinking that it wasn't ease of implementation or use. :) Brian Westerman Syzygy Incorporated https://protect2.fireeye.com/url?k=ec44547c-b018a073-ec447ee4-0cc47a33347c-11d4d09cb136ba57=http://www.syzygyinc.com/ -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN --
Re: JES NOTIFY EMAIL=
thanks for your insight Brian, I'll have to check my security once, more, I would hope IBM support would have seen the security issues back in August when I opened the PMR and received the first trace as I said before they assured my my security was setup correctly Carmen Vitullo - Original Message - From: "Brian Westerman" To: IBM-MAIN@LISTSERV.UA.EDU Sent: Saturday, November 9, 2019 4:27:48 PM Subject: Re: JES NOTIFY EMAIL= On Fri, 8 Nov 2019 09:35:43 -0600, Carmen Vitullo wrote: >David I feel your pain, we are also a TSS shop, CA (BROADCOM) has some good >doc on converting RACF to TSS, if you need I'll see if I can get the link to >you. > >my previous reply to Brian never was posted, > >agree, and what I do not understand, is the freebee software like JES2MAIL and >other paid products work well, access our SMTP passthru server with no issues, >this is not just a JES2EDS issue, but a normal notification issue from z/OSMF, >I can sent email's from OPS, from JCL batch, no issues, using the same >configuration, I'm trying to get ahead of the game and setup all the parts >pieces for z/OSMF, I suspect the notification, once we're are forced to us >this POC, will be very important. >another trace yesterday sent to level 2, SEV2 ticket still open since Aug 27th >:( > >-- >For IBM-MAIN subscribe / signoff / archive access instructions, >send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN Yes, the problem with the new JES mail option isn't getting CSSMTP to work with it, you will likely find that you missed one of the install steps or misinterpreted the results like I did (3 times). I ended up going through the entire install 4 times before I got it "right" thinking that everything was fine each time and it turned out that while the steps all seemed to have worked, checking the content of the issued messages themselves pointed to the problem I had with the izudflt.zosmf.notification.notify part. It turned out that no one (except zosmf itself) was authorized to send the email. :( But even when it was done and completely implemented, it wasn't even as nice as the stuff you can get off the freeware tapes. It is a particular pain to have to actually add the notify card to the jobs. I think there are several better ways that it could have been handled and it could have been much more comprehensively implemented. While it doesn't "suck" per se, it's not really worth the enormous effort for such a small "feature". If you already are running z/OSMF, then adding it is not going to really be a big deal, but I don't see any part of it which is worth the effort to implement (and actually run since z/OSMF is installed for you at serverpak now), all of z/OSMF just to get the notify part. I just keep falling back to the fact that if you don't make something simple and easy to use, that most people just won't bother to use it, at least not when it counts. We made SyzMPF/z and SyzMAIL/z so that normal installation is on the order of 10 minutes or less. I can't imagine what they were thinking when they decided to design the notify feature of z/OSMF but I'm thinking that it wasn't ease of implementation or use. :) Brian Westerman Syzygy Incorporated www.SyzygyInc.com -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: JES NOTIFY EMAIL=
On Fri, 8 Nov 2019 09:35:43 -0600, Carmen Vitullo wrote: >David I feel your pain, we are also a TSS shop, CA (BROADCOM) has some good >doc on converting RACF to TSS, if you need I'll see if I can get the link to >you. > >my previous reply to Brian never was posted, > >agree, and what I do not understand, is the freebee software like JES2MAIL and >other paid products work well, access our SMTP passthru server with no issues, >this is not just a JES2EDS issue, but a normal notification issue from z/OSMF, >I can sent email's from OPS, from JCL batch, no issues, using the same >configuration, I'm trying to get ahead of the game and setup all the parts >pieces for z/OSMF, I suspect the notification, once we're are forced to us >this POC, will be very important. >another trace yesterday sent to level 2, SEV2 ticket still open since Aug 27th >:( > >-- >For IBM-MAIN subscribe / signoff / archive access instructions, >send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN Yes, the problem with the new JES mail option isn't getting CSSMTP to work with it, you will likely find that you missed one of the install steps or misinterpreted the results like I did (3 times). I ended up going through the entire install 4 times before I got it "right" thinking that everything was fine each time and it turned out that while the steps all seemed to have worked, checking the content of the issued messages themselves pointed to the problem I had with the izudflt.zosmf.notification.notify part. It turned out that no one (except zosmf itself) was authorized to send the email. :( But even when it was done and completely implemented, it wasn't even as nice as the stuff you can get off the freeware tapes. It is a particular pain to have to actually add the notify card to the jobs. I think there are several better ways that it could have been handled and it could have been much more comprehensively implemented. While it doesn't "suck" per se, it's not really worth the enormous effort for such a small "feature". If you already are running z/OSMF, then adding it is not going to really be a big deal, but I don't see any part of it which is worth the effort to implement (and actually run since z/OSMF is installed for you at serverpak now), all of z/OSMF just to get the notify part. I just keep falling back to the fact that if you don't make something simple and easy to use, that most people just won't bother to use it, at least not when it counts. We made SyzMPF/z and SyzMAIL/z so that normal installation is on the order of 10 minutes or less. I can't imagine what they were thinking when they decided to design the notify feature of z/OSMF but I'm thinking that it wasn't ease of implementation or use. :) Brian Westerman Syzygy Incorporated www.SyzygyInc.com -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: JES NOTIFY EMAIL=
David I feel your pain, we are also a TSS shop, CA (BROADCOM) has some good doc on converting RACF to TSS, if you need I'll see if I can get the link to you. my previous reply to Brian never was posted, agree, and what I do not understand, is the freebee software like JES2MAIL and other paid products work well, access our SMTP passthru server with no issues, this is not just a JES2EDS issue, but a normal notification issue from z/OSMF, I can sent email's from OPS, from JCL batch, no issues, using the same configuration, I'm trying to get ahead of the game and setup all the parts pieces for z/OSMF, I suspect the notification, once we're are forced to us this POC, will be very important. another trace yesterday sent to level 2, SEV2 ticket still open since Aug 27th :( -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: JES NOTIFY EMAIL=
I agree with everything you just said. :) I also don’t personally care for the fact that JES2 has to rely on a function of z/OSMF for this feature. Give me the option to either leverage zOSMF, or a more generic option to write the notifications to a site specified JES NODE/output class that happens to have a SMTP/CSSMTP server listening on it. I'm confident that we'll eventually "get there" with zOSMF. I just don’t have the cycles right now to plow through the security requirements for user access. That part just needs to be easier. I'd love to see something (and I'm over simplifying here), almost like the old days of omegamon where you just permitted certain prebuilt "levels" of access. The fact we are TopSecret shop doesn’t make it any easier, and I know there are cook books to assist. Oh well, I'll quit complaining. _ Dave Jousma AVP | Manager, Systems Engineering Fifth Third Bank | 1830 East Paris Ave, SE | MD RSCB2H | Grand Rapids, MI 49546 616.653.8429 | fax: 616.653.2717 -Original Message- From: IBM Mainframe Discussion List On Behalf Of Brian Westerman Sent: Friday, November 8, 2019 1:37 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: JES NOTIFY EMAIL= One of the reasons, several years ago, that we decided not to do automated email the way IBM has implemented theirs was because the setup that we would have had to force on the client site was extremely difficult and there are several moving parts that have to all be in sync. It took me almost an entire day just to get IBM's JES NOTIFY working correctly and when I finished I was not impressed with the results. It's actually far less than I expected, but the good news is that it's not going to be any competition for SyzMFF/z or SyzEMAIl/z any time soon, if ever. :) I think IBM was trying to make it so that you can take advantage of the /* JECL and some of the job accounting fields, without resorting to exits, (which is what I did for the Syzygy Suite), but I think they ended up taking the long way around to get there, or maybe they wanted to make sure that they could support Jes2 and Jes3 (even though now they have decided to ditch JES3) with the same code layer, but I think basing anything on z/OSMF is a bad idea. Not may sites have seen any benefit that outweighs the effort and some sites don't have the extra CPU cycles to spend on it. Possibly someday z/OSMF will be better but it appears to be a slow process that part of IBM is embracing and part isn't. Also unfortunate is the amount of new stuff that is now z/OSMF only. Probably thinking sites will be forced to use it anyway, but all it really seems to be doing is turning them off. At least that's my take on what I have been hearing from our customers. Personally I like a lot of things about z/OSMF, but I think the approach IBM is taking with it is a bad idea. Brian Westerman Syzygy Incorporated www.SyzygyInc.com This e-mail transmission contains information that is confidential and may be privileged. It is intended only for the addressee(s) named above. If you receive this e-mail in error, please do not read, copy or disseminate it in any manner. If you are not the intended recipient, any disclosure, copying, distribution or use of the contents of this information is prohibited. Please reply to the message immediately by informing the sender that the message was misdirected. After replying, please erase it from your computer system. Your assistance in correcting this error is appreciated. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: JES NOTIFY EMAIL=
One of the reasons, several years ago, that we decided not to do automated email the way IBM has implemented theirs was because the setup that we would have had to force on the client site was extremely difficult and there are several moving parts that have to all be in sync. It took me almost an entire day just to get IBM's JES NOTIFY working correctly and when I finished I was not impressed with the results. It's actually far less than I expected, but the good news is that it's not going to be any competition for SyzMFF/z or SyzEMAIl/z any time soon, if ever. :) I think IBM was trying to make it so that you can take advantage of the /* JECL and some of the job accounting fields, without resorting to exits, (which is what I did for the Syzygy Suite), but I think they ended up taking the long way around to get there, or maybe they wanted to make sure that they could support Jes2 and Jes3 (even though now they have decided to ditch JES3) with the same code layer, but I think basing anything on z/OSMF is a bad idea. Not may sites have seen any benefit that outweighs the effort and some sites don't have the extra CPU cycles to spend on it. Possibly someday z/OSMF will be better but it appears to be a slow process that part of IBM is embracing and part isn't. Also unfortunate is the amount of new stuff that is now z/OSMF only. Probably thinking sites will be forced to use it anyway, but all it really seems to be doing is turning them off. At least that's my take on what I have been hearing from our customers. Personally I like a lot of things about z/OSMF, but I think the approach IBM is taking with it is a bad idea. Brian Westerman Syzygy Incorporated www.SyzygyInc.com -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: JES NOTIFY EMAIL=
Sounds like a good reason to wait. $DS($EDSQ*) $HASP003 RC=(52),D 262 $HASP003 RC=(52),D S($EDSQ*) - NO SELECTABLE ENTRIES FOUND $HASP003 MATCHING SPECIFICATION mail is not getting to the list :( I have an open case (PMR) with IBM Z/OSMF support due to this and other issues, It started with JES2 support and JES2EDS, there is a PTF to fix some issues with JES2EDS not shutting down with JES2 $PJES2, my case has been open since August 27th, traces, tests, more traces, tests, and still no fix. only thing I get out of support...my setup is correct, security definitions are correct.. and we're support to use this new fangled tool :( to maintain the OS. counting the daze till retirement sorry, also purging the elements require $PS($EDSQnnn) check the status screen from SDSF to get the nnn or the JES2 display $DS($EDSQ*) This e-mail transmission contains information that is confidential and may be privileged. It is intended only for the addressee(s) named above. If you receive this e-mail in error, please do not read, copy or disseminate it in any manner. If you are not the intended recipient, any disclosure, copying, distribution or use of the contents of this information is prohibited. Please reply to the message immediately by informing the sender that the message was misdirected. After replying, please erase it from your computer system. Your assistance in correcting this error is appreciated. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: JES NOTIFY EMAIL=
mail is not getting to the list :( I have an open case (PMR) with IBM Z/OSMF support due to this and other issues, It started with JES2 support and JES2EDS, there is a PTF to fix some issues with JES2EDS not shutting down with JES2 $PJES2, my case has been open since August 27th, traces, tests, more traces, tests, and still no fix. only thing I get out of support...my setup is correct, security definitions are correct.. and we're support to use this new fangled tool :( to maintain the OS. counting the daze till retirement sorry, also purging the elements require $PS($EDSQnnn) check the status screen from SDSF to get the nnn or the JES2 display $DS($EDSQ*) -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: JES NOTIFY EMAIL=
Yea, tried that too. If I get JES2EDS address space fired up, it may work. Looking at books to get ZOSMF notifications configured too. Looks like a bunch of additional security setup needed. _ Dave Jousma AVP | Manager, Systems Engineering Fifth Third Bank | 1830 East Paris Ave, SE | MD RSCB2H | Grand Rapids, MI 49546 616.653.8429 | fax: 616.653.2717 -Original Message- From: IBM Mainframe Discussion List On Behalf Of Steve Smith Sent: Thursday, November 7, 2019 9:40 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: JES NOTIFY EMAIL= **CAUTION EXTERNAL EMAIL** **DO NOT open attachments or click on links from unknown senders or unexpected emails** Good grief! $HASP003 seems to be a bundle of 167 not-obviously-related messages. Anyway, for RC=(89) the explanation doesn't appear relevant. You might try $PJ9832... I wouldn't bet on it working, but I would that you found a bug. sas On Thu, Nov 7, 2019 at 7:52 AM Jousma, David < 01a0403c5dc1-dmarc-requ...@listserv.ua.edu> wrote: > So, after playing around on my tech system with JCL NOTIFY statement > with email, I found that I have some additional configuration to do to > enable, namely setup the JES2EDS in security. Don't really have time > to mess around with making that and ZOSMF email setup to work at the moment. > > The odd thing is that the couple BR14 jobs I submitted to see the error > are now not purgeable by any command I can think of. They are only > visible on the STATUS panel, nothing in HELD or OUTPUT. Any ideas? > > -$CJ(9831) > JOB09831 $HASP003 RC=(89),C J(9831) - JOB CANNOT BE CANCELLED > -$CJ(9832) > JOB09831 $HASP890 JOB(E) >$HASP890 JOB(E) STATUS=(AWAITING OUTPUT),CLASS=X, >$HASP890PRIORITY=15,SYSAFF=(ANY),HOLD=(NONE), >$HASP890PURGE=YES,CANCEL=YES > JOB09832 $HASP003 RC=(89),C J(9832) - JOB CANNOT BE CANCELLED > JOB09832 $HASP890 JOB(E) >$HASP890 JOB(E) STATUS=(AWAITING OUTPUT),CLASS=X, >$HASP890PRIORITY=1,SYSAFF=(ANY),HOLD=(NONE), >$HASP890PURGE=YES,CANCEL=YES > -$CJOB(*),QUEUE=OUT > JOB09831 $HASP003 RC=(89),C JOB(*) - JOB CANNOT BE CANCELLED > JOB09832 $HASP003 RC=(89),C JOB(*) - JOB CANNOT BE CANCELLED > > > __ > ___ > Dave Jousma > AVP | Manager, Systems Engineering > [cid:image003.png@01D4F915.C9E34050] > > Fifth Third Bank | 1830 East Paris Ave, SE | MD RSCB2H | Grand > Rapids, MI 49546 > 616.653.8429 | fax: 616.653.2717 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN **CAUTION EXTERNAL EMAIL** **DO NOT open attachments or click on links from unknown senders or unexpected emails** This e-mail transmission contains information that is confidential and may be privileged. It is intended only for the addressee(s) named above. If you receive this e-mail in error, please do not read, copy or disseminate it in any manner. If you are not the intended recipient, any disclosure, copying, distribution or use of the contents of this information is prohibited. Please reply to the message immediately by informing the sender that the message was misdirected. After replying, please erase it from your computer system. Your assistance in correcting this error is appreciated. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: JES NOTIFY EMAIL=
Good grief! $HASP003 seems to be a bundle of 167 not-obviously-related messages. Anyway, for RC=(89) the explanation doesn't appear relevant. You might try $PJ9832... I wouldn't bet on it working, but I would that you found a bug. sas On Thu, Nov 7, 2019 at 7:52 AM Jousma, David < 01a0403c5dc1-dmarc-requ...@listserv.ua.edu> wrote: > So, after playing around on my tech system with JCL NOTIFY statement with > email, I found that I have some additional configuration to do to enable, > namely setup the JES2EDS in security. Don't really have time to mess > around with making that and ZOSMF email setup to work at the moment. > > The odd thing is that the couple BR14 jobs I submitted to see the error > are now not purgeable by any command I can think of. They are only > visible on the STATUS panel, nothing in HELD or OUTPUT. Any ideas? > > -$CJ(9831) > JOB09831 $HASP003 RC=(89),C J(9831) - JOB CANNOT BE CANCELLED > -$CJ(9832) > JOB09831 $HASP890 JOB(E) >$HASP890 JOB(E) STATUS=(AWAITING OUTPUT),CLASS=X, >$HASP890PRIORITY=15,SYSAFF=(ANY),HOLD=(NONE), >$HASP890PURGE=YES,CANCEL=YES > JOB09832 $HASP003 RC=(89),C J(9832) - JOB CANNOT BE CANCELLED > JOB09832 $HASP890 JOB(E) >$HASP890 JOB(E) STATUS=(AWAITING OUTPUT),CLASS=X, >$HASP890PRIORITY=1,SYSAFF=(ANY),HOLD=(NONE), >$HASP890PURGE=YES,CANCEL=YES > -$CJOB(*),QUEUE=OUT > JOB09831 $HASP003 RC=(89),C JOB(*) - JOB CANNOT BE CANCELLED > JOB09832 $HASP003 RC=(89),C JOB(*) - JOB CANNOT BE CANCELLED > > > _ > Dave Jousma > AVP | Manager, Systems Engineering > [cid:image003.png@01D4F915.C9E34050] > > Fifth Third Bank | 1830 East Paris Ave, SE | MD RSCB2H | Grand > Rapids, MI 49546 > 616.653.8429 | fax: 616.653.2717 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
JES NOTIFY EMAIL=
So, after playing around on my tech system with JCL NOTIFY statement with email, I found that I have some additional configuration to do to enable, namely setup the JES2EDS in security. Don't really have time to mess around with making that and ZOSMF email setup to work at the moment. The odd thing is that the couple BR14 jobs I submitted to see the error are now not purgeable by any command I can think of. They are only visible on the STATUS panel, nothing in HELD or OUTPUT. Any ideas? -$CJ(9831) JOB09831 $HASP003 RC=(89),C J(9831) - JOB CANNOT BE CANCELLED -$CJ(9832) JOB09831 $HASP890 JOB(E) $HASP890 JOB(E) STATUS=(AWAITING OUTPUT),CLASS=X, $HASP890PRIORITY=15,SYSAFF=(ANY),HOLD=(NONE), $HASP890PURGE=YES,CANCEL=YES JOB09832 $HASP003 RC=(89),C J(9832) - JOB CANNOT BE CANCELLED JOB09832 $HASP890 JOB(E) $HASP890 JOB(E) STATUS=(AWAITING OUTPUT),CLASS=X, $HASP890PRIORITY=1,SYSAFF=(ANY),HOLD=(NONE), $HASP890PURGE=YES,CANCEL=YES -$CJOB(*),QUEUE=OUT JOB09831 $HASP003 RC=(89),C JOB(*) - JOB CANNOT BE CANCELLED JOB09832 $HASP003 RC=(89),C JOB(*) - JOB CANNOT BE CANCELLED _ Dave Jousma AVP | Manager, Systems Engineering [cid:image003.png@01D4F915.C9E34050] Fifth Third Bank | 1830 East Paris Ave, SE | MD RSCB2H | Grand Rapids, MI 49546 616.653.8429 | fax: 616.653.2717 This e-mail transmission contains information that is confidential and may be privileged. It is intended only for the addressee(s) named above. If you receive this e-mail in error, please do not read, copy or disseminate it in any manner. If you are not the intended recipient, any disclosure, copying, distribution or use of the contents of this information is prohibited. Please reply to the message immediately by informing the sender that the message was misdirected. After replying, please erase it from your computer system. Your assistance in correcting this error is appreciated. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
