× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Coupla ideas...

You need to find out if the transfer is even making off the source system or
if it is received but not properly distributed at the target system.  Use
the DSPDSTLOG command to try to determine the problem.  Prompt it up and
enter the time frame you're interested in and change the ENTTYP parm to
*ALL.  You can then see just what is happening.  

Snags that I've hit with transfers that have worked "forever" are mode
descriptions that have been deleted, local net IDs changing, or QSNADS not
running at the target machine.  Mode deletion seems to be a favorite.

Two commands of use here are DSPNETA and CFGDSTSRV.

HTH,
Tom D.

 |  -----Original Message-----
 |  From: jmoreno@xxxxxxxxxxxxxxxx [mailto:jmoreno@xxxxxxxxxxxxxxxx]
 |  Sent: Tuesday, June 01, 2004 13:47
 |  To: Midrange-L@xxxxxxxxxxxx
 |  Subject: Cannot figure out SNADS transfer problem
 |  
 |  
 |  
 |  
 |  
 |  
 |  Hello all,
 |  
 |  I have two systems and I can SNADS (files and/or spooled 
 |  files) from system
 |  A to System B with no problems.
 |  However from System B to System A,  I cannot SNADS (files 
 |  and/or spooled
 |  files). I just run into problems.
 |  No error logs, no QSYSOPR messages no History messages. I 
 |  cannot figure it
 |  out.
 |  The System Storage threshold is set at 95 % and we are 
 |  running at 88%.
 |  I have ended and restarted the QSNADS subsystems, all the 
 |  Host servers.
 |  Started the TCP Server *DDM
 |  and yet .. the files and/or spooled files do not get to the 
 |  target system
 |  ..
 |  
 |  
 |  Where else should I look for ?
 |  
 |  Your advice will be greatly appreciated.
 |  
 |  Jorge Moreno
 |  Overseas Military Car Sales
 |  Woodbury, New York
 |  
 |  + - - - - - - - - - - - - - - - - - - - - - - - -
 |  This email, including its attachments, may contain 
 |  information that is
 |  confidential and may be protected by federal and/or state laws and
 |  regulations, or other confidentiality privileges.  This 
 |  email, including
 |  its attachments, may contain non-public information; therefore it is
 |  intended to be conveyed only to the designated 
 |  recipient(s).  If you are
 |  not an intended recipient, please delete this email, including its
 |  attachments, and notify the sender.  The unauthorized use, 
 |  dissemination,
 |  distribution or reproduction of this email, including its 
 |  attachments, is
 |  prohibited and may be unlawful.
 |  + - - - - - - - - - - - - - - - - - - - - - - - -
 |  
 |  --
 |  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.
 |  
 |  


As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.