Incorrect Output Problems

Edit online

The symptoms of an incorrect output problem are the following:

An application works differently under CL/SuperSession than it does without CL/SuperSession.
An application program message reports an unexpected result from a CL/SuperSession, such as a return code, sense code, or both.
A terminal user cannot enter data to an application.
A terminal user reports wrong or missing data at the terminal.
The cursor is positioned incorrectly on the screen.
A terminal user gets an unexpected response to a transaction.
The output data is formatted incorrectly.

Note: The above symptoms can also result from an error in a host-based application program such as TSO or IMS.

Incorrect output problems are caused by:

Communication definition problems: A terminal definition problem is the most common cause of incorrect output. Within a VTAM® network, mode entry definitions (MODEENTs) define terminal characteristics, parameters and protocols. If these definitions are incorrect, they cause unexpected results at the terminal, including corrupted screens. Refer to the appropriate IBM documentation for help in resolving incorrect output problems relating to mode entry definitions.

CL/SuperSession product installation and customization problems: Incorrect output and wait problems are frequently associated with incorrect installation and customization of CL/SuperSession.. Be sure to follow the instructions in the Program Directory for IBM CL/SuperSession for z/OS and the IBM CL/SuperSession for z/OS Basic Configuration Guide 3.1 for IMS data communications definitions to help resolve terminal definition problems.

File transfer: Incorrect output problems can occur during file transfer. The file transfer problem may be caused by immediate broadcast which interrupts file transfer. To solve the problem, disable immediate broadcast with the dialog function VIGIBC (1). When the file transfer is complete, enable immediate broadcast with dialog function VIGIBC (0).; Note: If you have the file transfer dialog available (usually through the trigger, \ft), immediate broadcast is disabled and enabled automatically.; If the problem is not caused by immediate broadcast, check logmodes to ensure that the bind images for the physical and virtual session are the same, and that the binds match the bind that was used on the PC for the native file transfer.; Also check session options as described in IBM CL/SuperSession for z/OS User's Guide 3.1 for the correct settings for file transfer. The session options are set automatically by the file transfer dialog.; If file transfer problems persist, get a trace of the file transfer without CL/SuperSession and a trace of the physical and virtual CL/SuperSession terminals during file transfer to the point when the problem occurs. Include the bind and the names and uses of logical units with the trace.

Compression problems: Compression problems can cause incorrect output. To correct the problem, try running the application in single-window display. (Running in single-window display allows the CL/SuperSession to automatically disable compression for file transfer and graphics output and other 3270 data stream facilities that do not work with data compression.)

If an incorrect output problem occurs, generate and review the documentation described in Table 2. Refer to Using Trace Facilities when generating and reviewing trace documentation. When CL/SuperSession is involved, you may wish to obtain a trace of the application running without CL/SuperSession for comparison. If you are unable to locate the problem, contact IBM Support for assistance.