Re: set share to stop a guest from getting service ?
On Tuesday, 04/01/2008 at 05:48 EDT, Rick Troth [EMAIL PROTECTED] wrote: cp send cp thebadguest sleep -or- cp send cp thebadguest stop Also an excellent use of the CP FOR command. For those not familiar with it, it has a slightly different authorization scheme: 1. If you are the active SECUSER of a user, you can use CP FOR command 2. If you are using an ESM and you have LOGON BY privilege to the target user, you can use FOR, even if you aren't the active SECUSER. Alan Altmark z/VM Development IBM Endicott
CAVMEN Meeting on Thursday, April 17, 2008 - Late Agenda Change
The second quarter meeting of the Chicago Area VM (and Linux) Enthusiasts will be held on Thursday, April 17, 2008. There is a late change to the agenda. The second presentation has been changed to TCP/IP for z/VM Update . The Final Final Agenda is included below. -- Meeting Location: *** NEW MEETING LOCATION *** This quarter's meeting will be held at the Hewitt Associates 'West Campus' in Lincolnshire, located at 4 Overlook Point, Building B, 2nd floor, Room M3. Do NOT park on the South side (visitor entrance). Instead: park and enter on the East side of the 4 Overlook Point building. Check in with the security guard when entering. If you have not attended a meeting at this location before, or you are not familiar with the area, http://cavmen.home.comcast.net/hewittp.htmlClick here for additional information on directions, maps, lodging and dining. -- Attendance: We would like to request a count of expected attendees by the Monday before the meeting, so that we may plan appropriately for arranging the facilities, and for refreshments and lunch, should one of the vendors wish to provide them. If you are planning to attend, PLEASE send an E-Mail by that date to mailto:[EMAIL PROTECTED][EMAIL PROTECTED] with a subject line of Meeting Attendance. This is meant to be a facilities planning aid and should not be interpreted as a registration requirement. If you suddenly become available at the last minute, please feel free to attend even if you have not responded. Thank you in advance for your cooperation in this matter. -- Final Meeting Agenda: 9:00 AM The IBM System z10 Hardware Innovation Overview This presentation will provide an overview of IBM's exciting new System z10 Server. It will include detailed information on the new processor, the enhanced memory and the I/O capabilities, and all the new features and functions associated with the new z10 server including the new 'just in time' capacity provisioning capabilities. The speaker will be Robert Neidig of the IBM Corporation. 10:30 AMCoffee Break 11:00 AMTCP/IP for z/VM Update z/VM V5.3 includes TCP/IP Function Level 530, a new level of the TCP/IP Feature that delivers significant new functions. This session gives an overview of these enhancements, as well as describing the VM TCP/IP product and the changes to it that were introduced in Function Level 520 with z/VM V5.2. The speaker will be Tracy Adams of the IBM Corporation. 12:30 PMLunch Break 1:30 PM Administration and Vendor Announcements 2:00 PM Link Aggregation with the z/VM Virtual Switch Link Aggregation is a new feature of z/VM V5.3. Are you already using a z/VM Virtual Switch to manage your network connections? Do you want to find out how to get more out of z/VM Virtual Switch technology? Come to this session to learn how to make your backup OSA cards work for you by increasing your throughput and creating near seamless failover for your virtual network. The speaker will be Tracy Adams of the IBM Corporation. 3:15 PM Coffee Break and Prize Drawing 3:30 PM OpenKicks: The CICS(R) API on Linux This is the first peek at the soon to be released CICS(R) emulation environment for Linux(R), UNIX(R), and Windows(R). Built to be friendly to mainframe programmers and UNIX(R) system administrators, OpenKicks takes a fresh look at emulating CICS(R) on UNIX(R). Four concepts set OpenKicks apart from other emulation environments: * Available source code to allow on-site customization/extension. * Built on a database for trusted data integrity. * Good third party vendor support to avoid compiler and database 'lock-in.' * Backward compatible to allow painless porting back to the mainframe. OpenKicks is a product of Replatform Technologies, LLC and not affiliated with IBM(R). IMPORTANT NOTE: This presentation has several demos which do not convert well to slides. If you are unable to attend the presentation, please contact me to arrange another time. The speaker will be Michael Potter of Replatform Technologies. 4:45 PM Free-for-All Members will attempt to answer any reasonable VM or hardware related questions. If you are having a problem and want to find out if others are experiencing it, or you are installing new hardware or software and want to find out what types of problems others have experienced, here is the place to find out. Members are encouraged to bring ideas for future presentations and speakers to this meeting. -- Please check the WEB site for Map and Directions: http://cavmen.home.comcast.net In addition, you will also find extensive information available on dining and lodging in the Hewitt Associates area. Additional information about the CAVMEN group, and other VM related items of interest are available on our web site. There is no charge for admission to meetings.
Re: DIRMAINT and MAINT
The easy solution to the peek problem, though if you ever have a really large reader file, it might cause other problems: Defaults set peek for * -- Robert P. Nix Mayo Foundation.~. RO-OE-5-55 200 First Street SW/V\ 507-284-0844 Rochester, MN 55905 /( )\ -^^-^^ In theory, theory and practice are the same, but in practice, theory and practice are different. On 4/2/08 1:00 PM, Kris Buelens [EMAIL PROTECTED] wrote: Maybe your are missing PEEK's message telling that you don't see all records in the reader file. PEEK's default is FOR 200, you can change that with DEFAULTS SET PEEK FOR 3000 At the other hand, there is my DIRME EXEC, part of the DRM package on VM's download lib. With DIRME you issue DIRME MAINT or DIRME MAINT LOCK or even PIPE literal MAINT VTAM TCPIP !split !rexx(DIRME EXEC)! cons 2008/4/2, Fox Blue [EMAIL PROTECTED]: Dear all, I have DIRMAINT now running and try to get familiar with it. I encountere d the following problem with it: I use MAINT to issue the dirm commnd to retrieve MAINT directory entry. D IRM punches me the directory entry to MAINT's reader but it has NO MDISK statements in it. For all other users I get the complete directory entrie s so this is working. Is there some configuration I am lacking or what is wrong with it? BR Fox
Re: Adding temp space
Dear all, You were right, of course. I overlooked this totally as my emulation wind ow was overlayed by another window. Because of the lot of comments in the MA INT directory it is bigger than all my other enties. Thanks so much for this help. BR Florian
VTAM R.I.P.
At 23:55 GMT on Monday, March 31, VTAM was removed from our VM system. May it rest in peace (as it has been doing since 1995). One more cash cow bites the dust. The only remnant left will be one of the large, old manuals. It is the perfect weight to silence the vibrations in the case of the Dell GX620 that sits on my desk. When the GX620 is replaced in about a year, I hope that even that manual can be put to rest. Regards, Richard Schuh
Re: VTAM R.I.P.
On Wednesday, 04/02/2008 at 03:06 EDT, Schuh, Richard [EMAIL PROTECTED] wrote: At 23:55 GMT on Monday, March 31, VTAM was removed from our VM system. May it rest in peace (as it has been doing since 1995). One more cash cow bites the dust. (head bowed...silent...I sure am gonna miss that cow...(sniff)...I sooo wanted to buy a new car this year with my share of the license fees) Alan Altmark z/VM Development IBM Endicott
Re: VTAM R.I.P.
Z NET,QUICK
Re: VTAM R.I.P.
VM/VTAM was an MVS product shoe-horned (with some pretty clever work) into VM. Wouldn't the appropriate VM and MVS-ish command be: Z NET,EOD Mike Walter Hewitt Associates Any opinions expressed herein are mine alone and do not necessarily represent the opinions or policies of Hewitt Associates. Rob van der Heij [EMAIL PROTECTED] Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU 04/02/2008 05:13 PM Please respond to The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU To IBMVM@LISTSERV.UARK.EDU cc Subject Re: VTAM R.I.P. Z NET,QUICK 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. All messages sent to and from this e-mail address may be monitored as permitted by applicable law and regulations to ensure compliance with our internal policies and to protect our business. E-mails are not secure and cannot be guaranteed to be error free as they can be intercepted, amended, lost or destroyed, or contain viruses. You are deemed to have accepted these risks if you communicate with us by e-mail.
Re: VTAM R.I.P.
Why bother? It was going away for good. Actually, I had a VTAM (MVS) expert in the office when I laid the tired old thing to rest. He couldn't remember the command and neither did I, so #CP LOGOFF is what I used :-) I had already removed any trace of VTAM from our service machine list, so there was no chance of it being resuscitated before I could tell VM:Secure to get it out of the directory. The strange thing is that even though there were 60 people accessing the system via TPX Monday morning and there were frequently as many as 150 concurrent TPXers in the weeks leading up to the decommissioning ceremony, I have been contacted by only 4 people who apparently could not click on the link to a document giving step-by-step, screenshot-by-screenshot, instructions on how to set up a TN3270 emulator session that would connect to VM. I expected the number to be more in line with the number who try to reply to mail that starts with Do not reply to this email ..., a much higher number. Regards, Richard Schuh -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Mike Walter Sent: Wednesday, April 02, 2008 3:18 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: VTAM R.I.P. VM/VTAM was an MVS product shoe-horned (with some pretty clever work) into VM. Wouldn't the appropriate VM and MVS-ish command be: Z NET,EOD Mike Walter Hewitt Associates Any opinions expressed herein are mine alone and do not necessarily represent the opinions or policies of Hewitt Associates. Rob van der Heij [EMAIL PROTECTED] Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU 04/02/2008 05:13 PM Please respond to The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU To IBMVM@LISTSERV.UARK.EDU cc Subject Re: VTAM R.I.P. Z NET,QUICK 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. All messages sent to and from this e-mail address may be monitored as permitted by applicable law and regulations to ensure compliance with our internal policies and to protect our business. E-mails are not secure and cannot be guaranteed to be error free as they can be intercepted, amended, lost or destroyed, or contain viruses. You are deemed to have accepted these risks if you communicate with us by e-mail.
Re: VTAM R.I.P.
We still have it here, but I suspect that it is not long lived. Some of my worst memories involve VTAM on VM. I was the VM team leader for the IBM Education support center in Dallas in 1985 and told my manager and my 2nd level that we should get VM/SP R4 for the remote locations we suppported and HPO R4 for the central site 3081's. R4 was the release with native VTAM support. VTAM had been supported for a while with VS/1 or DOS/VS hosting VTAM but someone decided that GCS was the way to go. They took a gutted MVS/XA and quickly fitted it into VM. I don't remember that GCS abended all the time, but CP certainly did. VM/SP R4, with and without HPO was an absolute disaster. If we went thru a day without a CP abend, we celebrated. R4 was probably the shortest lived VM release ever. I think it went GA in December of 1985 and was replaced with VM/SP 4.3 in about March. It was a great improvement. During the fall of '85, Barton Robinson practically lived with us being the expert from the East sent to help us. I remember the arguments inside IBM regarding VTAM vs. TCPIP. IBM was going to be pure VTAM. It's too bad that internal IBM was so stuck on SNA and VTAM that there could not have been an earlier combination of the two disciplines. Jim Schuh, Richard wrote: This is a multi-part message in MIME format. --_=_NextPart_001_01C894F4.805C40E4 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable At 23:55 GMT on Monday, March 31, VTAM was removed from our VM system. May it rest in peace (as it has been doing since 1995). One more cash cow bites the dust. The only remnant left will be one of the large, old manuals. It is the perfect weight to silence the vibrations in the case of the Dell GX620 that sits on my desk. When the GX620 is replaced in about a year, I hope that even that manual can be put to rest.=20 Regards,=20 Richard Schuh=20 --_=_NextPart_001_01C894F4.805C40E4 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: quoted-printable !DOCTYPE HTML PUBLIC -//W3C//DTD HTML 3.2//EN HTML HEAD META HTTP-EQUIV=3DContent-Type CONTENT=3Dtext/html; = charset=3Dus-ascii META NAME=3DGenerator CONTENT=3DMS Exchange Server version = 6.5.7652.24 TITLEVTAM R.I.P./TITLE /HEAD BODY !-- Converted from text/rtf format -- PFONT SIZE=3D2 FACE=3DArialAt 23:55 GMT on Monday, March 31, VTAM = was removed from our VM system. May it rest in peace (as it has been = doing since 1995). One more cash cow bites the dust./FONT/P PFONT SIZE=3D2 FACE=3DArialThe only remnant left will be one of = the large, old manuals. It is the perfect weight to silence the = vibrations in the case of the Dell GX620 that sits on my desk. When the = GX620 is replaced in about a year, I hope that even that manual can be = put to rest. /FONT/P PFONT FACE=3DArialRegards,BR Richard Schuh /FONT /P BR /BODY /HTML --_=_NextPart_001_01C894F4.805C40E4-- -- Jim Bohnsack Cornell University (607) 255-1760 [EMAIL PROTECTED]
Re: VTAM R.I.P.
On Wednesday, 04/02/2008 at 09:30 EDT, Jim Bohnsack [EMAIL PROTECTED] wrote: R4 was the release with native VTAM support. VTAM had been supported for a while with VS/1 or DOS/VS hosting VTAM but someone decided that GCS was the way to go. They took a gutted MVS/XA and quickly fitted it into VM. Nonsense. There is no more MVS/XA code in GCS than there is in CMS. Alan Altmark z/VM Development IBM Endicott
