RETR, STOR, RNFR, RNTO, APPE, or DELE of data set fails

If RETR, STOR, RNFR, RNTO, APPE, or DELE for the data set fails, check for the following problems:
  1. Is the data set protected by a security system, such as RACF® or permission bits or a retention period?
  2. Is the data set being used at the server site by another program or user?
  3. Was the data set available to the system, or was it migrated or on an unmounted volume?
  4. Did the data set or member exist?
  5. For RETR or STOR commands, did a REST command immediately precede the RETR or STOR?

    If so, the client is attempting to restart a file transfer. The server cannot detect certain REST argument errors until the RETR or STOR command is processed. If the trace options CMD and FSC are active, the server reply and server trace output provide insight into whether the REST command is implicated. Verify that the client and server have reestablished the original file transfer environment before attempting the restart.

The following problems apply to MVS™ data sets only:
  1. Did the specified path name follow MVS data set naming conventions?
  2. Was the requested data set a type of supported data set organization (PS, PDS, or PDS member) on a supported device type (DASD or tape)?
  3. Were the path name specifications consistent with the type of data set? For example, if a member was requested, was the data set a PDS?
Parent topic: Data transfer problems