Hi Offer,
All IPtables are off, both for v4 and v6.
Pinging from z/OS to zLinux does not work, nor does traceroute yield anything.
With all this said, I think it has something to do with the way I have routing
set up on the z/OS side. For all OSA traffic, I use OSPF while for
Hipersockets, I
Good morning list,
Does anyone have any quick advice? We are in Minnesota and have just switched
to Daylight Savings.Someone IPL'd ZVM differently yesterday than on past
IPL's. (TOD clock question answered yes). Now we are seeing the correct time
in CMS in zVM (I think) but Linux is
Shouldn't it be CST Now and if Operations adjusted the clock at IPL time then
VM is correct by Operator intervention.
When you installed Linux did you tell it to use GMT and apply its own offset or
use the Local time?
One answer I believe uses the hardware clock and the other uses the VMDBK
ZVM is showing CDT, Linux is showing CST. (so the clock is an hour off)
We use SUSE Linux. Yast2 timezone shows hardware clock set to UTC, and our
timezone as Central Time (Chicago).
It's like Linux isn't correctly recognizing that Daylight Savings began
yesterday. If I change the timezone
What does zdump -v | grep 2013 shows ya? What's the 'timezone' RPM
version (rpm -qa | grep timezone)?
--
Pedro Principeza.
From: Veencamp, Jonathon D. jdveenc...@fedins.com
To: LINUX-390@vm.marist.edu,
Date: 04/11/2013 11:24
Subject:Re: Daylight savings time issue
Sent by:
prd1linux:/etc # zdump -v
prd1linux:/etc # vmcp q time
TIME IS 07:31:48 CDT MONDAY 11/04/13
CONNECT= 18:06:19 VIRTCPU= 295:44.03 TOTCPU= 298:37.72
prd1linux:/etc # rpm -qa | grep time
timezone-2013d-0.5.1
-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On
Shouldn't you have switched to CST instead? We just started standard time,
not daylight savings time..
-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of
Veencamp, Jonathon D.
Sent: Monday, November 04, 2013 8:12 AM
To: LINUX-390@VM.MARIST.EDU
Welcome to WAS, Dorothy.
We have been running WAS since WAS 6 on SLES 8. I cannot give you answers
(then why the heck are you writing??) but I can give several well experienced
situations we have had.
1. Upping the memory solves it, you are correct - the opposite of
everything we have
You are correct.
So my problem statement is that ZVM is showing CDT - and should not. Linux is
showing CST. And even though Linux is set up to use UTC, the time offset is
still off by one hour. I suspect that is due to ZVM showing CDT.
How do I dynamically change zVM? (I'm googling, but you
To dynamically change the time zone, you can issue: CP SET TIMEZONE CST
However, this is not a good practice from VM point of view. Another problem
is that this may not correct the problem on your Linux side because Linux
may ignore this change once it has started.
Also, from the look of your
As I flail around I've correct the zone in ZVM, and now ZVM and ZLINUX
show the same time. That's progress. But because of whatever we did when we
IPL'd ZVM, the ZVM time is still off by an hour. Short of IPLing again, how
can I correct whatever is off in ZVM?
ZVM - before changing
That's what I pointed out in my last reply. You cannot change the time on a
running VM system. Your only option is to re IPL VM.
-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of
Veencamp, Jonathon D.
Sent: Monday, November 04, 2013 8:51 AM
To:
Hello!
Jonathon DST (Daylight Savings Time) ended yesterday at 2AM. And we
all were supposed to set our clocks back an hour over the Saturday
night.
How Linux does keep time has been addressed, but I am more curious as
to why your ZVM is still showing CDT when it also should be showing
CST.
-
We found a typo in our ZVM system config. So VM was still showing CDT rather
than CST, and evidently that affected Linux as well (even though Linux was
pulling the UTC time from hardware?!? )
-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Gregg
Hi
You might be correct and this is a sourcevipa issue but i cant tell as i am
lacking some data...
Not many know this but the order of the home statment matters... you must
place your hiper sockets interface before your vipa interface if you dont
want that vipa to be applied to that interface.
Offer,
I have a test system... let me give it a shot.
Right now, I know for a fact that my HS Home IP address is the last one listed.
Thanks,
David Diep
What would you like to see in the renovated Martin Luther King Jr. Memorial
Library?
Share your thoughts on the library's spaces and
EZZ2350I MVS TCP/IP NETSTAT CS V1R13 TCPIP Name: TCPIP
EZZ2700I Home address list:
EZZ2701I Address Link Flg
EZZ2703I 10.27.42.1 VLNKOS42 P
EZZ2703I 10.82.10.13 LOSA42P0
EZZ2703I 10.82.10.81 LOSA43P0
EZZ2703I 5.5.5.42 HSLINK42
EZZ2703I
What do your systems say is the current UTC? Could somebody have somehow
changed the hardware TOD clock (POR generally) and now _it_ is messed up?
And that would mess up all the guests.
On Mon, Nov 4, 2013 at 10:40 AM, Veencamp, Jonathon D.
jdveenc...@fedins.com wrote:
We found a typo in our
We did POR. But we have a other ZVM's on the same hardware that DO NOT have
the issue (evidently because they didn't have the typo in their system config).
So the other ZVM's display the correct time in VM and zLinux.
The correct time now is 11:24am
Bad-VM:
prd1linux:/ # date -u
Mon Nov 4
You can syntax check your SYSTEM CONFIG file
using the following:
'CPSYNTAX SYSTEM CONFIG F'
Doesn't help now, but may help in the furture.
Billy
On 4 Nov 2013 at 17:26, Veencamp, Jonathon D.
wrote:
We did POR. But we have a other ZVM's on the same hardware that DO
NOT have the issue
Offer,
It does work... why on earth?
I see from a packet trace that anything going to a Hipersockets address
(5.5.5.0) has a source IP address of 5.5.5.x, while anything going out normal
OSAD, leaves with the VIPA address.
What is with the HOME statement? I recall from OS390 TCPIP that the
If you are in U.S. Central time, your UTC is definitely off by one hour.
Which makes all the other systems clocks to be off by 1 hour. We are in
U.S. Central - Dallas, TX. On our z/OS system, the D T command responds
RESPONSE=LIH1 IEE136I LOCAL: TIME=11.44.49 DATE=2013.308 UTC:
The syntax was correct, just not the values: (2012 in the 2nd line)
Timezone_boundary on 2013-03-10 at 02:00:00 to CDT
Timezone_boundary on 2012-11-03 at 02:00:00 to CST
I changed the zone via command on ZVM with the SET TIMEZONE cp command, but
that did not correct the time for zLinux. This
On 11/1/2013 at 03:54 PM, Marcy Cortes marcy.d.cor...@wellsfargo.com
wrote:
This may trigger it on a 1G server
perl -e '$num=50_000_000; @a=(0..$num); foreach $j (0..4) { $a[$_] = $_
foreach (0..$num); $|=1; print Done with pass $j at, `date` ; } print
Done\n'
(thanks to my colleague
First of all i am glad to here it works...
The home statment order only matters with vipa addresses...
The way it works is all addresses after the vipa are sourced by it if the
sourcevipa parameter is specified...
If you want somthing to be excluded from that vipa you must place it before
the
On 11/4/2013 at 12:50 PM, Veencamp, Jonathon D. jdveenc...@fedins.com
wrote:
I changed the zone via command on ZVM with the SET TIMEZONE cp command, but
that did not correct the time for zLinux. This has me somewhat concerned
that the SYSTEM CONFIG change and IPL tonight will not correct
On 11/4/2013 at 08:32 AM, Veencamp, Jonathon D. jdveenc...@fedins.com
wrote:
prd1linux:/etc # zdump -v
This looks like a bug to me. zdump -v should have produced a ton of output.
Please open a service request with your support provider to get that looked at.
Mark Post
Thanks for helping me work through this... There needs to be a new redbook,
titled: The little things that you forget along the way.
Thanks again, Offer.
David Diep
What would you like to see in the renovated Martin Luther King Jr. Memorial
Library?
Share your thoughts on the library's
We've been in the land of WAS since WAS 5!
Everything was just peachy until this kernel.
One server was 1500M with 2 apps each with a heap size of 1024 and a dmgr and a
node agent.
He was even ok until this!I'm surprised it ran at all.(Note, dev/test,
not prod. We wouldn't do that to
On Mon, Nov 4, 2013 at 1:44 PM, Marcy Cortes
marcy.d.cor...@wellsfargo.com wrote:
We've been in the land of WAS since WAS 5!
Everything was just peachy until this kernel.
One server was 1500M with 2 apps each with a heap size of 1024 and a dmgr and
a node agent.
He was even ok until this!
Unrelated to your issue:
We got going with Websphere 3.5! (And IBM Servlet Express before that). I also
remember having the ZOS HTTP server running at least a year before any of the
Wintel guys here had their first HTTP server running. At the time with all the
literature in the press about
On Monday, 11/04/2013 at 09:00 EST, Aria Bamdad a...@bsc.gwu.edu wrote:
That's what I pointed out in my last reply. You cannot change the time
on a
running VM system. Your only option is to re IPL VM.
When you change the time at IPL, you actually change the TOD clock in the
LPAR. CP uses the
On Monday, 11/04/2013 at 03:59 EST, Billy R. Bingham
brbing...@stx.rr.com wrote:
You can syntax check your SYSTEM CONFIG file
using the following:
'CPSYNTAX SYSTEM CONFIG F'
Doesn't help now, but may help in the furture.
Alas, that won't help you if you put a valid, but wrong, value in
I think Websphere is a bit of a red herring. The trigger is probably any
process that asks for a lot more memory than the system has, for some value of
a lot.
The size of the array in the Perl script depends on how much memory your system
has. Fifty million works well with the 1 GB test
34 matches
Mail list logo
