Re: REDHAT KICKSTART
Posted on both Lists. Thanks Thank You, Terry Martin Lockheed Martin - Citic z/OS and z/VM Performance Tuning and Operating Systems Support Office - 443 348-2102 Cell - 443 632-4191 From: Martin, Terry R. (CMS/CTR) (CTR) Sent: Monday, July 12, 2010 5:27 PM To: linux-...@vm.marist.edu Subject: REDHAT KICKSTART Hi We have been Kick Starting new z/Linux guests under RHEL 5.2. We have a base build in the Kick Start of one MOD3 and two MOD27's. In the CONF file we specify these devices (700, 800-801) things work fine. Recently we started adding another MOD27 to the base build (700, 800-802). Now during the Kick Start it initializes 700, 800, and 801 but when it tries to init 802 it comes up with a message stating that it needs to init 802 and asks you to reply YESNO [ ]. Does something need to change in the Kick Start setup to tell it that we now have an 802 disk to init so to avoid this prompt? Thanks Thank You, Terry Martin Lockheed Martin - Citic z/OS and z/VM Performance Tuning and Operating Systems Support Office - 443 348-2102 Cell - 443 632-4191
Journaling/Incorrect Password Count
We have a system generated some time ago that does not have the ability to query and set journaling. According to the documentation, the default is 10 incorrect passwords and disable the terminal/IP address for 60 minutes. This system is kept up for extended periods. I have a situation where I was given bad information about the passwords on that system. The day before yesterday, I ran afoul of the limit. Is there any way to get counts reset in this system short of an IPL? Also, the count seems to be ever increasing, allowing only 1 attempt before the next lockout. Is this as desired? Please, no comments from Chucky about locking me out on a count of zero being appropriate.. Regards, Richard Schuh
Re: Journaling/Incorrect Password Count
Also, the count seems to be ever increasing, allowing only 1 attempt before the next lockout. You may be attempting logon before the lockout period has expired. If the lockout period is 60 minutes, that is 60 minutes after the *last attempt*. So if you wait 59 minutes and 45 seconds, then attempt a logon, the timer gets reset to 60 minutes. It can be very frustrating for impatient users. Best to wait for longer than you think the timer is set for before trying to logon. Peter The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review retransmission dissemination or other use of or taking any action in reliance upon this information by persons or entities other than the intended recipient or delegate is strictly prohibited. If you received this in error please contact the sender and delete the material from any computer. The integrity and security of this message cannot be guaranteed on the Internet. The sender accepts no liability for the content of this e-mail or for the consequences of any actions taken on the basis of information provided. The recipient should check this e-mail and any attachments for the presence of viruses. The sender accepts no liability for any damage caused by any virus transmitted by this e-mail. This disclaimer is property of the TTC and must not be altered or circumvented in any manner.
Re: Journaling/Incorrect Password Count
Does this help from HELP CPSET JOURNAL? 3. SET JOURNAL LOGON OFF disables the logon inductor and discards the count of logon attempts associated with terminals and user IDs that are not logged on at the time. If SET JOURNAL LOGON ON is then issued, no information about previous logon attempts is available. Note: The logon inductor is the CP facility that responds to excessive logon attempts with a bad password. It temporarily prohibits a terminal or user ID from logging on. Scott Rohling On Tue, Jul 13, 2010 at 8:39 AM, Schuh, Richard rsc...@visa.com wrote: We have a system generated some time ago that does not have the ability to query and set journaling. According to the documentation, the default is 10 incorrect passwords and disable the terminal/IP address for 60 minutes. This system is kept up for extended periods. I have a situation where I was given bad information about the passwords on that system. The day before yesterday, I ran afoul of the limit. Is there any way to get counts reset in this system short of an IPL? Also, the count seems to be ever increasing, allowing only 1 attempt before the next lockout. Is this as desired? Please, no comments from Chucky about locking me out on a count of zero being appropriate.. Regards, Richard Schuh
Re: Journaling/Incorrect Password Count
Nope - waited overnight. Regards, Richard Schuh From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of peter.w...@ttc.ca Sent: Tuesday, July 13, 2010 7:48 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Journaling/Incorrect Password Count Also, the count seems to be ever increasing, allowing only 1 attempt before the next lockout. You may be attempting logon before the lockout period has expired. If the lockout period is 60 minutes, that is 60 minutes after the *last attempt*. So if you wait 59 minutes and 45 seconds, then attempt a logon, the timer gets reset to 60 minutes. It can be very frustrating for impatient users. Best to wait for longer than you think the timer is set for before trying to logon. Peter The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review retransmission dissemination or other use of or taking any action in reliance upon this information by persons or entities other than the intended recipient or delegate is strictly prohibited. If you received this in error please contact the sender and delete the material from any computer. The integrity and security of this message cannot be guaranteed on the Internet. The sender accepts no liability for the content of this e-mail or for the consequences of any actions taken on the basis of information provided. The recipient should check this e-mail and any attachments for the presence of viruses. The sender accepts no liability for any damage caused by any virus transmitted by this e-mail. This disclaimer is property of the TTC and must not be altered or circumvented in any manner.
Re: Journaling/Incorrect Password Count
Query and SET commands have not been enabled via the SYSTEM CONFIG file. Regards, Richard Schuh From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Scott Rohling Sent: Tuesday, July 13, 2010 7:50 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Journaling/Incorrect Password Count Does this help from HELP CPSET JOURNAL? 3. SET JOURNAL LOGON OFF disables the logon inductor and discards the count of logon attempts associated with terminals and user IDs that are not logged on at the time. If SET JOURNAL LOGON ON is then issued, no information about previous logon attempts is available. Note: The logon inductor is the CP facility that responds to excessive logon attempts with a bad password. It temporarily prohibits a terminal or user ID from logging on. Scott Rohling On Tue, Jul 13, 2010 at 8:39 AM, Schuh, Richard rsc...@visa.commailto:rsc...@visa.com wrote: We have a system generated some time ago that does not have the ability to query and set journaling. According to the documentation, the default is 10 incorrect passwords and disable the terminal/IP address for 60 minutes. This system is kept up for extended periods. I have a situation where I was given bad information about the passwords on that system. The day before yesterday, I ran afoul of the limit. Is there any way to get counts reset in this system short of an IPL? Also, the count seems to be ever increasing, allowing only 1 attempt before the next lockout. Is this as desired? Please, no comments from Chucky about locking me out on a count of zero being appropriate.. Regards, Richard Schuh
TRLE with Vswitch
We are in the process of installing zOS V1R7 on our z10 BC machine. We are attempting to connect Our MVS TCPIP, running as a guest to VM, via VSWITCH to a QDIO OSA. We get the OSA address's Allocated and busy and we can ping the MVS TCPIP and that works fine. We cannot ping or connect To any other hast outside of the MVS TCPIP. The following is what we have coded in the TCPIP stack And in the VTAM TRLE; Device Link statement; DEVICE QDOSA1 MPCIPA LINK OSA1 IPAQENET QDOSA1 Home Statement; 137.99.26.9OSA1 Beginroutes Statement; BEGINROUTES ROUTE 137.99.26.9/27= OSA1MTU1500 ROUTE DEFAULT 137.99.26.1 OSA1MTU 1500 ENDROUTES VTAM TRLE NODE; A07TRLE VBUILD TYPE=TRL TRLED00 TRLE LNCTL=MPC, x READ=(FD00), x WRITE=(FD01), x DATAPATH=(FD02), x PORTNAME=QDOSA1, x MPCLEVEL=QDIO Are we missing something or have something out of order?? We would appreciate any help/suggestions in pointing out what is wrong or missing. TIA Dan
Re: TRLE with Vswitch
Does the PORTNAME match the name of the vswitch? From where can you PING the MVS TCPIP? On Tue, Jul 13, 2010 at 11:02 AM, Pelletier, Daniel daniel.pellet...@uconn.edu wrote: We are in the process of installing zOS V1R7 on our z10 BC machine. We are attempting to connect Our MVS TCPIP, running as a guest to VM, via VSWITCH to a QDIO OSA. We get the OSA address’s Allocated and busy and we can ping the MVS TCPIP and that works fine. We cannot ping or connect To any other hast outside of the MVS TCPIP. The following is what we have coded in the TCPIP stack And in the VTAM TRLE; Device Link statement; DEVICE QDOSA1 MPCIPA LINK OSA1 IPAQENET QDOSA1 Home Statement; 137.99.26.9OSA1 Beginroutes Statement; BEGINROUTES ROUTE 137.99.26.9/27= OSA1MTU1500 ROUTE DEFAULT 137.99.26.1 OSA1MTU 1500 ENDROUTES VTAM TRLE NODE; A07TRLE VBUILD TYPE=TRL TRLED00 TRLE LNCTL=MPC, x READ=(FD00), x WRITE=(FD01), x DATAPATH=(FD02), x PORTNAME=QDOSA1, x MPCLEVEL=QDIO Are we missing something or have something out of order?? We would appreciate any help/suggestions in pointing out what is wrong or missing. TIA Dan -- Mark Pace Mainline Information Systems 1700 Summit Lake Drive Tallahassee, FL. 32317
Re: TRLE with Vswitch
On Tuesday, 07/13/2010 at 11:10 EDT, Mark Pace mpac...@gmail.com wrote: Does the PORTNAME match the name of the vswitch? There is no requirement for the PORTNAME to match ANYTHING in z/VM unless you are sharing a virtual NIC. Alan Altmark z/VM Development IBM Endicott
Re: TRLE with Vswitch
OOPs I forgot to include the VSWITCH Portname. In the Vswitch; PORTNAME QDOSA1 In the VM Machine's Profile for the MVS guest we have coded; 'CP DEFINE NIC FD00 TYPE QDIO DEV 3 CHPID FD' 'CP COUPLE FD00 TO SYSTEM VSWT' From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Mark Pace Sent: Tuesday, July 13, 2010 11:08 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: TRLE with Vswitch Does the PORTNAME match the name of the vswitch? From where can you PING the MVS TCPIP? On Tue, Jul 13, 2010 at 11:02 AM, Pelletier, Daniel daniel.pellet...@uconn.edumailto:daniel.pellet...@uconn.edu wrote: We are in the process of installing zOS V1R7 on our z10 BC machine. We are attempting to connect Our MVS TCPIP, running as a guest to VM, via VSWITCH to a QDIO OSA. We get the OSA address's Allocated and busy and we can ping the MVS TCPIP and that works fine. We cannot ping or connect To any other hast outside of the MVS TCPIP. The following is what we have coded in the TCPIP stack And in the VTAM TRLE; Device Link statement; DEVICE QDOSA1 MPCIPA LINK OSA1 IPAQENET QDOSA1 Home Statement; 137.99.26.9OSA1 Beginroutes Statement; BEGINROUTES ROUTE 137.99.26.9/27http://137.99.26.9/27= OSA1 MTU1500 ROUTE DEFAULT 137.99.26.1 OSA1MTU 1500 ENDROUTES VTAM TRLE NODE; A07TRLE VBUILD TYPE=TRL TRLED00 TRLE LNCTL=MPC, x READ=(FD00), x WRITE=(FD01), x DATAPATH=(FD02), x PORTNAME=QDOSA1, x MPCLEVEL=QDIO Are we missing something or have something out of order?? We would appreciate any help/suggestions in pointing out what is wrong or missing. TIA Dan -- Mark Pace Mainline Information Systems 1700 Summit Lake Drive Tallahassee, FL. 32317
Re: TRLE with Vswitch
Alan,,, Thanks for the reply. We are not sharing a virtual NIC, so I guess the Portname is not needed. But, I still do not see why we cannot connect to our other Host Or to Telnet. Any ideas will be appreciated. TIA -Original Message- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Alan Altmark Sent: Tuesday, July 13, 2010 11:25 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: TRLE with Vswitch On Tuesday, 07/13/2010 at 11:10 EDT, Mark Pace mpac...@gmail.com wrote: Does the PORTNAME match the name of the vswitch? There is no requirement for the PORTNAME to match ANYTHING in z/VM unless you are sharing a virtual NIC. Alan Altmark z/VM Development IBM Endicott
Re: TRLE with Vswitch
On Tuesday, 07/13/2010 at 11:38 EDT, Pelletier, Daniel daniel.pellet...@uconn.edu wrote: Thanks for the reply. We are not sharing a virtual NIC, so I guess the Portname is not needed. But, I still do not see why we cannot connect to our other Host Or to Telnet. Any ideas will be appreciated. You've posted a networking problem with no pictures. That's 10 points from UConn. Remove the PORTNAME hazard from DEFINE VSWITCH. Only z/OS requires it. Its use in z/VM (and Linux) simply causes problems. Is the VSWITCH being used successfully by other guests? Is the VSWITCH plugged into the 137.99.26.9/27 subnet? Alan Altmark z/VM Development IBM Endicott
Re: A call to help Chair sessions at SHARE
Hi All, A new list is out for sessions. As for the canceled one I am waiting for confirmation on what to do with it. It also looks like two sessions opened up because of a conflict in the schedule, so they are also open. x86 Virtualization Technologies and Strategies Wed 2010-08-04, 15:00:00 Room 305 Steven Loeschorn Canceled Comparing and Contrasting Virtualization Technologies Thurs 2010-08-05, 08:00:00 Room 302 Mike Buzzetti Introduction to the new Linux on System z Terminal Server using IUCV Tue 2010-08-03, 16:30:00 Room 208 Hans-Joachim Picht Virtual Linux Server Disaster Recovery Planning Wed 2010-08-04, 13:30:00 Room 306 Rick Barlow Thank you; Brian Jagos TSO Principal Consultant z/OS z/VM Linux for System z Phone: (631) 342 - 6523 http://www.ca.com/
Re: A call to help Chair sessions at SHARE
Hi All, Sorry about that there are a few more I missed. x86 Virtualization Technologies and Strategies Wed 2010-08-04, 15:00:00 Room 305 Steven Loeschorn Canceled Comparing and Contrasting Virtualization Technologies Thurs 2010-08-05, 08:00:00 Room 302 Mike Buzzetti Introduction to the new Linux on System z Terminal Server using IUCV Tue 2010-08-03, 16:30:00 Room 208 Hans-Joachim Picht Virtual Linux Server Disaster Recovery Planning Wed 2010-08-04, 13:30:00 Room 306 Rick Barlow z/VM Platform Update Mon 2010-08-02, 11:00:00 Room 306 Alan Altmark System Z - Linux at its best Mon 2010-08-02, 15:00:00 Room 208 Mark L. Shackelford Innovative Computing Solutions with System z and Other Architectures; Including Implication in Performance Models Tue 2010-08-03, 09:30:00 Room 306 Bill Reeder Using Virtualization to Help Move a Data Center Tue 2010-08-03, 13:30:00 Room 305 Jim Moling Thank you; Brian Jagos TSO Principal Consultant z/OS z/VM Linux for System z Phone: (631) 342 - 6523 http://www.ca.com/ From: Jagos, Brian V Sent: Tuesday, July 13, 2010 14:11 To: Jagos, Brian V; 'SHARE VM Cluster leadership'; 'The IBM z/VM Operating System' Subject: RE: A call to help Chair sessions at SHARE Importance: High Hi All, A new list is out for sessions. As for the canceled one I am waiting for confirmation on what to do with it. It also looks like two sessions opened up because of a conflict in the schedule, so they are also open. Thank you; Brian Jagos TSO Principal Consultant z/OS z/VM Linux for System z Phone: (631) 342 - 6523 http://www.ca.com/
REDHAT KICKSTART
Hi We have been Kick Starting new z/Linux guests under RHEL 5.2. We have a base build in the Kick Start of one MOD3 and two MOD27's. In the CONF file we specify these devices (700, 800-801) things work fine. Recently we started adding another MOD27 to the base build (700, 800-802). Now during the Kick Start it initializes 700, 800, and 801 but when it tries to init 802 it comes up with a message stating that it needs to init 802 and asks you to reply YESNO [ ]. Does something need to change in the Kick Start setup to tell it that we now have an 802 disk to init so to avoid this prompt? Thank You, Terry Martin Lockheed Martin - Citic z/OS and z/VM Performance Tuning and Operating Systems Support Office - 443 348-2102 Cell - 443 632-4191
Re: REDHAT KICKSTART
On 7/13/2010 at 03:19 PM, Martin, Terry R. (CMS/CTR) (CTR) terry.mar...@cms.hhs.gov wrote: Does something need to change in the Kick Start setup to tell it that we now have an 802 disk to init so to avoid this prompt? Seeing a copy of your kickstart file might be helpful. Mark Post
Re: z/VM c/c++ or REXX for socket programming??
Hello, Ashwin. I would suggest that you first attempt a straight port of your C application over to z/VM.it supports the same C/C++ compiler that is available on z/OS, and the z/VM LE level is at (if I remember correctly) the z/OS 1.9 level. In fact, if you do not have the z/VM C/C++ compiler installed, you might try simply compiling the code on z/OS, and then move the object text file(s) over to z/VM and bind it there with z/VM's LE libraries. z/VM now supports the z/OS binder as well. The LE socket library calls (BPX1xxx) should work on z/VM as they do on z/OS. Let us know if you run into any problems..I think you'll find the CMS environment a pleasant one to do code development in. On 07/12/2010 06:04 PM, Bhemidhi, Ashwin wrote: Hello all, I am working on porting an application written in 'c' (socket based) that is used to report events to a central server. The application is the client part of the client-server architecture of event utility that is home grown system. We use this application in z/OS ( an other systems) to report event to the central server. We also have 24/7 operators that use an event viewer (client) of the central server to monitor for any critical events. I would like to extend the same functionality to our z/VM system as we already have the monitoring setup/infrastructure. The question I have before I start on the port is, is it better/easier to compile the z/OS c client code under z/VM LE or rewrite the client using REXX sockets? Is there any performance efficiency gained using c/LE compared to REXX. I am not (yet) an experienced z/VM system programmer and I just started reading the LE for z/VM so there is some stuff that I have to figure out even before I start compiling c socket programs. Thank you, Ashwin Bhemidhi Texas Instruments Inc. -- Dave Jones V/Soft www.vsoft-software.com Houston, TX 281.578.7544
Re: Journaling/Incorrect Password Count
On: Tue, Jul 13, 2010 at 07:52:26AM -0700,Schuh, Richard Wrote: } Query and SET commands have not been enabled via the SYSTEM CONFIG file. Well, put them in now (if you didn't already) so when you do an IPL, you will be in better shape. -- Rich Greenberg Sarasota, FL, USA richgr atsign panix.com + 1 941 378 2097 Eastern time. N6LRT I speak for myself my dogs only.VM'er since CP-67 Canines: Val, Red, Shasta, Zero Casey (At the bridge)Owner:Chinook-L Canines: Red Cinnar (Siberians) Retired at the beach Asst Owner:Sibernet-L
Re: Journaling/Incorrect Password Count
Way ahead of you there, but thanks for the thought. :-) Regards, Richard Schuh -Original Message- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Rich Greenberg Sent: Tuesday, July 13, 2010 3:15 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Journaling/Incorrect Password Count On: Tue, Jul 13, 2010 at 07:52:26AM -0700,Schuh, Richard Wrote: } Query and SET commands have not been enabled via the SYSTEM CONFIG file. Well, put them in now (if you didn't already) so when you do an IPL, you will be in better shape. -- Rich Greenberg Sarasota, FL, USA richgr atsign panix.com + 1 941 378 2097 Eastern time. N6LRT I speak for myself my dogs only. VM'er since CP-67 Canines: Val, Red, Shasta, Zero Casey (At the bridge) Owner:Chinook-L Canines: Red Cinnar (Siberians) Retired at the beach Asst Owner:Sibernet-L
