RE: CPYTOIMPF -- MIDRANGE-L

Thanks Eric.  That sort of makes sense.  Change the retries and the timeout 
times to let Windows catch up with the 400!  I'll let you know if it works.



-----Original Message-----
From: DeLong, Eric [mailto:EDeLong@xxxxxxxxxxxxxxx] 
Sent: Thursday, April 03, 2003 1:54 PM
To: 'Midrange Systems Technical Discussion'
Subject: RE: CPYTOIMPF


Mary,

I changed our NetBios Description file to deal with a similar reliability 
issue. 

WRKNTBD (Work with NetBios Descriptions)

                         Display NetBIOS Description                
                                                            04/03/03 12:42:44
NetBIOS description  . . . . . . . :   QNTBIBM

Full buffer datagrams  . . . . . . :   *NO

Adaptive window interval . . . . . :   1000

Maximum window errors  . . . . . . :   0

Maximum receive data size  . . . . :   4168

Inactivity timer . . . . . . . . . :   30000

Response timer . . . . . . . . . . :   500

Acknowledgement timer  . . . . . . :   200

Maximum outstanding receives . . . :   1

Maximum outstanding transmits  . . :   1

Query timeout  . . . . . . . . . . :   500

NetBIOS retry  . . . . . . . . . . :   15

Allow multiple acknowledgement . . :   *YES

Prebuilt message packets . . . . . :   50

Packet confirms for restart  . . . :   2

DLC retries  . . . . . . . . . . . :   25

Ethernet standard  . . . . . . . . :   *IEEE8023

Text 'description' . . . . . . . . :   This NTBD is IBM Supplied


Honestly, I just sort of tried things until it seemed to get better.  It was 
totally a stab in the dark, so this might not help you at all.  Perhaps someone 
with more networking experience could explain more of the effects of these 
parms.  

As I recall, I only changed the NetBios retries and the prebuilt message 
packets, but there could have been others (Maybe DLC reties??)..... 

hth,
Eric DeLong
Sally Beauty Company
MIS-Project Manager (BSG)
940-898-7863 or ext. 1863



-----Original Message-----
From: Kern, Mary T [mailto:MKern4@xxxxxxxxxxxxxxxxx]
Sent: Thursday, April 03, 2003 9:15 AM
To: midrange-l@xxxxxxxxxxxx
Subject: CPYTOIMPF


I have a CL program that sends files (using the QNTC file system) to a Windows 
2000 SQL server in another building on campus and also to an NT
server that sits right next to the 400.   It works fine most of the time.
Occasionally, (semi regularly) it fails to send the file to the SQL server. The 
transfer to the NT server in our computer room *never* fails.  I have asked the 
"server gods" on campus.  They say they can see no reason for it to fail on 
their end.  If we IPL, the transfer will work again ... for a while.  
Apparently, we are stopping some service and not restarting it.  Any ideas what 
would cause the transfer to fail out of our building but not inside?  


¤»¥«¤»§«¤»¥«¤»§«¤»¥«¤»§«¤»¥«¤»§«¤»¥«¤»§«¤»¥« 
Mary Kern 
Director of Information Services 
University of Toledo Foundation 
2801 W Bancroft St Mail Stop 319
Toledo, OH 43606
Voice: (419) 530-7730  (800) 640-0147 
Fax: 419-530-2895 
Email: mary.kern4@xxxxxxxxxxx
> Imagine there> '> s no countries, it isn> '> t hard to do;
> nothing to kill or die for, and no religion too. 
> Imagine all the people living life in peace.
> 
>                               John Lennon (1940 - 1980), Imagine
¤»¥«¤»§«¤»¥«¤»§«¤»¥«¤»§«¤»¥«¤»§«¤»¥«¤»§«¤»¥« 

_______________________________________________
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.