FUJITSU BS2000 - Manual (Page 31)

30
- SJMSFILE
- SYSTEM-JOBPOOL
- entry in the user catalog of the user IDs involved
- in exceptional cases: diagnostic dump instead of SLED
- SCHEDLOG file
For problems in the binder loader system:
- if the error can be reproduced: libraries involved and phase
- for SHARE problems: console log and entire class 4 memory dump
- for ELDE problems: phase
For SYSFILE management problems:
- procedures/enter jobs in file form
- SYSOUT or SYSLST log
For NDM problems:
- NDMDAMP (PRODAMP procedure, see 'Diagnostics Manual': DAMP)
- CONSLOG file
For BCAM problems:
- activate all DCM traces with /DCDIAG DCM.,MODE=SAVE and
after reproducing the error, save the generated trace files
S.DCTRAC.* with /DCDIAG DCM.,MODE=CLOSE or submit the diagnos-
tic information to main memory with /DCDIAG DCM.,MODE=HOLD and
evaluate it with ASTRID.
For IORM problems:
- IORM dump
- CONSLOG file
If problems occur with the IORM DPAV or IOLVM functions, under
VM operation these documents are required from both the guest
and the monitor system.
For problems at the hardware and software interface:
- HERSFILE
- hardware and software configuration
- possibly IOTRACE listing
For communication problems between BS2000 and X2000 consoles:
1. BEFORE generating SLED
- prkdump (see types of documents)
- sysdb trace (see types of documents)
- KVP trace file /var/opt/SMAW/X2000/diag/KVP/KVP
(suffixed with the system name for additional KVPs)
2. Generate SLED. The generated memory dumps OHDUMP and
IOSDUMP of the X2000 Carrier System are stored in section
IOHIOSDP of the SLED file (see types of documents).
For tape problems:
- if possible you should send in the original tape for error
diagnosis, otherwise you should at least provide a listing of
all tape labels and the first data blocks
- SYSOUT log and CONSLOG file.
- NDMDAMP
Final note
The above description does not contain any information on generat-
ing documents using BS2000 tracers. Please consult the reference
manuals of the individual tracers for this.