This problem has been solved. In fulfillment of a promise, here is
as much of the explanation as I am permitted to share.
As many suspected, this was indeed a SUE (Stupid User Error).
The program being directly executed, i.e., via JCL, was not itself
failing. The S0C4 was occurring in IBM code, and was happening
because of a dynamically loaded subroutine. It was the subroutine
that was faulty.
The error occurred because the bad subroutine was where it shouldn't
have been. That, in turn, occurred because a developer (a) put it
into a library where it did not belong in the first place, and (b)
failed to clean up his garbage when his project ended several months
ago. When the bogus module was deleted, the problem went away with it.
In summary, this was an instance of Murphy taking full advantage when
someone did not follow correct procedure, and then did not clean up
after himself. We have drawn several instructive lessons from the
experience, none of which I intend to dwell on here.
Thanks to everyone who took an interest and offered constructive suggestions.
David
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
