TLMS

 View Only
  • 1.  TLMSTRS ABEND S16E after zOS RSU1807 maintenance.

    Broadcom Employee
    Posted Aug 24, 2018 03:13 PM

    TLMSTRS abends with an S16E after IBM zOS RSU1807 / OA56018. Restore off RSU1807 / OA56018 and open a PMR with IBM.

    Status as of 8/24/2018.



  • 2.  Re: TLMSTRS ABEND S16E after zOS RSU1807 maintenance.

    Broadcom Employee
    Posted Aug 24, 2018 03:13 PM

    Pending update from IBM.



  • 3.  Re: TLMSTRS ABEND S16E after zOS RSU1807 maintenance.

    Posted Aug 27, 2018 10:37 AM

    TLMSTRS in version 12.6 of TLMS only.  The TLMSTRS version 14 works OK and can be used with 12.6 as a workaround until IBM provides a fix.  Here is the text from IBM apar OA56018 ...

     

    ERROR DESCRIPTION:
    When processing a VSAM data set that is opened using the ISAM Interface in VSAM, an Abend S16E RC24 will occur after  installing PTFs for new function apars OA53954, OA53955, OA55315 which require greater control of the DEB control block.
     

    Users Affected:
    Any users of old applications that were written for ISAM data sets, AMORG=IS.

     

    User Impact:
    An ABEND16E rc24 will occur when closing the data set because  the call to delete the DEB does not specify the new requirement of UNLOCKDELETE to ensure integrity.
     
    History:
    The ISAM Interface in VSAM was added many years ago to VSAM so that programs that accessed ISAM data sets using an ISAM DCB could access VSAM data sets without the code in the program being changed. Adding the parameter AMP=AMORG was the minimum JCL requirement to process a VSAM data set that was converted from an ISAM data set at some point in the past.
     
    LOCAL FIX:
    If you do not run any ISAM programs, you are not affected by this issue.

     

    If you do run ISAM programs, you can ignore the ABEND16E's or apply the ++APAR which will be available by Sept 1,2018 or remove the New Function PTFs.
     

     

     



  • 4.  Re: TLMSTRS ABEND S16E after zOS RSU1807 maintenance.
    Best Answer

    Broadcom Employee
    Posted Aug 30, 2018 12:51 PM

    Update from a TLMS client.

    After the application of the IBM fix(OA56018) to our test lpar, our TLMS retention job processed to a successful completion.