Having spent several days going through the problems of others, I am still
unable to get TT32test to work on windows XP.
I have WINPCAP 4.0.2 installed and when I run TT32TEST I get
00:20:02.234 ** CFishPackApp::FishPackGetWinPCapInfo: ReadFile() failed; rc=23
(0x00000017):
00:20:02.234 Begin TT32Test.exe, version: "3.2.1.160" (3.2.1.160): "Release
version" ...
00:20:02.234 Copyright (C) 2002-2007, Software Development Laboratories (aka
'Fish' (David B. Trout)).
00:20:02.234
00:20:02.234 Running on Windows XP (MP=2), version 5.1.2600 Service Pack 3

00:20:02.234 ERROR:                                       **
00:20:02.234 ERROR:  **   CTCI-W32 was unable to load the WinPCap 'packet.dll'  
**
00:20:02.234 ERROR:  **   support module indicating that WinPCap is either not  
**
00:20:02.234 ERROR:  **   installed at all or improperly installed. CTCI-W32    
**
00:20:02.234 ERROR:  **   is unable to function without a proper installation   
**
00:20:02.234 ERROR:  **   of WinPCap.                                           
**
00:20:02.234 ERROR:  **                                                         
**
00:20:02.234 ERROR:  **   Please either install WinPCap first before continuing 
**
00:20:02.234 ERROR:  **   or uninstall and then reinstall it again if you have  
**
00:20:02.234 ERROR:  **   reason to suspect it might not be properly installed. 
**
00:20:02.234 ERROR:  **                                                         
**
00:20:02.234 ERROR: 
**************************************************************
00:20:02.234
00:20:02.234 Using FishPack.dll, version: "3.2.1.160" (3.2.1.160): "Release
version" ...
00:20:02.234 Copyright (C) 2002-2007, Software Development Laboratories (aka
'Fish' (David B. Trout)).
00:20:02.234
00:20:02.234 Using TunTap32.dll, version: "3.2.1.160" (3.2.1.160): "Release
version" ...
00:20:02.234 Copyright (C) 2002-2007, Software Development Laboratories (aka
'Fish' (David B. Trout)).

MS32INFO shows NPF started. All the CTCI-W32 bits are in windows/system32
Is there still a problem with ZoneAlarm as I have that installed although I have
tried stopping it but that makes no difference.
Any suggestions would be greatfully received.
Cheers
Ian

Help:

I have tried now several times to install Debian Linux/390 on Hercules
and keep coming up with a problem during the Linux/390 install phase.

Where I am expecting Linux/390 to find and load partitions on my 120 and
121 drives, the procedure does not find any partitions to load.

To see if I actually have 120 and 121 drives, I issue devlist under
Hercules and sure enough, they are where the config file says they are.

It was suggested that I run dmesg from the shell on the install console
for Linux/390 and I have done so, but I don't see any reference to any
DASD and in particular nothing about either 120 or 121.

Is there any specific information I would expect from dmesg that would
confirm their existence? Or is there any other command that I could use
from the console to verify they are or are not there?

Or, is there any other command(s) I can issue to allocate these files,
which I created as 3390-3 disks using Hercules' dasdinit?

Any suggestions? Anyone out there successfully install Debian Linux/390
on Hercules that can provide some advice?

Mike Myers

Mainframers are not a dying breed.  In fact, we are proud of our heritage,
and like to share our experiences with others.  If you have stories to
share,
problems to solve, answers to offer, or just need a place to hang with other
folks with similar history;  join us at www.t-rexxers.com.  You can also
find a
good article in the recent "IBM Systems Magazine" promoting the website.
This forum is open to all with interest in mainframes.  There are no
requirements,
to join, just be ready to share your ideas, thoughts, and stories.  Or just
enjoy
reading about folks with similar backgrounds and interest.

Here is the link
http://www.ibmsystemsmagmainframedigital.com/nxtbooks/ibmsystemsmag/mainfram
e_20091112/#/44
<http://www.ibmsystemsmagmainframedigital.com/nxtbooks/ibmsystemsmag/mainfra
me_20091112/%23/44>


zNorman@...


[Non-text portions of this message have been removed]

Whoops small typo in the begion route section

should be 10.1.11.1   which I believe is the gatway on your lan or your internet
router

--- In hercules-390@yahoogroups.com, "Rocky" <rocsystems@...> wrote:
>
>
>
>
>
>
>
>
> BEGINROUTES
>
> ROUTE 10.1.11 255.255.255.0 = ETH1 MTU 1492 (that's your local lan)
>
> ROUTE DEFAULT 10.1.11.11 ETH1 MTU 1492  (that's your gateway to theworld)
>
>
> ENDROUTES
>
>
>
>

Suggest you get the Mainframe parameters correct first - since you can ping,

Only after that and it still doesn't work you can move on to the LCS.



But for starters - remove the extra device in the configuration,







PROFILE.tcpip

---------------



IN ZOS you don't put the telnet parms is the TCPIP profile but in the
TN3270 Profile. You should be getting a message about that.



Remove the section telnet parms.

Remove the gateway parms and the default net parms and use the following:



BEGINROUTES

ROUTE 10.1.11 255.255.255.0 = ETH1 MTU 1492 (that's your local lan)

ROUTE DEFAULT 10.1.11.11 ETH1 MTU 1492  (that's your gateway to theworld)


ENDROUTES



In the reserved ports section you are reserving port 23 for a server called
TN3270



Is the job are you starting TN3270 or TN3270A?

Name and port  that you reserve must match the job you submit



So check the startup to see that you are starting the proper procedure







In the TN3270 Configuration you have some errors.

Not sure how critical that is But I modifies yours parameter file and it now
looks like this.

try it.



TelnetGlobals

   INACTIVE 28800

   SMFINIT STD

   SMFTERM STD

   TIMEMARK 14400       ; NO IP ACTIVITY FOR 4 HOURS, SEND TIMEMAR

   LUSESSIONPEND

   ScanInterval 3600    ; Check for IP activity every 1 hour

   MAXRECEIVE  65535

   MAXVTAMSENDQ 50

   TCPIPJOBNAME TCPIP

   ; ----------------------------------------


   TELNETDEVICE 3278-2-E NSX32702 ; 24 line screen -

   TELNETDEVICE 3279-2-E NSX32702 ; 24 line screen -

   TELNETDEVICE 3278-3-E NSX32703 ; 32 line screen -

   TELNETDEVICE 3279-3-E NSX32703 ; 32 line screen -

   TELNETDEVICE 3278-4-E NSX32704 ; 48 line screen -

   TELNETDEVICE 3279-4-E NSX32704 ; 48 line screen -

   TELNETDEVICE 3278-5-E NSX32705 ; 132 column screen-

   TELNETDEVICE 3279-5-E NSX32705 ; 132 column screen -



EndTelnetGlobals



***** pay attention to the WLM parameter --- same name as the reserved in
the port



; ---------------------------------------------------------------------

; Required Port Configuration affects the specified port

; ---------------------------------------------------------------------



TelnetParms            ; Standard TN3270 Telnet server port

   Port 23

     WLMClusterName     ; Define WLM name for this port

       TN3270           ;         Must have JOBNAME coded to use WLM

     EndWLMClusterName

EndTelnetParms



BeginVTAM              ; Mapping for basic and TTLS ports.

  Port 23;

  DEFAULTLUS           ; Define LUs to be used for general users.

    SC0TCP01..SC0TCP30

  ENDDEFAULTLUS

  LUGROUP EVERYONE

     SC0TCP01..SC0TCP30

  ENDLUGROUP

  LINEMODEAPPL TSO     ; Send all line-mode terminals directly to TSO.

  ALLOWAPPL TSO* DISCONNECTABLE

                       ; Allow all users access to TSO applications.

                       ; TSO uses unique applications for each session

                       ; which all begin with TSO.  Use TSO* to cover

                       ; all TSO sessions.

                       ; If a session is closed, disconnect the user

                       ; rather than log off the user.

  ALLOWAPPL *          ; Allow access to all applications.

  USSTCP USSN          ; Send out the default TN USS table

  LUMAP EVERYONE KEEPOPEN



  EndVTAM





Rocky













   _____

From: hercules-390@yahoogroups.com [mailto:hercules-390@yahoogroups.com] On
Behalf Of jsganino
Sent: Thursday, November 12, 2009 18:19
To: hercules-390@yahoogroups.com
Subject: [hercules-390] Re: Using LCS interface and getting TCP error 10061





Tom,

Hmmm... SLES has both devices, eth0 and eth1, defined to it at 10.1.11.21
and 10.11.1.24, respectively, and your MVS has 10.1.11.24 defined to it,
too? My first guess is that you need to enable proxy_arp and give your MVS a
different IP address. There may be a way to dedicate one of the NIC's to
Hercules, but I have to toss that one out to the group. But, if SLES is
reporting both NICs and is reporting an IP address for each, that pretty
much has to mean that SLES has both and Hercules has none.

Your zip file didn't make it (Fish explained why in an earlier post), so I'm
working blind here, but I will hazard the following offering:

1) Change the IP address on the TCPIP under MVS to something new, like
10.1.11.25.

2) Verify you can still ping and X3270 to MVS at the new address

3) Enable proxy_arp on one (or both) NIC's:
sysctl -w net.ipv4.conf.eth0.proxy_arp=1
sysctl -w net.ipv4.conf.eth1.proxy_arp=1

4) Then try VISTA from across the wire to MVS.

Good Luck,

Jim

--- In hercules-390@ <mailto:hercules-390%40yahoogroups.com>
yahoogroups.com, Thomas Dunlap <thomas.dunlap@...> wrote:
>
> Jim,
>
> I have attached a "zip" file with 5 TXT files that contains the
> information on my configuration.
>
> The SLES configuration is as follows"
> eth0 Firewall disabled MTU 1500 10.1.11.21 mask of 255.255.255.0
> eth1 Firewall disabled MTU 1500 10.1.11.24 mask of 255.255.255.0
>
> I can both PING and TRACERT to the two addresses listed above.
>
> I am able to logon to MVS from an X3270 session running under SLES.
> There were no errors when I start TCPIP or TN3270 address spaces under
> MVS. It seems to be related to trying to connect through either NIC
> adapter. I even tried FTP and received an error that the connection was
> rejected by remote host.
>
> Cheers,
> Tom
>





[Non-text portions of this message have been removed]

Tom,

    Hmmm...  SLES has both devices, eth0 and eth1, defined to it at 10.1.11.21
and 10.11.1.24, respectively, and your MVS has 10.1.11.24 defined to it, too?  
My first guess is that you need to enable proxy_arp and give your MVS a
different IP address.  There may be a way to dedicate one of the NIC's to
Hercules, but I have to toss that one out to the group.  But, if SLES is
reporting both NICs and is reporting an IP address for each, that pretty much
has to mean that SLES has both and Hercules has none.

    Your zip file didn't make it (Fish explained why in an earlier post), so I'm
working blind here, but I will hazard the following offering:

1) Change the IP address on the TCPIP under MVS to something new, like
10.1.11.25.

2) Verify you can still ping and X3270 to MVS at the new address

3) Enable proxy_arp on one (or both) NIC's:
sysctl -w net.ipv4.conf.eth0.proxy_arp=1
sysctl -w net.ipv4.conf.eth1.proxy_arp=1

4) Then try VISTA from across the wire to MVS.

Good Luck,

Jim

--- In hercules-390@yahoogroups.com, Thomas Dunlap <thomas.dunlap@...> wrote:
>
> Jim,
>
> I have attached a "zip" file with 5 TXT files that contains the
> information on my configuration.
>
> The SLES configuration is as follows"
> eth0 Firewall disabled MTU 1500 10.1.11.21 mask of 255.255.255.0
> eth1 Firewall disabled MTU 1500 10.1.11.24 mask of 255.255.255.0
>
> I can both PING and TRACERT to the two addresses listed above.
>
> I am able to logon to MVS from an X3270 session running under SLES.
> There were no errors when I start TCPIP or TN3270 address spaces under
> MVS. It seems to be related to trying to connect through either NIC
> adapter. I even tried FTP and received an error that the connection was
> rejected by remote host.
>
> Cheers,
> Tom
>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Nigel DeFreitas wrote:

> I'm using a Aluminium Macbook/64 bit with Leopard
> (OS X 10.6.1). I installed the Leopard download of
> Hercules from here:
> http://www.hercules-390.org/hercules-3.06-leopard.dmg


[...]
> cckd invalid keyword: cache
> HHCCF090I Default Allowed AUTOMOUNT directory =
> "/Users/nigeldefreitas/tapes/"
> HHCCF091S Invalid AUTOMOUNT directory: "/tapes": No such file or directory
  [...]

<snip>

> ####################################################################
> # HERCULES EMULATOR CONTROL FILE #
> # (Note: not all parameters are shown) #
> ####################################################################

[...]

> CCKD cache=8

[...]

> DEFSYM TAPEDIR "$(HOME)/tapes"
> AUTOMOUNT $(TAPEDIR)
> AUTOMOUNT +/tapes
> AUTOMOUNT -/tapes/vault
<snip>


> Any ideas what I'm doing incorrectly here?

Yes:


First (non-fatal) problem: "cckd invalid keyword: cache":

It appears you are using our "sample" configuration file which unfortunately
contains an error. We apologize for that. Just like the error message says,
"cache" is indeed an invalid keyword.

The error has already been corrected in current SVN and will formally appear
in the next release (hopefully).


Second (fatal) problem: "HHCCF091S Invalid AUTOMOUNT directory: "/tapes":

The directory specified in the SAMPLE configuration file you are using was
"/tapes" (i.e. the "AUTOMOUNT +/tapes" statement). On the host operating
system you are using (Apple Leopard OS X 10.6.1), path specifications
starting with "/" are ABSOLUTE paths, not relative paths.

The directory it is looking for is "/tapes".

The directory it is NOT looking for is "/Users/nigeldefreitas/tapes/".

The two directories (paths) are completely different from each other. They
are NOT the same thing.


> I tried creating a folder called "tapes" in the location
> specified,

Actually no, you did not.  :)

You THOUGHT you did, but you actually didn't.  :)


> but that had no effect. I commented the LCS line but that had
> no effect either: # 0440.2 LCS -n /dev/net/tun 192.168.200.2

The LCS device statement does not have anything to do with the error that
was reported.


> I installed tun tap, but didn't perform any additional
> configuration (just installed with defaults by double-clicking
> the package).

LCS devices have nothing to do with the error you are reporting.


> I'm not sure why I get the tapes message even after I manually
> create the tapes folder in OS X.

You created your tapes directory in the wrong place.  :)

Either: a) create the directory in the correct location, or: b) remove the
AUTOMOUNT statement from your configuration file.

Or better yet, create your OWN configuration file instead of trying to use
our sample (which is only meant to be illustrative but not necessarily
correct/valid for anyone's particular system).


<snip remainder>


Welcome to Hercules, Nigel. We hope your stay is a pleasant one.

   :)

- --
"Fish" (David B. Trout) - fish@...
Fight Spam! Join CAUCE! <http://www.cauce.org/>
7 reasons why HTML email is a bad thing
http://www.georgedillon.com/web/html_email_is_evil.shtml
PGP key fingerprints:
DH/DSS: 9F9B BAB0 BA7F C458 1A89 FE26 48F5 D7F4 C4EE 3E2A
RSA: 6B37 7110 7201 9917 9B0D 99E3 55DB 5D58 FADE 4A52





-----BEGIN PGP SIGNATURE-----
Version: PGP Desktop 9.8.0 (Build 2158)
Charset: us-ascii

wj8DBQFK/BWNSPXX9MTuPioRArUvAKCObhEJ2lrbabRlREUOHqopQfK9vACeIezA
1zWIsdLZRcodst+m0HYYSjU=
=Rza+
-----END PGP SIGNATURE-----

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

BernardL wrote:

> Sorry, from delay, i send the return of ckofflod:
[...]
> Conclusion :
> disable all inbound CHECKSUM OFFLOADING on the adapter.
> How you doing, please?


You obviously missed my follow-up message where I said:


> ACK! I meant OUTBOUND!
>
> Disable all OUTBOUND (i.e. "Transmit") checksum offloading!
>
> It's the *inbound* that you can leave enabled if you want.
>
> Sorry!
>
>
> (grumble... I hate it when I do that... typing too fast.. grumble)


Please disable all OUTBOUND, repeat, *>> OUTBOUND <<* checksum offloading:

Start -> Settings -> Network Connections.

Right-click on your Local Area Connections icon, and select Properties.

Click the "Configure" button for your adapter. You should then see a
Properties dialog for your adapter.

Click the Advanced tab.

On the Advanced page, you should see a box on the left listing many
properties, and a small combobox on the right labeled "Value".

The properties related to Checksum Offloading are named differently for each
different type (manufacturer) of network adapter, but they are probably
named similarly to "TCP/IP Offload".

For each 'Property' in your list related to Checksum Offloading (left side
of dialog), click the property to select it.

The "Value" box (right side of dialog) will probably have three entries in
it:

   *  None
   *  Rx TCP/IP Checksum
   *  Tx TCP/IP Checksum
   *  Tx/Rx TCP/IP Checksum

(Note again that YOUR values may be slightly different from mine.)

What you want to do is select the entry for either "Rx TCP/IP Checksum" -or-
"None".

The idea here is you do NOT want the "Tx TCP/IP Checksum" nor the " Tx/Rx
TCP/IP Checksum"!!

Repeat: you do NOT want "Tx"!!

You *DO* want either "Rx" -or- "None".

Repeat: you DO want to either disable *all* offloading -OR- enable *only*
"Rx"!!

Do this for every property you see related to Checksum Offloading. (Again,
your list of properties may be different from mine. Each adapter
manufacturer is different).

Click the 'OK' button. Your adapter should then reconfigure itself.

If you want, you can reboot just to be safe/sure.

Then retry your TT32Test ping test again and/or retry your Hercules.

Please let us know if the above helps you or not.

Thanks.

- --
"Fish" (David B. Trout) - fish@...
Fight Spam! Join CAUCE! <http://www.cauce.org/>
7 reasons why HTML email is a bad thing
http://www.georgedillon.com/web/html_email_is_evil.shtml
PGP key fingerprints:
DH/DSS: 9F9B BAB0 BA7F C458 1A89 FE26 48F5 D7F4 C4EE 3E2A
RSA: 6B37 7110 7201 9917 9B0D 99E3 55DB 5D58 FADE 4A52





-----BEGIN PGP SIGNATURE-----
Version: PGP Desktop 9.8.0 (Build 2158)
Charset: us-ascii

wj8DBQFK+5N8SPXX9MTuPioRAszfAKCqfDGx4qCHUB1Eo2PZubDk51pfsQCgid1B
Dhl1KJ9EXyd/BGu1xl4OhBI=
=JKM6
-----END PGP SIGNATURE-----

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Thomas Dunlap wrote:

[...]
> I have attached a "zip" file with 5 TXT files that contains
> the information on my configuration. [...]


FYI: this group does not allow file attachments.


Instead, upload your file(s) to the group's "Files" area:


   http://tech.groups.yahoo.com/group/hercules-390/files/


and then post a message with the filename you used.


- --
"Fish" (David B. Trout) - fish@...
Fight Spam! Join CAUCE! <http://www.cauce.org/>
7 reasons why HTML email is a bad thing
http://www.georgedillon.com/web/html_email_is_evil.shtml
PGP key fingerprints:
DH/DSS: 9F9B BAB0 BA7F C458 1A89 FE26 48F5 D7F4 C4EE 3E2A
RSA: 6B37 7110 7201 9917 9B0D 99E3 55DB 5D58 FADE 4A52





-----BEGIN PGP SIGNATURE-----
Version: PGP Desktop 9.8.0 (Build 2158)
Charset: us-ascii

wj8DBQFK+4foSPXX9MTuPioRAgL4AJ9rrw+SlM5DyB4UyeeI2nihuPiVrQCgy0z7
8rqZnt7D/urrBdy8WlnhSf8=
=KPAP
-----END PGP SIGNATURE-----

paoloG wrote:
>
> opcode.h
>
> old code: (line 988)
> + (uintptr_t)(_aaddr)) \
>
> new code:
> + (uintptr_t)((_aaddr) & PAGEFRAME_PAGEMASK)) \
>
> dat.h
>
> old code: (lines 2238-2263)
> regs->tlb.main[ix]       = NEW_MAINADDR (regs, addr, apfra);
> regs->tlb.main[ix]    = NEW_MAINADDR (regs, addr, apfra);
>
> new code:
> regs->tlb.main[ix]       = NEW_MAINADDR (regs, addr, aaddr);
> regs->tlb.main[ix]    = NEW_MAINADDR (regs, addr, aaddr);
>

Please don't do that (I mean.. please no-one apply this to SVN !)

This will very likely break any ESA/390 guest running ZSIE if there is
more than 2GB of storage. The problem is that the page mask is being
applied at the WRONG time. The *absolute* page frame can very well lie
beyond the addressable limit of the guest. Therefore calling
'NEW_MAINADDR' in ESA/390 mode in SIE mode and masking it with the
*guest* page frame mask is going to give you the wrong page frame if the
page frame is above 2GB.

The reason for the 'apfra' trick is that we are using regs->dat.rpfra
which is computed during SIE translation (that is, when the DAT
translation is performed on the HOST side of SIE).. That's what

      apfra=APPLY_PREFIXING(regs->dat.rpfra,regs->PX);

is all about.. (regs->dat.rpfra is the real page frame with the *HOST*
page frame mask applied - not the guest page frame mask !)

Now, why this is NOT working for a S/370 guest running on a ESA/390 host
is still something I have to figure out..

--Ivan

(Sorry not being more active here.. Some "Real Life" issue I am trying
to sort out)


[Non-text portions of this message have been removed]

Jim,

I have attached a "zip" file with 5 TXT files that contains the
information on my configuration.

The SLES configuration is as follows"
eth0 Firewall disabled MTU 1500 10.1.11.21 mask of 255.255.255.0
eth1 Firewall disabled MTU 1500 10.1.11.24 mask of 255.255.255.0

I can both PING and TRACERT to the two addresses listed above.

I am able to logon to MVS from an X3270 session running under SLES.
There were no errors when I start TCPIP or TN3270 address spaces under
MVS. It seems to be related to trying to connect through either NIC
adapter. I even tried FTP and received an error that the connection was
rejected by remote host.

Cheers,
Tom



jsganino wrote:
>
> Tom,
>
> I hate it when that happens. Conceptually, everything is the same,
> except for one little thing, but it just won't work. Alas, I'm afraid
> were going to have ask a bunch of silly questions to tease out the answer.
>
> 1) Is the LCS device defined on a pair of channels, presumably E20 and
> E21?
>
> 2) When your TCPIP is running under MVS under Hercules, does a tun0
> device show up in your routing table on the SLES system?
>
> 3) Does the TCPIP software come up cleanly under MVS. (I'm more of a
> VM person, so I'm used to looking at the console of the TCPIP virtual
> machine. I have to believe that all that good information is captured
> somewhere in MVS. Maybe SYSPRINT?)
>
> 4) Can you ping the MVS machine from the SLES machine?
>
> 5) Can you access the MVS machine with an X3270 client from the SLES
> machine?
>
> If you can let us know, I'll scratch my head a bit and see whether I
> conjure up some possible things to check.
>
> Jim
>
> BTW, VISTA is *very* nifty.
>
> --- In hercules-390@yahoogroups.com
> <mailto:hercules-390%40yahoogroups.com>, Thomas Dunlap
> <thomas.dunlap@...> wrote:
> >
> > I am trying to use TN3270 software (Tom Brennan's Vista) to connect to
> > MVS. I have define an LCS device on E20 with IP 10.1.11.24. This the
> > same setup we utilized on our Flexes system without fail. With Hercules
> > we seem to get a TCP error 10061, which seems to indicate that the host
> > has rejected the connection. I have tried several configurations
> > without any success. Any help or thoughts would be greatly appreciated.
> >
> > This is Hercules 3.06 running under SLES 11. Also, I have configured
> > the two NICs, one with and IP of 10.1.11.21 and the other with
> > 10.1.11.24. I have even reversed these between the two adapters with
> > the same results.
> >
> > Cheers,
> > Tom Dunlap
> >
>
>



[Non-text portions of this message have been removed]

Rocky,

I have attached a "zip" file with 5 TXT files that contain the
information you requested.

The SLES configuration is as follows"
eth0 Firewall disabled MTU 1500 10.1.11.21 mask of 255.255.255.0
eth1 Firewall disabled MTU 1500 10.1.11.24 mask of 255.255.255.0

Cheers,
Tom

Rocky wrote:
>
> Can you send the first 60 or so lines from the LOG as Hercules comes up.
>
> Also the relevant lines from the configuration file.
>
> Also your network configuration and Ip addresses.
>
> Subnet mask - gateway address - host computer address and guest operating
> system address
>
> Finally - The beginroute section from the TCPIP configuration
>
> Roc
>
> _____
>
> From: hercules-390@yahoogroups.com
> <mailto:hercules-390%40yahoogroups.com>
> [mailto:hercules-390@yahoogroups.com
> <mailto:hercules-390%40yahoogroups.com>] On
> Behalf Of Thomas Dunlap
> Sent: Wednesday, November 11, 2009 14:18
> To: hercules-390@yahoogroups.com <mailto:hercules-390%40yahoogroups.com>
> Subject: [hercules-390] Using LCS interface and getting TCP error 10061
>
> I am trying to use TN3270 software (Tom Brennan's Vista) to connect to
> MVS. I have define an LCS device on E20 with IP 10.1.11.24. This the
> same setup we utilized on our Flexes system without fail. With Hercules
> we seem to get a TCP error 10061, which seems to indicate that the host
> has rejected the connection. I have tried several configurations
> without any success. Any help or thoughts would be greatly appreciated.
>
> This is Hercules 3.06 running under SLES 11. Also, I have configured
> the two NICs, one with and IP of 10.1.11.21 and the other with
> 10.1.11.24. I have even reversed these between the two adapters with
> the same results.
>
> Cheers,
> Tom Dunlap
>
> [Non-text portions of this message have been removed]
>
>



[Non-text portions of this message have been removed]

Tom,

     I hate it when that happens.  Conceptually, everything is the same, except
for one little thing, but it just won't work.   Alas, I'm afraid were going to
have ask a bunch of silly questions to tease out the answer.

1) Is the LCS device defined on a pair of channels, presumably E20 and E21?

2) When your TCPIP is running under MVS under Hercules, does a tun0 device show
up in your routing table on the SLES system?

3) Does the TCPIP software come up cleanly under MVS.  (I'm more of a VM person,
so I'm used to looking at the console of the TCPIP virtual machine.  I have to
believe that all that good information is captured somewhere in MVS.  Maybe
SYSPRINT?)

4) Can you ping the MVS machine from the SLES machine?

5) Can you access the MVS machine with an X3270 client from the SLES machine?

If you can let us know, I'll scratch my head a bit and see whether I conjure up
some possible things to check.

Jim

BTW, VISTA is *very* nifty.

--- In hercules-390@yahoogroups.com, Thomas Dunlap <thomas.dunlap@...> wrote:
>
> I am trying to use TN3270 software (Tom Brennan's Vista) to connect to
> MVS.   I have define an LCS device on E20 with IP 10.1.11.24.  This the
> same setup we utilized on our Flexes system without fail.  With Hercules
> we seem to get a TCP error 10061, which seems to indicate that the host
> has rejected the connection.  I have tried several configurations
> without any success.  Any help or thoughts would be greatly appreciated.
>
> This is Hercules 3.06 running under SLES 11.  Also, I have configured
> the two NICs, one with and IP of 10.1.11.21 and the other with
> 10.1.11.24.  I have even reversed these between the two adapters with
> the same results.
>
> Cheers,
> Tom Dunlap
>

--- In hercules-390@yahoogroups.com, Dave Wade <g4ugm@...> wrote:
>
>
>
> Alexey wrote:
> > [skipped]
> >
> > p> Jim, many thanks for your suggestions; but IMHO there's a bug in
> > p> Hercules, because with Hercules 3.05 I can IPL quite a lot of 370
> > p> guests under VM/ESA 2.4 (DOS/360, DOS/VS, OS/MVT, OS/MFT, OS/VS1,
> > p> VM/370, VM/SP, MVS, CMS of VM/SP).
> > p> Starting from Revision Date: Mon, 8 Dec 2008 20:38:20 UTC to the
> > p> last CSV available when I try to IPL a 370 guest I get the error
described.
> >
> > p> I could try to modify the modified sources but I'm not too skilled in C++
....;-(
> >
> > p> Regards.
> >
>
> That's right, but there are lots of "gotchas" I think ESA will object
> unless the hardware type is set to a model that has 370 support in the
> SIE. The VM should have issued a "SET MACHINE 370" or have an approriate
> directory statement. It most be an old version of VM/ESA as support was
> removed at some point. I don't remember when. Any way if all the above
> caveats are true then the the combination of CP and SIE should allow 370
> guests to IPL in VMs.
>
> I suspect something is broken in SIE in Hercules but that probably needs
> Ivan to look at it.

Dave,
as usual you're right.
If I IPL VM/ESA under z/VM 5.3 Evaluation (or 4.4 as well), SET MACHINE 370
fails (SIE for ESAME doesn't support 370 mode).
Your suspect of a broken Hercules is right; I took one of the last snaphots and
modified the following modules:

opcode.h

old code: (line 988)
+ (uintptr_t)(_aaddr)) \

new code:
+ (uintptr_t)((_aaddr) & PAGEFRAME_PAGEMASK)) \

dat.h

old code: (lines 2238-2263)
regs->tlb.main[ix]       = NEW_MAINADDR (regs, addr, apfra);
regs->tlb.main[ix]    = NEW_MAINADDR (regs, addr, apfra);

new code:
regs->tlb.main[ix]       = NEW_MAINADDR (regs, addr, aaddr);
regs->tlb.main[ix]    = NEW_MAINADDR (regs, addr, aaddr);

and now IPL of VM/SP under VM/ESA works like a charm.
Not sure if something other is no more working .. ;-)

Let's hope that our great experts may fix officially the bug.

Regards.

Paul

Can you send the first 60 or so lines from the LOG as Hercules comes up.

Also the relevant lines from the configuration file.



Also your network configuration and Ip addresses.



Subnet mask - gateway address - host computer address and guest operating
system address



Finally - The beginroute section from the TCPIP configuration



Roc



   _____

From: hercules-390@yahoogroups.com [mailto:hercules-390@yahoogroups.com] On
Behalf Of Thomas Dunlap
Sent: Wednesday, November 11, 2009 14:18
To: hercules-390@yahoogroups.com
Subject: [hercules-390] Using LCS interface and getting TCP error 10061





I am trying to use TN3270 software (Tom Brennan's Vista) to connect to
MVS. I have define an LCS device on E20 with IP 10.1.11.24. This the
same setup we utilized on our Flexes system without fail. With Hercules
we seem to get a TCP error 10061, which seems to indicate that the host
has rejected the connection. I have tried several configurations
without any success. Any help or thoughts would be greatly appreciated.

This is Hercules 3.06 running under SLES 11. Also, I have configured
the two NICs, one with and IP of 10.1.11.21 and the other with
10.1.11.24. I have even reversed these between the two adapters with
the same results.

Cheers,
Tom Dunlap







[Non-text portions of this message have been removed]

DW> Alexey wrote:
>> [skipped]
>>
>> p> Jim, many thanks for your suggestions; but IMHO there's a bug in
>> p> Hercules, because with Hercules 3.05 I can IPL quite a lot of 370
>> p> guests under VM/ESA 2.4 (DOS/360, DOS/VS, OS/MVT, OS/MFT, OS/VS1,
>> p> VM/370, VM/SP, MVS, CMS of VM/SP).
>> p> Starting from Revision Date: Mon, 8 Dec 2008 20:38:20 UTC to the
>> p> last CSV available when I try to IPL a 370 guest I get the error
described.
>>
>> p> I could try to modify the modified sources but I'm not too skilled in C++
....;-(
>>
>> p> Regards.
>>
>> My  apologies for breaking into the conversation. I had the impression
>> that  370  guests  could  only  IPL on VM/ESA 370 feature (which never
>> reached   version   2.4),   as  virtual  machine  provides  underlying
>> architecture  (that  is - ESA/390). What you are saying (or, at least,
>> what  I  understood)  is  that  you  can IPL VM/ESA 2.4 in Herc (using
>> ARCHMODE  ESA/390) and then IPL VM/370 in a 370 virtual machine? Is it
>> correct?
>>

DW> That's right, but there are lots of "gotchas" I think ESA will object
DW> unless the hardware type is set to a model that has 370 support in the
DW> SIE. The VM should have issued a "SET MACHINE 370" or have an approriate
DW> directory statement. It most be an old version of VM/ESA as support was
DW> removed at some point. I don't remember when. Any way if all the above
DW> caveats are true then the the combination of CP and SIE should allow 370
DW> guests to IPL in VMs.

Hmmm! Will try with Herc 3.05 then.. I failed few times, but all my
attempts were with 3.06

Alexey

DW> I suspect something is broken in SIE in Hercules but that probably needs
DW> Ivan to look at it.



** All intelligent species own cats.

Alexey wrote:
> [skipped]
>
> p> Jim, many thanks for your suggestions; but IMHO there's a bug in
> p> Hercules, because with Hercules 3.05 I can IPL quite a lot of 370
> p> guests under VM/ESA 2.4 (DOS/360, DOS/VS, OS/MVT, OS/MFT, OS/VS1,
> p> VM/370, VM/SP, MVS, CMS of VM/SP).
> p> Starting from Revision Date: Mon, 8 Dec 2008 20:38:20 UTC to the
> p> last CSV available when I try to IPL a 370 guest I get the error described.
>
> p> I could try to modify the modified sources but I'm not too skilled in C++
....;-(
>
> p> Regards.
>
> My  apologies for breaking into the conversation. I had the impression
> that  370  guests  could  only  IPL on VM/ESA 370 feature (which never
> reached   version   2.4),   as  virtual  machine  provides  underlying
> architecture  (that  is - ESA/390). What you are saying (or, at least,
> what  I  understood)  is  that  you  can IPL VM/ESA 2.4 in Herc (using
> ARCHMODE  ESA/390) and then IPL VM/370 in a 370 virtual machine? Is it
> correct?
>

That's right, but there are lots of "gotchas" I think ESA will object
unless the hardware type is set to a model that has 370 support in the
SIE. The VM should have issued a "SET MACHINE 370" or have an approriate
directory statement. It most be an old version of VM/ESA as support was
removed at some point. I don't remember when. Any way if all the above
caveats are true then the the combination of CP and SIE should allow 370
guests to IPL in VMs.

I suspect something is broken in SIE in Hercules but that probably needs
Ivan to look at it.



>
> Alexey
>

I am trying to use TN3270 software (Tom Brennan's Vista) to connect to
MVS.   I have define an LCS device on E20 with IP 10.1.11.24.  This the
same setup we utilized on our Flexes system without fail.  With Hercules
we seem to get a TCP error 10061, which seems to indicate that the host
has rejected the connection.  I have tried several configurations
without any success.  Any help or thoughts would be greatly appreciated.

This is Hercules 3.06 running under SLES 11.  Also, I have configured
the two NICs, one with and IP of 10.1.11.21 and the other with
10.1.11.24.  I have even reversed these between the two adapters with
the same results.

Cheers,
Tom Dunlap

--- In hercules-390@yahoogroups.com, Alexey <bozy@...> wrote:
>
>
> [skipped]
>
> p> Jim, many thanks for your suggestions; but IMHO there's a bug in
> p> Hercules, because with Hercules 3.05 I can IPL quite a lot of 370
> p> guests under VM/ESA 2.4 (DOS/360, DOS/VS, OS/MVT, OS/MFT, OS/VS1,
> p> VM/370, VM/SP, MVS, CMS of VM/SP).
> p> Starting from Revision Date: Mon, 8 Dec 2008 20:38:20 UTC to the
> p> last CSV available when I try to IPL a 370 guest I get the error described.
>
> p> I could try to modify the modified sources but I'm not too skilled in C++
....;-(
>
> p> Regards.
>
> My  apologies for breaking into the conversation. I had the impression
> that  370  guests  could  only  IPL on VM/ESA 370 feature (which never
> reached   version   2.4),   as  virtual  machine  provides  underlying
> architecture  (that  is - ESA/390). What you are saying (or, at least,
> what  I  understood)  is  that  you  can IPL VM/ESA 2.4 in Herc (using
> ARCHMODE  ESA/390) and then IPL VM/370 in a 370 virtual machine? Is it
> correct?

Alexey,
you can IPL VM/370 in a 370 virtual machine under VM/ESA 2.4 provided that:

1) Hercules works correctly (version 3.05 is OK; for actual version I'm
waiting....:-( ).
2) You must give the command SET MACH 370 in the virtual machine, or define
MACHINE 370 in directory.
3) VM/ESA 2.4 doesn't sense correctly 3350 dasds, so you have to define them in
HCPRIO and regen CP nucleus.

VM/ESA 2.4 can be IPL'd only in ESA/390 mode.

Regards.

Paul

> Alexey
>
>
> ** There are many intelligent species in the universe, and they all own cats.
>

[skipped]

p> Jim, many thanks for your suggestions; but IMHO there's a bug in
p> Hercules, because with Hercules 3.05 I can IPL quite a lot of 370
p> guests under VM/ESA 2.4 (DOS/360, DOS/VS, OS/MVT, OS/MFT, OS/VS1,
p> VM/370, VM/SP, MVS, CMS of VM/SP).
p> Starting from Revision Date: Mon, 8 Dec 2008 20:38:20 UTC to the
p> last CSV available when I try to IPL a 370 guest I get the error described.

p> I could try to modify the modified sources but I'm not too skilled in C++
....;-(

p> Regards.

My  apologies for breaking into the conversation. I had the impression
that  370  guests  could  only  IPL on VM/ESA 370 feature (which never
reached   version   2.4),   as  virtual  machine  provides  underlying
architecture  (that  is - ESA/390). What you are saying (or, at least,
what  I  understood)  is  that  you  can IPL VM/ESA 2.4 in Herc (using
ARCHMODE  ESA/390) and then IPL VM/370 in a 370 virtual machine? Is it
correct?


Alexey


** There are many intelligent species in the universe, and they all own cats.

--- In hercules-390@yahoogroups.com, "Gregg C Levine" <hansolofalcon@...> wrote:
>
> Hello!
> Mike, the link expired. You might want to try again with that. In addition
> the site wanted me to register for it. (Which I am not about to do.)

Try again:

http://www.facebook.com/album.php?aid=2037698&id=1528659644&l=6c0b26d489

Mike

--- In hercules-390@yahoogroups.com, "jsganino" <James.Ganino@...> wrote:
>
> Paolo,
>
>     I've seen this in z/VM when IPL'ing a VM/ESA guest on real hardware.  My
circumstances were admittedly different, but could you check a couple things and
let the group know?
>
> 1) What is your terminal CONMODE setting?   To IPL some operating systems,
there is a requirement that the CONMODE be 3270.

CONMODE 3270 or 3215 : the same error.

> 2) How much memory is defined in the 370 mode guest that you are trying to
IPL?   Just in case there is some peculiar side effect, I'd recommend that you
limit it to 16MB before trying to IPL.
>

16M, less than 16M, more than 16M : the same error.

>
> As an aside, there was a bug in VM/ESA up to about 2.4 that prevented 2nd
level VM's from manipulating tape drives.  (This created a real challenge for me
in disaster recovery exercise several years ago.)  The details are fuzzy, but I
remember we had to map the guest's disks to the first level directory and
restore them at first level before we could IPL the restored system at second
level.
>
>                                                                              
One last tidbit:  the following comes from the help page for HCP453W:
>
> Programmer Response:  To determine the reason for the loop, examine the
> program-check information in page zero of your virtual storage.  If this error
> occurred immediately after the IPL command, the problem may be that you are
> trying to run a 370 guest in XA mode, or the reverse (issue the QUERY SET
> command to find out the current MACHINE setting).  In this case, issue the SET
> MACHINE command to select the proper mode.
>
>
> That's all the light I can shed; I hope there's something useful in it.  Good
Luck.
>
> Jim
>

Jim, many thanks for your suggestions; but IMHO there's a bug in Hercules,
because with Hercules 3.05 I can IPL quite a lot of 370 guests under VM/ESA 2.4
(DOS/360, DOS/VS, OS/MVT, OS/MFT, OS/VS1, VM/370, VM/SP, MVS, CMS of VM/SP).
Starting from Revision Date: Mon, 8 Dec 2008 20:38:20 UTC to the last CSV
available when I try to IPL a 370 guest I get the error described.

I could try to modify the modified sources but I'm not too skilled in C++
....;-(

Regards.

> --- In hercules-390@yahoogroups.com, "paoloG" <crc@> wrote:
> >
> > Hi all,
> > The IPL command in a 370 mode guest of VM/ESA 2.4 doesn't work.
> > Any kind of IPL (from dasd-tape-reader) gives the same message; for example
IPL from an empty card reader:
> >
> > IPL 00C
> > HCPGIR453W CP entered; program interrupt loop.
> >
> > from tape:
> >
> > IPL 181
> > HCPGIR453W CP entered; program interrupt loop.
> >
> > An I/O trace shows that IPL command fails without even trying to do any I/O
on the IPL device.
> >
> > I've noticed that in Hercules 3.05 the 370 mode guest IPL is working; so
I've made some research and have discovered that the offending revision of
Hercules is:
> >
> > Author: ivan
> > Revision Date: Mon, 8 Dec 2008 20:38:20 UTC
> > Revision comments: Fix SIE DAT Issue with ESA/390 Guest on z/Arch host with
>2GB of storage
> >
> > In any CSV version before that date IPL in a 370 guest machine works fine;
to do a simple test in any CMS guest you can IPL 00C with an empty card reader:
> >
> > SET MACH 370
> > IPL 00C
> >
> > If IPL works you get this message:
> >
> > HCPVMJ232E IPL UNIT ERROR; CSW 00000000 02000000 SNS 40
> > HCPGIR450W CP entered; disabled wait PSW 00060000 00000232
> >
> > If IPL doesn't work you'll get this one:
> >
> > HCPGIR453W CP entered; program interrupt loop.
> >
> >
> > Hoping that some Hercules developer can correct the error.
> >
> > Regards.
> >
>

Sorry, from delay, i send the return of ckofflod:
E:\Hercules\CTCI-W32_3.2.1.160_bin\bin>ckofflod NPF_{9C158014-7B1C-4639-BCB4-3D7
1A6A04594}

Supports NDIS 5.1 "OID_TCP_TASK_OFFLOAD" (0xFC010201) = yes


Supports NDIS 6.0 "OID_TCP_OFFLOAD_CURRENT_CONFIG" (0xFC01020B) = no


GetChecksumOffloadTask( OID_TCP_TASK_OFFLOAD (NDIS 5.1) ) success!

    V4Transmit.IpOptionsSupported:  YES
    V4Transmit.TcpOptionsSupported: YES
    V4Transmit.TcpChecksum:         ENABLED
    V4Transmit.UdpChecksum:         ENABLED
    V4Transmit.IpChecksum:          ENABLED

    V4Receive.IpOptionsSupported:   no
    V4Receive.TcpOptionsSupported:  no
    V4Receive.TcpChecksum:          no
    V4Receive.UdpChecksum:          no
    V4Receive.IpChecksum:           no

Conclusion :
disable all inbound CHECKSUM OFFLOADING on the adapter.
How you doing, please?

Thousand Thanks
BLM

-- In hercules-390@yahoogroups.com, "conan_le_cimerien" <bernard.le-merrer@...>
wrote:
>
> I have the following Meesage :
> HHCTU002E Error opening TUN/TAP device: 00-1C-23-54-3B-42: No error
> HHCCF044E Initialization failed for device 0E21,
>
>
> Platform carateristics :
> -             WINDOW            2003 server SP 2 en fran�ais
> -             Hercules              3.06
> -             WinpCap             4.0.0.1040
> -             CTCI-W32           3.2.1.160
> -             Runtime Visual Basic 2005
>
> The good PAth are correct with the directory WinPCap & CTCI-W32 & Hercules
>
> The driver npf is started (see msinfo32)
>
> My IPaddress IP are not dynamics :  z/OS(192.168.2.51) et
Windows(192.168.2.47)
>
> All the Hercule program even Hercule Gui have the Administrator authority
>
> When I start TT32test, It's correct, this is the sysout :
> 14:14:04.781 Begin TT32Test.exe, version: "3.2.1.160" (3.2.1.160): "Release
version" ...
> 14:14:04.781 Copyright (C) 2002-2007, Software Development Laboratories (aka
'Fish' (David B. Trout)).
> 14:14:04.781
> 14:14:04.781 Running on Windows XP (MP=2), version 5.2.3790 Service Pack 2
> 14:14:04.781
> 14:14:04.781 Using WinPCap Packet.DLL, version "4.0.0.1040" (1.0.4.0), driver
version "4.0.0.1040" ...
> 14:14:04.781
> 14:14:04.781 Using FishPack.dll, version: "3.2.1.160" (3.2.1.160): "Release
version" ...
> 14:14:04.781 Copyright (C) 2002-2007, Software Development Laboratories (aka
'Fish' (David B. Trout)).
> 14:14:04.781
> 14:14:04.781 Using TunTap32.dll, version: "3.2.1.160" (3.2.1.160): "Release
version" ...
> 14:14:04.781 Copyright (C) 2002-2007, Software Development Laboratories (aka
'Fish' (David B. Trout)).
> 14:14:04.781
> 14:14:04.781 ---------  The following relevant DosDevices are defined
---------
> 14:14:04.781
> 14:14:04.781 NPF_NdisWanBh
> 14:14:04.781 NPF_NdisWanIp
> 14:14:04.781 NPF_{2A3C2BCB-015B-463F-A698-1C946FE4D1D3}
> 14:14:04.781 NPF_{44EBC665-7160-47DA-BE83-B8A403A6F13A}
> 14:14:04.781 NPF_{54C7D140-09EF-11D1-B25A-F5FE627ED95E}
> 14:14:04.781 NPF_{7989E598-3AFC-44C7-A4DB-2CAF98527E47}
> 14:14:04.781 NPF_{C61CB80C-6E1B-4243-9D3B-9289EE251C44}
> 14:14:04.781 NPF_{C84A2606-0FBC-4EB5-88EA-46F7A75C8955}
> 14:14:04.781 NPF_{D017E754-2BCC-423C-BC7B-6F2D3E07AAE1}
> 14:14:04.781 NPF_{D54D3E5C-D7F9-482A-B730-B455E5140652}
> 14:14:04.781 {2A3C2BCB-015B-463F-A698-1C946FE4D1D3}
> 14:14:04.781 {7989E598-3AFC-44C7-A4DB-2CAF98527E47}
> 14:14:04.781 {C61CB80C-6E1B-4243-9D3B-9289EE251C44}
> 14:14:04.781 {C84A2606-0FBC-4EB5-88EA-46F7A75C8955}
> 14:14:04.781 {D017E754-2BCC-423C-BC7B-6F2D3E07AAE1}
> 14:14:04.781 {D54D3E5C-D7F9-482A-B730-B455E5140652}
> 14:14:04.781
> 14:14:04.781 -------------------------  Network Information 
-------------------------
> 14:14:04.781
> 14:14:04.781   Host Name . . . . . . . . . : ao-windows2k3
> 14:14:04.781   Node Type . . . . . . . . . : (unknown)
> 14:14:04.781   DNS Servers . . . . . . . . : 192.168.2.15
> 14:14:04.781                                              192.168.2.16
> 14:14:04.781   IP Routing Enabled. . . . . : yes
> 14:14:04.781
> 14:14:04.781   Network Address    Netmask        Gateway    Address
Interface      Metric
> 14:14:04.781                      0.0.0.0                    0.0.0.0
192.168.2.1     192.168.2.47              10
> 14:14:04.781                  127.0.0.0               255.0.0.0
127.0.0.1            127.0.0.1               1
> 14:14:04.781                  127.0.0.1  255.255.255.255                      
127.0.0.1            127.0.0.1               1
> 14:14:04.781             192.168.2.0       255.255.255.0                
192.168.2.47     192.168.2.47            10
> 14:14:04.781           192.168.2.47  255.255.255.255                       
127.0.0.1            127.0.0.1            10
> 14:14:04.781         192.168.2.255  255.255.255.255                
192.168.2.47     192.168.2.47            10
> 14:14:04.781                  224.0.0.0               240.0.0.0
192.168.2.47     192.168.2.47            10
> 14:14:04.781   255.255.255.255  255.255.255.255                   192.168.2.47
192.168.2.47              1
> 14:14:04.781
> 14:14:04.781   Default gateway:  192.168.2.1
> 14:14:04.781
> 14:14:04.781 --------------------------  Detected Adapters 
--------------------------
> 14:14:04.781
> 14:14:04.781 AdapterName         = NPF_{D017E754-2BCC-423C-BC7B-6F2D3E07AAE1}
> 14:14:04.781 Description         = Broadcom NetXtreme 57xx Gigabit Controller
> 14:14:04.781 PhysAddr            = 00-1C-23-54-3B-42
> 14:14:04.781 LinkType            = NdisMedium802_3
> 14:14:04.781 MediaConnected      = Yes
> 14:14:04.781 LinkSpeed           = 100.0 Mbps
> 14:14:04.781 IPAddr              = 192.168.2.47
> 14:14:04.781 IPAddrMask          = 255.255.255.0
> 14:14:04.781 GatewayIPAddr       = 192.168.2.1
> 14:14:04.781 dwIndex             = 0x00030003
> 14:14:04.781 Checksum offloading = as follows:
> 14:14:04.781
> 14:14:04.781    V4Transmit.IpOptionsSupported:  YES
> 14:14:04.781    V4Transmit.TcpOptionsSupported: YES
> 14:14:04.781    V4Transmit.TcpChecksum:         ENABLED
> 14:14:04.781    V4Transmit.UdpChecksum:         ENABLED
> 14:14:04.781    V4Transmit.IpChecksum:          ENABLED
> 14:14:04.781
> 14:14:04.781    V4Receive.IpOptionsSupported:   no
> 14:14:04.781    V4Receive.TcpOptionsSupported:  no
> 14:14:04.781    V4Receive.TcpChecksum:          no
> 14:14:04.781    V4Receive.UdpChecksum:          no
> 14:14:04.781    V4Receive.IpChecksum:           no
> 14:14:04.781
> 14:14:04.781    V6Transmit.IpOptionsSupported:  no
> 14:14:04.781    V6Transmit.TcpOptionsSupported: no
> 14:14:04.781    V6Transmit.TcpChecksum:         no
> 14:14:04.781    V6Transmit.UdpChecksum:         no
> 14:14:04.781
> 14:14:04.781    V6Receive.IpOptionsSupported:   no
> 14:14:04.781    V6Receive.TcpOptionsSupported:  no
> 14:14:04.781    V6Receive.TcpChecksum:          no
> 14:14:04.781    V6Receive.UdpChecksum:          no
> 14:14:04.781
>
> I  see no error ??
>
> This is  the CONF member used :
> #
> # Hercules Emulator Control file...
> # Description:
> # MaxShutdownSecs: 15
> #
> #
> # System parameters
> #
>
> DEFSYM DASDDIR8 "E:\Hercules\Zos18\DASD"
> DEFSYM DASDDIR5 "E:\Hercules\Zos15\DASD"
>
> ARCHMODE  z/Arch
> CNSLPORT  3270
> # CONKPALV  (3,1,10)
> CPUMODEL  2094
> CPUSERIAL 000611
> ECPSVM    NO
> HTTPPORT  8081 NOAUTH
> LOADPARM  5B44BLM1
> LPARNAME  HERCULES
> MAINSIZE  1024
> # MOUNTED_TAPE_REINIT  DISALLOW
> NUMCPU    1
> OSTAILOR  Z/OS
> PANRATE   50
> PGMPRDOS  LICENSED
> SHCMDOPT  NODIAG8
> SYSEPOCH  1900
> # TIMERINT  50
> TZOFFSET  +0200
> YROFFSET  0
>
> HERCPRIO  0
> TODPRIO   -20
> DEVPRIO   8
> CPUPRIO   15
>
> # Display Terminals
>
> 0CA0-0CA1,0CC0-0CC1    3270
>
> # DASD Devices
>
> 5B41    3390    $(DASDDIR8)\PTFZ81.5B41
> 5B42    3390    $(DASDDIR8)\PTFZ82.5B42
> 5B43    3390    $(DASDDIR8)\PTFZ83.5B43
> 5B44    3390    $(DASDDIR8)\SYSZ8B.5B44
> 5B45    3390    $(DASDDIR8)\DLBZ81.5B45
> 5B46    3390    $(DASDDIR8)\DLBZ82.5B46
> 5B47    3390    $(DASDDIR8)\DLBZ83.5B47
> 5B48    3390    $(DASDDIR8)\DLBZ84.5B48
> 5B49    3390    $(DASDDIR8)\DLBZ85.5B49
> 5B4A    3390    $(DASDDIR8)\THER01_1.AA3
> 5B4B    3390    $(DASDDIR8)\THER02_1.AA4
> 5B4C    3390    $(DASDDIR8)\THER03_1.AA5
> 5B4D    3390    $(DASDDIR8)\THER04_1.AA6
> 5B4E    3390    $(DASDDIR8)\THER05_1.AA7
> 5B4F    3390    $(DASDDIR8)\THER06_1.AA8
> 5B50    3390    $(DASDDIR8)\WORK01_1.AA9
> 5B51    3390    $(DASDDIR8)\SMS001_1.AAA
> 5B52    3390    $(DASDDIR8)\SMS002_1.AAB
> 5B53    3390    $(DASDDIR8)\SMS003_1.AAC
> 5B55    3390    $(DASDDIR8)\PAGE01_1.5B55
> # 5B56    3390    $(DASDDIR8)\TRANS01.5B56
>
> # TAPE Devices
>
> 0590-0591    3490    E:\Hercules\Zos18\tape\
>
> # CTC Adapters
>
> 0E20.2 CTCI 192.168.2.51 192.168.2.47
>
>
> Regards
> BLM
>

Paolo,

     I've seen this in z/VM when IPL'ing a VM/ESA guest on real hardware.  My
circumstances were admittedly different, but could you check a couple things and
let the group know?

1) What is your terminal CONMODE setting?   To IPL some operating systems, there
is a requirement that the CONMODE be 3270.

2) How much memory is defined in the 370 mode guest that you are trying to IPL?
Just in case there is some peculiar side effect, I'd recommend that you limit it
to 16MB before trying to IPL.

As an aside, there was a bug in VM/ESA up to about 2.4 that prevented 2nd level
VM's from manipulating tape drives.  (This created a real challenge for me in
disaster recovery exercise several years ago.)  The details are fuzzy, but I
remember we had to map the guest's disks to the first level directory and
restore them at first level before we could IPL the restored system at second
level.

                                                                              
One last tidbit:  the following comes from the help page for HCP453W:

Programmer Response:  To determine the reason for the loop, examine the
program-check information in page zero of your virtual storage.  If this error
occurred immediately after the IPL command, the problem may be that you are
trying to run a 370 guest in XA mode, or the reverse (issue the QUERY SET
command to find out the current MACHINE setting).  In this case, issue the SET
MACHINE command to select the proper mode.


That's all the light I can shed; I hope there's something useful in it.  Good
Luck.

Jim

--- In hercules-390@yahoogroups.com, "paoloG" <crc@...> wrote:
>
> Hi all,
> The IPL command in a 370 mode guest of VM/ESA 2.4 doesn't work.
> Any kind of IPL (from dasd-tape-reader) gives the same message; for example
IPL from an empty card reader:
>
> IPL 00C
> HCPGIR453W CP entered; program interrupt loop.
>
> from tape:
>
> IPL 181
> HCPGIR453W CP entered; program interrupt loop.
>
> An I/O trace shows that IPL command fails without even trying to do any I/O on
the IPL device.
>
> I've noticed that in Hercules 3.05 the 370 mode guest IPL is working; so I've
made some research and have discovered that the offending revision of Hercules
is:
>
> Author: ivan
> Revision Date: Mon, 8 Dec 2008 20:38:20 UTC
> Revision comments: Fix SIE DAT Issue with ESA/390 Guest on z/Arch host with
>2GB of storage
>
> In any CSV version before that date IPL in a 370 guest machine works fine; to
do a simple test in any CMS guest you can IPL 00C with an empty card reader:
>
> SET MACH 370
> IPL 00C
>
> If IPL works you get this message:
>
> HCPVMJ232E IPL UNIT ERROR; CSW 00000000 02000000 SNS 40
> HCPGIR450W CP entered; disabled wait PSW 00060000 00000232
>
> If IPL doesn't work you'll get this one:
>
> HCPGIR453W CP entered; program interrupt loop.
>
>
> Hoping that some Hercules developer can correct the error.
>
> Regards.
>

I'm using a Aluminium Macbook/64 bit with Leopard (OS X 10.6.1). I
installed the Leopard download of Hercules from here:
http://www.hercules-390.org/hercules-3.06-leopard.dmg

Here's my startup output...

*** start output ***

MacBook:conf nigeldefreitas$ sudo hercules -f hercules.cnf
Hercules Version 3.06
(c)Copyright 1999-2007 by Roger Bowler, Jan Jaeger, and others
Built on Jan 9 2009 at 20:10:10
Build information:
Modes: S/370 ESA/390 z/Arch
Max CPU Engines: 8
Using setreuid() for setting privileges
Dynamic loading support
Loadable module default base directory is /usr/local/lib/hercules
Using shared libraries
No External GUI support
HTTP Server support
Regular Expressions support
Automatic Operator support
Machine dependent assists: cmpxchg1 cmpxchg4 cmpxchg8
Running on MacBook.local Darwin-10.0.0.Darwin Kernel Version 10.0.0:
Fri Jul 31 22:47:34 i386 MP=2
Crypto module loaded (c) Copyright Bernard van der Helm, 2003-2008
Active: Message Security Assist
Message Security Assist Extension 1
Message Security Assist Extension 2
HHCCF020W Vector Facility support not configured
HHCCF077I Engine 0 set to type 0 (CP)
cckd invalid keyword: cache
HHCCF090I Default Allowed AUTOMOUNT directory = "/Users/nigeldefreitas/tapes/"
HHCCF091S Invalid AUTOMOUNT directory: "/tapes": No such file or directory
HHCIN900I Begin Hercules shutdown
HHCIN901I Releasing configuration
HHCIN902I Configuration release complete
HHCIN903I Calling termination routines
HHCHD900I Begin shutdown sequence
HHCHD901I Calling hdl_term
HHCHD950I Begin HDL termination sequence
HHCHD951I Calling module *Hercules cleanup routine
HHCHD952I Module *Hercules cleanup complete
HHCHD959I HDL Termination sequence complete
HHCHD902I hdl_term complete
HHCHD901I Calling logger_term
HHCLG014I logger thread terminating
HHCHD902I logger_term complete
HHCHD909I Shutdown sequence complete
HHCIN904I All termination routines complete
HHCIN909I Hercules shutdown complete
HHCHD900I Begin shutdown sequence
HHCHD909I Shutdown sequence complete
MacBook:conf nigeldefreitas$

*** end output ***

and the config file I'm using....

*** start cnf file ***

####################################################################
# HERCULES EMULATOR CONTROL FILE #
# (Note: not all parameters are shown) #
####################################################################


#
# System parameters
#


ARCHMODE ESA/390
OSTAILOR OS/390
LOADPARM 0120....

CPUSERIAL 000611
CPUMODEL 3090
CPUVERID FD
LPARNAME HERCULES
MODEL EMULATOR
PLANT ZZ
MANUFACTURER HRC
MAINSIZE 64
XPNDSIZE 0
NUMCPU 1
NUMVEC 1
ENGINES CP
SYSEPOCH 1900
YROFFSET -28
TZOFFSET -0500

HTTPROOT /usr/local/share/hercules/
HTTPPORT 8081 NOAUTH

CCKD cache=8
SHRDPORT 3990

PANTITLE "My own private MAINFRAME!"
PANRATE FAST
LOGOPT TIMESTAMP
CODEPAGE default
CNSLPORT 3270
CONKPALV (3,1,10)
LEGACYSENSEID OFF

HERCPRIO 0
TODPRIO -20
DEVPRIO 8
CPUPRIO 15

TIMERINT DEFAULT
TODDRAG 1.0
DEVTMAX 8

DIAG8CMD disable
SHCMDOPT disable

DEFSYM TAPEDIR "$(HOME)/tapes"
AUTOMOUNT $(TAPEDIR)
AUTOMOUNT +/tapes
AUTOMOUNT -/tapes/vault

MODPATH /usr/local/hercules
LDMOD dyncrypt

PGMPRDOS restricted
ECPSVM no
ASN_AND_LX_REUSE disable

AUTO_SCSI_MOUNT no
MOUNTED_TAPE_REINIT allow

INCLUDE mydevs.cfg
IGNORE INCLUDE_ERRORS
INCLUDE optdevs.cfg


#
# Device statements
#


0009 3215-C /

000A 1442 adrdmprs.rdr
000C 3505 jcl.txt ascii trunc
000D 3525 pch00d.txt ascii
000E 1403 prt00e.txt

001F 3270 * 192.168.0.1
0200.4 3270 * 192.168.0.0 255.255.255.0
0220.8 3270 GROUP1 192.168.100.0 255.255.255.0
0228.8 3270 GROUP2
0230.16 3270

0000 SYSG SYSGCONS

0120 3380 ${DASD_PATH=dasd/}mvsv5r.120
0121 3380 ${DASD_PATH=dasd/}mvsv5d.121
0122 3380 ${DASD_PATH=dasd/}mvswk1.122
0123 3380 192.168.1.100

0140 3370 dosres.140
0141 3370 syswk1.141
0300 3370 sysres.300

0400 CTCT 30880 192.168.100.2 30880 2048
0401 CTCT 30881 192.168.100.2 30881 2048
0420.2 CTCI 192.168.200.1 192.168.200.2
# 0440.2 LCS -n /dev/net/tun 192.168.200.2

0580 3420 /dev/nst0 # SCSI (Linux or Windows)
0581 3420 \\.\Tape0 # SCSI (Windows only)
0582 3420 ickdsf.aws noautomount
0583 3420 /cdrom/tapes/uaa196.tdf
0584-0587 3420 $(TAPEDIR)/volumes.$(CUU) maxsizeM=170 eotmargin=131072

0590 3480 /dev/nst0 --no-erg --blkid-32 # Quantum DLT SCSI

0023 2703 lport=3780 rhost=localhost rport=3781 dial=no

*** end cnf file ***

Any ideas what I'm doing incorrectly here? I tried creating a folder
called "tapes" in the location specified, but that had no effect. I
commented the LCS line but that had no effect either: # 0440.2 LCS -n
/dev/net/tun 192.168.200.2

I installed tun tap, but didn't perform any additional configuration
(just installed with defaults by double-clicking the package). I'm not
sure why I get the tapes
message even after I manually create the tapes folder in OS X. I'm
using this command to launch "sudo hercules -f hercules.cnf" where my
hercules.cnf file is located here:
/Users/nigeldefreitas/Projects/Hercules - Mainframe Emulator/conf/

Thanks.

--
Nigel DeFreitas



--
Nigel DeFreitas

Hello!
Mike, the link expired. You might want to try again with that. In addition
the site wanted me to register for it. (Which I am not about to do.)

--
Gregg C Levine hansolofalcon@...
"The Force will be with you always." Obi-Wan Kenobi
 


> -----Original Message-----
> From: hercules-390@yahoogroups.com [mailto:hercules-390@yahoogroups.com]
On
> Behalf Of edamjr
> Sent: Friday, November 06, 2009 8:42 PM
> To: hercules-390@yahoogroups.com
> Subject: [hercules-390] Hercules on SiCortex
>
> Since no other bugger has tried it, I bought a box on ebay:
>
> http://www.facebook.com/album.php?aid=2037698&id=1528659644&l=6c0b26d48
>
> I'll be playing with Herc on it over the next week or two. In my copious
free time.
>
> Mike

Kayhan,

     It sounds like you are trying to read from your write side, and write to
your read side.  In a CTC connection, there are two channels, in your case, E20
and E21, to provide a read path and a write path for the network traffic.  By
convention, TCPIP reads from the lower address and writes to the upper address. 
This results pretty quickly in both ends reading from the E20 CTC and writing to
the E21 CTC.  My first thought to fix this paralleled yours - switch the
connections somewhere:

> CTCA 0E21 COUPLED BY LINUX43 0E20
> CTCA 0E20 COUPLED TO LINUX43 0E21

It didn't work for me, either.  But, I found (with some help from the folks
here) that there is a 0/1 switch in the PROFILE TCPIP device definitions for a
CTC

> DEVICE DEVÞ0E20 CTC E20LINK   ETH0     CTC 0

Try

> DEVICE DEVÞ0E20 CTC E20LINK   ETH0     CTC 1

and couple the CTCA's straight (E20 to E20 and E21 to E21) and see what happens.

Good Luck,

Jim

--- In hercules-390@yahoogroups.com, "k_tanriverir" <k_tanriverir@...> wrote:
>
>
> While attempting to install SuSE SLES9 /S390 with CTC connection under
> zVM in Hercules, I have got the following message:
>
> ch-0.0.0e21 (TX in ch_action_txretry): Busy Ð
>
>
>
> How can I solve this problem?
>
> Regards,
>
>
>
> Kayhan Tanrýverir
>
>
>
>        CTC channels are 0E20 :read and 0E21:write
>
>
>
> The CTC device statement(s) from my Hercules configuration file:
>
>
> 0E20-0E21 CTCI -n 00-15-B7-FF-3F-61 192.168.10.85 0.0.0.0
>
>
> The TCP/IP configuration statements for VM operating system my running
> under Hercules:
>
>
> DEVICE DEVÞ0E20 CTC E20LINK   ETH0     CTC 0   DEVÞ0E20 MTU
> 1500... HOME192.168.10.85 255.255.255.0 ETH0... GATEWAY192.168.10.1
> 255.255.255.0   =    ETH0 1500  ...DEFAULTNET 192.168.10.1    ETH0
> 1500 ...START DEVÞ0E20
>
>
> When I login to Linux machine I have got the correct messages:
>
>
> CTCA 0E20 DEFINED                       CTCA 0E21 DEFINED
> CTCA 0E21 COUPLED BY LINUX43 0E20       CTCA 0E20 COUPLED TO LINUX43
> 0E21       CTCA 0E20 COUPLED BY LINUX43 0E21       CTCA 0E21 COUPLED TO
> LINUX43 0E20
>
>
> IP address of LINUX43 is : 192.168.10.85
>
> Default gateway is : 192.168.10.1
>
> It is successfully ping 192.168.10.1 from 192.168.10.85
>
>
>
> DTCPARMS member is below:
> **************************************************************** *
> SYSTEM DTCPARMS created by DTCIPWIZ EXEC on 31 Oct 2009                *
> Configuration program run by MAINT at 19:26:38
> ****************************************************************
> nick.TCPIP    :type.server
> :class.stack
> :attach.0E20-0E21
>
>
> ******  SLES9 Installation Messages *******
>
> ctc0: read: ch-0.0.0e20, write: ch-0.0.0e21, proto: 3
>
> ctc0 detected.
>
> ctc0 is available, continuing with network setup.
>
>
>
> Please enter your full host name, e.g. 'linux.example.com'
> (linux.example.com):
>
> linux.vm
>
> Please enter your IP address, e.g. '192.168.0.1' (192.168.0.1):
> 192.168.10.86
>
> Please enter the IP address of your peer, e.g. '192.168.0.254'
> (192.168.0.254):
>
> 192.168.10.1
>
> Please enter the IP address of the DNS server or 'none' for no DNS
> (none): none
>
> Please enter the MTU (Maximum Transfer Unit),
>
> leave blank for default: (1500): 1500
>
>
>
> Trying to ping my IP address:
>
> PING 192.168.10.86 (192.168.10.86) 56(84) bytes of data.
>
> 64 bytes from 192.168.10.86: icmp_seq=1 ttl=64 time=0.789 ms
>
> 64 bytes from 192.168.10.86: icmp_seq=2 ttl=64 time=1.09 ms
>
> 64 bytes from 192.168.10.86: icmp_seq=3 ttl=64 time=1.38 ms
>
>
>
> --- 192.168.10.86 ping statistics ---
>
> 3 packets transmitted, 3 received, 0% packet loss, time 2062ms
>
> rtt min/avg/max/mdev = 0.789/1.088/1.384/0.245 ms
>
> Trying to ping the IP address of the peer:
>
> PING 192.168.10.1 (192.168.10.1) 56(84) bytes of data.
>
> ch-0.0.0e21 (TX in ch_action_txretry): Busy Ð
>
>
>
> --- 192.168.10.1 ping statistics ---
>
> 10 packets transmitted, 0 received, 100% packet loss, time 9147ms
>
>
>
> Warning: The peer address 192.168.10.1 did not ping.
>
> Statistics from ctc0:
>
> rx_dropped: 1
>
> rx_length_errors: 1
>
>
>
>
>
>
>
> [Non-text portions of this message have been removed]
>

Hi all,
The IPL command in a 370 mode guest of VM/ESA 2.4 doesn't work.
Any kind of IPL (from dasd-tape-reader) gives the same message; for example IPL
from an empty card reader:

IPL 00C
HCPGIR453W CP entered; program interrupt loop.

from tape:

IPL 181
HCPGIR453W CP entered; program interrupt loop.

An I/O trace shows that IPL command fails without even trying to do any I/O on
the IPL device.

I've noticed that in Hercules 3.05 the 370 mode guest IPL is working; so I've
made some research and have discovered that the offending revision of Hercules
is:

Author: ivan
Revision Date: Mon, 8 Dec 2008 20:38:20 UTC
Revision comments: Fix SIE DAT Issue with ESA/390 Guest on z/Arch host with >2GB
of storage

In any CSV version before that date IPL in a 370 guest machine works fine; to do
a simple test in any CMS guest you can IPL 00C with an empty card reader:

SET MACH 370
IPL 00C

If IPL works you get this message:

HCPVMJ232E IPL UNIT ERROR; CSW 00000000 02000000 SNS 40
HCPGIR450W CP entered; disabled wait PSW 00060000 00000232

If IPL doesn't work you'll get this one:

HCPGIR453W CP entered; program interrupt loop.


Hoping that some Hercules developer can correct the error.

Regards.

While attempting to install SuSE SLES9 /S390 with CTC connection under
zVM in Hercules, I have got the following message:

ch-0.0.0e21 (TX in ch_action_txretry): Busy Ð



How can I solve this problem?

Regards,



Kayhan Tanrýverir



        CTC channels are 0E20 :read and 0E21:write



The CTC device statement(s) from my Hercules configuration file:


0E20-0E21 CTCI -n 00-15-B7-FF-3F-61 192.168.10.85 0.0.0.0


The TCP/IP configuration statements for VM operating system my running
under Hercules:


DEVICE DEVÞ0E20 CTC E20LINK   ETH0     CTC 0   DEVÞ0E20 MTU
1500... HOME192.168.10.85 255.255.255.0 ETH0... GATEWAY192.168.10.1
255.255.255.0   =    ETH0 1500  ...DEFAULTNET 192.168.10.1    ETH0
1500 ...START DEVÞ0E20


When I login to Linux machine I have got the correct messages:


CTCA 0E20 DEFINED                       CTCA 0E21 DEFINED
CTCA 0E21 COUPLED BY LINUX43 0E20       CTCA 0E20 COUPLED TO LINUX43
0E21       CTCA 0E20 COUPLED BY LINUX43 0E21       CTCA 0E21 COUPLED TO
LINUX43 0E20


IP address of LINUX43 is : 192.168.10.85

Default gateway is : 192.168.10.1

It is successfully ping 192.168.10.1 from 192.168.10.85



DTCPARMS member is below:
**************************************************************** *
SYSTEM DTCPARMS created by DTCIPWIZ EXEC on 31 Oct 2009                *
Configuration program run by MAINT at 19:26:38
****************************************************************
nick.TCPIP    :type.server
:class.stack
:attach.0E20-0E21


******  SLES9 Installation Messages *******

ctc0: read: ch-0.0.0e20, write: ch-0.0.0e21, proto: 3

ctc0 detected.

ctc0 is available, continuing with network setup.



Please enter your full host name, e.g. 'linux.example.com'
(linux.example.com):

linux.vm

Please enter your IP address, e.g. '192.168.0.1' (192.168.0.1):
192.168.10.86

Please enter the IP address of your peer, e.g. '192.168.0.254'
(192.168.0.254):

192.168.10.1

Please enter the IP address of the DNS server or 'none' for no DNS
(none): none

Please enter the MTU (Maximum Transfer Unit),

leave blank for default: (1500): 1500



Trying to ping my IP address:

PING 192.168.10.86 (192.168.10.86) 56(84) bytes of data.

64 bytes from 192.168.10.86: icmp_seq=1 ttl=64 time=0.789 ms

64 bytes from 192.168.10.86: icmp_seq=2 ttl=64 time=1.09 ms

64 bytes from 192.168.10.86: icmp_seq=3 ttl=64 time=1.38 ms



--- 192.168.10.86 ping statistics ---

3 packets transmitted, 3 received, 0% packet loss, time 2062ms

rtt min/avg/max/mdev = 0.789/1.088/1.384/0.245 ms

Trying to ping the IP address of the peer:

PING 192.168.10.1 (192.168.10.1) 56(84) bytes of data.

ch-0.0.0e21 (TX in ch_action_txretry): Busy Ð



--- 192.168.10.1 ping statistics ---

10 packets transmitted, 0 received, 100% packet loss, time 9147ms



Warning: The peer address 192.168.10.1 did not ping.

Statistics from ctc0:

rx_dropped: 1

rx_length_errors: 1







[Non-text portions of this message have been removed]

On Nov 7, 2009, at 10:02 PM, Tony Harminc wrote:

> 2009/11/7 Adam Thornton <adam@...>:
>
> > I think that GNU Mailman is a much better mailing list manager than
> > LISTSERV, and it's free.
>
> Free software, sure, but is there somewhere that'll host it for free?
> Much as I don't like or trust Yahoo, I'm not sure who I would trust to
> set up and run GNU Mailman for these lists, keep the archives, etc.
>
> Why is it better than LISTSERV, btw?
> _,___
>

Almost zero work to set up, open source and reasonably readable code,
does nice web archives out of the box with reasonable threading
options, easy to integrate with Exim, sane startup/shutdown scripts.

Adam

[Non-text portions of this message have been removed]