This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

MVSER0031S "ABC1" is not a valid subsystem id

HI,

I have same issue but my issue still persists even if i changed the XA name to DSN name. Any help here.

Micro Focus ESMVS/TSO Version 7.0.000. Copyright (C) Micro Focus 1997-2021. All rights reserved.
DSN SYSTEM(ABC1)
RUN PROGRAM(PGM1) PLAN(PGM1G)
MVSER0031S "ABC1" is not a valid subsystem id. Sub-command stream flushed.:
MVSER0099S Remainder of command stream flushed.:
END

Note: My XA source name is as same as DSN system i.e ABC1

Thanks,

Basavaraj

Labels:

Enterprise Developer
Parents
  • 0  

    Hi Basav, can you share the  XA resource definition to understand what that is configured as (you can omit the open string and other sensitive information).

  • 0 in reply to   

  • Verified Answer

    +1   in reply to 

    This page:
    www.microfocus.com/.../GUID-FB11C86F-FD8D-4DE6-AABF-6F2D17A7F4A1.html

    Explains that the DSN command will use SQLServerConnection, and that is the name of an established connection to a SQL Server database. In your screenshot you use "XA/ACB1", as a test can you test with "XA/ACB1" in your JCL, and confirm the result.

    Also, why do you use the / character? Is there a specific reason for that in the XA name?

  • 0 in reply to   

    Hi KimH,

    Though have used XA/ABC1 and ABC1(DSN name defined in my system) but no luck at all. its keep giving me the same issue.

    Thanks,

    Basav

  • Suggested Answer

    0   in reply to 

    Hi Basav,

    I tested on my own ED 7.0 instance, region has a XA Resource ID/Name: XB0R, with following job:

    //MFTEST JOB 'MFTK',CLASS=A,MSGCLASS=A
    //STEP1 EXEC PGM=IKJEFT01,REGION=1024K
    //INPUT1 DD DSN=ADDTODB.INPUT,DISP=SHR
    //SYSUDUMP DD SYSOUT=*
    //SYSPRINT DD SYSOUT=*
    //SYSOUT DD SYSOUT=*
    //SYSREPT DD SYSOUT=*
    //SYSTSPRT DD SYSOUT=*
    //SYSTSIN DD *
    DSN SYSTEM(XB0R)
    RUN PROGRAM(PGM1) -
    PARM(STRINGTOPASS)
    //

    And do not encounter an issue.
    How does your job compare?

  • 0 in reply to   

    When i restart the server , i got below mentioned error in my windows environment. 

    CASXO0001S XA Resource Manager initialization error. Resource ABC1 open failed, reason -00003
    CASXO0023S Severe error detected in ABC1 XA interface, RM interface disabled

  • Verified Answer

    +1   in reply to 

    That indicates there is an issue with the connection, as a test can you connect to the database from a 3rd party tool , from the same machine , using the same credentials? That will help ensure you are using the correct details,e.g. in the XA resource's open string.

Reply
  • Verified Answer

    +1   in reply to 

    That indicates there is an issue with the connection, as a test can you connect to the database from a 3rd party tool , from the same machine , using the same credentials? That will help ensure you are using the correct details,e.g. in the XA resource's open string.

Children