Request req to agent failed: value=n, code=rc, reason=rsn
Explanation: An error occurred with the VFTP client running agent communication services. Messages SFMC900I and SFMC950I are also displayed to define the source of the error.
req Internal request function:
1 Step initialization
2 Session initiation
3 Session detail log
4 WTO message request
5 Transfer size (client only)
6 Confidence of success
7 Session termination
8 Step termination
9 Command rejection (server only)
10 Trace entry (server only)
11 SFM record
12 Multiple transfer (MGET/MPUT)
13 Remote filename
14 User data
15 Login failure
16 VST security parameters
n Return value:
-1 Error in agent communications
-2 Error encountered with the NMI interface
-3 Data space processing error
rc Return code; see the following tables.
rsn Reason codes vary according to the result from the request function.
When n (return value) is -1, use this table to interpret the rc value:
| rc | Definition | Action |
| 8 | Storage allocation error. | Rerun the job with a larger REGION size. |
| 12 | Failed to load NMI routine EZBNMIFR. | Contact SDS Technical Support. |
| 16 | Field exceeds maximum length. Session detail text exceeded buffer size. | Contact SDS Technical Support. |
| 20 | No connection found. NMI could not establish a connection. | Contact SDS Technical Support. |
| 24 | More than one NMI connection returned for the FTP control connection. | Contact SDS Technical Support. |
| 28 | Unrecognized (invalid) socket address from NMI. | Contact SDS Technical Support. |
| 32 | The client was not able to find the agent’s token. This can happen if the agent has not run since the last IPL. | Start the VFTP agent. |
| 36 | Cannot locate SAAB. Invalid SAAB eyecatcher found. | Contact SDS Technical Support. |
| 44 | Cannot locate stack name. No TCPIP stack identified for the NMI. | Contact SDS Technical Support. |
| 52 | The VFTP administrator established a client configuration rule that says this FTP job must run over a SOCKS server, but no SOCKS server was detected. | Use a SOCKS server for the FTP connection. |
| 128 | Invalid (unsupported) request received. | Contact SDS Technical Support. |
When n (return value) is -2, the rc and rsn values are documented in the z/OS Communications Server: IP Programmer’s Guide, under TCP/IP callable NMI (EZBNMIFR). Contact SDS Technical Support.
When n (return value) is -3, use this table to interpret the rc value:
| rc | Definition | Action |
| 4 | No data now | Call back soon. If the problem persists, contact SDS Technical Support. |
| 8 | Invalid request | Contact SDS Technical Support. |
| 12 | Unable to obtain buffer | Contact SDS Technical Support. |
| 16 | Error reading dataspace | Contact SDS Technical Support. |
| 20 | An abend occurred | Contact SDS Technical Support. |
| 32 | Agent stopped logging | Try later. If the problem persists, contact SDS Technical Support. |
| 36 | Record too big for dataspace buffer | Contact SDS Technical Support. |
| 40 | ALET/STOKEN mismatch | Contact SDS Technical Support. |
| 44 | ALET is not valid | Contact SDS Technical Support. |
| 64 | Agent is coming down | Restart the agent. |
| 128 | Fatal error | Contact SDS Technical Support. |