A fix is available
APAR status
Closed as program error.
Error description
When running ISPF GUI with TSO GUI linemode support ( i.e., TSO linemode data output and input in an ISPF/TSO GUI Window ), running some full screen applications such as RMFMON , CSP and OMVS results in various errors. These errors include screen erasure errors and hangs requiring the userid to be canceled. ISPF documents that fullscreen TPUTs from an application will appear in the emulator screen ( 3270 window ), while non-full screen TGETs will go to the ISPF/TSO GUI window. The problem applications have a mixture of fullscreen TPUTs and linemode TGETs. This results in the displays going to the 3270 window, but the line mode TGETs are done against the ISPF/TSO GUI window, resulting in the error or wait . . KEYWORDS: ISPFCS CLIENT SERVER
Local fix
From the 3270 window try doing a PA1/ATTENTION to breakout of the hang/wait and then push the OK button on the ISPF/TSO GUI window... RMS - 01/13/97
Problem summary
**************************************************************** * USERS AFFECTED: All users running ISPF GUI with TSO linemode * * support. * **************************************************************** * PROBLEM DESCRIPTION: Users running fullscreen applications * * from an ISPF GUI session with TSO * * linemode support may encounter * * problems such as fullscreen displays * * appearing in the 3270 session but * * input data being requested from the * * ISPF/TSO GUI Window. This can result * * in screen erasure errors or hung * * userids. * **************************************************************** * RECOMMENDATION: * **************************************************************** Some fullscreen applications like RMFMON, CSP, and OMVS issue fullscreen TPUTS but linemode TGETS. When running these apps from an ISPF GUI session with TSO linemode support the displays appear back in the 3270 session but the input is requested from the ISPF/TSO Window since it is a linemode TGET.
Problem conclusion
User's running fullscreen applications like RMFMON, CSP, and OMVS from an ISPF GUI session with GUI TSO linemode support should first suspend the ISPF/TSO Window to force all fullscreen and linemode data to appear in the 3270 screen until the completion of the fullscreen application. The ISPF/TSO Window should be resumed at the completion of this fullscreen application. The user can query the current status of the ISPF/TSO Window using the new 'CONTROL TSOGUI QUERY' service, and can suspend and resume this window using one of the two methods described below: 1. New ISPF Service - CONTROL TSOGUI QUERY|OFF|ON QUERY - gives current status of ISPF/TSO window Return Code = 0 - means either the user is not running ISPF GUI with TSO linemode support or TSOGUI is OFF - all TSO input and output will be directed to the 3270 session 1 - means all TSO linemode output will display in the ISPF/TSO Window and linemode input must be entered into the ISPF/TSO Window's input field. OFF - specifies that the ISPF/TSO Window is suspended and all fullscreen and linemode data will appear in the 3270 window until CONTROL TSOGUI ON is issued ON - specifies that the ISPF/TSO Window is to be resumed and all TSO linemode output and input will be directed to the ISPF/TSO Window. Notes: 1. CONTROL TSOGUI is a NOP if not running ISPF GUI with TSO linemode support. 2. CONTROL TSOGUI defaults to ON during ISPF GUI session initialization. Example clist: PROC 0 ISPEXEC CONTROL TSOGUI QUERY SET &TSOGUIST= &LASTCC IF (&TSOGUIST = 1) THEN + DO ISPEXEC CONTROL TSOGUI OFF END ISPEXEC SELECT CMD(OMVS) IF (&TSOGUIST = 1) THEN + DO ISPEXEC CONTROL TSOGUI ON END 2. New ISPF command - TSOGUI Add the TSOGUI command to your ISPF command table: SELECT PGM(ISPISM) PARM(TSOGUI,&ZPARM) For results as described above for CONTROL TSOGUI OFF or ON, from any ISPF command line enter: tsogui off or tsogui on
Temporary fix
Comments
APAR Information
APAR number
OW24689
Reported component name
ISPF V4 OS390
Reported component ID
565504201
Reported release
404
Status
CLOSED PER
PE
NoPE
HIPER
YesHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
1997-01-13
Closed date
1997-03-06
Last modified date
1997-04-01
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UW36726 UW36727
Modules/Macros
DCLTSODT ISPCCR ISPCMP ISPDTGET ISPDTPC ISPDTPUT ISPDTTSK ISPIGU ISPISM ISPSC93 ISPSC93X ISPSDT
Fix information
Fixed component name
ISPF V4 OS390
Fixed component ID
565504201
Applicable component levels
Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.
[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SSCDKBM","label":"ISPF"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"404","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"404","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
01 April 1997