SNDNETF issues

There is a  job in our system(SYS A) that tries to send one save file to the remote system(SYS B). In the same job where we are sending save file to remote system, after the command SNDNETF, we are using a command RUNRMTCMD to execute a program in the remote system SYS B.  This remote program in the SYS B receives this net file and doing processing. Currently this process is not working properly(i.e it is not receiving save file).  I checked the WRKDSTQ in the SYS A(sending system) and found that status "Rty-Fail". I am not exactly sure what is this error message and how to make this successful.  Can anyone answer me ?
Who is Participating?
Gary PattersonConnect With a Mentor VP Technology / Senior Consultant Commented:
Distribution Services is having trouble completing the distribution to the remote system, has retried the maximum number of times, and has put the queue into "Retry-Fail" status.  

If you use the WRKDSTQ command and put your cursor on the Rty-Fail status and press F1, you will find detailed help text for this error:

Rty-Fail    The sender job is active.  However, the number of retry attempts for the queue has been reached.  The sender will not attempt to send again until one of the following occurs:                                                    o  The current sender job ends and a new sender is                   started.                                                        o  The start or force time occurs.                                o  The queue is sent (SNDDSTQ or option 2).                        o  A remote receiver job starts the local sender.                  o  The send-while-receive function is enabled, and a                 receiver starts.                                                o  The distribution queue is held and then released.

Try using option 2 to force a send, try holding and releasing the queue.  Try ending and restarting distribution services at both ends.

Check the job log for the QSNADS subsystem sender job associated with the queue (job is named the same as the remote destination associated with the queue).  Do a WRKDSTQ, F10 to see the remote location name.  Then do a WRKSBSJOB QSNADS to see the sender jobs in QSNADS.  Look at the job log of the sender job (5 Work with, 10 - Job log, F10 - Detailed Messages), then roll through the messages and pull up extended help (cursor on message, F1) on any relevant error messages.  Post the extended error messages here if you need more help.

Has this ever worked correctly?  Has something changed?  Are you experiencing communication problems between the two hosts?

- Gary Patterson

Check out my EE profile:

MurpheyApplication ConsultantCommented:

Check the Configuration status on SYS B : WRKCFGSTS
DO this for *CTL and *LIN

srkumarAuthor Commented:
Gary - Thanks for your comments. It really helped a lot.
Cloud Class® Course: Microsoft Office 2010

This course will introduce you to the interfaces and features of Microsoft Office 2010 Word, Excel, PowerPoint, Outlook, and Access. You will learn about the features that are shared between all products in the Office suite, as well as the new features that are product specific.

Gary PattersonVP Technology / Senior Consultant Commented:
Happy to help.  Did you get it up and running?

- Gary
srkumarAuthor Commented:
Yes it was up and running.
Gary PattersonVP Technology / Senior Consultant Commented:
Glad to hear it.  So what fixed it?
srkumarAuthor Commented:
holding and releasing the queue
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.