Ansible for IBM Z

Ansible for IBM Z

Ansible for IBM Z

Facilitate communication, user interaction and feedback for Red Hat Ansible Certified Content for IBM Z

 View Only

  • 1.  Issues using new zOAU

    Posted 01/04/24 10:19 AM

    Hello,

    Wasn't sure where I should post this or who to turn to, hoping someone here can help me out.

    We installed the latest zOAU version (v1.3.0.0) on our systems (z/OS v2.5), this was via pax. We tried running a simple operator command "D SMS" and we received the following error:

    CEE3250C The system or user abend SD22  R=00000020 was issued.
         From entry point JMONCONS at compile unit offset +00000232 at entry offset +00000232 at address 1F20C282.

    This is from the syslog:

    IEA630I  OPERATOR DAVU0000 NOW ACTIVE,   SYSTEM=SYL1    , LU=DAVUSER
CNZ4200I CONSOLE DAVU0000 HAS FAILED. REASON=ABTERM                 
IEA631I  OPERATOR DAVU0000 NOW INACTIVE, SYSTEM=SYL1    , LU=DAVUSER
IEF450I DAVUSER9 STEP1 - ABEND=SD22 U0000 REASON=00000020 232       
        TIME=15.06.26

    This also create a CEEDUMP in USS.

    We made sure that:

    1. Resource "MVS.MCSOPER.ZOAU" is defined and the user has permissions to it.
    2. Output from "zoaversion -c" returned without issues.
    3. The user has permissions to issue "D SMS".
    4. The following utilities have the APF bit turned on: 
      ddlshelper
jcanhelper
jlshelper
jsubhelper
mvscmdauth
mvscmdauthhelper
opercmdhelper
pconhelper
pjddhelper

    Other commands, like "jls" work without an issue.

    Did we miss something? Did anyone come across this issue with JMONCONS?

    Any assistance would be greatly appreciated!



    ------------------------------
    David Rabinov
    ------------------------------


  • 2.  RE: Issues using new zOAU

    Posted 01/05/24 03:17 PM

    Posting on behalf of  "Onno Van den Troost" and "Frank De Gilio" who are having trouble posting here.

    A D22-20 ABEND points to an APF issue. Since you say the ZOAU modules have the APF bit set, the most likely cause is that the file system in which ZOAU resides is mounted with the NOSETUID flag set. When set, z/OS UNIX will not honor the APF extended attribute. 
The "df -v $ZOAU_HOME" command will tell you (No SUID) if the NOSETUID flag is active.

     



    ------------------------------
    Sri Hari Kolusu
    ------------------------------



  • 3.  RE: Issues using new zOAU

    Posted 01/05/24 03:24 PM

    Hello David,

    Referring to the documentation for an SD22 ABEND with reason code 20, that is issued when the program trying to issue the 'D SMS' command via SVC 34 " ... is not authorized to issue the MGCR or MGCRE macro. The program must be in supervisor state and PSW key 0-7."  I suspect in this case, the module is JMONCONS or whatever module contains that entry point.  I wasn't able to find any thing during a search for "jmoncons zoau" or "jmoncons zos".  If the CEEDUMP shows that name of the module that contains entry point JMONCONS, then perhaps you can make sure that module is in an APF authorized library.

    I apologize if that is information you already knew, or if it isn't helpful.

    Regards, Fred




  • 4.  RE: Issues using new zOAU

    Posted 01/05/24 05:02 PM

    I'd offer one more thing.

    "The program must be in supervisor state and PSW key 0-7."

    Not only does the program have to be in an APF authorized library, it must also MODESET to supervisor state prior to MGCR(E)-ing the "D SMS" command.  Even if the code is in an APF-authorized library, it does not appear that this MODESET is occuring before issuing SVC 34 -- if it had been done, the system would have issued a MODESET to get to SUP state.  If the program was not in an APF-authorized library, the program would have received an ABEND047.  So there might be something more wrong here...



    ------------------------------
    Scott Fagen
    Mainframe Evangelist
    CDW
    www.cdw.com/content/cdw/en/solutions/ibm-zsystems.html
    ------------------------------

    Original Message


  • 5.  RE: Issues using new zOAU

    Posted 01/05/24 08:12 PM

    What sort of environment are you running in?  Is this perhaps an ADCD running as a guest somewhere?  I'm wondering because we got a similar report from a user in that kind of environment.  I'm wondering if there's a common thread here.



    ------------------------------
    Anthony Giorgio
    Senior Software Engineer
    IBM
    Poughkeepsie NY
    ------------------------------



  • 6.  RE: Issues using new zOAU

    Posted 01/14/24 07:26 AM

    Hello,

    Posting on behalf of  "David Rabinov" who is having trouble posting here.

    > Hey Sri, thanks for the response. We've checked the ZFS mount and seems it was mounted with SETUID & SECURITY. Anything else you'd suggest to check?

    > Re Anthony's question: Running z/OS 2.5 serverpac, LPAR on z15. Anything you'd like us to check?



    ------------------------------
    Roded Bahat
    ------------------------------

    Original Message


  • 7.  RE: Issues using new zOAU

    Posted 01/24/24 11:00 AM

    I dug into this problem, and it's definitely a bug.  We've opened APARS PH59329 (v1.3) and PH59327 (v1.2) for this. 



    ------------------------------
    Anthony Giorgio
    Senior Software Engineer
    IBM
    Poughkeepsie NY
    ------------------------------

    Original Message


  • 8.  RE: Issues using new zOAU

    Posted 01/29/24 10:31 AM

    @David, could you please contact me directly at agiorgio@us.ibm.com?  I want to discuss the ZOAU APARs with you.



    ------------------------------
    Anthony Giorgio
    Senior Software Engineer
    IBM
    Poughkeepsie NY
    ------------------------------



  • 9.  RE: Issues using new zOAU

    Posted 02/06/24 03:11 PM

    Hello,

    We are seeing this same issue after upgrading from ZOAU 1.2.4.5 to 1.2.5.2. We also have a 1.3.0 install where we're seeing the same issue.  We are using the .pax install for all versions.

    I see PH59327 is still open. Are there any updates on when a fix might be available? 

    We are going to rollback to 1.2.4.5 for now, which was working before our upgrade.

    If you need any additional info from a 1.2 install, just let me know and I will be happy to provide it. So far, though, all the behavior is the same as reported above.

    Thanks



    ------------------------------
    Tony Partin
    ------------------------------

    Original Message


  • 10.  RE: Issues using new zOAU

    Posted 02/06/24 04:35 PM

    Tony,

    I'm working on packaging the fixes this week, so hopefully you'll see the APARs close soon. 

    Also, could you contact me directly about this issue?  You can use my email from the prior message.



    ------------------------------
    Anthony Giorgio
    Senior Software Engineer
    IBM
    Poughkeepsie NY
    ------------------------------

    Original Message