GDDM V3R2 Diagnosis
|
Previous topic |
Next topic |
Contents |
Index |
Contact z/OS |
Library |
PDF |
BOOK
Problem Report Form GDDM V3R2 Diagnosis SC33-0870-01 |
|
________________________________________________________________________ | | | | | | | Part A: BACKGROUND INFORMATION | | | | 1.a. Customer Number: 1.b. Customer Name | | | | 1.c. Service Coordinator Name: | | | | 2. Problem Numbers: | | Problem Management Record Number: | | | | Authorized Program Analysis Report (APAR) Number: | | | | 3.a. Program Name: OS/2 Extended Edition or | | OS/2 Standard Edition | | | | b. OS/2 Version Number: 1.3, 2.0 | | | | c. Level: | | | | d. Extended Edition or Extended Services ?: EE ( ) ES ( ) | | | | e. EE or ES Level: | | | | f. Output from OS/2 Links GQFLEVEL program: | | | | g. Component reporting the problem: place a check mark (X) next | | to one or more: | | | | ___ Base Operating System ___ Database Manager | | | | ___ LAN Requester* ___ Communications Manager| | | | *For LAN problems, also complete Part E: LAN Requester-Server | | Information | | | | 4. Priority. | | Check the appropriate priority: | | | | Priority 1 Priority 2 Priority 3 Priority 4 | | | | O O O O | | | | 5. Problem Abstract: | | | | | | | | | | | |________________________________________________________________________| ________________________________________________________________________ | | | | | | | Part B: PROBLEM DESCRIPTION | | | | 1. Check one or more problem symptoms: | | | | ___INSTALL Installation | | | | ___ABEND Abnormal Termination | | | | ___WAIT/LOOP Wait or Loop | | | | ___DOC User Documentation | | | | ___PERFM Performance Problem | | | | ___INCORROUT Incorrect Output | | | | ___MSG Error Message | | | | (for messages, provide the following information if appropriate)| | | | | | Message Identification Number: | | | | | | Return Codes and Error Codes: | | | | | | Originator or Environment (if applicable): | | | | | | Message Text (optional--see related directions for Part B):| | | | | | 2. Describe the problem in the following space: | | | | | | | | | | | | | | | | | | | | 3. List any traces and dumps that you have completed: | | | | | | | | | | | | | | | |________________________________________________________________________| ________________________________________________________________________ | | | | | | | | | Part C: WORKSTATION HARDWARE CONFIGURATION INFORMATION | | | | | | 1. What is the computer type and model of the involved workstation?| | | | | | | | | | | | | | 2. What was the IBM plant of manufacture (if known) | | and serial number for this computer? | | | | | | | | | | | | | | 3. How much memory is installed on the workstation? | | | | | | | | | | | | | | | | 4. For fixed-disk systems, what is the size of the fixed disk? | | | | | | | | | | | | 5. List any adapters installed in the workstation in the following | | space (include the manufacturer and part number): | | | | | | | | | | | | | |________________________________________________________________________| ________________________________________________________________________ | | | | | | | | | Part D: HOST COMPUTER AND NETWORK INFORMATION COMPLETE | | THIS SECTION FOR COMMUNICATIONS PROBLEMS | | | | 1. What is the host computer operating system? | | | | | | | | 2. What is the release level of the host system? | | | | | | | | 3. What is the host application (CICS, TSO, VM, or CMS)? | | | | | | | | 4. How is the personal computer connected to the host network? | | | | | | | | 5. If SDLC or ASYNC, what is the modem type, make, and line speed? | | | | | | | | 6. If ASYNC protocol converter, what is the type, and model number?| | | | | | | | 7. If DFT or Token-Ring, what is the controller model and level? | | | | | | | | 8. For file transfer problem, what is the IND$FILE | | version number of the host file transfer program? | | | | | | | | 9. If X.25, what is the name and type of the network? | | | | | | | | | | | |________________________________________________________________________| ________________________________________________________________________ | | | | | | | | | PART E: LAN REQUESTER-SERVER INFORMATION | | | | | | 1.a. If this is a server, provide the following information: | | | | | | OS/2 LAN Server Version number: Level:| | | | 1.b. If this is a DOS requester or an OS/2 LAN Server that supports| | remote program load, provide the following information, if | | applicable: | | | | | | IBM DOS Version number: Level:| | | | | | IBM PC LAN Program Version number: Level:| | | | | | IBM LAN Support Program Version number: Level:| | | | | | IBM PC Network Protocol Version number: Level:| | | | | | | | 3. List the LAN services that were running on this machine when the| | problem occurred: | | | | | | | | | | | | 4. List the name and version number of any tested and compatible | | software involved prior to or during the time the problem | | occurred. Include if the software requires configuration data. | | | | | | Name of Software Version Number Configuration Data | | | | | | | | | | | | | |________________________________________________________________________| ________________________________________________________________________ | | | | | | | Part F: PROBLEM RESOLUTION | | | | | | | | 1. Describe the resolution of the problem in the following space. | | If necessary, attach additional text. | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |________________________________________________________________________| |
Copyright IBM Corporation 1990, 2012 |