Map Vols and Problem Dataset

M Lee Klein · New User Joined: 08 Feb 2022 Posts: 39 Location: USA

DBA here filling in while a new mainframe staffer can be replaced. I have a job that abended with a S0C9. It appears to run an assembler program called MAPUSR but that appears to execute a MAP VOLS. It produces a list of datasets along with dataset details.

From archived emails I can see where this job abended months ago and the offending dataset deleted to fix the issue.

MAPVOLS PGM03 - ABEND=S0C9 U0000 REASON=00000009 827

How do I determine which dataset is the problem one? I already requested the admin delete the last referenced dataset which did not fix the issue.

sergeyken · Posted: Fri Dec 15, 2023 8:07 pm

Your MAPUSR is a hand-made program created by your company, or taken from unknown source.
I doubt that anybody at this forum can give you a response on its wrong behaviour.

ABEND S0C9 means that this MAPUSR either tried to divide a binary value by binary zero (= value F'0'), or tried to convert a too long packed decimal value (= PL16, with maximum value 9,999,999,999,999,999,999,999,999,999,999) to its binary equivalent (a full-word value, maximum X'7FFFFFFF')

Where any of those wrong values come from - nobody here can guess. You should ask any support from MAPUSR developers.

M Lee Klein · New User Joined: 08 Feb 2022 Posts: 39 Location: USA

Thank you for that explanation.