AW: Re: Would SHARE kindly kick IBM in the ass for what the've done with their web content?
Hello Harry,thank you very much for you response, and especially for picking this up. I know the subject I chose was a bit harshly formulated, but I did this on purpose. I was hoping that it would get things going, and it did. I'm grateful. Best regardsPeter -- Peter Hunkeler -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
AW: z/OS Internet Library Broken (again)
ROTFLOL. This is ridiculous, IBM! Case b) below is an intra-page reference; they don't get even this most basic of HTML right. -- Peter Hunkeler >b) Redisplays the same page: >https://www-304.ibm.com/servers/resourcelink/svc00100.nsf/pages/zosv2r2-pdf-download?OpenDocument#DGW -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Would SHARE kindly kick IBM in the ass for what the've done with their web content?
Dear Peter I apologize for not responding sooner to your plea for help, but I do want to publicly respond on behalf of SHARE. SHARE is a community of people representing users of enterprise technology. As such, we regularly participate in discussions with various vendors in the Z ecosystem to influence the ability of those within the ecosystem to accomplish their business objectives, and that includes regular conversations with IBM. We do often find that open, frank conversations in private achieves more than ass-kicking in public so our response may be quieter. Because of you and others, we are aware of the situation with z/OS 2.1 documentation and others that are at risk. For the information of IBM-MAIN readers, several members of the SHARE community have been actively engaging IBM on this issue for some weeks now, through a variety of formal as well as informal channels. As those efforts continue, please be assured that SHARE’s leadership is well aware of the concern and stands ready to assist as appropriate. SHARE is always willing to listen in order to determine if there is a role that we can and should play to solve a problem that is impacting the ecosystem, regardless if someone is a Member of SHARE. The best way to reach out to us to start those conversations is via email to shar...@share.org A. Harry Williams President SHARE Association -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: z/OS Internet Library Broken (again)
I ran into an issue this weekend looking for a z/OS 2.2 manual. What happened was when I selected a link to a 2.2 manual I got a 2.1 manual. With some hunting I was able to find the 2.2 version of the manual. I reported this issue to the "feedback" link over the weekend. When I was asked "How likely are you to recommend the ibm.com website to a colleague or business partner?" I gave it a 0 (zero). I'm not going to recommend something that is broken. Thanks.. Paul Feller AGT Mainframe Technical Support -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Allan Staller Sent: Wednesday, June 27, 2018 1:05 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: z/OS Internet Library Broken (again) This seems to be an exact duplicate of the problem repaired a couple of weeks ago! https://urldefense.proofpoint.com/v2/url?u=https-3A__www-2D304.ibm.com_servers_resourcelink_svc00100.nsf_pages_zosInternetLibrary-3FOpenDocument=DwIFAg=9g4MJkl2VjLjS6R4ei18BA=eUhu3PeeWy6RTndlJVKembFjFsvwCa8eeU_gm45NyOc=WeBzk67HDzbrSL1pq4yZsym0yD4vV0ug_LSnOE0ggMY=TXBewknfxUJkrkzg9dgCjYk7CYToJWvWW_Yz0gvCJ-U= Select "Download Books in PDF Format" for z/OS 2.2. Displays URL below: https://urldefense.proofpoint.com/v2/url?u=https-3A__www-2D304.ibm.com_servers_resourcelink_svc00100.nsf_pages_zosv2r2-2Dpdf-2Ddownload-3FOpenDocument=DwIFAg=9g4MJkl2VjLjS6R4ei18BA=eUhu3PeeWy6RTndlJVKembFjFsvwCa8eeU_gm45NyOc=WeBzk67HDzbrSL1pq4yZsym0yD4vV0ug_LSnOE0ggMY=93wrbTwQSIQ6dlJXBvdcjkSPSKgkwADnSdyG0wjRl4Q= Select anything from the selections displayed will show: a) HTTP 404 error message b) Redisplays the same page: https://urldefense.proofpoint.com/v2/url?u=https-3A__www-2D304.ibm.com_servers_resourcelink_svc00100.nsf_pages_zosv2r2-2Dpdf-2Ddownload-3FOpenDocument-23DGW=DwIFAg=9g4MJkl2VjLjS6R4ei18BA=eUhu3PeeWy6RTndlJVKembFjFsvwCa8eeU_gm45NyOc=WeBzk67HDzbrSL1pq4yZsym0yD4vV0ug_LSnOE0ggMY=eKrj2mw7EwztauE4_iZgqzHRAIZiAR4exuRDOdloui0= I did not do as exhaustive of a check for z/OS 2.3 and z/OS 2.1 Selecting z/OS2.1 from the initial page returns http 404 message Selecting z/OS 2.3 seems to work. How many times is IBM going to repeat the same mistake? C'mon IBM. Lets get it together! Think! "If you don't have time to do it right, when will you have the time to do it over?" - John Wooden ::DISCLAIMER:: -- The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. E-mail transmission is not guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or may contain viruses in transmission. The e mail and its contents (with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates. Views or opinions, if any, presented in this email are solely those of the author and may not necessarily reflect the views or opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of authorized representative of HCL is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any email and/or attachments, please check them for viruses and other defects. -- -- 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
z/OS Internet Library Broken (again)
This seems to be an exact duplicate of the problem repaired a couple of weeks ago! https://www-304.ibm.com/servers/resourcelink/svc00100.nsf/pages/zosInternetLibrary?OpenDocument Select "Download Books in PDF Format" for z/OS 2.2. Displays URL below: https://www-304.ibm.com/servers/resourcelink/svc00100.nsf/pages/zosv2r2-pdf-download?OpenDocument Select anything from the selections displayed will show: a) HTTP 404 error message b) Redisplays the same page: https://www-304.ibm.com/servers/resourcelink/svc00100.nsf/pages/zosv2r2-pdf-download?OpenDocument#DGW I did not do as exhaustive of a check for z/OS 2.3 and z/OS 2.1 Selecting z/OS2.1 from the initial page returns http 404 message Selecting z/OS 2.3 seems to work. How many times is IBM going to repeat the same mistake? C'mon IBM. Lets get it together! Think! "If you don't have time to do it right, when will you have the time to do it over?" - John Wooden ::DISCLAIMER:: -- The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. E-mail transmission is not guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or may contain viruses in transmission. The e mail and its contents (with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates. Views or opinions, if any, presented in this email are solely those of the author and may not necessarily reflect the views or opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of authorized representative of HCL is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any email and/or attachments, please check them for viruses and other defects. -- -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Two new RFE's to consider supporting
Mouse selection exists. Configure your mouse to send CUR SEL, which emulates a light-pen press. The panel needs to make the field light-pen/CUR SEL compatible. We did this in the early 80s, writing an in-house emulator, before emulators were available. OREXXMan JCL is the buggy whip of 21st century computing. Stabilize it. Put Pipelines in the z/OS base. Would you rather process data one character at a time (Unix/C style), or one record at a time? IBM has been looking for an HLL for program products; REXX is that language. On Fri, Jun 22, 2018 at 5:41 PM, Frank Swarbrick < frank.swarbr...@outlook.com> wrote: > I've been utilizing this new "point and shoot" feature in SDSF for about a > week now. I like it, but its not perfect, for reasons others have > mentioned. > > In this particular case it seems to me what would be ideal is if the > feature did not require the cursor to be placed within the JOBNAME column. > Rather, it seems to me that: > - If the cursor is anywhere in a particular row, > - and the NP column for that row is "empty", > - then "pressing enter" would have the same action as if the NP column had > '?' entered in to it. > > Can't think of anything that would break, but who knows. I believe it > would eliminate any need to turn on the ISPF "Tab to point-and-shoot > fields" option. Basically, if not using a mouse, you could simply > "newline" to the NP column on the desired line (without having to worry > about "tabable" column headers) and press enter. > > I have no idea if this would address the actual reason the RFE was opened. > > Frank > > From: IBM Mainframe Discussion List on behalf > of Jesse 1 Robinson > Sent: Friday, June 22, 2018 11:08 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: Two new RFE's to consider supporting > > I voted for the PAS RFE as a user, not considering what I know--or don't > know--about the underlying technology. A particular ISV product some time > ago changed a screen to create exactly what Lionel is complaining about. A > column title on a PDS member list was suddenly tabbable, 'capturing' the > cursor on its way to the first member entry. I complained and got the > answer that some customers wanted this behavior so they could (re)sort the > list based on that column. My objection was that 99% of the time a(ny) user > wants to select a member entry, not sort the list. ISV gave me some kind of > fix. > > I recently started a thread here on the new default behavior of SDSF in > z/OS 2.3. PAS, if it's useful at all, should be controllable by the user. I > question the value of PAS if only because it interrupts the 'finger flow' > of an application. You have to keep a wary eye peeled on the screen all the > time to know where you're at. That might be fine for a first-time or > occasional user, but it compromises productivity for the experienced user. > Which most of us are. > > . > . > J.O.Skip Robinson > Southern California Edison Company > Electric Dragon Team Paddler > SHARE MVS Program Co-Manager > 323-715-0595 Mobile > 626-543-6132 Office ⇐=== NEW > robin...@sce.com > > > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of Seymour J Metz > Sent: Friday, June 22, 2018 9:10 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: (External):Re: Two new RFE's to consider supporting > > Given that ISPF already supports point and shoot and that IBM has no > control over 3rd party 3270 simulators and TN3270 clients, you'll need a > strong business case. The only solution I know of within the existing 3270 > protocol is a zero-width field. > > > -- > Shmuel (Seymour J.) Metz > http://mason.gmu.edu/~smetz3 > > > From: IBM Mainframe Discussion List on behalf > of Dyck, Lionel B. (RavenTek) > Sent: Thursday, June 21, 2018 3:08 PM > To: IBM-MAIN@listserv.ua.edu > Subject: Two new RFE's to consider supporting > > Please consider supporting these RFE's that I just submitted: > > ISPF Point and Shoot Protected Fields > > https://secure-web.cisco.com/1eSaRV5UJ3V1J9lFuWduNMNEXKwsjE > r0nnYLCdtANa5wcGIytP_p89VwxV76dUYujSzZGvsssoum5dfWf > 031TCGUtebzzpwdlkSgZJnaqbpOkVLJas5jtys5H1gU8JRFNOD2vMXd3U8ab > HHyUJFosa64XBfNSgGc5MvffGa_1ZfKyWEpmQAA3kv0sNVrx-whBQbW89l_3pWtg15_ > 7MBLqVtWvke6na3t-Tk6vOswu28yUE4IUe2koNEA8oyONAN > QER39qJALUqHMLIzs58oysAkIsJcmb1ccODLmdnzKY2gXS9eVRancgDDeqgV > BCArpyN5npMA64aVH_B47XdVoSdSV7DtHk5UyIdPlCkMjOI6 > 9Dv8kpj0u74ruw1jKi-4U9/https%3A%2F%2Fwww.ibm.com%2Fdeveloperworks%2Frfe% > 2Fexecute%3Fuse_case%3DviewRfe%26CR_ID%3D121576 > > And > > Improve ISPF 3.17 by allowing CD on the command line > > https://secure-web.cisco.com/1xtqTd4IbEpSIeq1S0zeI1IMPcAcWs > FuqmZWHpViLukOiAtsG1u7lb2OGbEuJwHffWY-3ICATc1LstgliNG5YJwm_ehvRmlvFVRjp1_ > ELkgd2iFLph4vBOuNp9wHVtL3RKyceFMRN7yre-njqs_Cp5ejI7zvJhlJ9KQNaY5Uf- > 3lQTeIfIugyV8IIgCZR8TlawkDi4qZiF7y_zgKvvN0SxF_ >
Re: IOEZ00793E Error=111 reason=EF016015 received while attempting to convert directory / to version 5 format
zFS Thu Jan 26 14:45:58 EST 2017 Description: SAF CKACC returned error. Action: The user did not have the correct permission on the object for the operation requested. Change the permissions on the object or have a user that is authorized execute the operation. *** -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Tom Conley Sent: Wednesday, June 27, 2018 11:12 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: IOEZ00793E Error=111 reason=EF016015 received while attempting to convert directory / to version 5 format On 6/27/2018 12:01 PM, Jantje. wrote: > Dear Listers, > > Can anyone please point me to some documentation where the error code and/or > reason code for the above error message is? > > I am converting directories in a zFS to version 1.5 and for some directories > this is not working. I get the above error message, but the manual says only: > > IOEZ00793E Error=ReturnCode reason=ReasonCode received while attempting to > convert directory name to version 5 format TSO BPXMTEXT EF016015. If that doesn't work, run it directly from SYS1.SBPXEXEC or whatever name you call that dataset. Regards, Tom Conley -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN *** Disclaimer *** This communication (including all attachments) is solely for the use of the person to whom it is addressed and is a confidential AAA communication. If you are not the intended recipient, any use, distribution, printing, or copying is prohibited. If you received this email in error, please immediately delete it and notify the sender. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: IOEZ00793E Error=111 reason=EF016015 received while attempting to convert directory / to version 5 format
On 6/27/2018 12:01 PM, Jantje. wrote: Dear Listers, Can anyone please point me to some documentation where the error code and/or reason code for the above error message is? I am converting directories in a zFS to version 1.5 and for some directories this is not working. I get the above error message, but the manual says only: IOEZ00793E Error=ReturnCode reason=ReasonCode received while attempting to convert directory name to version 5 format TSO BPXMTEXT EF016015. If that doesn't work, run it directly from SYS1.SBPXEXEC or whatever name you call that dataset. Regards, Tom Conley -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
IOEZ00793E Error=111 reason=EF016015 received while attempting to convert directory / to version 5 format
Dear Listers, Can anyone please point me to some documentation where the error code and/or reason code for the above error message is? I am converting directories in a zFS to version 1.5 and for some directories this is not working. I get the above error message, but the manual says only: IOEZ00793E Error=ReturnCode reason=ReasonCode received while attempting to convert directory name to version 5 format Explanation The directory failed to convert to version 5 format. ReturnCode The error code. ReasonCode The reason code. name The directory name. System action The program continues. Severity svc_c_sev_error Administrator Response Correct the error and try again. OK, great. :-( what is the error??? Thanks and very best regards, Jantje. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: ICSF and millions of RSA keys
If you have the ability, I'd open a Q PMR with IBM crypto support. I suspect it can handle it, but doesn't hurt to ask. For crypto, years ago we were running into catalog contention with ICSF accessing the KDS datasets. We created new dedicated usercat/alias and have been fine ever since. _ Dave Jousma Manager Mainframe Engineering, Assistant Vice President david.jou...@53.com 1830 East Paris, Grand Rapids, MI 49546 MD RSCB2H p 616.653.8429 f 616.653.2717 -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of R.S. Sent: Wednesday, June 27, 2018 10:47 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: ICSF and millions of RSA keys **CAUTION EXTERNAL EMAIL** **DO NOT open attachments or click on links from unknown senders or unexpected emails** Usually ICSF use the key kept in its repositories - CKDS for symmetric keys and PKDS for assymetric cryptography. There is a plan to use several millions of public keys (private key reside out of the mainframe). Some questions and doubts: 1. Is it good idea to have millions of keys in PKDS? Would it be a problem for ICSF? VSAM limits seem to be not a problem, but maybe ICSF have some bottlenecks or limitations. 2. Can I keep the keys out of PKDS, for example in DB2 table? Note, we talk about public key, so there is no big reason to keep it secret. For example: tell ICSF to check msg using given key value, instead of given key label. I remeber such solution is feasible for symmetric keys (the key was encrypted using Master Key). 3. What about performance? While DB2 table can be buffered, what about PKDS? Does it require I/O for every key use? -- Radoslaw Skorupka Lodz, Poland == -- Treść tej wiadomości może zawierać informacje prawnie chronione Banku przeznaczone wyłącznie do użytku służbowego adresata. Odbiorcą może być jedynie jej adresat z wyłączeniem dostępu osób trzecich. Jeżeli nie jesteś adresatem niniejszej wiadomości lub pracownikiem upoważnionym do jej przekazania adresatowi, informujemy, że jej rozpowszechnianie, kopiowanie, rozprowadzanie lub inne działanie o podobnym charakterze jest prawnie zabronione i może być karalne. Jeżeli otrzymałeś tę wiadomość omyłkowo, prosimy niezwłocznie zawiadomić nadawcę wysyłając odpowiedź oraz trwale usunąć tę wiadomość włączając w to wszelkie jej kopie wydrukowane lub zapisane na dysku. This e-mail may contain legally privileged information of the Bank and is intended solely for business use of the addressee. This e-mail may only be received by the addressee and may not be disclosed to any third parties. If you are not the intended addressee of this e-mail or the employee authorized to forward it to the addressee, be advised that any dissemination, copying, distribution or any other similar activity is legally prohibited and may be punishable. If you received this e-mail by mistake please advise the sender immediately by using the reply facility in your e-mail software and delete permanently this e-mail including any copies of it either printed or saved to hard drive. mBank S.A. z siedzibą w Warszawie, ul. Senatorska 18, 00-950 Warszawa, www.mBank.pl, e-mail: kont...@mbank.plsąd Rejonowy dla m. st. Warszawy XII Wydział Gospodarczy Krajowego Rejestru Sądowego, nr rejestru przedsiębiorców KRS 025237, NIP: 526-021-50-88. Według stanu na dzień 01.01.2018 r. kapitał zakładowy mBanku S.A. (w całości wpłacony) wynosi 169.248.488 złotych. -- 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
ICSF and millions of RSA keys
Usually ICSF use the key kept in its repositories - CKDS for symmetric keys and PKDS for assymetric cryptography. There is a plan to use several millions of public keys (private key reside out of the mainframe). Some questions and doubts: 1. Is it good idea to have millions of keys in PKDS? Would it be a problem for ICSF? VSAM limits seem to be not a problem, but maybe ICSF have some bottlenecks or limitations. 2. Can I keep the keys out of PKDS, for example in DB2 table? Note, we talk about public key, so there is no big reason to keep it secret. For example: tell ICSF to check msg using given key value, instead of given key label. I remeber such solution is feasible for symmetric keys (the key was encrypted using Master Key). 3. What about performance? While DB2 table can be buffered, what about PKDS? Does it require I/O for every key use? -- Radoslaw Skorupka Lodz, Poland == -- Treść tej wiadomości może zawierać informacje prawnie chronione Banku przeznaczone wyłącznie do użytku służbowego adresata. Odbiorcą może być jedynie jej adresat z wyłączeniem dostępu osób trzecich. Jeżeli nie jesteś adresatem niniejszej wiadomości lub pracownikiem upoważnionym do jej przekazania adresatowi, informujemy, że jej rozpowszechnianie, kopiowanie, rozprowadzanie lub inne działanie o podobnym charakterze jest prawnie zabronione i może być karalne. Jeżeli otrzymałeś tę wiadomość omyłkowo, prosimy niezwłocznie zawiadomić nadawcę wysyłając odpowiedź oraz trwale usunąć tę wiadomość włączając w to wszelkie jej kopie wydrukowane lub zapisane na dysku. This e-mail may contain legally privileged information of the Bank and is intended solely for business use of the addressee. This e-mail may only be received by the addressee and may not be disclosed to any third parties. If you are not the intended addressee of this e-mail or the employee authorized to forward it to the addressee, be advised that any dissemination, copying, distribution or any other similar activity is legally prohibited and may be punishable. If you received this e-mail by mistake please advise the sender immediately by using the reply facility in your e-mail software and delete permanently this e-mail including any copies of it either printed or saved to hard drive. mBank S.A. z siedzibą w Warszawie, ul. Senatorska 18, 00-950 Warszawa, www.mBank.pl, e-mail: kont...@mbank.plsąd Rejonowy dla m. st. Warszawy XII Wydział Gospodarczy Krajowego Rejestru Sądowego, nr rejestru przedsiębiorców KRS 025237, NIP: 526-021-50-88. Według stanu na dzień 01.01.2018 r. kapitał zakładowy mBanku S.A. (w całości wpłacony) wynosi 169.248.488 złotych. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Eternal WAIT on un-waited ECB
You would not use pause/release for its individual-call performance characteristics, but for other things. For example, pause/release is not subject to the cross-memory post case where the interface's being an "ASCB address" leaves things subject to question if the target terminates and then a new space gets that same ASCB address (hence, see the IEAMSXMP macro, where that service wrapper basically schedules an SRB to do a non-XM post, after having validated the target, since that service utilizes an stoken/ttoken rather than ASCB address for identification). Also, pause/release does not use the local lock, so it could help avoid local lock contention which can significantly degrade performance. But it is surely true that (with enough concurrent use) pause/release could run into its own lock contention problems on the lock(s) that it does use. It is certainly true that wait/post will be around for the life of the operating system, regardless of what other options are provided. Peter Relson z/OS Core Technology Design -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
