SOLVE

 View Only

Problems running SOLVE:Access V5 with z/OS 2.3 and using an RLS ACDB whilst executing in SRB mode - message N28511

  • 1.  Problems running SOLVE:Access V5 with z/OS 2.3 and using an RLS ACDB whilst executing in SRB mode - message N28511

    Broadcom Employee
    Posted Apr 17, 2018 11:37 PM

    Problems running SOLVE:Access V5 with z/OS 2.3 and using an RLS ACDB whilst executing in SRB mode -

    message N28511

     

    We have experienced problems in IBM software and SOLVE:Access, have caused S0F8 abends or S0C3 abends in SOLVE:Access, and with maintenance from IBM and CA applied, an RLS dataset cannot be opened whilst the Access region is running with XM=ZIIP. 

     

    All issues (and another with SOLVE:Operations where a customer file is VSAM RLS) are related to problems with IBM changes in z/OS 2.3 when issuing VSAM macros SHOWCB and TESTCB in SRB mode (XM=ZIIP) on a file that is opened in RLS mode. 

     

    The initial problem was an S0F8 abend in VSAM code when opening an RLS dataset in SRB mode and the solution is PTF UA95316 for IBM solution OA54317. 

    We have experienced a problem with this, we noticed it returns bad data to a SHOWCB and an incorrect condition code for one use of TESTCB, both are issued when opening a VSAM file with module NM000285 – again the problem only occurs for RLS files when executing in SRB mode.

     

    A consequence of this bad data is an S0C3 abend in NetMaster or SOLVE. 

    This was corrected by our Sustaining Engineering Team in the source for DL81 (NM suite 12.2) and has since been corrected by these PTFs NMS 2202:

    Product   Release   Sol. Type   Apar #

    NMS       6.7                             SO01050 SOLVE:Access

    NMS       7.1                             SO01048 SOLVE:Operations

    NMS       7.6                             SO01022 NetMaster suite 12.1

     

    However, it’s still impossible to open an RLS dataset in SRB mode until IBM corrects UA95316. 

    The current workaround is to run XM=TASK. 

     

    The symptom of the bad data returned is that NM000285 does not regard the file format as supported and issues this message to the log:

    N28511 VSAM DATASET OPEN FAILED, DD=ACDB - UNKNOWN DATASET FORMAT