APAR status
Closed as canceled.
Error description
THE SOLUTION OF TCAM/TIOC PROBLEMS REQUIRE PRECISE AND COMPLETE DOCUMENTATION. FOLLOWING IS A LIST OF THE DOCUMENTATION REQUIRE- MENTS. (ALSO REFERENCE INFO APAR II02202 FOR MAINTENANCE AND CHANGES TO THE TCAM MCP). 1. TSO VIDEO OUTPUT TRACE (MUST BE AT UZ72050 LEVEL) (AT THIS LEVEL, ALL TSO DEVICE TYPES ARE TRACED.) THIS TRACE IS ACTIVATED BY: A. STARTING GTF AND REQUESTING USR TYPE TRACE ENTRIES. B. STARTING EITHER CHANNEL I/O TRACE OR A PIU TRACE. THE CHANNEL I/O TRACE IS STARTED FOR CHANNEL ATTACHED RESOURCES OR FOR THOSE ATTACHED THROUGH A COMMUNICATION CONTROLLER EMULATOR PROGRAM. THE PIU TRACE IS STARTED FOR NCP-ATTACHED RESOURCES AND CHANNEL ATTACHED SNA RE- SOURCES *FOR LOCAL-REMOTE ASSOCIATE DEVICES, THE PIU TRACE MUST BE STARTED TO THE REMOTE DEVICE. *BE AWARE THAT STARTING THE GLOBAL PIU TRACE WILL NOT CAUSE THE VIDEO TRACE TO ACTIVATE. PIU TRACING MUST BE STARTED TO EACH INDIVIDUAL DEVICE. *NOTE: BE SURE TO START THE GTF TRACE BEFORE THE USER LOGS ON TO TCAM/TSO. C. AN INPUT OPERATION FROM THE TSO TERMINAL BEING TRACED WILL COMPLETE THE ACTIVATION OF THE TRACE OPERATION. * ONCE THE VIDEO TRACE IS STARTED AND THE FAILING DEVICES ARE LOGGED ON AND BEING TRACED, THE CHANNEL I/O TRACE MAY BE STOPPED TO ELIMINATE VIDEO TRACING OF UNWANTED DEVICES ON A MULTI-DROP LINE. 2. GTF TRACE OF SVCS 93 THROUGH 101 * THE GTF OUTPUT OF BOTH THE VIDEO TRACE AND THE TRACE OF THE SVCS SHOULD BE PRINTED TOGETHER IN ONE JOB. 3. TCAM SUBTASK (STCB) TRACE SPOOLED TO COMWRITE DATASET 4. TCAM FORMATTED DUMP WHICH INCLUDES CSA. * THIS DUMP SHOULD BE TAKEN AS CLOSE AS POSSIBLE TO THE FAIL- URE AND BEFORE ANY RECOVERY IS ATTEMPTED. 5. MVS CONSOLE LISTING AROUND THE TIME OF FAILURE 6. LISTING OF THE USER'S TCAM MCP. NORMALLY A SOURCE LISTING WILL SUFFICE. 7. COMPLETE, DETAILED DESCRIPTION OF THE PROBLEM AS SEEN BY THE TERMINAL OPERATOR. KEYWORDS: TCAMINFO DOC TSO FULLSCREEN ISPF LAST CHANGE: 87/07/17 RHB
Local fix
Problem summary
Problem conclusion
Temporary fix
Comments
APAR Information
APAR number
II02180
Reported component name
V2 LIB INFO ITE
Reported component ID
INFOV2LIB
Reported release
001
Status
CLOSED CAN
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
1985-10-01
Closed date
1985-10-02
Last modified date
1987-07-17
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Applicable component levels
[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19N","label":"APARs - OS\/390 environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","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":"001","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":null,"label":null},"Product":{"code":"SG19O","label":"APARs - MVS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SSSN3L","label":"z\/OS Communications Server"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]
Document Information
Modified date:
13 December 2020