OS/390 MVS IPCS User's Guid

More documents

Recommendations

Info

v A compressed extended sequential data set cannot be updated. Therefore, IPCS cannot add secondary symptoms generated during dump analysis into the header record of a compressed dump. This restriction has the most impact for an SVC dump requested by an operator DUMP command or for a stand-alone dump. Using IPCS at the Terminal Trace Data Set Processing These data sets have certain requirements, which are described in OS/390 MVS Diagnosis: Tools and Service Aids. You can use the IPCS subcommands that apply to component traces or GTF traces when formatting the trace records. VSAM and Other Data Set Processing When IPCS does not consider the source to be a system dump or trace data set, IPCS provides general purpose processing. In this processing, IPCS initializes the data set, processes records in the data set, and makes the unformatted records available for accessing and viewing. However, you cannot use IPCS subcommands for these data sets. Active Storage Processing IPCS can process as a dump the central storage for the address space in which IPCS is currently running, private storage, and any common storage accessible by an unauthorized problem state program. IPCS does not create a storage map when processing active storage, but it does maintain a limited symbol table. Limitations on IPCS subcommands exist when processing active storage. IPCS has three modes of operation: v Line mode on a terminal v Full-screen mode on a terminal, known as the IPCS dialog v Batch mode using the terminal monitor program (TMP) The following sections summarize these modes. IPCS Line Mode IPCS is a TSO/E command processor. When you enter the IPCS command at the TSO/E READY prompt, you begin an IPCS line mode session. In this mode you can enter IPCS subcommands and invoke REXX execs and CLISTs. IPCS provides online explanations of the function, syntax, and parameters of each IPCS subcommand. IPCS Dialog IPCS provides a full-screen dialog through the Interactive System Productivity Facility (ISPF). This mode, known as the IPCS dialog, runs on top of ISPF and the IPCS command processor. The IPCS dialog provides the following advantages over line mode: v Organizes the approach to diagnosis v Provides easy-to-use panels for selecting dump analysis, formatting, and management procedures v Enhances the functions available when browsing unformatted storage records v Captures analysis reports for easier viewing v Offers online help for reading analysis reports and a tutorial on using the IPCS dialog. 6 OS/390 V2R10.0 MVS IPCS User’s Guide
IPCS Dialog Requirement The IPCS Dialog requires an interactive environment where TSO/E line mode messages are shown as they are written, not buffered. It is supported when run under supported levels of the following products: v MVS/System Product or OS/390 MVS v TSO/E or OS/390 TSO/E v ISPF or OS/390 ISPF To process a source in the IPCS dialog, specify the data set as the source on the IPCS default panel, in a SETDEF subcommand, or in a parameter on a subcommand. If the source is active storage, specify the MAIN parameter. Each IPCS panel has its own local defaults, including the source. The dialog facilities, subcommands, and command procedures used on the panel use the same source as the panel. Another panel, with its subcommands and command procedures, can use a different set of local defaults, including a different source. This arrangement allows you to view several, related dumps in parallel, which is helpful in diagnosing problems on different systems in a sysplex. Commands entered from a window run on the dump being viewed in the window. IPCS Batch Mode You can submit batch jobs that access IPCS to perform dump analysis against a specific dump. Saving Dump Analysis Results As you examine a dump of a software failure, IPCS accumulates information about the dump. IPCS uses the information it gathers each time you process the dump. IPCS saves the results of dump analysis. User Dump Directory The majority of the information generated by dump analysis is stored in the user dump directory, which is a data set allocated to the ddname IPCSDDIR. The user dump directory contains information, called a source description, used by IPCS to process dumps, traces, and other sources efficiently. The source descriptions resemble a notebook that IPCS uses as it processes a source; IPCS writes notes about the dump, such as its symbols, the location of control blocks, and session defaults. Later, when IPCS needs some information from its notes to format a dump, IPCS obtains it from the source description for the dump. Sysplex Dump Directory In a sysplex, the systems can share a sysplex dump directory. This directory contains source descriptions like the ones in a user dump directory, but the source descriptions are for sources from all the systems that share the sysplex dump directory. When any system that shares the sysplex dump directory produces an SVC dump, the system automatically writes a source description for the dump in the sysplex dump directory. If you want to analyze the dump, you can copy the source description from the sysplex dump directory to your user dump directory. Chapter 1. Introduction to IPCS 7
Page 1: OS/390 MVS Interactive Problem Con
Page 4 and 5: Note Before using this information
Page 6 and 7: | Option 6 — COMMAND . . . . . .
Page 8 and 9: Associating and Dissociating Data S
Page 10 and 11: 52. Example of a REXX EXEC Function
Page 12 and 13: x OS/390 V2R10.0 MVS IPCS User’s
Page 14 and 15: xii OS/390 V2R10.0 MVS IPCS User’
Page 16 and 17: This book contains information prev
Page 18 and 19: Requesting IPCS Functions . . . . .
Page 20 and 21: v v v v Mix formatted GTF and compo
Page 24 and 25: Dump Header Record When IPCS identi
Page 26 and 27: Table 1. Libraries that Contain IPC
Page 28 and 29: 12 OS/390 V2R10.0 MVS IPCS User’s
Page 30 and 31: v v See OS/390 MVS IPCS Customizati
Page 32 and 33: establishes these defaults. See the
Page 34 and 35: You can specify the source data set
Page 36 and 37: Requesting IPCS Functions subcomman
Page 38 and 39: Using a Three-Step Process . . . .
Page 40 and 41: 24 OS/390 V2R10.0 MVS IPCS User’s
Page 42 and 43: Use the browse option to display a
Page 44 and 45: Note: Overriding default values on
Page 46 and 47: Use the STATUS option to request a
Page 48 and 49: The following chart lists the optio
Page 50 and 51: Option 3 — UTILITY Use the GTFTRA
Page 52 and 53: Command A B D Description Adds the
Page 54 and 55: v v v v v v AC: The leftmost column
Page 56 and 57: Option 4 — INVENTORY REFR Refresh
Page 58 and 59: Option 5 — SUBMIT ---------------
Page 60 and 61: Option 6 — COMMAND --------------
Page 62 and 63: v v The pointer and storage panels
Page 64 and 65: Command PF Key CURSOR command (ISPF
Page 66 and 67: v v For stand-alone dumps, IPCS use
Page 68 and 69: DSNAME('D83DUMP.DUMPC.PB00465') POI
Page 70 and 71: Figure 26. IPCS Storage Panel Brows
Page 72 and 73:
ASID(X'0001') STORAGE -------------
Page 74 and 75:
2. If you issue the IPCS primary co
Page 76 and 77:
Source of Dump Blocks Bytes DSNAME(
Page 78 and 79:
IPCS OUTPUT STREAM ----------------
Page 80 and 81:
Help Entering IPCS Subcommands Thro
Page 82 and 83:
ISPF profile data set. Deletion of
Page 84 and 85:
68 OS/390 V2R10.0 MVS IPCS User’s
Page 86 and 87:
group. For ease in assigning and re
Page 88 and 89:
the dump directory. However, compre
Page 90 and 91:
----------------------------- Copy
Page 92 and 93:
looking for, it generates a name fo
Page 94 and 95:
Note: Processing for certain IPCS s
Page 96 and 97:
The following example, which was ru
Page 98 and 99:
LIST 00000000. NOCPU ASID(X'0001')
Page 100 and 101:
When You Want to Identify data sets
Page 102 and 103:
ADDR1 X is the symbolic address ass
Page 104 and 105:
list aaa+4 Because location AAA+4 i
Page 106 and 107:
Example: Invoking a REXX EXEC or CL
Page 108 and 109:
does not wait for the END subcomman
Page 110 and 111:
CLISTs that Print Screening Dump Re
Page 112 and 113:
Writing IPCS REXX EXECs This sectio
Page 114 and 115:
* REXX */ Signal on halt Trace off
Page 116 and 117:
if rc > 0 then do /*---------------
Page 118 and 119:
Put_Error: nop Retc = 16 Signal Exi
Page 120 and 121:
on page 99) to retrieve the TCB poi
Page 122 and 123:
Customizing the TCB Pointer Chain F
Page 124 and 125:
Table 2. Considerations for Designi
Page 126 and 127:
110 OS/390 V2R10.0 MVS IPCS User’
Page 128 and 129:
parameters for this session. You us
Page 130 and 131:
Page 132 and 133:
IPCSJOB JOB 'acctinfo','IPCSU1 outp
Page 134 and 135:
IPCSJOB JOB 'acctinfo','IPCSU1 outp
Page 136 and 137:
DISP DSORG RECFM NEW, OLD, or MOD W
Page 138 and 139:
v ALLOCATE DDNAME(IPCSPRNT) SYSOUT(
Page 140 and 141:
Use STACK to control duplication of
Page 142 and 143:
Page 144 and 145:
Page 146 and 147:
IPCSJOB JOB //* //* SUBMIT THIS JOB
Page 148 and 149:
PROC 3 DSN OUTFILE CLEAR /*--------
Page 150 and 151:
BLSCDDIR BLSCBSVB CLIST provided by
Page 152 and 153:
If no one at your installation has
Page 154 and 155:
ADDPROB subcommand. Once the proble
Page 156 and 157:
You have considerable flexibility i
Page 158 and 159:
alloc fi(b) ds('ipcs.data.set.direc
Page 160 and 161:
adddsn dsname(prob31.dump) problem(
Page 162 and 163:
Page 164 and 165:
Avoid moving the data set to a diff
Page 166 and 167:
Licensees of this program who wish
Page 168 and 169:
CLIST (command list) (continued) wr
Page 170 and 171:
IPCS dialog (continued) customize P
Page 172 and 173:
storage map associated subcommands
Page 174:
Readers’ Comments — We’d Like
show all

OS/390 MVS IPCS User's Guid

Create successful ePaper yourself

Delete template?

Save as template?