PCSXFER041 timeout during Personal Communications file transfer TSO session

Technote (troubleshooting)


Problem(Abstract)

This hint details three situations that might cause a timeout at the Personal Communications client and a solution is provided for each case.

Resolving the problem

CUT mode transfer
By default, Personal Communications uses DFT mode for transfers to and from a TSO host. When using Dial to connect to TSO, the host might be configured to do the transfer in CUT mode, while Personal Communications is still in DFT mode.

You can modify the workstation profile that you use to dial the TSO session, in order to manually change the DFT/CUT setting. Add the following case-sensitive line to the Transfer stanza of the .WS file:

[Transfer]
CUTprotocol=Y

You can also change the LU Description on the zSeries host. Change the VTAM BIND image so that the Write Structured Field query support bit is set in the PSERVIC. Refer to the VTAM documentation for more information.


Using \FT trigger in SuperSession Manager
If you encounter the timeout problem when using Supersession, you can use the \FT trigger before logon. This can be applied on an individual user and session basis.

The \FT trigger invokes the file transfer script KLSXFER, which enables query passthru. It also inhibits immediate broadcasts and session locking.


Document Mode and Word Wrap mode
If Document Mode or Word Wrap mode is enabled, the file transfer will fail. If you have a key mapped to toggle this feature on or off, turn it off before initiating the file transfer. If you want to disable this feature, change the case-sensitive line in the ENTRYASSIST stanza of the .WS file:

[ENTRYASSIST]
DocmodeWordWrap=N

Rate this page:

(0 users)Average rating

Document information


More support for:

Personal Communications

Software version:

5.6, 5.7, 5.8, 5.9, 6.0

Operating system(s):

Windows

Reference #:

1080537

Modified date:

2014-02-26

Translate my page

Machine Translation

Content navigation