We have reorganized the IMS database. The length of one segment has been increased. We have changed the DBD's, Copy books and programs to reflect the length change.
when a multimodular cobol program is run against the reorganized database IMS 0260 abend is faced. The JCL is pointing to the correct loadlibs and DBD libraries. The PSBs are not impacted due to this change as there are no sensitive fields defined. We are running the JCL in batch mode with DBB parameter.
The program is not using the parameter count for any of the DLI calls which trigger off this abend.
however this abend is not there when eazytrieve program is run against the reorganized database.
The possible explanation of the abend is as follows
Explanation: Abend U0260 was issued for one of the following reasons:Code:
The number of parameters in the application program call to IMS
exceeded the allowable limit of 18 or is equal to 0.
The checkpoint call was used and one of the following applies:
Too few parameters were specified.
The number of user-specified areas exceeds the number specified
on the XRST call.
The user area parameters are not paired (a length and address
for each area to be dumped).
The application program overlaid the DL/I function code so that
the first character was not alphanumeric. This causes the field
to be treated as a count field.
System Action: The online dependent or stand-alone batch region
terminates abnormally. Other IMS regions are not affected.
Programmer Response: If the problem is an incorrect number of
parameters, correct the DL/I call from the application program to
conform to the format.
If ne one can give some pointers to resolve that wud be gr8ful.
Joined: 07 Nov 2005 Posts: 1105 Location: The Netherlands at Hole 19
This should be solved by your IMS systems programmer. Give him a call and tell him how your call looks like. You might have coded too many SSA's for example. Since we don't know at what call you abended nor doe we know the system implementation we can't give answers in the blind. So please have a nice conversation with your system programmer first in order to find out where the problem really rests; there are more reasons so we have to eliminate them.