RE: EE connections including STRPASTHR, SNADS, SAVRSTLIB and DDM will hang for 20 seconds to 4 minutes

Rob,

I was quoting your remote file.
Mine is GPL/PENCOR06, no member, no data.

2/10/16 Display File Description
DSPFD Command Input
File . . . . . . . . . . . . . . . . . . . : FILE PENCOR06
Library . . . . . . . . . . . . . . . . . : *LIBL
Type of information . . . . . . . . . . . . : TYPE *MBRLIST
File attributes . . . . . . . . . . . . . . : FILEATR *ALL
System . . . . . . . . . . . . . . . . . . : SYSTEM *LCL
File Description Header
File . . . . . . . . . . . . . . . . . . . : FILE PENCOR06
Library . . . . . . . . . . . . . . . . . . : GPL
Type of file . . . . . . . . . . . . . . . : Physical
File type . . . . . . . . . . . . . . . . . : FILETYPE *DATA
Auxiliary storage pool ID . . . . . . . . . : 00001
Member List
(No members in file)

From IBM help text.

Remote file (RMTFILE) - Help

Specifies the name of the remote file as it is coded on the target
system. This file name must be specified in code page 500. The remote
file does not need to exist when the Distributed Data Management (DDM)
file is created.

This is a required parameter.

name
Specify the name of the remote file as it is known on the remote
system. If the remote system is a System i5, specify the file
name. The file name can be up to 10 characters in length. If
the remote system is a System/36, the file name is the same as
its System/36 file label. The file name can be up to eight
characters in length. If the remote system is a System/38, a
simple (unqualified) file name can be specified. The file name
can be up to 10 characters in length. Labels for all other
remote systems (including qualified file names for System/38)
must use *NONSTD followed by the remote file name in
apostrophes.

Paul

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Wednesday, February 10, 2016 10:51 AM
To: Midrange Systems Technical Discussion
Subject: RE: EE connections including STRPASTHR, SNADS, SAVRSTLIB and DDM will hang for 20 seconds to 4 minutes

<snip>
I see one exists on each LPAR, matches my LPAR name, PF with no members, created in 1997, never changed or used.
</snip>

That's why I picked it for a remote file.
But I'm confused. If the LIBRARY is SYSIBM and the file name is SYSDUMMY1 how does that match your lpar name?
And it should have a member, also named SYSDUMMY1.
It has one column, IBMREQD. And it's a very short variable length column.
Perhaps someone there initialized the contents to your lpar name? I have to look at the contents of it in hex mode.

The purpose of this table is this:
Back before SQL supported
VALUES INTO
You used to have to write a dummy sql select like SELECT CURRENT DATE FROM SYSIBM/SYSDUMMY1 INTO :myhostvariable Now you can do that with VALUES CURRENT DATE INTO :myhostvariable

Some people never change and still do the dummy select.



Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600 Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





From: "Steinmetz, Paul" <PSteinmetz@xxxxxxxxxx>
To: "'Midrange Systems Technical Discussion'"
<midrange-l@xxxxxxxxxxxx>
Date: 02/10/2016 10:41 AM
Subject: RE: EE connections including STRPASTHR, SNADS, SAVRSTLIB
and DDM will hang for 20 seconds to 4 minutes
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>



Rob,

What is the RMTFILE(SYSIBM/SYSDUMMY1) and how is it used?

I see one exists on each LPAR, matches my LPAR name, PF with no members,
created in 1997, never changed or used.

Paul

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
rob@xxxxxxxxx
Sent: Tuesday, February 09, 2016 2:24 PM
To: Midrange Systems Technical Discussion
Subject: RE: EE connections including STRPASTHR, SNADS, SAVRSTLIB and DDM
will hang for 20 seconds to 4 minutes

STRPASTHR, TELNET do not use DDM files. So changing that will have no
effect.

If you can ping it (and at least get back the right IP address even if
they block pings) then you can use that name in CRTDDMF.

There is a tiny risk that SNA DDM will use a different port than TCP DDM
and that may take some firewall work but, hey, you can always create a new
ddm file and test that first, eh?

SNDNETSPLF and SNDNETF don't give a RA about DDM. That's all tied up in
that CFGDSTSRV, and ADDDIRE, kind of stuff. Same as STRPASTHR, (only
STRPASTHR doesn't need ADDDIRE).

There are only two risks that I can think of:
1 - Getting the right location name. If you can telnet to it, or ping it,
then you've got the right location name.
2 - Port blocking. That's a really simple test by creating a DDM file
named differently yet pointing to the same location.
CRTDDMF FILE(TESTLIB/OTHERSITE) RMTFILE(SYSIBM/SYSDUMMY1)
RMTLOCNAME(OTHERSITE *IP) DSPPFM FILE(TESTLIB/OTHERSITE) If you can see
the contents of the remote SYSIBM/SYSDUMMY1 then the port is not blocked.

And if the CRTDDMF is not buried in code anywhere you do not have to
change ONE line of code to convert SBMRMTCMD.

Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600 Mail
to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





From: "Steinmetz, Paul" <PSteinmetz@xxxxxxxxxx>
To: "'Midrange Systems Technical Discussion'"
<midrange-l@xxxxxxxxxxxx>
Date: 02/09/2016 02:00 PM
Subject: RE: EE connections including STRPASTHR, SNADS, SAVRSTLIB
and DDM will hang for 20 seconds to 4 minutes
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>



Rob,

Does this only change the way SBMRMTCMD functions or does it impact other
areas.

Can I simply do a 2=Change DDM file
Change the Type . . . . . . . . . . . . . *SNA from current default of
*SNA to *IP?

Can remote location stay the same or does it need to change?

Remote location:
Name or address . . . . . . . PENCOR06

Will anything stop working?
Will STRPASTHR still work?
Will SNDSPLF and SNDNETF still work.

Paul

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Jeff Young
Sent: Tuesday, February 09, 2016 1:57 PM
To: Midrange Systems Technical Discussion
Subject: Re: EE connections including STRPASTHR, SNADS, SAVRSTLIB and DDM
will hang for 20 seconds to 4 minutes

Thanks Rob,
Back when, we used to have to use the ADDSVRAUTE command to setup each
user as authorized to the remote system. This was a giant PITA.
Glad that it is no longer needed.

Jeff Young
Sr. Programmer Analyst

On Tue, Feb 9, 2016 at 1:49 PM, <rob@xxxxxxxxx> wrote:

I think you're confusing relational database directory entries

ADDRDBDIRE.

These are used for sql connections like CONNECT TO MYLPAR. DDM is a
different animal.

I ran this on two lpars:
CRTUSRPRF DUMMY

I ran this on one lpar
CRTDDMF FILE(QGPL/GDI) RMTFILE(SYSIBM/SYSDUMMY1) RMTLOCNAME(gdi *IP)
and this on the other CRTDDMF FILE(QGPL/GDISYS)
RMTFILE(SYSIBM/SYSDUMMY1) RMTLOCNAME(gdisys *IP)

Signed on as DUMMY on either machine.
Do a DSPPFM QGPL/GDI or QGPL/GDISYS (whichever is appropriate) and it
works fine.

Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





From: Jeff Young <jyoung0950@xxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 02/09/2016 01:25 PM
Subject: Re: EE connections including STRPASTHR, SNADS, SAVRSTLIB
and DDM will hang for 20 seconds to 4 minutes
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>



Rob,
If I recall correctly, to use IP DDM, he needs to add a server
authorization entry on the target LPAR for *each* user that will
access it. Group profiles are *not* allowed.

Granted, my exposure to this was a long time ago, and it might have
changed since then.

Jeff Young
Sr. Programmer Analyst

On Tue, Feb 9, 2016 at 1:17 PM, <rob@xxxxxxxxx> wrote:

Prompt SBMRMTCMD. You have two prompts:
- Name of command
- DDM file.
Do you see name of lpar anywhere? No.

CRTDDMF FILE(MYLIB/MYLPAR)
RMTFILE(RMTLIB/RMTFILE)
RMTLOCNAME(mylpar.corp.mycompany.com *IP)

The key being change the default of *SNA to *IP.

QED.


Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





From: "Steinmetz, Paul" <PSteinmetz@xxxxxxxxxx>
To: "'Midrange Systems Technical Discussion'"
<midrange-l@xxxxxxxxxxxx>
Date: 02/09/2016 11:59 AM
Subject: RE: EE connections including STRPASTHR, SNADS,

SAVRSTLIB

and DDM will hang for 20 seconds to 4 minutes
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>



Rob,

STRPASTHR vs TELNET - We use both
SNADS DDM vs ip DDM - I thought with SBMRMTCMD it could only be name
of

a

remote LPAR. Tell me more.
SNDNETF does have a TCP version - SNDTCPSPLF

Paul

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf
Of rob@xxxxxxxxx
Sent: Tuesday, February 09, 2016 7:14 AM
To: Midrange Systems Technical Discussion
Subject: Re: EE connections including STRPASTHR, SNADS, SAVRSTLIB
and

DDM

will hang for 20 seconds to 4 minutes

I can maybe understand using EE for the SAVRST* genre but why would

anyone

still be using:
STRPASTHR vs TELNET
SNADS DDM vs ip DDM
using a snads based ddm file instead of an IP based one for
SBMRMTCMD

SNDNETF was a nice "fire and forget" method of sending a file to a

remote

system and let SNADS handle system outages, or the remote system
handle when it didn't feel like receiving a file due to conflicts
with other processes. But we weaned off of that.

I'm pretty sure there's an IP substitute for SNDNETSPLF. Maybe not

quite

the same as we used to use that to copy a spool file to another
output queue as a backup.

Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600

Mail

to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





From: "Steinmetz, Paul" <PSteinmetz@xxxxxxxxxx>
To: "'Midrange Systems Technical Discussion'"
<midrange-l@xxxxxxxxxxxx>
Date: 02/08/2016 04:17 PM
Subject: EE connections including STRPASTHR, SNADS, SAVRSTLIB

and

DDM will hang for 20 seconds to 4 minutes
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>



Anyone having intermittent issues with EE connections including

STRPASTHR,

SNADS, SAVRSTLIB and DDM will hang for 20 seconds to 4 minutes.
Sessions may also timeout and disconnect.

CORRECTION FOR APAR MA45188 :
-----------------------------
Several conditions can hang the RTP connection when the burst
timer is not restarted. One condition is where a data or burst
window is filled at the same time the burst timer fails to pop.
Another condition is burst timer can be checked and restarted if
needed when the short request timer pops. Also detection for a
missing burst timer window has been reduced from two seconds to
10 milisecs.

DESCRIPTION OF PROBLEM FIXED FOR APAR MA45260 :
-----------------------------------------------
Intermittently, the EE connection can hang for a few minutes and
then be dropped suddenly. This is happening about three times a
week. SNADS sender job got CPF5107, error code E015, and SNA
sense code 8002. E015 means UNBIND received, and sense code 8002
means data link failure. To recover, the customer must vary both
CTLD and DEVD OFF and ON.

CORRECTION FOR APAR MA45260 :
-----------------------------
The RTP alive timer on the target side system of the user's RTP
data connection on port 12003 timed out due to inactivity over
the previous three minute interval. The target side system then
initiated a new SYNC echo pending status exchange retry sequence
which also timed out due to the network dropping all packets sent
from target system on port 12003. This initiated a failed HPR path
switch resulting in a data link failure. Keep-alive TEST packets on
port 12000 do continue normal bidirectional flow. A code change was
made to add more status exchange requests sent from the target side
to detect network recovery sooner, thus preventing a retry timeout
and data link failure notification for this scenario.

I've applied MF61265, still having issues.
Open PMR since July 2015.
Problem is very intermittent, sometimes only once every two months.

2/6/16 failure started with a STRRMTCMD that just hung, over 24
hours,

had

to cancel.
STRPASTRH then also failed, had to vary off/on EE controllers.
SAVRSTOBJ resulted in damaged objects.

Per IBM support request, I'm setting up an hourly test job, with
traces, hopefully to recreate the error quicker.

TRCINT SET(*ON) TRCTBL(TRCEE) SIZE(700 *MB) TRCFULL(*STOPTRC) TRCTY
STRCMNTRC CFGOBJ(ETHVIRT00) CFGTYPE(*LIN) MAXSTG(32M) USRDTA(*MAX)

Paul




-----Original Message-----
From: Steinmetz, Paul
Sent: Tuesday, August 04, 2015 4:54 PM
To: 'Midrange Systems Technical Discussion'
Subject: RE: savrstobj and strpasthr both hanging for 2 to 4 minutes

Jim,

1) Utilizing AJS, I have two jobs on each LPAR.

I have both traces starting 1 minutes before the SAVRSTOBJ runs.
DLTCMNTRC CFGOBJ(ETHVIRT00) CFGTYPE(*LIN) TRCINT SET(*END)
TRCTBL('TRCEE') TRCINT SET(*ON) TRCTBL(TRCEE) SIZE(700 *MB)
TRCFULL(*STOPTRC) TRCTY...
STRCMNTRC CFGOBJ(ETHVIRT00) CFGTYPE(*LIN) MAXSTG(32M) USRDTA(*MAX) ...

I have both traces stopping 6 minutes later, which is slightly
longer

than

the SAVRSTOBJ hangs.

TRCINT SET(*OFF) TRCTBL('TRCEE') OUTPUT(*PRINT) ENDCMNTRC
CFGOBJ(ETHVIRT00) CFGTYPE(*LIN) PRTCMNTRC CFGOBJ(ETHVIRT00)
CFGTYPE(*LIN) CODE(*ASCII) FMTTCP(*YES)...

The TRCINT is 420,000 pages for the 6 minutes.
The PRTCMNTRC is 23,000 pages for the same window.

2) I ran a query over the AJS job history file (QAIJSHST), selecting
SAVRSTOBJ job when the run time was greater than 3 minutes,
indicating probably a failure/hang.
A normal run is 2 minutes or less.
Below are the results.
This reveals the SAVRSTOBJ hang is occurring more often than I
thought, not always reported.

Management requested that I move the SAVRSTOBJ job outside the 8 to
5 window, not to impact production.
Job now runs at 6:25.

08/04/15 10:48:24 AJS OBJCLNL SAVRSTOBJ failures PAGE 1
Job Name Last Run Last Start Last End Elapsed
Date Time Time Time
OBJCLNL 14/03/05 8:00 8:05 6
OBJCLNL 14/03/12 6:30 6:35 6
OBJCLNL 14/03/28 6:30 6:36 6
OBJCLNL 14/03/30 6:30 6:36 6
OBJCLNL 14/04/05 6:30 6:36 7
OBJCLNL 14/05/19 6:30 8:19 109
OBJCLNL 14/10/03 8:30 8:37 8
OBJCLNL 14/11/21 8:30 8:34 5
OBJCLNL 15/01/22 8:30 8:35 6
OBJCLNL 15/02/02 8:30 8:37 8
OBJCLNL 15/02/13 8:30 8:38 8
OBJCLNL 15/02/17 8:30 8:35 6
OBJCLNL 15/02/28 8:30 8:35 6
OBJCLNL 15/03/10 8:30 8:34 4
OBJCLNL 15/03/15 8:30 8:34 5
OBJCLNL 15/07/21 8:30 8:35 6
OBJCLNL 15/07/29 8:30 8:37 7
OBJCLNL 15/08/03 8:30 8:35 5
* * * E N D O F R E P O R T * * *

Paul

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf
Of

Jim

Oberholtzer
Sent: Tuesday, August 04, 2015 8:01 AM
To: 'Midrange Systems Technical Discussion'
Subject: RE: savrstobj and strpasthr both hanging for 2 to 4 minutes

Paul:

The only thing I'm seeing is an occasional B6007101 which is an APPN
session failure, and I know why those happened. A comm line went

down.

I think a comm trace and PMR are in your near future unfortunately.

--
Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects


-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf
Of Steinmetz, Paul
Sent: Monday, August 03, 2015 7:55 AM
To: 'Midrange Systems Technical Discussion'
Subject: RE: savrstobj and strpasthr both hanging for 2 to 4 minutes

Jim,

Did you ever get to check your LIC LOG entries.

We had a reoccurrence this morning.
The same job containing a SAVRSTOBJ job triggered the issue at 8:31.
Same LIC log entry
08002376 Source/Sink information 0701 0C00 08/03/15 08:31:11 6

At least two users that were already passed through on LPAR B -
Pencor06

,

were hung.
Once the SAVRSTOBJ completed, they were fine.

The SAVRSTOBJ normally takes 50 seconds.
When the STRPASTHR jobs notice the hanging, the SAVRSTOBJ takes
about 4 minutes.

Paul

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf
Of

Jim

Oberholtzer
Sent: Friday, July 24, 2015 2:41 PM
To: 'Midrange Systems Technical Discussion'
Subject: RE: savrstobj and strpasthr both hanging for 2 to 4 minutes

I will but it will be later since I'm not in the office until

Wednesday.

--
Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects


-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf
Of Steinmetz, Paul
Sent: Friday, July 24, 2015 10:38 AM
To: 'Midrange Systems Technical Discussion'
Subject: RE: savrstobj and strpasthr both hanging for 2 to 4 minutes

Jim,

Please check if you have this same error in your lic log at the time
of the failure.

08000F46 Source/Sink information 0701 0C00 07/21/15 08:32:17 6

Paul

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf
Of Steinmetz, Paul
Sent: Friday, July 24, 2015 10:38 AM
To: 'Midrange Systems Technical Discussion'
Subject: RE: savrstobj and strpasthr both hanging for 2 to 4 minutes

Jim,

On both your V5R4 and V7R1 systems?

1) Do you have EE configured?
2) Do you use SAVRST*** cmds?
3) Do you use STRPASTHR?

I also only see this once every several months.
We SAVRST*** both directions, but the issue only occurs A to B.
STRPASTHR is only A to B.

Paul


-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf
Of

Jim

Oberholtzer
Sent: Wednesday, July 22, 2015 4:53 PM
To: 'Midrange Systems Technical Discussion'
Subject: RE: savrstobj and strpasthr both hanging for 2 to 4 minutes

On that system about every 90 days or so.

On my V7Rx systems I've not had a problem.

I like the thought of the AJS to set the comm trace.

--
Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects


-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf
Of Steinmetz, Paul
Sent: Wednesday, July 22, 2015 3:48 PM
To: 'Midrange Systems Technical Discussion'
Subject: RE: savrstobj and strpasthr both hanging for 2 to 4 minutes

Jim,

How often do you see this?
I was not successful in gathering comm traces, they need to be
running prior to the error.
I'm considering setting up AJS scheduled jobs to start and end the
comm traces, during the same time we run the SAVRST*** jobs.

Paul

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf
Of

Jim

Oberholtzer
Sent: Wednesday, July 22, 2015 4:36 PM
To: 'Midrange Systems Technical Discussion'
Subject: RE: savrstobj and strpasthr both hanging for 2 to 4 minutes

Paul,

I've seen this behavior but it's on a V5R4 system so I'm not sure
it's relevant. When that happens we force the vary off of the
enterprise controller and the controller named for the target. Same
thing on the target side. Then restart the target then the local
system. There must be a TCP timeout somewhere because we have to
leave the controllers

varied

off for at least 3 minutes.

My own guess, and its' purely a guess is the HPR transport code has

some

sort of problem. IBM's gonna want a comm trace to diagnose it.

--
Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects


-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf
Of Steinmetz, Paul
Sent: Wednesday, July 22, 2015 3:16 PM
To: 'Midrange Systems Technical Discussion'
Subject: savrstobj and strpasthr both hanging for 2 to 4 minutes

I had a repeat of an old issue, savrstobj and strpasthr both hanging
for

2

to 4 minutes.
Had multiple previous posts on similar issue.

We use both SAVRSTOBJ and SAVRSTLIB to move objects between LPARS.
We also use STRPASTHR to connect from LPAR to LPAR.

Previously, Enterprise Extender controllers needed resets, not this

time.

This time, no error messages, no resets, just a hang.

Could this be a lock, seize, other issue?
Is there any reason why multiple processes (Strpasthr/Savrrstob)
cannot

be

started/initiated concurrently?

Any thoughts?

Thank You
_____
Paul Steinmetz
IBM i Systems Administrator

Pencor Services, Inc.
462 Delaware Ave
Palmerton Pa 18071

610-826-9117 work
610-826-9188 fax
610-349-0913 cell
610-377-6012 home

psteinmetz@xxxxxxxxxx
http://www.pencor.com/

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L)
mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To
subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please
take a moment to review the archives at

http://archive.midrange.com/midrange-l.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L)
mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To
subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please
take a moment to review the archives at

http://archive.midrange.com/midrange-l.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L)
mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To
subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please
take a moment to review the archives at

http://archive.midrange.com/midrange-l.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L)
mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To
subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please
take a moment to review the archives at

http://archive.midrange.com/midrange-l.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L)
mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To
subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please
take a moment to review the archives at

http://archive.midrange.com/midrange-l.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L)
mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To
subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please
take a moment to review the archives at

http://archive.midrange.com/midrange-l.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L)
mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To
subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please
take a moment to review the archives at

http://archive.midrange.com/midrange-l.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L)
mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To
subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please
take a moment to review the archives at

http://archive.midrange.com/midrange-l.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L)
mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To
subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please
take a moment to review the archives at

http://archive.midrange.com/midrange-l.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L)
mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To
subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please
take a moment to review the archives at
http://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L)
mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To
subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please
take a moment to review the archives at
http://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L)
mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To
subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please
take a moment to review the archives at
http://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L)
mailing

list

To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please
take a moment to review the archives at
http://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take
a moment to review the archives at
http://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take
a moment to review the archives at
http://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at http://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.