SNDNETF command not working

30 pts.
Tags:
AS/400 commands
SNDNETF
No error message but --> The file via sndnetf says sent to 1 user but the receiving AS/400 does not get it via the wrknetf command??? SNDNETF FILE(QGPL/TESTCAT) TOUSRID((TEST CORP))

Answer Wiki

Thanks. We'll let you know when a new response is added.

Hi,

Try to find the error with command DSPDSTLOG.

Regards,
Wilson

What about WRKDSTQ? Does that give you any information?

HTH,
Debbie

Discuss This Question: 9  Replies

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.
  • ITGut
    Thanks bu the DSPDSTLOG gives me the screen Display Distribution Services Log Entry which is just kind of informational but thanks anyway.
    30 pointsBadges:
    report
  • Rrbond07
    I am having the same issue. The log tells me nothing. Source system says it was sent, but when I do a WRKNETF to receive the file it is not on the target system. I have a ticket in with IBM to see if there is something with the configuration list that has to be addressed. We switch to Enterprise Extender. It didn't work before extender was implemented either.
    735 pointsBadges:
    report
  • ToddN2000
    @Rrbond07: Use a WRKDIRE to make sure the user in question is in the directory.. If not there,  you need to add them with ADDDIRE.
    117,375 pointsBadges:
    report
  • TheRealRaven
    Start with WRKSBS to verify that the QSNADS subsystem is active on both systems. Then use WRKDSTQ to verify that the *DSTQ is in at LEAST "Waiting" status.

    Depending on what shows, the appropriate actions will change.
    29,400 pointsBadges:
    report
  • TheRealRaven
    Of course, you should also verify that both systems actually support SNDNETF.
    29,400 pointsBadges:
    report
  • mmanley
    This can be a very trying experience. If the process was working before, and you're using the same ID's to send and receive, it can frequently be caused by the line or controller being unavailable. After checking the obvious WRKDSTQ, if you find an unusual status, look at the line and controller associated with the distribution queues (on both systems). If you find one with a recovery pending, vary it off and back on. You probably need to end the QSNADS subsystems and restart them after you find the problem with the line or controller. We generally see this type problem after a communications failure. You might also look at the system operator message queue and see if there are messages about the remote controller not being contacted.
    470 pointsBadges:
    report
  • Rrbond07
    User(s) are in the system directory.  Checking the job log for QNFTP running under QSNADS shows that the file was sent to the user on the target system.  WRKNETF does not show the file made it.  It is successful if I send it to my ID on another system, but it is not successful when I send it to another user ID.  Have a Webex session with IBM this morning.  Will post information should we resolve the issue.
    735 pointsBadges:
    report
  • Rrbond07
    When you are sending a physical file from the source system to a different user on the target system, the source system will state that the file was sent.  Go to the target system and use command WRKNETF and prompt it.  The first parm is set at *CURRENT.  Change it to the user ID you sent the file to and the file will be there, or it should be.  You can then do RCVNETF.
    735 pointsBadges:
    report
  • Rrbond07
    Do command WRKNETF on the target system that you sent the file to.  exp-  WRKNETF TEST  It should show the file sent to user TEST.  Hope this helps.
    735 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

Thanks! We'll email you when relevant content is added and updated.

Following

Share this item with your network: