DRSF0106E A REMOTE SUBFILE COULD NOT BE READ FROM THE rdsName REMOTE DATA STORE. THE tpfrdsClient JAM RETURNED AN ERROR. JVM PID - pid STATUS CODE - statusCode REASON - reason

Where

rdsName
The remote data store name.
pid
One of the following values:
  • The process ID of the JVM that processed the update request if available.
  • N/A if the process ID is not available.
statusCode
The HTTP status code that was returned by the tpfrdsClient JAM.
reason
The reason text that was returned by the tpfrdsClient JAM. If the reason text is longer than 220 characters, only the first 220 characters are displayed.

Last updated

Added in 2020.

Explanation

An application tried to read a z/TPFDF subfile that is stored in a remote location, but the tpfrdsClient JAM returned an error.

System action

The read request is rejected. Control returns to the application with bit 0 of the SW00RTN field set to 1 and an error value set in SW00RSE. The error count for the specified data store is incremented.

User response

Complete the following steps:
  1. If the status code and reason in the message indicate that files are not deployed or a service is unavailable, enter the ZMDES command to ensure that the following deployment descriptors are deployed:
    • tpfrdsClient.srvc.json
    • tpfrdsClient.swagger.json
    • tpfrdsClient.jam.xml
    • tpffdes.srvc.json
    • tpffdes.swagger.json
    • Any remote data store descriptor that you want to use. The remote data store descriptors have a suffix of rds.properties.
    • Any remote file descriptor that you want to use. The remote file descriptors have a suffix of remfil.json.

    If you need to deploy any artifacts and the JAM is already running, you must recycle the JAM by entering ZJAMC RECYCLE NAME-tpfrdsClient.

  2. To locate the tpfrdsClient JAM error logs, complete the following steps:
    1. Enter ZJAMC DISPLAY NAME-tpfrdsClient.
    2. Find the JVM error logs in the /tpfjam/tpfrdsClient/pid directory, where pid is the JVM PID that was indicated in the previous step.
  3. Review the JVM error logs, status code, and reason text to diagnose the error.
  4. Correct the error.
  5. If the problem continues, contact IBM® Support.