A JES2 customer just reported (yesterday!) abend0C1s from various (E)JES requests after applying a recent z/OS service RSU over the weekend. We never saw the dump, but IBM recommended PTF UA96556 (APAR OA54595) to fix the problem.

APAR OA54595 has the following description:

OA54595: SERVICE TO TRACK STORAGE AREAS RETURNED BY JES FOR VARIOUS SSIS IS REQUIRED.

    Various JES SSIs (such as extended status, SSI 80) return
    storage areas to the SSI caller containing the output of the SSI
    request.  The tracking of these areas is currently left to the
    caller of the SSI, but JES should also track the location of
    these storage areas.  This needs to be done using a service that
    is common to JES2 and JES3 since the areas may not be freed by
    the subsystem that obtained them (for example, when a broadcast
    SSI is used with poly-JES).

Adding a new tracking service to the JESes should not -- by itself -- fix an 0C1 abend.

My theory is that the JES2 developers, in some recent PTF, retrofit some code into the field that calls this new "address keep" service and forgot the necessary pre/co-req on that PTF to ensure the service itself actually got installed. Loading a service entry point address of zeros and branching there is a great way to generate an abend0C1! LOL

I suggest folks put this APAR on their lists of "must have" maintenance before you encounter similar errors from (E)JES, SDSF, and other exploiters of JES2 services.

--
Phoenix Software International
Edward E. Jaffe
831 Parkview Drive North
El Segundo, CA 90245
https://www.phoenixsoftware.com/

--------------------------------------------------------------------------------
This e-mail message, including any attachments, appended messages and the
information contained therein, is for the sole use of the intended
recipient(s). If you are not an intended recipient or have otherwise
received this email message in error, any use, dissemination, distribution,
review, storage or copying of this e-mail message and the information
contained therein is strictly prohibited. If you are not an intended
recipient, please contact the sender by reply e-mail and destroy all copies
of this email message and do not otherwise utilize or retain this email
message or any or all of the information contained therein. Although this
email message and any attachments or appended messages are believed to be
free of any virus or other defect that might affect any computer system into
which it is received and opened, it is the responsibility of the recipient
to ensure that it is virus free and no responsibility is accepted by the
sender for any loss or damage arising in any way from its opening or use.

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to