CPU Capability values

[Quay, Jonathan (IHG)]

We had a situation the other day where one of our z10's was taking
"thermals" for lack of a better word.  The kernel dutifully reported:

 

Feb 11 15:08:29 zsles10sp3ctl kernel: sclp_config: cpu capability
changed. 

 

sclp_config: cpu capability changed. 

 

The CE replaced the MRU on the box and all is well.  But this led us too
look a little bit closer.  On the lpar in question (an IFL lpar on a
502):   

 

Ready; T=0.01/0.01 14:02:56

q cap  

14:03:08 CAPABILITY: PRIMARY 1760 SECONDARY 904

 

And 

 

zsles10sp3ctl:/sys/devices/system/cpu/cpu0 # cat capability

1760

 

It looks like the kernel uses the wrong value.  IBM says that the
"secondary" number is the IFL capability (lower is faster). 


--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Re: Location of network configuration

[Dean, David (I/S)]

Correct.  Ifup command will not make it permanent.  There is a pretty good step 
through in here starting at page 97.  This is for HiperSockets but it works the 
same.

www.redbooks.ibm.com/redbooks/pdfs/sg246816.pdf




-Original Message-
From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Rob van 
der Heij
Sent: Monday, February 15, 2010 6:30 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Location of network configuration

2010/2/15 van Sleeuwen, Berry :

> The test machine can't start the connection for TSM backup. ifconfig
> shows only eth0. The f10 device is indeed available but for some reason
> it isn't started. I have compared the two guests but can't find a
> difference that could tell me why this networkinterface isn't started.

Does "ifup" start the device afterwards?

I recall with SLES10 an interface that worked upon "ifup" but did not
start by itself. I wasted quite some time without spotting the missing
MODULE="qeth" in the hwcfg-qeth-bus-ccw* file.

Rob

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

-
Please see the following link for the BlueCross BlueShield of Tennessee E-mail 
disclaimer:  http://www.bcbst.com/email_disclaimer.shtm

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Re: Location of network configuration

[van Sleeuwen, Berry]

I can't access bugzilla so I can't look into the details.

Anyway. Since a race could be a problem here I have rebooted the guest.
And indeed now the eth1 is available. And since it is available the
network is started. In the near future we have to restart guests quite a
bit so I'll have to check this more often. Let's just hope this was just
this one time.

Thank you all for responding.

Regards, Berry.

-Original Message-
From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of
Ursula Braun
Sent: maandag 15 februari 2010 13:10
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Location of network configuration

Berry,

there is a known problem (race in udev) in activation of network
interfaces. Details can be found in Novell-bugzilla number 506571.

Regards, Ursula Braun, IBM Germany, Linux on System z development

On Mon, 2010-02-15 at 11:55 +0100, van Sleeuwen, Berry wrote:
> Hello listers,
>
> We have two SLES10 guests running SAMBA. The two machines should be 
> identical, and in VM they are.
>
> The production machine has two network interfaces defined, F00 and
F10.
> The first is the network for regular connections, the second is the 
> connection to our TSM backup server.
>
> The test machine can't start the connection for TSM backup. ifconfig 
> shows only eth0. The f10 device is indeed available but for some 
> reason it isn't started. I have compared the two guests but can't find

> a difference that could tell me why this networkinterface isn't
started.
>
> The nic f10 is defined and coupled to the vswitch.
> The /etc/sysconfig/hardware contains identical entries.
> The /etc/sysconfig/network contains configuration for both f00 (eth0) 
> and f10 (eth1). Other than the IP address these members are identical 
> too.
>
> rcnetwork restart only starts lo and eth0. ifup eth1 shows interface
> eth1 is not available.
>
> How to get eth1 available? Is there any other location that defines a 
> NIC that I can check?
>
>
> Met vriendelijke groet/With kind regards, Berry van Sleeuwen Flight 
> Forum 3000 5657 EW Eindhoven
>
> ( +31 (0)6 22564276
>
>
>
>
>
> Atos Origin 
>
> MO CF SC Mainframe Services
>
>
>
>
>
> --
> For LINUX-390 subscribe / signoff / archive access instructions, send 
> email to lists...@vm.marist.edu with the message: INFO LINUX-390 or 
> visit http://www.marist.edu/htbin/wlvindex?LINUX-390

--
For LINUX-390 subscribe / signoff / archive access instructions, send
email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
visit http://www.marist.edu/htbin/wlvindex?LINUX-390


--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
ÿþDit bericht is vertrouwelijk en kan 
geheime informatie bevatten enkel

bestemd voor de geadresseerde. Indien 
dit bericht niet voor u is bestemd,

verzoeken wij u dit onmiddellijk aan 
ons te melden en het bericht te

vernietigen.

Aangezien de integriteit van het 
bericht niet veilig gesteld is middels

verzending via internet, kan Atos 
Origin niet aansprakelijk worden 
gehouden

voor de inhoud daarvan.

Hoewel wij ons inspannen een virusvrij 
netwerk te hanteren, geven

wij geen enkele garantie dat dit 
bericht virusvrij is, noch aanvaarden 
wij

enige aansprakelijkheid voor de 
mogelijke aanwezigheid van een virus in 
dit

bericht.

 

Op al onze rechtsverhoudingen, 
aanbiedingen en overeenkomsten 
waaronder

Atos Origin goederen en/of diensten 
levert zijn met uitsluiting van alle

andere voorwaarden de 
Leveringsvoorwaarden van Atos Origin 
van toepassing.

Deze worden u op aanvraag direct 
kosteloos toegezonden.

 

This e-mail and the documents attached 
are confidential and intended solel

Re: Location of network configuration

[Ursula Braun]

Berry,

there is a known problem (race in udev) in activation of network
interfaces. Details can be found in Novell-bugzilla number 506571.

Regards, Ursula Braun, IBM Germany, Linux on System z development

On Mon, 2010-02-15 at 11:55 +0100, van Sleeuwen, Berry wrote:
> Hello listers,
>
> We have two SLES10 guests running SAMBA. The two machines should be
> identical, and in VM they are.
>
> The production machine has two network interfaces defined, F00 and F10.
> The first is the network for regular connections, the second is the
> connection to our TSM backup server.
>
> The test machine can't start the connection for TSM backup. ifconfig
> shows only eth0. The f10 device is indeed available but for some reason
> it isn't started. I have compared the two guests but can't find a
> difference that could tell me why this networkinterface isn't started.
>
> The nic f10 is defined and coupled to the vswitch.
> The /etc/sysconfig/hardware contains identical entries.
> The /etc/sysconfig/network contains configuration for both f00 (eth0)
> and f10 (eth1). Other than the IP address these members are identical
> too.
>
> rcnetwork restart only starts lo and eth0. ifup eth1 shows interface
> eth1 is not available.
>
> How to get eth1 available? Is there any other location that defines a
> NIC that I can check?
>
>
> Met vriendelijke groet/With kind regards,
> Berry van Sleeuwen
> Flight Forum 3000 5657 EW Eindhoven
>
> ( +31 (0)6 22564276
>
>
>
>
>
> Atos Origin 
>
> MO CF SC Mainframe Services
>
>
>
>
>
> --
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
> http://www.marist.edu/htbin/wlvindex?LINUX-390

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Re: Location of network configuration

[van Sleeuwen, Berry]

Sorry, I mean the directories on the two servers are identical.
Obviously, the configuration for device f00 is not the same as for f10.
But the f00 for the production samba is the same as the f00 for the test
server. And the same goes for the f10 configuration. Well, that is, the
IP address is different.

-Original Message-
From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of
Michael MacIsaac
Sent: maandag 15 februari 2010 12:51
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Location of network configuration

Barry,

> The /etc/sysconfig/hardware contains identical entries.
Are they really identical?

I have a system with two interfaces connected to NICs at 600 and 700.
The /etc/sysconfig/hardware configuration files are different:
# cat /etc/*release
SUSE Linux Enterprise Server 10 (s390x)
VERSION = 10
PATCHLEVEL = 3
# cd /etc/sysconfig/hardware
# diff *600 *700
9c9
< CCW_CHAN_IDS="0.0.0600 0.0.0601 0.0.0602"
---
> CCW_CHAN_IDS="0.0.0700 0.0.0701 0.0.0702"

Also, for reference, here are the ifcfg-* files:
# cd ../network
# diff *600 *700
4,8c4,8
< IPADDR="9.60.18.241"
< NETMASK="255.255.255.128"
< NETWORK="9.60.18.128"
< BROADCAST="9.60.18.255"
< _nm_name='qeth-bus-ccw-0.0.0600'
---
> IPADDR="10.1.150.241"
> NETMASK="255.255.0.0"
> NETWORK="10.1.0.0"
> BROADCAST="10.1.255.255"
> _nm_name='qeth-bus-ccw-0.0.0700'

Hope this helps.

"Mike MacIsaac"(845) 433-7061

--
For LINUX-390 subscribe / signoff / archive access instructions, send
email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
visit http://www.marist.edu/htbin/wlvindex?LINUX-390


--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
ÿþDit bericht is vertrouwelijk en kan 
geheime informatie bevatten enkel

bestemd voor de geadresseerde. Indien 
dit bericht niet voor u is bestemd,

verzoeken wij u dit onmiddellijk aan 
ons te melden en het bericht te

vernietigen.

Aangezien de integriteit van het 
bericht niet veilig gesteld is middels

verzending via internet, kan Atos 
Origin niet aansprakelijk worden 
gehouden

voor de inhoud daarvan.

Hoewel wij ons inspannen een virusvrij 
netwerk te hanteren, geven

wij geen enkele garantie dat dit 
bericht virusvrij is, noch aanvaarden 
wij

enige aansprakelijkheid voor de 
mogelijke aanwezigheid van een virus in 
dit

bericht.

 

Op al onze rechtsverhoudingen, 
aanbiedingen en overeenkomsten 
waaronder

Atos Origin goederen en/of diensten 
levert zijn met uitsluiting van alle

andere voorwaarden de 
Leveringsvoorwaarden van Atos Origin 
van toepassing.

Deze worden u op aanvraag direct 
kosteloos toegezonden.

 

This e-mail and the documents attached 
are confidential and intended solely

for the addressee; it may also be 
privileged. If you receive this e-mail

in error, please notify the sender 
immediately and destroy it.

As its integrity cannot be secured on 
the Internet, the Atos Origin group

liability cannot be triggered for the 
message content. Although the

sender endeavours to maintain a 
computer virus-free network, the sender

does not warrant that this transmission 
is virus-free and will not be

liable for any damages resulting from 
any virus transmitted.

 

On all offers and agreements un

Re: Location of network configuration

[van Sleeuwen, Berry]

No, ifup doesn't start it. It should be on eth1 but eth1 is not
available.

The module parameter was missing at first, so I added the MODULE='qeth'
but is made no difference.

I have tried /etc/sysconfig/network/ifcfg-qeth-bus-ccw-0.0.0f10 with
ETHERDEVICE='eth1' and, as listed in the production server, with
_nm_name='qeth-bus-ccw-0.0.0f10'. But in both cases the network isn't
started.
 

-Original Message-
From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of
Rob van der Heij
Sent: maandag 15 februari 2010 12:30
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Location of network configuration

2010/2/15 van Sleeuwen, Berry :

> The test machine can't start the connection for TSM backup. ifconfig 
> shows only eth0. The f10 device is indeed available but for some 
> reason it isn't started. I have compared the two guests but can't find

> a difference that could tell me why this networkinterface isn't
started.

Does "ifup" start the device afterwards?

I recall with SLES10 an interface that worked upon "ifup" but did not
start by itself. I wasted quite some time without spotting the missing
MODULE="qeth" in the hwcfg-qeth-bus-ccw* file.

Rob

--
For LINUX-390 subscribe / signoff / archive access instructions, send
email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
visit http://www.marist.edu/htbin/wlvindex?LINUX-390


--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
ÿþDit bericht is vertrouwelijk en kan 
geheime informatie bevatten enkel

bestemd voor de geadresseerde. Indien 
dit bericht niet voor u is bestemd,

verzoeken wij u dit onmiddellijk aan 
ons te melden en het bericht te

vernietigen.

Aangezien de integriteit van het 
bericht niet veilig gesteld is middels

verzending via internet, kan Atos 
Origin niet aansprakelijk worden 
gehouden

voor de inhoud daarvan.

Hoewel wij ons inspannen een virusvrij 
netwerk te hanteren, geven

wij geen enkele garantie dat dit 
bericht virusvrij is, noch aanvaarden 
wij

enige aansprakelijkheid voor de 
mogelijke aanwezigheid van een virus in 
dit

bericht.

 

Op al onze rechtsverhoudingen, 
aanbiedingen en overeenkomsten 
waaronder

Atos Origin goederen en/of diensten 
levert zijn met uitsluiting van alle

andere voorwaarden de 
Leveringsvoorwaarden van Atos Origin 
van toepassing.

Deze worden u op aanvraag direct 
kosteloos toegezonden.

 

This e-mail and the documents attached 
are confidential and intended solely

for the addressee; it may also be 
privileged. If you receive this e-mail

in error, please notify the sender 
immediately and destroy it.

As its integrity cannot be secured on 
the Internet, the Atos Origin group

liability cannot be triggered for the 
message content. Although the

sender endeavours to maintain a 
computer virus-free network, the sender

does not warrant that this transmission 
is virus-free and will not be

liable for any damages resulting from 
any virus transmitted.

 

On all offers and agreements under 
which Atos Origin supplies goods and/or

services of whatever nature, the Terms 
of Delivery from Atos Origin

Re: Location of network configuration

[Michael MacIsaac]

Barry,

> The /etc/sysconfig/hardware contains identical entries.
Are they really identical?

I have a system with two interfaces connected to NICs at 600 and 700. The
/etc/sysconfig/hardware configuration files are different:
# cat /etc/*release
SUSE Linux Enterprise Server 10 (s390x)
VERSION = 10
PATCHLEVEL = 3
# cd /etc/sysconfig/hardware
# diff *600 *700
9c9
< CCW_CHAN_IDS="0.0.0600 0.0.0601 0.0.0602"
---
> CCW_CHAN_IDS="0.0.0700 0.0.0701 0.0.0702"

Also, for reference, here are the ifcfg-* files:
# cd ../network
# diff *600 *700
4,8c4,8
< IPADDR="9.60.18.241"
< NETMASK="255.255.255.128"
< NETWORK="9.60.18.128"
< BROADCAST="9.60.18.255"
< _nm_name='qeth-bus-ccw-0.0.0600'
---
> IPADDR="10.1.150.241"
> NETMASK="255.255.0.0"
> NETWORK="10.1.0.0"
> BROADCAST="10.1.255.255"
> _nm_name='qeth-bus-ccw-0.0.0700'

Hope this helps.

"Mike MacIsaac"(845) 433-7061

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Re: Location of network configuration

[van Sleeuwen, Berry]

Only one nic, eth0. No information on eth1. The production server shows
both eth0 and eth1. 

-Original Message-
From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of
Harder, Pieter
Sent: maandag 15 februari 2010 12:04
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Location of network configuration

Seems some operational hiccup if you got the configs right. What does
lsqeth tell you about the state of the nics?

Best regards,
Pieter Harder


Van: Linux on 390 Port [linux-...@vm.marist.edu] namens van Sleeuwen,
Berry [berry.vansleeu...@atosorigin.com]
Verzonden: maandag 15 februari 2010 11:55
Aan: LINUX-390@VM.MARIST.EDU
Onderwerp: Location of network configuration

Hello listers,

We have two SLES10 guests running SAMBA. The two machines should be
identical, and in VM they are.

The production machine has two network interfaces defined, F00 and F10.
The first is the network for regular connections, the second is the
connection to our TSM backup server.

The test machine can't start the connection for TSM backup. ifconfig
shows only eth0. The f10 device is indeed available but for some reason
it isn't started. I have compared the two guests but can't find a
difference that could tell me why this networkinterface isn't started.

The nic f10 is defined and coupled to the vswitch.
The /etc/sysconfig/hardware contains identical entries.
The /etc/sysconfig/network contains configuration for both f00 (eth0)
and f10 (eth1). Other than the IP address these members are identical
too.

rcnetwork restart only starts lo and eth0. ifup eth1 shows interface
eth1 is not available.

How to get eth1 available? Is there any other location that defines a
NIC that I can check?


Met vriendelijke groet/With kind regards, Berry van Sleeuwen Flight
Forum 3000 5657 EW Eindhoven

( +31 (0)6 22564276





Atos Origin 

MO CF SC Mainframe Services





--
For LINUX-390 subscribe / signoff / archive access instructions, send
email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
visit http://www.marist.edu/htbin/wlvindex?LINUX-390

Brabant Water N.V.
Postbus 1068
5200 BC  's-Hertogenbosch
http://www.brabantwater.nl
Handelsregister: 16005077

--
For LINUX-390 subscribe / signoff / archive access instructions, send
email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
visit http://www.marist.edu/htbin/wlvindex?LINUX-390


--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
ÿþDit bericht is vertrouwelijk en kan 
geheime informatie bevatten enkel

bestemd voor de geadresseerde. Indien 
dit bericht niet voor u is bestemd,

verzoeken wij u dit onmiddellijk aan 
ons te melden en het bericht te

vernietigen.

Aangezien de integriteit van het 
bericht niet veilig gesteld is middels

verzending via internet, kan Atos 
Origin niet aansprakelijk worden 
gehouden

voor de inhoud daarvan.

Hoewel wij ons inspannen een virusvrij 
netwerk te hanteren, geven

wij geen enkele garantie dat dit 
bericht virusvrij is, noch aanvaarden 
wij

enige aansprakelijkheid voor de 
mogelijke aanwezigheid van een virus in 
dit

bericht.

 

Op al onze rechtsverhoudingen, 
aanbiedingen en overeenkomsten 
waaronder

Atos Origin goederen en/of diensten 
levert zijn met uitsluiting van alle

andere voorwaarden de 
Leveringsvoorwaarden van Atos Origin 
van toepassing.

Deze worden u op aanvraag direct 
kosteloos toegezonden.

 

This e-mail and the documents attached 
are confidential and intended solely

for the addressee; it may also be 
privileged. If you receive this e-m

Re: Location of network configuration

[Rob van der Heij]

2010/2/15 van Sleeuwen, Berry :

> The test machine can't start the connection for TSM backup. ifconfig
> shows only eth0. The f10 device is indeed available but for some reason
> it isn't started. I have compared the two guests but can't find a
> difference that could tell me why this networkinterface isn't started.

Does "ifup" start the device afterwards?

I recall with SLES10 an interface that worked upon "ifup" but did not
start by itself. I wasted quite some time without spotting the missing
MODULE="qeth" in the hwcfg-qeth-bus-ccw* file.

Rob

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Re: Location of network configuration

[Harder, Pieter]

Seems some operational hiccup if you got the configs right. What does lsqeth 
tell you about the state of the nics?

Best regards,
Pieter Harder


Van: Linux on 390 Port [linux-...@vm.marist.edu] namens van Sleeuwen, Berry 
[berry.vansleeu...@atosorigin.com]
Verzonden: maandag 15 februari 2010 11:55
Aan: LINUX-390@VM.MARIST.EDU
Onderwerp: Location of network configuration

Hello listers,

We have two SLES10 guests running SAMBA. The two machines should be
identical, and in VM they are.

The production machine has two network interfaces defined, F00 and F10.
The first is the network for regular connections, the second is the
connection to our TSM backup server.

The test machine can't start the connection for TSM backup. ifconfig
shows only eth0. The f10 device is indeed available but for some reason
it isn't started. I have compared the two guests but can't find a
difference that could tell me why this networkinterface isn't started.

The nic f10 is defined and coupled to the vswitch.
The /etc/sysconfig/hardware contains identical entries.
The /etc/sysconfig/network contains configuration for both f00 (eth0)
and f10 (eth1). Other than the IP address these members are identical
too.

rcnetwork restart only starts lo and eth0. ifup eth1 shows interface
eth1 is not available.

How to get eth1 available? Is there any other location that defines a
NIC that I can check?


Met vriendelijke groet/With kind regards,
Berry van Sleeuwen
Flight Forum 3000 5657 EW Eindhoven

( +31 (0)6 22564276





Atos Origin 

MO CF SC Mainframe Services





--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Brabant Water N.V.
Postbus 1068
5200 BC  's-Hertogenbosch
http://www.brabantwater.nl
Handelsregister: 16005077

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Location of network configuration

[van Sleeuwen, Berry]

Hello listers,
 
We have two SLES10 guests running SAMBA. The two machines should be
identical, and in VM they are.
 
The production machine has two network interfaces defined, F00 and F10.
The first is the network for regular connections, the second is the
connection to our TSM backup server.
 
The test machine can't start the connection for TSM backup. ifconfig
shows only eth0. The f10 device is indeed available but for some reason
it isn't started. I have compared the two guests but can't find a
difference that could tell me why this networkinterface isn't started.
 
The nic f10 is defined and coupled to the vswitch.
The /etc/sysconfig/hardware contains identical entries.
The /etc/sysconfig/network contains configuration for both f00 (eth0)
and f10 (eth1). Other than the IP address these members are identical
too.
 
rcnetwork restart only starts lo and eth0. ifup eth1 shows interface
eth1 is not available.
 
How to get eth1 available? Is there any other location that defines a
NIC that I can check?
 

Met vriendelijke groet/With kind regards, 
Berry van Sleeuwen 
Flight Forum 3000 5657 EW Eindhoven

( +31 (0)6 22564276





Atos Origin  

MO CF SC Mainframe Services

 

 

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
<><>ÿþDit bericht is vertrouwelijk en kan 
geheime informatie bevatten enkel

bestemd voor de geadresseerde. Indien 
dit bericht niet voor u is bestemd,

verzoeken wij u dit onmiddellijk aan 
ons te melden en het bericht te

vernietigen.

Aangezien de integriteit van het 
bericht niet veilig gesteld is middels

verzending via internet, kan Atos 
Origin niet aansprakelijk worden 
gehouden

voor de inhoud daarvan.

Hoewel wij ons inspannen een virusvrij 
netwerk te hanteren, geven

wij geen enkele garantie dat dit 
bericht virusvrij is, noch aanvaarden 
wij

enige aansprakelijkheid voor de 
mogelijke aanwezigheid van een virus in 
dit

bericht.

 

Op al onze rechtsverhoudingen, 
aanbiedingen en overeenkomsten 
waaronder

Atos Origin goederen en/of diensten 
levert zijn met uitsluiting van alle

andere voorwaarden de 
Leveringsvoorwaarden van Atos Origin 
van toepassing.

Deze worden u op aanvraag direct 
kosteloos toegezonden.

 

This e-mail and the documents attached 
are confidential and intended solely

for the addressee; it may also be 
privileged. If you receive this e-mail

in error, please notify the sender 
immediately and destroy it.

As its integrity cannot be secured on 
the Internet, the Atos Origin group

liability cannot be triggered for the 
message content. Although the

sender endeavours to maintain a 
computer virus-free network, the sender

does not warrant that this transmission 
is virus-free and will not be

liable for any damages resulting from 
any virus transmitted.

 

On all offers and agreements under 
which Atos Origin supplies goods and/or

services of whatever nature, the Terms 
of Delivery from Atos Origin

exclusively apply. 

The Terms of Delivery shall be promptly 
submitted to you on your request.