Re: IBM ServiceLink greenscreen to be discontinued March 31, 2007
In addition to the issues already mentioned, I know of 2 other problems with the web interface. The first one is that there is no way to send (e-mail) anything back to yourself. If you want to research 100 PTFs for a product, it is a lot easier to send the list back to a place where you can manipulate the list. Lest anyone think that I haven't researched this issue, I know that I could cut-and-paste or view source or a number of other relatively manual processes. However, all of those are much more time-consuming than tapping the PF key to print and send the output back to my VM system. I will also miss this function for being able to print and archive old PMR text so that I can find old problems after IBMLink deletes them (28 days). The ability to use a text mode browser might improve this but I am not aware of a text mode browser that handles https. The other significant productivity hit is the lack of shortcuts to get between functions. The point-and-click option requires a lot more waiting for transitions between tasks in IBMLink. I first heard about the probability of the 3270 interface being discontinued in October 2003 from someone in the IBMLink development team. I mentioned these issues then and, while the web interface has improved, these functions still do not exist. I guess customer requirements aren't as important as they used to be. (sigh!) Rick Barlow Systems Engineering Consultant Nationwide Services Co., Enterprise Business Intelligence Services Mainframe, z/VM and zSeries Linux Support One Nationwide Plaza 3-20-13 Columbus OH 43215-2220 U.S.A Voice: (614) 249-5213Fax: (614) 677-0821 mailto:[EMAIL PROTECTED]
Re: IBM ServiceLink greenscreen to be discontinued March 31, 2007
Exactly! -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Rick Barlow Sent: Thursday, January 04, 2007 8:15 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: IBM ServiceLink greenscreen to be discontinued March 31, 2007 In addition to the issues already mentioned, I know of 2 other problems with the web interface. The first one is that there is no way to send (e-mail) anything back to yourself. If you want to research 100 PTFs for a product, it is a lot easier to send the list back to a place where you can manipulate the list. Lest anyone think that I haven't researched this issue, I know that I could cut-and-paste or view source or a number of other relatively manual processes. However, all of those are much more time-consuming than tapping the PF key to print and send the output back to my VM system. I will also miss this function for being able to print and archive old PMR text so that I can find old problems after IBMLink deletes them (28 days). The ability to use a text mode browser might improve this but I am not aware of a text mode browser that handles https. The other significant productivity hit is the lack of shortcuts to get between functions. The point-and-click option requires a lot more waiting for transitions between tasks in IBMLink. I first heard about the probability of the 3270 interface being discontinued in October 2003 from someone in the IBMLink development team. I mentioned these issues then and, while the web interface has improved, these functions still do not exist. I guess customer requirements aren't as important as they used to be. (sigh!) Rick Barlow Systems Engineering Consultant Nationwide Services Co., Enterprise Business Intelligence Services Mainframe, z/VM and zSeries Linux Support One Nationwide Plaza 3-20-13 Columbus OH 43215-2220 U.S.A Voice: (614) 249-5213Fax: (614) 677-0821 mailto:[EMAIL PROTECTED] If you are not an intended recipient of this e-mail, please notify the sender, delete it and do not read, act upon, print, disclose, copy, retain or redistribute it. Click here for important additional terms relating to this e-mail. http://www.ml.com/email_terms/
Re: IBM ServiceLink greenscreen to be discontinued March 31, 2007
On Thursday, 01/04/2007 at 08:14 EST, Rick Barlow [EMAIL PROTECTED] wrote: I will also miss this function for being able to print and archive old PMR text so that I can find old problems after IBMLink deletes them (28 days). FYI, closed PMRs are deleted from RETAIN after 28 days. IBMLink gets its information from RETAIN. I first heard about the probability of the 3270 interface being discontinued in October 2003 from someone in the IBMLink development team. I mentioned these issues then and, while the web interface has improved, these functions still do not exist. I guess customer requirements aren't as important as they used to be. (sigh!) From Chuckie: As he-who-has-access-to-the-power-switch tried to say in an earlier post, EVERYONE that has an issue with IBMLink must make their issues known. Every month that goes by without improvement should be met by the same avalanche of Feedbacks and calls to the IBMLink Support desk. Lack of contact by the IBMLink team should be met with calls to the helpdesk. Press your case. Use the word 'escalate' as necessary. Squeaky wheels get the grease. BE the wheel. Better, get with your VM, MVS, VSE, and TPF friends and be an 18-squeaky-wheeler (Wolf Creek Pass, way across the Great Divide, truckin' on down the other side). My keeper has used the alien phrase user group requirements. That might be an interesting path to take, simply to give notice to PHBs that IBMLink is just as important to your business as the products are themselves. Could you meet your SLAs by calling the Support Center all the time? That is Chuckie's opinion, of course, not Policy or an Official Recommendation. Alan Altmark z/VM Development IBM Endicott
Re: FTP to tape
Connect Direct VM can copy to/from tape. Thanks, Bob
Re: IBM ServiceLink greenscreen to be discontinued March 31, 2007
Please know that you are 'preaching to the choir' so to speak. The last thing VM'ers want to do is get rid of another VM or mainframe application. I second Alan. Please let the ServicLink folks know about these problems. (After all the VM community has always been a very vocal community!) Colleen M Brown IBM z/VM and Related Products Development and Service Stracka, James (GTI) [EMAIL PROTECTED] Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU 01/04/2007 08:45 AM Please respond to The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU To IBMVM@LISTSERV.UARK.EDU cc Subject Re: IBM ServiceLink greenscreen to be discontinued March 31, 2007 Exactly! -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Rick Barlow Sent: Thursday, January 04, 2007 8:15 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: IBM ServiceLink greenscreen to be discontinued March 31, 2007 In addition to the issues already mentioned, I know of 2 other problems with the web interface. The first one is that there is no way to send (e-mail) anything back to yourself. If you want to research 100 PTFs for a product, it is a lot easier to send the list back to a place where you can manipulate the list. Lest anyone think that I haven't researched this issue, I know that I could cut-and-paste or view source or a number of other relatively manual processes. However, all of those are much more time-consuming than tapping the PF key to print and send the output back to my VM system. I will also miss this function for being able to print and archive old PMR text so that I can find old problems after IBMLink deletes them (28 days). The ability to use a text mode browser might improve this but I am not aware of a text mode browser that handles https. The other significant productivity hit is the lack of shortcuts to get between functions. The point-and-click option requires a lot more waiting for transitions between tasks in IBMLink. I first heard about the probability of the 3270 interface being discontinued in October 2003 from someone in the IBMLink development team. I mentioned these issues then and, while the web interface has improved, these functions still do not exist. I guess customer requirements aren't as important as they used to be. (sigh!) Rick Barlow Systems Engineering Consultant Nationwide Services Co., Enterprise Business Intelligence Services Mainframe, z/VM and zSeries Linux Support One Nationwide Plaza 3-20-13 Columbus OH 43215-2220 U.S.A Voice: (614) 249-5213Fax: (614) 677-0821 mailto:[EMAIL PROTECTED] If you are not an intended recipient of this e-mail, please notify the sender, delete it and do not read, act upon, print, disclose, copy, retain or redistribute it. Click here for important additional terms relating to this e-mail. http://www.ml.com/email_terms/
Logoff force pending
Hello list, The past week my userid was in a logoff force pending state. Yesterday this status has changed. So I can use my userid again. But I can't figure out why my user was waiting to logoff like this. The system is our z/Linux production VM that is running z/VM 4.4.0 on a z990 machine. It all started when I tried to vary online two DASD devices. A query revealed that DASD 21EC and 21ED were offline. We have other DASD in the same ranges and on the same paths that were online. So I issued VARY ON 21EC 21ED. But I did not get a ready in return. But I could vary on these devices in a different VM. After some ten minutes I forced the user. Yes, I know, it was a risk. The logoff force pending was expected. I guess the IO associated with the VARY operation was still pending and therefore the user could not be logged off by CP. Nothing strange so far, other than th e question why the VARY did not appear to be processed on this VM. I looked for a way to solve this issue. But no advices I'd found were successfull. The devices I tried to work with were still offline so I could not VARY them offline. I could not query or tinker with CP Storage for my user (not even if I wanted to) because the VMDBK block was not available anymore. (A LOCATE returned with User not logged on) And beeing a 24x7 production system an IPL is out of the question. Yesterday an OSA device was removed from the configuration. At the same second my user is finaly logged off and ready for use again. (And yes, th e DASD is still offline so the command has not been processed at all.) Now, what I can't understand is why my user suddenly freed itself when a totaly unrelated device is beeing changed. Or why it turns out to be pending on an other device in the first place. As far as I know nothing has been changed on the DASD devices. And the OSA was not in use, at leas t not by my user. So a pending console IO is not the case here. Can anyone think of a reason why this has happened? Thanks, Berry.
SHARE: Chairbear call to arms!
Hi, Did you know the second amendment of the US Constitution gives you the right to arm bears? And in that same spirit, we call the bears, and penguins, to arms [and wings]! It's time to round up the chairs for sessions at the next SHARE in Tampa, this coming February! So come one, come all! Gain the prestige, honor and glory that are yours as an elite session chair for any VM and Linux program session. You'll get exclusive red carpet treatment, your own entourage, lots of paparazzi, an exclusive write up in the next issue of LinuxWorld with centerfold spread, and a million dollars cash! OK, not really. You won't get that. You won't get free admission to SHARE. You won't get free admission to a session. In other words, you have to be registered for the day you can chair a session. You get three slaps with a wet noodle if you try to chair your own session. BUT: the job's not hard...just a few minutes to introduce the speaker, make sure the room is all set, help with evaluation forms (passing them out, collecting them and returning them, not filling them in!), etc. And you'll have the gratitude of this session-chair herder, as well as the speakers! The audience will delight in your wit and acumen...the debonair flair that you exude as you introduce the session...truly not to be missed. So don't pass up on your opportunity to be a piece of SHARE history! (A small piece, but a piece nonetheless!) Simply e-mail me a list, in preferential order, of the session # and titles you would like to help with! Non ribbon-wearers have priority, otherwise it's first come, first serve. Contest void where prohibited. Sales tax not applicable in MH, AH, BV, CT, PA, and Ghana. Some restrictions apply. Limit 5 per customer. Side effects may include dizziness, nausea, loss of breath, or even death (in only 96% of the cases). Your mileage may vary. Check with dealer for details. --- Mark Boltz, CISSP Sr. Solutions Architect [EMAIL PROTECTED] http://www.stonesoft.com Toll Free: 1.866.869.4075 Cell: 1.571.218.2481 Fax: 1.703.288.4811 8133 Leesburg Pike, Suite 610 Vienna, VA 22182-2730 USA Subscribe to a Webletter on Trends in Network Security at http://www.stonesoft.com/network_security/
Re: IBM ServiceLink greenscreen to be discontinued March 31, 2007
On Thu, 4 Jan 2007 08:14:36 -0500 Rick Barlow said:
{snip} The
ability to use a text mode browser might improve this but I am not aware of
a text mode browser that handles https.
CHARLOTTE is a CMS web browser that handles HTTPS.
It is available on my VM FTP site. For best results do the FTP in a
CMS machine so you will have no reblocking issues.
ftp zvm.sru.edu
user sruftp
pass guest
ebcdic
mode b
get charlott.vmarc
quit
/Fran Hensler at Slippery Rock University of Pennsylvania USA for 43 years
[EMAIL PROTECTED] +1.724.738.2153
Yes, Virginia, there is a Slippery Rock
SHARE: Chairbear session list
Hi, OK, someone pointed out that you might need the session list, or find it useful in some way for determining which ones you want to chair. :-P And you know you want to chair some sessions! So here's a PDF of the list of sessions as I last had it provided to me just prior to the holidays. You can double check the SHARE Web site's session list if you like. (See attached file: Session List.pdf) --- Mark Boltz, CISSP Sr. Solutions Architect [EMAIL PROTECTED] http://www.stonesoft.com Toll Free: 1.866.869.4075 Cell: 1.571.218.2481 Fax: 1.703.288.4811 8133 Leesburg Pike, Suite 610 Vienna, VA 22182-2730 USA Subscribe to a Webletter on Trends in Network Security at http://www.stonesoft.com/network_security/
Re: IBM ServiceLink greenscreen to be discontinued March 31, 2007
Well, I confess to not knowing every IBMLink greenscreen feature that will be lost or become less functional when using the browser version. And with business being what it is today, I simply don't have the time to perform an in-depth feature and usability analysis. One would think that IBMLink designers would have done that **before** announcing a withdrawl (sic) of the greenscreen access. Certainly they must have analyzed greenscreen usage over the past six months or so, right? So... I posted the notice here, where people with passion and experience are likely (pretty much guaranteed) to respond. I volunteer to package up the posts with specific, actionable comments into a single Feedback which I will submit here, and to IBMLink on or before Monday, January 15 . That permits IBMVM listserve members more time to comment on this thread, and allows IBMLink half the 31 day time period between the notice of, and the actual withdrawal deadline to take a graceful step back, consider the implications of the greenscreen withdrawal on its customer's productivity, and extend the deadline until the web application inadequacies have been acceptably addressed. Thank you all for your consideration and comments. Keep them coming! Mike Walter Hewitt Associates Any opinions expressed herein are mine alone and do not necessarily represent the opinions or policies of Hewitt Associates. Alan Altmark [EMAIL PROTECTED] Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU 01/03/2007 11:11 PM Please respond to The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU To IBMVM@LISTSERV.UARK.EDU cc Subject Re: IBM ServiceLink greenscreen to be discontinued March 31, 2007 On Wednesday, 01/03/2007 at 02:49 EST, Stracka, James (GTI) [EMAIL PROTECTED] wrote: Yes, and when doing a search for fixes (5735FAL00 r520 1000) I cannot get the output to go to a file as with 3270. Anyone who finds the web interface ... deficient ... in some area or other should, of course, register their Feedback with the ServiceLink folks. Alan Altmark z/VM Development IBM Endicott The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message, including any attachments. Any dissemination, distribution or other use of the contents of this message by anyone other than the intended recipient is strictly prohibited.
Re: IBM ServiceLink greenscreen to be discontinued March 31, 2007
But didn't Alan (or was it Chuckie?) indicate multiple squeaks would be better than one in this case? Perhaps a single comprehensive laundry list from one customer is not the best way to be heard ... JR (Steven) Imler CA Senior Software Engineer Tel: +1 703 708 3479 Fax: +1 703 708 3267 [EMAIL PROTECTED] -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Mike Walter Sent: Thursday, January 04, 2007 09:57 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: IBM ServiceLink greenscreen to be discontinued March 31, 2007 Well, I confess to not knowing every IBMLink greenscreen feature that will be lost or become less functional when using the browser version. And with business being what it is today, I simply don't have the time to perform an in-depth feature and usability analysis. One would think that IBMLink designers would have done that **before** announcing a withdrawl (sic) of the greenscreen access. Certainly they must have analyzed greenscreen usage over the past six months or so, right? So... I posted the notice here, where people with passion and experience are likely (pretty much guaranteed) to respond. I volunteer to package up the posts with specific, actionable comments into a single Feedback which I will submit here, and to IBMLink on or before Monday, January 15 . That permits IBMVM listserve members more time to comment on this thread, and allows IBMLink half the 31 day time period between the notice of, and the actual withdrawal deadline to take a graceful step back, consider the implications of the greenscreen withdrawal on its customer's productivity, and extend the deadline until the web application inadequacies have been acceptably addressed. Thank you all for your consideration and comments. Keep them coming! Mike Walter Hewitt Associates Any opinions expressed herein are mine alone and do not necessarily represent the opinions or policies of Hewitt Associates. Alan Altmark [EMAIL PROTECTED] Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU 01/03/2007 11:11 PM Please respond to The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU To IBMVM@LISTSERV.UARK.EDU cc Subject Re: IBM ServiceLink greenscreen to be discontinued March 31, 2007 On Wednesday, 01/03/2007 at 02:49 EST, Stracka, James (GTI) [EMAIL PROTECTED] wrote: Yes, and when doing a search for fixes (5735FAL00 r520 1000) I cannot get the output to go to a file as with 3270. Anyone who finds the web interface ... deficient ... in some area or other should, of course, register their Feedback with the ServiceLink folks. Alan Altmark z/VM Development IBM Endicott The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message, including any attachments. Any dissemination, distribution or other use of the contents of this message by anyone other than the intended recipient is strictly prohibited.
Re: IBM ServiceLink greenscreen to be discontinued March 31, 2007
On Thu, 4 Jan 2007 08:14:36 -0500 Rick Barlow said:
{snip}
The
ability to use a text mode browser might improve this but I am not
aware
of
a text mode browser that handles https.
Lynx does on Linux, and I believe that Charlotte does on CMS.
Ironically, both are usable (if somewhat painfully) with Sun and HP's
service WWW sites.
Hillgang
It's short notice but the holiday season made it difficult to co-ordinate people and places. In any event we have three excellent presentations scheduled for Thursday January 11 (yes just one week from today). For those with mime-enabled mailers there's a PDF attachment. For those who don't this document will be on the z/VM website just as soon as Pam Christina can arrange it. Please RSVP as soon as you can. Neale Ferguson
Re: Logoff force pending
Berry, Hung user situations have been dramatically reduced since the good old days of VM/SP, VM/HPO, and VM/XA. Back then, when the hung user was critical enough, I would explain to my management that I could zap the in-storage VMBLOK (wasn't that the old name before VMDBK?) and could guarantee with 100% certainty that the hung user would be cleared off the system -- but that about 50% of the time it would crash the system in the process. The possibility to crashing the system (heavily used by PROFS and CMS apps at the time) caused management to seriously consider how important that hung user actually was, and whether an overnight IPL might be a better choice. Over the years I've been accumulating tips from this list, SHARE, CAVMEN, etc. on what to do when a userid ends up in a FORCE/LOGOFF pending status (more suggestions are openly welcomed). Those tips are included in the session I present at SHARE (which is coming up Feb 11-16, 2007 in Tampa Bay, FL) called z/VM Installation - It's Installed, NOW what?. The tips are also included below. It might help to keep them on your System Programmers Toolbox minidisk or SFS directory for the next time this occurs. Mike Walter Hewitt Associates Any opinions expressed herein are mine alone and do not necessarily represent the opinions or policies of Hewitt Associates. READ: HUNGUSER HELPME (handy when issuing: HELP ME HUNGUSER) When a userid becomes hung in a LOGOFF/FORCE PENDING state, the following alternatives may be tried -- some require more than class G privs: - If you have the time, simply waiting 15 minutes for CP to perform housecleaning chores might free the userid, completing the LOGOFF or FORCE. - Use the public domain utility TRACK to determine if the userid is awaiting completion of an I/O to a particular unresponsive device. Use the commands: TRACK hungid DEV CLASS * IO PENDing TRACK hungid DEV CLASS * IO ACTIVE Nota bene: As of 23 Feb 2006 TRACK can be obtained from: http://vm.marist.edu/track/code.html - Before attempting anything that actually changes the hung userid, if you can (consider communication time-outs which may occur that could affect other users) before muddying the waters, get a current system dump for IBM to diagnose later. From a privclass A' user: CP QUERY DUMP (then ensure that it is going to disk) Then: CP WNG ALL This system may be non-responsive for a few minutes while diagnostic information is obtained. Then: CP SNAPDUMP - Sometimes a simple message frees up the hungid without further ado. From a privclass A, B, or C userid, issue: CP WNG hungid Hello - If the ID was awaiting I/O to a terminal, simply connecting from a working terminal may free the ID. From a free terminal, issue: CP LOGON hungid HERE - For users logged on via TELNET terminals, issue: NETSTAT TELNET Find the matching tn3270 connection, and issue: NETSTAT DROP conn_num - CPHX is reported to cancel pending CP commands: ATTACH, LOCATE, LOCATEVM, and VARY ONLINE|OFFLINE (see HELP for more detail). From a privclass A userid, issue: CP CPHX hungid - If TRACK (above) showed an active I/O which cannot be remedied (e.g. by making a tape drive Ready), the I/O may be able to be cancelled. From a privclass A userid, issue: CP HALT rdev Due to queued I/Os or recalcitrant devices, HALT may need to be issued repeatedly until the following message is received: Halt was not initiated to tape because the device as not active - If nothing freed the hung user, open a Problem Management Report with IBM, and provide the SNAPDUMP for analysis. .cm Last updated 20070104 * * * End of File * * * Berry van Sleeuwen [EMAIL PROTECTED] Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU 01/04/2007 02:36 AM Please respond to The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU To IBMVM@LISTSERV.UARK.EDU cc Subject Logoff force pending Hello list, The past week my userid was in a logoff force pending state. Yesterday this status has changed. So I can use my userid again. But I can't figure out why my user was waiting to logoff like this. The system is our z/Linux production VM that is running z/VM 4.4.0 on a z990 machine. It all started when I tried to vary online two DASD devices. A query revealed that DASD 21EC and 21ED were offline. We have other DASD in the same ranges and on the same paths that were online. So I issued VARY ON 21EC 21ED. But I did not get a ready in return. But I could vary on these devices in a different VM. After some ten minutes I forced the user. Yes, I know, it was a risk. The logoff force pending was expected. I guess the IO associated with the VARY operation was still pending and therefore the user could not be logged off
Re: IBM ServiceLink greenscreen to be discontinued March 31, 2007
Oh, by all means any and everyone with an issue **should** provide feedback. I merely presume that some list members will be too busy to open an IBMLink feedback for something they report on the list. Providing IBMLink with a single, comprehensive list might help to prevent those issues from being dropped through the cracks, Also the size of a single, comprehensive summary might force the issue to become clear enough to merit swift action! Mike Walter Hewitt Associates Any opinions expressed herein are mine alone and do not necessarily represent the opinions or policies of Hewitt Associates. Imler, Steven J [EMAIL PROTECTED] Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU 01/04/2007 09:04 AM Please respond to The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU To IBMVM@LISTSERV.UARK.EDU cc Subject Re: IBM ServiceLink greenscreen to be discontinued March 31, 2007 But didn't Alan (or was it Chuckie?) indicate multiple squeaks would be better than one in this case? Perhaps a single comprehensive laundry list from one customer is not the best way to be heard ... JR (Steven) Imler CA Senior Software Engineer Tel: +1 703 708 3479 Fax: +1 703 708 3267 [EMAIL PROTECTED] -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Mike Walter Sent: Thursday, January 04, 2007 09:57 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: IBM ServiceLink greenscreen to be discontinued March 31, 2007 Well, I confess to not knowing every IBMLink greenscreen feature that will be lost or become less functional when using the browser version. And with business being what it is today, I simply don't have the time to perform an in-depth feature and usability analysis. One would think that IBMLink designers would have done that **before** announcing a withdrawl (sic) of the greenscreen access. Certainly they must have analyzed greenscreen usage over the past six months or so, right? So... I posted the notice here, where people with passion and experience are likely (pretty much guaranteed) to respond. I volunteer to package up the posts with specific, actionable comments into a single Feedback which I will submit here, and to IBMLink on or before Monday, January 15 . That permits IBMVM listserve members more time to comment on this thread, and allows IBMLink half the 31 day time period between the notice of, and the actual withdrawal deadline to take a graceful step back, consider the implications of the greenscreen withdrawal on its customer's productivity, and extend the deadline until the web application inadequacies have been acceptably addressed. Thank you all for your consideration and comments. Keep them coming! Mike Walter Hewitt Associates Any opinions expressed herein are mine alone and do not necessarily represent the opinions or policies of Hewitt Associates. Alan Altmark [EMAIL PROTECTED] Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU 01/03/2007 11:11 PM Please respond to The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU To IBMVM@LISTSERV.UARK.EDU cc Subject Re: IBM ServiceLink greenscreen to be discontinued March 31, 2007 On Wednesday, 01/03/2007 at 02:49 EST, Stracka, James (GTI) [EMAIL PROTECTED] wrote: Yes, and when doing a search for fixes (5735FAL00 r520 1000) I cannot get the output to go to a file as with 3270. Anyone who finds the web interface ... deficient ... in some area or other should, of course, register their Feedback with the ServiceLink folks. Alan Altmark z/VM Development IBM Endicott The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message, including any attachments. Any dissemination, distribution or other use of the contents of this message by anyone other than the intended recipient is strictly prohibited. The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message, including any attachments. Any dissemination, distribution or other use of the contents of this message by anyone other than the intended recipient is strictly prohibited.
Re: IBM ServiceLink greenscreen to be discontinued March 31, 2007
On Jan 4, 2007, at 7:14 AM, Rick Barlow wrote: I am not aware of a text mode browser that handles https. Lynx, links, or w3m, at least, do. I won't swear that versions compiled with SSL support are what's present in your Linux or whatever distribution, but those three (which are the three browsers I use from time to time) all do have SSL support available. Not that I don't prefer greenscreen myself, but SSL on text browsers is pretty mature these days. Adam
Re: Logoff force pending
Mike: In the past, when the hung user is an operating system (VSE or MVS), I create a NEW directory entry with everything the same as the hung user (DASD, minidisks, etc.) EXCEPT the user name. That new user then can IPL fine. Later, when convenient to IPL, we do so, removing the temporary user directory entry before the IPL. The advantage of this method is there is no risk to crashing the system. David Wakser InfoCrossing From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Mike Walter Sent: Thursday, January 04, 2007 10:19 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Logoff force pending Berry, Hung user situations have been dramatically reduced since the good old days of VM/SP, VM/HPO, and VM/XA. Back then, when the hung user was critical enough, I would explain to my management that I could zap the in-storage VMBLOK (wasn't that the old name before VMDBK?) and could guarantee with 100% certainty that the hung user would be cleared off the system -- but that about 50% of the time it would crash the system in the process. The possibility to crashing the system (heavily used by PROFS and CMS apps at the time) caused management to seriously consider how important that hung user actually was, and whether an overnight IPL might be a better choice. Over the years I've been accumulating tips from this list, SHARE, CAVMEN, etc. on what to do when a userid ends up in a FORCE/LOGOFF pending status (more suggestions are openly welcomed). Those tips are included in the session I present at SHARE (which is coming up Feb 11-16, 2007 in Tampa Bay, FL) called z/VM Installation - It's Installed, NOW what?. The tips are also included below. It might help to keep them on your System Programmers Toolbox minidisk or SFS directory for the next time this occurs. Mike Walter Hewitt Associates Any opinions expressed herein are mine alone and do not necessarily represent the opinions or policies of Hewitt Associates. READ: HUNGUSER HELPME (handy when issuing: HELP ME HUNGUSER) When a userid becomes hung in a LOGOFF/FORCE PENDING state, the following alternatives may be tried -- some require more than class G privs: - If you have the time, simply waiting 15 minutes for CP to perform housecleaning chores might free the userid, completing the LOGOFF or FORCE. - Use the public domain utility TRACK to determine if the userid is awaiting completion of an I/O to a particular unresponsive device. Use the commands: TRACK hungid DEV CLASS * IO PENDing TRACK hungid DEV CLASS * IO ACTIVE Nota bene: As of 23 Feb 2006 TRACK can be obtained from: http://vm.marist.edu/track/code.html - Before attempting anything that actually changes the hung userid, if you can (consider communication time-outs which may occur that could affect other users) before muddying the waters, get a current system dump for IBM to diagnose later. From a privclass A' user: CP QUERY DUMP (then ensure that it is going to disk) Then: CP WNG ALL This system may be non-responsive for a few minutes while diagnostic information is obtained. Then: CP SNAPDUMP - Sometimes a simple message frees up the hungid without further ado. From a privclass A, B, or C userid, issue: CP WNG hungid Hello - If the ID was awaiting I/O to a terminal, simply connecting from a working terminal may free the ID. From a free terminal, issue: CP LOGON hungid HERE - For users logged on via TELNET terminals, issue: NETSTAT TELNET Find the matching tn3270 connection, and issue: NETSTAT DROP conn_num - CPHX is reported to cancel pending CP commands: ATTACH, LOCATE, LOCATEVM, and VARY ONLINE|OFFLINE (see HELP for more detail). From a privclass A userid, issue: CP CPHX hungid - If TRACK (above) showed an active I/O which cannot be remedied (e.g. by making a tape drive Ready), the I/O may be able to be cancelled. From a privclass A userid, issue: CP HALT rdev Due to queued I/Os or recalcitrant devices, HALT may need to be issued repeatedly until the following message is received: Halt was not initiated to tape because the device as not active - If nothing freed the hung user, open a Problem Management Report with IBM, and provide the SNAPDUMP for analysis.
Hillgang (resend w/o attachment)
It's short notice but the holiday season made it difficult to co-ordinate people and places. In any event we have three excellent presentations scheduled for Thursday January 11 (yes just one week from today). The agenda will be on the VM website soon but in the meantime it can be found at http://vm.marist.edu/~neale/hillgang.pdf. Please RSVP as soon as you can. Neale Ferguson
Hillgang (resend w/o attachment)
Apologies for my e-mail incompetence. This time the message has no attachment. Sheesh! It's short notice but the holiday season made it difficult to co-ordinate people and places. In any event we have three excellent presentations scheduled for Thursday January 11 (yes just one week from today). The agenda will be on the VM website soon but in the meantime it can be found at http://vm.marist.edu/~neale/hillgang.pdf. Please RSVP as soon as you can. Neale Ferguson
Re: Logoff force pending
David, If that works, great. But because you have the NEW directory entry with R/W access (presumably MW or MWV, since the hung user already has them R/W) to the same DASD/MDISKs as the hung user, you are taking a chance. If that hung user should reawaken (perhaps the device it was hung up on was IMLed, etc.) and start writing to the same DASD/MDISKs as the NEW userid, you have what I call one-way encryption (aka: hosed DASD). Hung users have been known to reawaken (Arise Lazarus!). If they complete an I/O all heck can break loose. With luck (what it seems you have been relying on), they just complete logoff without completing any pending I/O. Summary: your gun, your foot. But it's important to be aware that you loaded the gun and pointed it there. Your Aim May Vary. :-) But perhaps you have a different technique that prevents the hung user from writing to the same DASD/MDISKS as the NEW userid? Mike Walter Hewitt Associates Any opinions expressed herein are mine alone and do not necessarily represent the opinions or policies of Hewitt Associates. In reply to post: --- Mike: In the past, when the hung user is an operating system (VSE or MVS), I create a NEW directory entry with everything the same as the hung user (DASD, minidisks, etc.) EXCEPT the user name. That new user then can IPL fine. Later, when convenient to IPL, we do so, removing the temporary user directory entry before the IPL. The advantage of this method is there is no risk to crashing the system. David Wakser InfoCrossing The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message, including any attachments. Any dissemination, distribution or other use of the contents of this message by anyone other than the intended recipient is strictly prohibited.
Re: IBM ServiceLink greenscreen to be discontinued March 31, 2007
Heh. I had that album. Jon -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] Behalf Of Adam Thornton Sent: Thursday, January 04, 2007 10:53 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: IBM ServiceLink greenscreen to be discontinued March 31, 2007 On Jan 4, 2007, at 7:56 AM, Alan Altmark wrote: (Wolf Creek Pass, way across the Great Divide, truckin' on down the other side). It's not every man who knows the OTHER hit of a one-hit wonder. Adam
Re: IBM ServiceLink greenscreen to be discontinued March 31, 2007
Have you ever tried Nehi and Onion Soup mix? Steve Mitchell Sr Systems Software Specialist Blue Cross Blue Shield of Kansas (785) 291-8885 'There are no degrees of Honesty-you're either Honest or you're not! Jon Brock [EMAIL PROTECTED] Sent by: The IBM To z/VM OperatingIBMVM@LISTSERV.UARK.EDU System cc [EMAIL PROTECTED] ARK.EDUTopic Subject 01/04/2007 10:50 Re: IBM ServiceLink greenscreen to AMbe discontinued March 31, 2007 Please respond to The IBM z/VM Operating System [EMAIL PROTECTED] ARK.EDU Heh. I had that album. Jon -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] Behalf Of Adam Thornton Sent: Thursday, January 04, 2007 10:53 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: IBM ServiceLink greenscreen to be discontinued March 31, 2007 On Jan 4, 2007, at 7:56 AM, Alan Altmark wrote: (Wolf Creek Pass, way across the Great Divide, truckin' on down the other side). It's not every man who knows the OTHER hit of a one-hit wonder. Adam
Re: Logoff force pending
I seem to remember that the old V/Force included somehow disabling all devices attached to the hung user, so that even if it DID 'wake up', it no longer would/could do any new I/O. I think it might have also detached devices not 'in use', but I am less sure of this. Anyone remember more details? Shimon On 4 Jan 2007 at 10:40, Mike Walter wrote: David, If that works, great. But because you have the NEW directory entry with R/W access (presumably MW or MWV, since the hung user already has them R/W) to the same DASD/MDISKs as the hung user, you are taking a chance. If that hung user should reawaken (perhaps the device it was hung up on was IMLed, etc.) and start writing to the same DASD/MDISKs as the NEW userid, you have what I call one-way encryption (aka: hosed DASD). Hung users have been known to reawaken (Arise Lazarus!). If they complete an I/O all heck can break loose. With luck (what it seems you have been relying on), they just complete logoff without completing any pending I/O. Summary: your gun, your foot. But it's important to be aware that you loaded the gun and pointed it there. Your Aim May Vary. :-) But perhaps you have a different technique that prevents the hung user from writing to the same DASD/MDISKS as the NEW userid? Mike Walter Hewitt Associates Any opinions expressed herein are mine alone and do not necessarily represent the opinions or policies of Hewitt Associates. In reply to post: --- Mike: In the past, when the hung user is an operating system (VSE or MVS), I create a NEW directory entry with everything the same as the hung user (DASD, minidisks, etc.) EXCEPT the user name. That new user then can IPL fine. Later, when convenient to IPL, we do so, removing the temporary user directory entry before the IPL. The advantage of this method is there is no risk to crashing the system. David Wakser InfoCrossing The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message, including any attachments. Any dissemination, distribution or other use of the contents of this message by anyone other than the intended recipient is strictly prohibited. -- Shimon Lebowitzmailto:[EMAIL PROTECTED] VM System Programmer . Israel Police National HQ. http://www.poboxes.com/shimonpgp Jerusalem, Israel phone: +972 2 542-9877 fax: 542-9308
Re: Logoff force pending
Mike: Yes, I am aware of the pitfalls. However, here the hung user with operating systems has always been because Operations (AKA the brain trust) insists on using a FORCE command to log off guest operating systems. Thus, I would NOT expect the user to wake up - the operating system was already brought down. David Wakser -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Mike Walter Sent: Thursday, January 04, 2007 11:41 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Logoff force pending David, If that works, great. But because you have the NEW directory entry with R/W access (presumably MW or MWV, since the hung user already has them R/W) to the same DASD/MDISKs as the hung user, you are taking a chance. If that hung user should reawaken (perhaps the device it was hung up on was IMLed, etc.) and start writing to the same DASD/MDISKs as the NEW userid, you have what I call one-way encryption (aka: hosed DASD). Hung users have been known to reawaken (Arise Lazarus!). If they complete an I/O all heck can break loose. With luck (what it seems you have been relying on), they just complete logoff without completing any pending I/O. Summary: your gun, your foot. But it's important to be aware that you loaded the gun and pointed it there. Your Aim May Vary. :-) But perhaps you have a different technique that prevents the hung user from writing to the same DASD/MDISKS as the NEW userid? Mike Walter Hewitt Associates Any opinions expressed herein are mine alone and do not necessarily represent the opinions or policies of Hewitt Associates. In reply to post: --- Mike: In the past, when the hung user is an operating system (VSE or MVS), I create a NEW directory entry with everything the same as the hung user (DASD, minidisks, etc.) EXCEPT the user name. That new user then can IPL fine. Later, when convenient to IPL, we do so, removing the temporary user directory entry before the IPL. The advantage of this method is there is no risk to crashing the system. David Wakser InfoCrossing The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message, including any attachments. Any dissemination, distribution or other use of the contents of this message by anyone other than the intended recipient is strictly prohibited.
Re: IBM ServiceLink greenscreen to be discontinued March 31, 2007
Hey, he had a couple of others, but none that approached Convoy. Later, Ray -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Adam Thornton Sent: Thursday January 04 2007 07:53 To: IBMVM@LISTSERV.UARK.EDU Subject: Re: IBM ServiceLink greenscreen to be discontinued March 31, 2007 On Jan 4, 2007, at 7:56 AM, Alan Altmark wrote: (Wolf Creek Pass, way across the Great Divide, truckin' on down the other side). It's not every man who knows the OTHER hit of a one-hit wonder. Adam
Re: IBM ServiceLink greenscreen to be discontinued March 31, 2007
Have all of 'em, including the 'Convoy' soundtrack and the American Gramophone CD + the albums re-issued on CD. Charter member of his fan club from 1974, Ray -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Jon Brock Sent: Thursday January 04 2007 08:50 To: IBMVM@LISTSERV.UARK.EDU Subject: Re: IBM ServiceLink greenscreen to be discontinued March 31, 2007 Heh. I had that album. Jon -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] Behalf Of Adam Thornton Sent: Thursday, January 04, 2007 10:53 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: IBM ServiceLink greenscreen to be discontinued March 31, 2007 On Jan 4, 2007, at 7:56 AM, Alan Altmark wrote: (Wolf Creek Pass, way across the Great Divide, truckin' on down the other side). It's not every man who knows the OTHER hit of a one-hit wonder. Adam
Re: Logoff force pending
I distinctly remember back in 1986 bringing in V/Safe (intercepted common CP ABENDS, doing fix-ups where possible and letting the system continue without an IPL), V/Snap (before IBM had a CP SNAPDUMP command), and V/Force. When we needed it, V/Force went into recursive ABENDs, taking down the system (and almost my next salary increase!). John (don't remember his last name) from VMSG flew in several times for weekend S/A time to recreate (successful) and resolve (unsuccessful) the problem. Pity. But now we seldom see the error anyway (hence, my HUNGUSER HELPME since I won't remember all the techniques to diagnose it from memory). Mike Walter Hewitt Associates Any opinions expressed herein are mine alone and do not necessarily represent the opinions or policies of Hewitt Associates. Shimon Lebowitz [EMAIL PROTECTED] Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU 01/04/2007 10:53 AM Please respond to The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU To IBMVM@LISTSERV.UARK.EDU cc Subject Re: Logoff force pending I seem to remember that the old V/Force included somehow disabling all devices attached to the hung user, so that even if it DID 'wake up', it no longer would/could do any new I/O. I think it might have also detached devices not 'in use', but I am less sure of this. Anyone remember more details? Shimon On 4 Jan 2007 at 10:40, Mike Walter wrote: David, If that works, great. But because you have the NEW directory entry with R/W access (presumably MW or MWV, since the hung user already has them R/W) to the same DASD/MDISKs as the hung user, you are taking a chance. If that hung user should reawaken (perhaps the device it was hung up on was IMLed, etc.) and start writing to the same DASD/MDISKs as the NEW userid, you have what I call one-way encryption (aka: hosed DASD). Hung users have been known to reawaken (Arise Lazarus!). If they complete an I/O all heck can break loose. With luck (what it seems you have been relying on), they just complete logoff without completing any pending I/O. Summary: your gun, your foot. But it's important to be aware that you loaded the gun and pointed it there. Your Aim May Vary. :-) But perhaps you have a different technique that prevents the hung user from writing to the same DASD/MDISKS as the NEW userid? Mike Walter Hewitt Associates Any opinions expressed herein are mine alone and do not necessarily represent the opinions or policies of Hewitt Associates. In reply to post: --- Mike: In the past, when the hung user is an operating system (VSE or MVS), I create a NEW directory entry with everything the same as the hung user (DASD, minidisks, etc.) EXCEPT the user name. That new user then can IPL fine. Later, when convenient to IPL, we do so, removing the temporary user directory entry before the IPL. The advantage of this method is there is no risk to crashing the system. David Wakser InfoCrossing The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message, including any attachments. Any dissemination, distribution or other use of the contents of this message by anyone other than the intended recipient is strictly prohibited. -- Shimon Lebowitzmailto:[EMAIL PROTECTED] VM System Programmer . Israel Police National HQ. http://www.poboxes.com/shimonpgp Jerusalem, Israel phone: +972 2 542-9877 fax: 542-9308 The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message, including any attachments. Any dissemination, distribution or other use of the contents of this message by anyone other than the intended recipient is strictly prohibited.
Re: IBM ServiceLink greenscreen to be discontinued March 31, 2007
Nope. Can't say I have. Jon snip Have you ever tried Nehi and Onion Soup mix? /snip
Re: Logoff force pending
If the guest operating systems set themselves up to be notified for the shutdown signal, and you've defined a default shutdown interval (which you can check with cp q signal shutdown) then by default a FORCE command will signal the guest to shut down cleanly. You can check which guests are set up to be notified of a shutdown with the comomand cp q signals. Then you'd just have to hope that your Operations staff doesn't read the help file for FORCE and find out about the IMMED option... On 1/4/07, Wakser, David [EMAIL PROTECTED] wrote: Mike: Yes, I am aware of the pitfalls. However, here the hung user with operating systems has always been because Operations (AKA the brain trust) insists on using a FORCE command to log off guest operating systems. Thus, I would NOT expect the user to wake up - the operating system was already brought down. David Wakser -- Bruce Hayden IBM Global Technology Services, System z Linux Endicott, NY
Re: IBM ServiceLink greenscreen to be discontinued March 31, 2007
On Thursday, 01/04/2007 at 09:31 CST, Mike Walter [EMAIL PROTECTED] wrote: Oh, by all means any and everyone with an issue **should** provide feedback. I merely presume that some list members will be too busy to open an IBMLink feedback for something they report on the list. Providing IBMLink with a single, comprehensive list might help to prevent those issues from being dropped through the cracks, Also the size of a single, comprehensive summary might force the issue to become clear enough to merit swift action! Inquiries have been made to the IBMLink folks to find out how they would like to handle these concerns. If anyone depends on VPL, note that it is going away, too. We ship source anyway, so that shouldn't be too big of a problem for z/VM installations. Alan Altmark z/VM Development IBM Endicott
Re: IBM ServiceLink greenscreen to be discontinued March 31, 2007
On 1/4/07, Alan Altmark [EMAIL PROTECTED] wrote: If anyone depends on VPL, note that it is going away, too. We ship source anyway, so that shouldn't be too big of a problem for z/VM installations. Except if you want to view OCM listings... Rob
REXX compiling / EXECLOAD
Is there any performance benefit to compiling a REXX EXEC if it will be EXECLOAD'd for the lifetime of it's use? For example, I have a service machine which, upon startup, EXECLOADs some EXECs it needs over and over. It/they remain EXECLOADd until the service machine is shutdown. The EXEC is not particularly complex/large, but does compiling it actually make any difference? Does EXECLOAD tokenize/optimize the EXEC if it's not compiled? Thank you, Don Russell
Re: REXX compiling / EXECLOAD
EXECLOAD simply loads it, so it saves on I/O, no more no less, no tokenization like what happens on OS/2. Compliling will save CPU cycles, but the compiled exec is larger, hence EXECLOAD of a compiled exec is even more recommended. 2007/1/4, Don Russell [EMAIL PROTECTED]: Is there any performance benefit to compiling a REXX EXEC if it will be EXECLOAD'd for the lifetime of it's use? For example, I have a service machine which, upon startup, EXECLOADs some EXECs it needs over and over. It/they remain EXECLOADd until the service machine is shutdown. The EXEC is not particularly complex/large, but does compiling it actually make any difference? Does EXECLOAD tokenize/optimize the EXEC if it's not compiled? Thank you, Don Russell -- Kris Buelens, IBM Belgium, VM customer support
Re: REXX compiling / EXECLOAD
In my experience with compiling REXX my initial response would be no you would not see much (if any) benefit. There are two general reasons for compiling a REXX routine: to hide the contents from the casual observer or to improve performance when the logic does a lot of repetitive things (code loops). For any case though, TEST it! In some cases compiling will cause the performance to get worse; at best since you said the code is not large/complex, I would bet you won't see enough difference to make it worthwhile. And if you are EXECLOAD'ing it, compiling it usually increases the size of the executable so memory consumption will be impacted for the EXECLOAD. ___ James Vincent Systems Engineering Consultant Nationwide Services Co., Technology Solutions Mainframe, z/VM and z/Linux Support One Nationwide Plaza 3-20-13 Columbus OH 43215-2220 U.S.A Voice: (614) 249-5547Fax: (614) 677-7681 mailto:[EMAIL PROTECTED] The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU wrote on 01/04/2007 02:12:41 PM: IBMVM@LISTSERV.UARK.EDU Is there any performance benefit to compiling a REXX EXEC if it will be EXECLOAD'd for the lifetime of it's use? For example, I have a service machine which, upon startup, EXECLOADs some EXECs it needs over and over. It/they remain EXECLOADd until the service machine is shutdown. The EXEC is not particularly complex/large, but does compiling it actually make any difference? Does EXECLOAD tokenize/optimize the EXEC if it's not compiled? Thank you, Don Russell
Re: REXX compiling / EXECLOAD
Oh yes! EXECLOAD simply loads a file into storage. If you display memory, you'll see the source (compiled or non-compiled data directly from your file) ... and that's what is interpreted when you run the non-compiled EXEC or run directly from a compiled EXEC. If you see a performance benefit from compile, it will still be there if EXECLOADed. A non-compiled EXEC must still be interpreted, even if EXECLOADed. cheers, wayne Don Russell wrote, in part, on 1/4/2007 2:12 PM: Is there any performance benefit to compiling a REXX EXEC if it will be EXECLOAD'd for the lifetime of it's use? For example, I have a service machine which, upon startup, EXECLOADs some EXECs it needs over and over. It/they remain EXECLOADd until the service machine is shutdown. The EXEC is not particularly complex/large, but does compiling it actually make any difference? Does EXECLOAD tokenize/optimize the EXEC if it's not compiled? Thank you, Don Russell
Re: IBM ServiceLink greenscreen to be discontinued March 31, 2007
We ship source anyway, ... I respectfully beg to differ gov'nor! IBM ships *most* source for z/VM. Kudos! But page xi of the pub GC24-6099-00 z/VM Guide for Automated Installation and Service Version 5 Release 1.0 (the most current I can find as of 20070104) rightfully states: o PLX and Restricted Source no longer ship with z/VM. They are available upon request from IBM Resource Link?. Minor point to anyone but those needing access to the lesser-frequented dark corners of z/VM. But an important point of which to be aware when hunting unsuccessfully for the source to such a piece of the system. Mike Walter Hewitt Associates Any opinions expressed herein are mine alone and do not necessarily represent the opinions or policies of Hewitt Associates. Alan Altmark [EMAIL PROTECTED] Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU 01/04/2007 12:33 PM Please respond to The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU To IBMVM@LISTSERV.UARK.EDU cc Subject Re: IBM ServiceLink greenscreen to be discontinued March 31, 2007 On Thursday, 01/04/2007 at 09:31 CST, Mike Walter [EMAIL PROTECTED] wrote: Oh, by all means any and everyone with an issue **should** provide feedback. I merely presume that some list members will be too busy to open an IBMLink feedback for something they report on the list. Providing IBMLink with a single, comprehensive list might help to prevent those issues from being dropped through the cracks, Also the size of a single, comprehensive summary might force the issue to become clear enough to merit swift action! Inquiries have been made to the IBMLink folks to find out how they would like to handle these concerns. If anyone depends on VPL, note that it is going away, too. We ship source anyway, so that shouldn't be too big of a problem for z/VM installations. Alan Altmark z/VM Development IBM Endicott The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message, including any attachments. Any dissemination, distribution or other use of the contents of this message by anyone other than the intended recipient is strictly prohibited.
Re: IBM ServiceLink greenscreen to be discontinued March 31, 2007
Don't forget The Old Home Fill'er Up And Keep On A Truckin' Cafe, that was a good one, too!! On Thursday, 01/04/2007 at 09:53 CST, Adam Thornton [EMAIL PROTECTED] wrote: (Wolf Creek Pass, way across the Great Divide, truckin' on down the other side). It's not every man who knows the OTHER hit of a one-hit wonder. Watch it, pal. I read the Shelby County Tribune now, looking for more good deals on older-model cars. (It's Friday somewhere...) -- Chuckie
Re: IBM ServiceLink greenscreen to be discontinued March 31, 2007
I initially said: It's not every man who knows the OTHER hit of a one-hit wonder. But actually it appears that C. W. McCall's fan club is, ah, amazingly well represented here. Adam
OT: McCall's fan club. Was: IBM ServiceLink greenscreen to be discontinued March 31, 2007
In the interests of staying on-topic (yeah, a lot to ask of a bunch of caffiene-hyped A.D.D. sufferers), can we post further discussion of great country music/trucking songs and singers to this thread - keeping the original thread easier to follow? Thanks! Elvis has left the listserve. Mike Walter Hewitt Associates Any opinions expressed herein are mine alone and do not necessarily represent the opinions or policies of Hewitt Associates. Adam Thornton [EMAIL PROTECTED] Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU 01/04/2007 02:08 PM Please respond to The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU To IBMVM@LISTSERV.UARK.EDU cc Subject Re: IBM ServiceLink greenscreen to be discontinued March 31, 2007 I initially said: It's not every man who knows the OTHER hit of a one-hit wonder. But actually it appears that C. W. McCall's fan club is, ah, amazingly well represented here. Adam The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message, including any attachments. Any dissemination, distribution or other use of the contents of this message by anyone other than the intended recipient is strictly prohibited.
SHARE: Chairbear session list: Ancient No Frills ASCII Version
Heya, OK, maybe third time's the charm. And no, I'm not putting it into EBCDIC. The following are the VM/Linux program sessions that still require a session chair, as per my previous call to arms this morning. So if you're ready, willing and able, send me the session numbers you'd like to chair. Don't make me go all Martha on you! Day Time 24-hr Number Title Chair Email Speaker Mon 09:30a 930 9100 z/VM Platform UpdateReed Mullen Mon 09:30a 930 9102 The Very Basics of z/VM - Concepts and Terminology Bill Bitner Mon 01:30p 1330 9106 VM Performance Update Bill Bitner Mon 01:30p 1330 9214 sudo - Secure and Convenient Michael Potter Mon 01:30p 1330 9242 Linux for Beginners Hands-on-Lab - Part 1 of 3 Neale Ferguson Mon 01:30p 1330 9262 What's New in Linux on System z? Ulrich Weigand Mon 03:00p 1500 9127 z/VM for MVS Systems Programmers - Part 1 of 2 Martha McConaghy/Mark Post Mon 03:00p 1500 9210 Cloning WebSphere, DB2 and WebSphere MQ on Linux under z/VM Michael MacIsaac Mon 03:00p 1500 9243 Linux for Beginners Hands-on-Lab - Part 2 of 3 Neale Ferguson Mon 03:00p 1500 9248 Help! My (Virtual) Penguin is Sick! Philip Smith Mon 04:30p 1630 9128 z/VM for MVS Systems Programmers - Part 2 of 2 Martha McConaghy/Mark Post Mon 04:30p 1630 9215 Penguins Board the Stagecoach for the Linux Frontier: A User Experience with Linux on zSeries Marcy Cortes Mon 04:30p 1630 9241 Linux on System z - What to Do When There is a Problem Klaus Wacker Mon 04:30p 1630 9244 Linux for Beginners Hands-on-Lab - Part 3 of 3 Neale Ferguson Tue 08:00a 800 9125 Virtual Networking with z/VM Guest LANs and the z/VM Virtual Switch Alan Altmark Tue 08:00a 800 9235 Analyzing and Tuning Linux Storage in z/VM environment Barton Robinson Tue 08:00a 800 9263 Compiler Improvements Coming with gcc 4.2 Wolfgang Gellerich Tue 09:30a 930 9124 Using z/VM VSWITCH David Kreuter Tue 09:30a 930 9237 Linux under z/VM Performance Analysis Case Studies Barton Robinson Tue 09:30a 930 9274 The Linux IPL Procedure Edmund MacKenty Tue 11:00a 1100 9132 Migrating to the z/VM Virtual Switch Alan Altmark Tue 11:00a 1100 9233 Linux Installation Planning Mark Post Tue 11:00a 1100 9259 Making Your Penguins Fly - Introduction to SCSI over FCP for Linux on System z Christian Borntraeger Tue 01:30p 1330 9115 VM Performance Introduction Bill Bitner Tue 01:30p 1330 9129 z/VM Security and Integrity Alan Altmark Tue 01:30p 1330 9202 The W5 about Linux on System z - Who, What, Why, When and WhereJim Elliott Tue 01:30p 1330 9227 Linux for IBM System z Installation Hands-On-Lab - Part 1 of 3Richard Lewis/Chuck Morse Tue 03:00p 1500 9119 z/VM Installation - What Are You Afraid of? Mike Walter Tue 03:00p 1500 9204 Now that I have Linux, What Do I Do with My JCL? Michael Potter Tue 03:00p 1500 9212 Linux for System z at Nationwide - From Woe to Whoa! How did We Get Here, Toto? Jim Vincent Tue 03:00p 1500 9228 Linux for IBM System z Installation Hands-On-Lab - Part 2 of 3Richard Lewis/Chuck Morse Tue 04:30p 1630 9120 z/VM Installation - It's Installed, NOW What? Mike Walter Tue 04:30p 1630 9206 Cloning Linux Images under z/VM Steve Carl Tue 04:30p 1630 9213 Linux for System z at Nationwide - From Woe to Whoa! Where do we go now? Rick Barlow Tue 04:30p 1630 9229 Linux for IBM System z Installation Hands-On-Lab - Part 3 of 3Richard Lewis/Chuck Morse Wed 08:00a 800 9110 z/VM Live Guest Migration Romney White Wed 08:00a 800 9250 Were the Walls of Minas Tirith Unbreachable? Defending Linux on VM Hands-on-Lab - Part 1 of 3 Mark Boltz Wed 08:00a 800 9266 Monitoring Linux Guests and Processes with Linux Tools Christian Borntraeger Wed 08:00a 800 9267 Networking with Linux on System z - Part 1 of 2 Klaus Wacker Wed 09:30a 930 9113 The z/VM Control Program (CP) - Useful Things to Know John Franciscovich Wed 09:30a 930 9117 Introduction to Installation and Service of z/VM using VMSES/E Jim Vincent Wed 09:30a 930 9251 Were the Walls of Minas Tirith Unbreachable? Defending Linux on VM Hands-on-Lab - Part 2 of 3 Mark Boltz Wed 09:30a 930 9268 Networking with Linux on System z - Part 2 of 2 Klaus Wacker
Re: REXX compiling / EXECLOAD
On Thursday, 01/04/2007 at 11:12 PST, Don Russell [EMAIL PROTECTED] wrote: Is there any performance benefit to compiling a REXX EXEC if it will be EXECLOAD'd for the lifetime of it's use? For example, I have a service machine which, upon startup, EXECLOADs some EXECs it needs over and over. It/they remain EXECLOADd until the service machine is shutdown. The EXEC is not particularly complex/large, but does compiling it actually make any difference? The advantage of compilation is not really based on how long you use it, but on what you are doing and how often you are doing it. An exec that spends all of its time in CMS and CP commands (e.g. diag or pipes) will see very little improvement, if any, by compiling. If you do a lot of parsing, string manipulation, and arithmetic, then you'll see gains. EXECLOADing is useful when you run the exec repeatedly, avoiding reading it from disk every time. Obviously that's only meaningful if the disk I/Os are a problem. These are, of course, generalizations and my motto is Never Generalize. Alan Altmark z/VM Development IBM Endicott
Re: REXX compiling / EXECLOAD
You will not see the source if you include the NOSLINE option when you compile the program. -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Wayne T Smith Sent: Thursday, January 04, 2007 11:28 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: REXX compiling / EXECLOAD Oh yes! EXECLOAD simply loads a file into storage. If you display memory, you'll see the source (compiled or non-compiled data directly from your file) ... and that's what is interpreted when you run the non-compiled EXEC or run directly from a compiled EXEC. If you see a performance benefit from compile, it will still be there if EXECLOADed. A non-compiled EXEC must still be interpreted, even if EXECLOADed. cheers, wayne Don Russell wrote, in part, on 1/4/2007 2:12 PM: Is there any performance benefit to compiling a REXX EXEC if it will be EXECLOAD'd for the lifetime of it's use? For example, I have a service machine which, upon startup, EXECLOADs some EXECs it needs over and over. It/they remain EXECLOADd until the service machine is shutdown. The EXEC is not particularly complex/large, but does compiling it actually make any difference? Does EXECLOAD tokenize/optimize the EXEC if it's not compiled? Thank you, Don Russell
Re: IBM ServiceLink greenscreen to be discontinued March 31, 2007
H. If you ship source, what is the purpose of the HTTxxx series of abend codes? -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Alan Altmark Sent: Thursday, January 04, 2007 10:34 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: IBM ServiceLink greenscreen to be discontinued March 31, 2007 On Thursday, 01/04/2007 at 09:31 CST, Mike Walter [EMAIL PROTECTED] wrote: Oh, by all means any and everyone with an issue **should** provide feedback. I merely presume that some list members will be too busy to open an IBMLink feedback for something they report on the list. Providing IBMLink with a single, comprehensive list might help to prevent those issues from being dropped through the cracks, Also the size of a single, comprehensive summary might force the issue to become clear enough to merit swift action! Inquiries have been made to the IBMLink folks to find out how they would like to handle these concerns. If anyone depends on VPL, note that it is going away, too. We ship source anyway, so that shouldn't be too big of a problem for z/VM installations. Alan Altmark z/VM Development IBM Endicott
Re: REXX compiling / EXECLOAD
Depending on how extensively commented and how much white space there is in the EXEC, you will see some improvement if you remove all but the executable code from the version being interpreted. True, it is probably a somewhat piddly amount, but piddly times millions can be pretty big. -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Alan Altmark Sent: Thursday, January 04, 2007 1:35 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: REXX compiling / EXECLOAD On Thursday, 01/04/2007 at 11:12 PST, Don Russell [EMAIL PROTECTED] wrote: Is there any performance benefit to compiling a REXX EXEC if it will be EXECLOAD'd for the lifetime of it's use? For example, I have a service machine which, upon startup, EXECLOADs some EXECs it needs over and over. It/they remain EXECLOADd until the service machine is shutdown. The EXEC is not particularly complex/large, but does compiling it actually make any difference? The advantage of compilation is not really based on how long you use it, but on what you are doing and how often you are doing it. An exec that spends all of its time in CMS and CP commands (e.g. diag or pipes) will see very little improvement, if any, by compiling. If you do a lot of parsing, string manipulation, and arithmetic, then you'll see gains. EXECLOADing is useful when you run the exec repeatedly, avoiding reading it from disk every time. Obviously that's only meaningful if the disk I/Os are a problem. These are, of course, generalizations and my motto is Never Generalize. Alan Altmark z/VM Development IBM Endicott
Re: IBM ServiceLink greenscreen to be discontinued March 31, 2007
There are more of us out here. Ed Martin Aultman Health Foundation 330-588-4723 [EMAIL PROTECTED] ext. 40441 -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Adam Thornton Sent: Thursday, January 04, 2007 3:08 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: IBM ServiceLink greenscreen to be discontinued March 31, 2007 I initially said: It's not every man who knows the OTHER hit of a one-hit wonder. But actually it appears that C. W. McCall's fan club is, ah, amazingly well represented here. Adam
Re: IBM ServiceLink greenscreen to be discontinued March 31, 2007
On Thursday, 01/04/2007 at 01:37 PST, Schuh, Richard [EMAIL PROTECTED] wrote: H. If you ship source, what is the purpose of the HTTxxx series of abend codes? Ooooh! Pop quiz! From a read of HTT001-HTT003 the z/VM 5.2 CP Messages Codes book, they are abends dealing with incorrect linkage between CP modules (programming errors). Yes, OCO modules can issue abends. Sometimes we give details on those abends and sometimes we just say Call us. (All HTT abend explanations end with Contact IBM.) But I'm not sure how our shipping source (or not) changes the explanations of abend codes or your use of VPL. Alan Altmark z/VM Development IBM Endicott
Re: IBM ServiceLink greenscreen to be discontinued March 31, 2007
When we got HTT00x abends, the explanation was more generic, something like, A module which is OCO had a problem. Contact IBM. The same generic explanation was there, verbatim, for every HTTxxx abend. If the source were shipped, there would be no reason for these codes. It doesn't explain the abend. Rather, the existence and explanation of the abend refutes the statement that you ship source, at least for some components. The very first HTT abend we had was caused by another vendor's software. I am glad to see that the RCFs do some good. Now, there is information that might have led us to them as the source or, perhaps led them to the problem. When it happened, we naturally sent the dump to IBM, as instructed, and waited until your folks said, It isn't our problem, before the other vendor really got involved. (We sent them the dump right after sending it to IBM, but they did not have any idea where to look based on the abend code or description. They waited for IBM to make the first determination. Then, they had to enlist help from IBM in order to find the problem.) -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Alan Altmark Sent: Thursday, January 04, 2007 2:35 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: IBM ServiceLink greenscreen to be discontinued March 31, 2007 On Thursday, 01/04/2007 at 01:37 PST, Schuh, Richard [EMAIL PROTECTED] wrote: H. If you ship source, what is the purpose of the HTTxxx series of abend codes? Ooooh! Pop quiz! From a read of HTT001-HTT003 the z/VM 5.2 CP Messages Codes book, they are abends dealing with incorrect linkage between CP modules (programming errors). Yes, OCO modules can issue abends. Sometimes we give details on those abends and sometimes we just say Call us. (All HTT abend explanations end with Contact IBM.) But I'm not sure how our shipping source (or not) changes the explanations of abend codes or your use of VPL. Alan Altmark z/VM Development IBM Endicott
