7023392: IND$FILE File Transfer trouble-shooting tips with Reflection for the Web

Basic Trouble-Shooting:

Verify that the Host session is at a location where it can launch the Host-based IBM IND$FILE file transfer program:

The user typically needs to be located at one of two following host screen locations:

1.) At the TSO “READY” prompt logged into the MVS system but outside of ISPF

2.) At the ISPF Menu Option 6 – “ISPF Command Shell”

– the cursor must be on the line that begins with the “===>”

– if there are two “===>” prompts on the screen, then make sure the cursor is located on the top one

Note: To determine if a prompt on the Host screen will allow access to the IND$FILE command:

– At the current cursor location type the words “IND$FILE” then press the ENTER key.

– If this command gives get back a TRANS type error or information that says “IBM File Transfer Program”
than the user can access the IND$FILE program on the Host from this location.

(Depending on the Host system, the user may have to press the ENTER key a second or third time to get back to the prompt they started at)


Resolve any TRANS errors that occur during the file transfer attempt:

The IBM IND$FILE file transfer application will generate a TRANS code for specific type of errors that can be detected. There are lists of these codes available in a variety of locations on the internet including: https://www.microfocus.com/documentation/rumba/desktop951/RumbaSystemAdminGuide/GUID-44F7F207-D285-43B0-92D0-B5E641DB5CC6.html. These errors typically appear in a Reflection for the Web dialog box for easy review and must be dismissed to continue. After an error of this sort, make sure the Host session has returned to a READY prompt before attempting the next file transfer.

One of the more common TRANS errors seen in TSO is the “TRANS18 – Incorrect Option Specified” error. To resolve this error on a SEND command, in the Reflection for the Web file Transfer settings change the “Record Format” from the value of “variable” to the value of “default”.


Confirm that the naming convention for the TSO file/dataset is correct:

Each element (username, dataset, member) of a TSO dataset is limited to a maximum of 8 characters.

When in doubt, use the fully qualified name of the TSO data set surrounded by single tick marks and include any member names inside matched sets of parenthesis.

Example:

‘username.dataset(member)’


Problems with figuring out PC File Names or Host Dataset/Member Names:

Reflection for the Web 12.1 HF80, Reflection for the Web 12.2 HF40, Reflection for the Web 12.3 HF5, and later versions now fully support the ability to drag-and-drop files during an IND$FILE file transfer to and from the members of a TSO dataset. In the past, the user had to use the SEND AS and RECEIVE AS options and type in the name of either the PC or the Host file including possible PC path information and Host dataset and member information. Having to remember to type the proper format could lead to errors especially in the TSO naming conventions. If the SEND AS or RECEIVE AS is failing, try using the drag-and-drop method so that Reflection for the Web is responsible for figuring out the proper naming conventions. Also, if using drag-and-drop and having a file name issue, try using the SEND AS or RECEIVE AS methods and manually enter in the appropriate names of the files.

Advanced Trouble-Shooting:

Examine Java Console Logs with Reflection for the Web Client logging turned on

The Java Console Log can be used to view historical data about previous IND$FILE file transfer success and failures. Short of taking a full-blown communication trace, the Java Console log can be used to quickly examine previous file transfers but before the Java Console can be used, there is some configuration that must occur.

1. In the Windows Control Panel, open the Java applet and go to the Advanced Tab and check the boxes under “Debugging” to “Enable tracing” and “Enable logging”.

2. In the Reflection for the Web Administrative WebStation, go to the Settings option and select the Logging tab, and check the box for “Write client debug output to console”.

3. Launch the Windows browser and the Reflection for the Web session.

The Java Console log can be viewed from the Java Console itself or from the Windows WordPad or Notepad application by opening the file that is saved in the C:Users<username>AppDataLocalLowSunJavaDeploymentlog location. Use the log file created with the *.trace extension for information about IND$FILE transfers.

What to look for:

– Look for the strings “IND$FILE PUT” or “IND$FILE GET” to find the start of the file transfer attempt. This line will show you the Host name that was generated by Reflection for the Web and sent to the Host, as well as any file transfer options specified. A quick check of this line can tell you if the correct or appropriate command was sent to the Host

– Look for a string that contains the words “TRANS…”. This line(s) will show the results of the file transfer. A TRANS03 is success, but other errors can be listed.


Communication Trace from Reflection for the Web

When all else fails, a communication trace taken in the Reflection for the Web session (from the Help / Trace menu) with a description of what was tested can be used to examine a IND$FILE transfer failure. The Reflection for the Werb communication trace shows all the exchanges of data with the Host including the commands sent and the responses received so if any Host error messages or data has scrolled off the screen it will be captured in this trace. This step requires that the trace be sent to Micro Focus Technical Support and a Support Engineer with IND$FILE file transfer expertise be available to review the trace.

Related:

Leave a Reply