Posted: Tue Sep 05, 2006 3:47 am Post subject: Need guidance on IMS DC Abend
We are trying to execute a transaction which executes a Telon program. As soon as we execute the transaction and even before the initial screen is displayed we get the following abend
DFS555I TRAN WHRADD39 ABEND S000,U0103 SYS ID 020; MSG IN PROCESS:
Also log has the below Information.
DFS555I TRAN WHRADD39 ABEND S000,U0103 SYS ID 020; MSG IN PROCESS:
We are not able to ascertain whether the problem is with the transaction or with the program. Any info on this would be helpful to us to proceed forward. Thanks.
Joined: 02 Dec 2002 Posts: 155 Topics: 25 Location: N.Ireland
Posted: Tue Sep 05, 2006 4:45 am Post subject:
Is your program issuing a CHKP,
Code:
0103
Explanation: The length field for one of the user areas pointed to by the
parameter list for the CHKP call is either zero or negative.
System Action: The application program terminates abnormally.
Programmer Response: Check the length fields for the user areas that you
have specified in the parameter list for the CHKP call. If one is found to
be invalid, change it and rerun the job. See ABENDU0103 in IMS Version 8:
Failure Analysis Structure Tables (FAST) for Dump Analysis, LY37-3743.
Problem Determination: 2, 3, 11
************ Additional information for this item appears below: *************
IMS Problem Determination
IMS messages and codes problem determination is accomplished by using
procedures established by IBM for identifying a failing hardware unit or
program and determining whether the user or IBM is responsible for
resolution of a given problem.
Problem determination information is included, as appropriate, for
messages and codes listed throughout this manual. In most instances, one
or more numbers (for example, "4,6") appear after the heading "Problem
Determination" for a given message or code. These numbers are
cross-references to the numbered items that appear in the following list
of standard problem determination actions to be taken by the user.
1. Save the console sheet from the MVS console.
2. Save the input associated with the job.
3. Save the SYSOUT (system output) associated with the job.
4. Save the storage dump at time of failure of the IMS control
region, and save the dump of all associated message regions. (If
SYS1.DUMP is used, it should be printed and saved.)
5. Save the IMS log printout.
6. Save the IMS master terminal printout.
7. Save the local/remote terminal printout.
8. Save the JCL listings.
9. Save the ACB generation output.
10. Save the IMSGEN listing.
11. Save the SYSABEND dump. (If SYS1.DUMP is used, it should be
printed and saved.)
12. Save the assembly listing of any user-modified IMS modules.
13. Save the link-edit map.
14. Save the LOG trace.
15. Save the IMS log printout starting with the records that were
written just before abnormal termination.
16. Save the output listing from the MFS Language Utility execution.
17. Collect the following problem-related data:
a. System dump if running batch.
b. If running online, print log records type X'67',
sub-record type X'FF' (Pseudoabend). Use the File
Select and Formatting Print program to print these
records. The OPTION PRINT control statement must
specify EXITR=DFSERA30.
c. Run the DL/I test program (DFSDDLTO) with SNAP
statements before and after the failing call.
d. Save the PSB and DBD listings and/or statements
related to the failure.
e. A dump of log records type X'67'. Sub-record type
X'FE' (program isolation trace). Use the File Select
and Formatting print program to print the records.
Program isolation trace must be enabled when the log
is created. The OPTION PRINT control statement must
specify EXITR=DFSERA40.
f. If online, a snap from the log of the online region.
g. A history of the database backout, recovery, and
reorganization activity.
18. Save the assembly listing for the associated DBDs.
19. Save the assembly listing for the associated PSBs.
20. Save a listing of the VSAM catalog entries for the associated
data sets at the time of failure.
23. Contact IBM for hardware support.
24. Dump the 3270 diagnostic error log records off the IMS log.
Record type X'67'. Sub-record type X'03'.
25. Submit a copy of the IMS log.
26. Determine the CCB involved from the SPACCB field of the scratch
pad area or from the CTBCCBPT field. Determine the associated
(a) source and output CNT, and (b) the line and PTERM (CTB).
Determine from log records 01, 02, 03, 07, 08, 11, 12 and 13 the
status of the conversation:
a. The message was ready, but the application was not
scheduled. A 01 destination is a conversational SMB.
b. The application was scheduled and a 08 record was
produced.
c. The application inserted a segment to a conversational
terminal. If the destination of the message is CNT, 03
and 13 records are produced.
d. The application inserted a segment to a conversational
program. SPA is the first segment of a message in the
03 records.
e. The application finished normally or terminated
abnormally. The 07 record contains the completion code
of a conversational application. The DLRFLAG2 area
(the last word of the 07 log record) contains
synchronization point information.
f. A 12 record indicates that the conversation was
terminated.
g. Determine if 02 records, produced for the following
commands, affected the terminal in conversation: /EX1,
/HOLD, /REL, or /STA LINE (no PTERM).
h. Does restarting IMS affect the conversation? For
details, see the input to and output logs from
restart.
27. Save the MVS hard-copy message log output.
28. Determine the status of MVS and IRLM operating in the other
system with which this system is connected during normal
operations.
29. Save the IRLM address space dump generated at the time of the
failure.
30. Save the dump of any IMS online or batch address space that
failed near the time of the IRLM failure. Follow IMS problem
determination procedures relative to the IMS dump. The IMS
failure might be related to the IRLM failure.
31. Save a listing of the IRLM start procedure JCL.
32. Save a listing of the IMSGEN performed to install the IRLM.
33. Save listings of the VTAM definitions performed to install the
IRLM.
34. Save the GTF trace output, if any is available showing activity
at the time of the failure.
35. Refer to the following manuals for further assistance to resolve
your problem:
o IMS Version 8: Failure Analysis Structure Tables (FAST) for
Dump Analysis, LY37-3743
o IMS Version 8: Diagnosis Guide and Reference, LY37-3742
Check all input for accuracy and analyze any dumps.
If you are still unable to solve your problem, contact the IBM
Support Center for further assistance.
36 If you are unable to solve the problem, contact the IBM Support
Center for assistance.
37 Submit a copy of the type X'02' log records.
38. Save the CCTL SNAP or SDUMP data set.
39. Save the output from the Security Maintenance utility.
40. Save a listing of the DBRC RECON.
41. Take an SVC dump and contact the IBM Support Center for further
assistance.
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
FAQ
Search
Quick Manuals
Register
Profile
Log in to check your private messages
Log in
