Automated Testing

Automated Testing

Automated Testing

Build an automated testing process to enable continuous integration of your hybrid cloud applications including z/OS

 View Only
Back to discussions
Expand all | Collapse all

Issue with Mainframe z Development and Test Environment server(INDEX creating error)

  • 1.  Issue with Mainframe z Development and Test Environment server(INDEX creating error)

    Posted Wed October 09, 2019 09:55 PM

    When I tried to create talbe index in z Development and Test Environment, unexpected error occurrs.

    Please look at the attached file. It seems that tablespace 'SYSTSISS' is lack of resource. But I don't know how to recover 'SYSTSISS' resource.

    So could you reply the followin two questions?

    1. There is almost no storage to store the VOL required to create a database or data set. Is 'SYSTSISS' running out of resources due to this storage capacity? If I incease storage capacity, will this issue be resolved?

    2. If No.1 is 'No' could you support another approach in fixing this issue?

    shigeto.iwata


  • 2.  Re: Issue with Mainframe z Development and Test Environment server(INDEX creating error)

    Posted Fri October 11, 2019 05:33 AM

    Hi

    This is really a DB2z question rather than a ZD&T question, but let me try.

    A storage groups maps to one or more disk volumes through the SMS definitions.

    So I would add a new SMS-managed disk volume, find the SMS ACS routine that maps to your storage group, and then add the disk to that.

    If you don't know how, you should get SMS- and DB2-skilled people to help you. Or read the manuals carefully.

    Br

    Michael Erichsen,

    Xact Consulting

    MichaelErichsen,Xact


  • 3.  Re: Issue with Mainframe z Development and Test Environment server(INDEX creating error)

    Posted Fri October 11, 2019 06:20 AM

    Hi Michael,

    Thank you for replyin.

    SMS is set by another person based on the attached manual.

    However, I couldn't figure out how the problem with this DB2 table index creation was related to SMS.

    Can this problem be solved by changing the SMS settings?

    shigeto.iwata

    Attachments

    SMS ADMINISTRATION.docx


  • 4.  Re: Issue with Mainframe z Development and Test Environment server(INDEX creating error)

    Posted Fri October 11, 2019 06:29 AM

    Hi

    It is quite complicated. Your CREATE statement refers to a DB2 STORAGE GROUP.

    That DB2 storage group is connected through SMS ACS routines to SMS GROUPS.

    That SMS group maps to a disk volume.

    Check the definitions in DB2 and in the ISMS panels. And make a drawing :-)

    Br

    Michael Erichsen,

    Xact Consulting

    MichaelErichsen,Xact


  • 5.  Re: Issue with Mainframe z Development and Test Environment server(INDEX creating error)

    Posted Wed October 16, 2019 07:03 AM

    I checked the DB2 and SMS panels. However, I don't know where this error applies.

     

    Please look at the attached file. Other person created 'SMS ADMINISTRATION.docx'. It is written about SMS pannel setting.

    'SMS PANEL_20191016.xlsx' is current SMS pannel. And 'DB2 PANNEL.xlsx' is for DB2.

     

    Can you confirm how to solve the problem from these contents?

    shigeto.iwata

    Attachments

    SMS ADMINISTRATION.docx
    SMS PANEL_20191016.xlsx
    DB2 PANNEL.xlsx


  • 6.  Re: Issue with Mainframe z Development and Test Environment server(INDEX creating error)

    Posted Wed October 16, 2019 08:38 AM

    Hello,

     

    Db2 Code 00C2010D indicates the following:
     

    00C2010D

    Explanation

    Db2 was unable to open a required data set because an unexpected level ID was encountered.

    The reason code and the data set name are made available in the SQLCA or in messages.

    System action

    A 'resource unavailable' code is returned to the user. Message DSNB232I is issued to the console if it was not already issued for the data set. Db2 failed to open the data set.

    Operator response

    Notify the system programmer.

    System programmer response

    Refer to message DSNB232I for help in determining the cause of the error. Run the utility REPAIR LEVELID or recover the table space or index, and then tell the user to rerun the application.

     

    In case this error is not space related then you may need to run Db2 REPAIR utility. If the problem is related to space then you need to determine if you have run out of z/OS Disk space. The fact that your Linux host filesystem is 97% full (as seen from your attachment) does not necessarily mean you have no z/OS disk space. You may have to obtain help from whomever setup your SMS configuration.

     

    Cheers,

    Greg

    gkeuken


  • 7.  Re: Issue with Mainframe z Development and Test Environment server(INDEX creating error)

    Posted Wed October 16, 2019 09:17 PM

    Hi

     

    Thank you for quick replying. I think the problem is related to space. So I need to confirm if I have run out z/OS Disk space.

    But unfortunately the person who set up SMS configuration has been resigned our project.

    Do you know where I should check to see if there is enough capacity in the SMS settings to confirm z/OS Disk space ?

     

    Regards,

     

    Shigeto Iwata.

    shigeto.iwata


  • 8.  Re: Issue with Mainframe z Development and Test Environment server(INDEX creating error)

    Posted Thu October 17, 2019 07:00 AM

    Hello,

    Assuming this is SMS, you would need to determine which SMS Storage Group is being used by Db2 stogroup Y1DG016.  Once you know the SMS Storage group then you can find out which volumes are being used (and how much or little free space they have) by SMS by using the ISMF panels (Option 2.1). 

     

    Regards,

    Greg

    gkeuken


  • 9.  Re: Issue with Mainframe z Development and Test Environment server(INDEX creating error)

    Posted Thu October 17, 2019 09:36 PM

    Hi,

     

    Thank you for replying.

    I have confirmed ISMF panels (Option 2.1) .

    Please look at the attached file. Apparently nothing is set and it seems to be the default.

    What is the default capacity? And which item can be changed to solve this issue?

    shigeto.iwata

    Attachments

    ISMF panels (Option 2.1) result_20191018.xlsx


  • 10.  Re: Issue with Mainframe z Development and Test Environment server(INDEX creating error)

    Posted Fri October 18, 2019 01:16 PM

    Hello,

     

    Just hit Enter .. you can leave panels 2 and 3 blank (default).  All you want is the resulting display which should show you the disk utilization. 

    gkeuken


  • 11.  Re: Issue with Mainframe z Development and Test Environment server(INDEX creating error)

    Posted Wed October 23, 2019 02:41 AM

    Hi

     

    Thank you for replying.

     

    The volume seems to have enough space. Please look at the attached file.

     

    Best Regards.

    shigeto.iwata

    Attachments

    Confirming how much or little free space in the volume_2019.xlsx


  • 12.  Re: Issue with Mainframe z Development and Test Environment server(INDEX creating error)

    Posted Wed October 23, 2019 07:11 AM

    Hello,

     

    If space is not the problem then you may need to look back at my first post which briefly describes Db2 Code 00C2010D, and you may need to take actions based on that error.

     

    Regards,

    Greg

    gkeuken


  • 13.  Re: Issue with Mainframe z Development and Test Environment server(INDEX creating error)

    Posted Thu October 24, 2019 01:26 AM

    Hi.

     

    If space is not the problem there two solutions.
    Either run the utility REPAIR LEVELID or recover the table space or index.
    IBM manual is wrriten like that.


    I have tried to run the utility REPAIR LEVELID. But invalid error occurred.
    Please look at the attached file 'Executing REPAIR LEVELID(Invalid selection error).xlsx'.

    To recover the table space or index is so complicated.
    I think 'SYSTSISS' table space may be used for system configuration.
    If I drop and re-create this table space, Our z / os system may break.

    Is it really OK to drop and re-create 'SYSTSISS'?

    shigeto.iwata

    Attachments

    Executing REPAIR LEVELID(Invalid selection error).xlsx


  • 14.  Re: Issue with Mainframe z Development and Test Environment server(INDEX creating error)

    Posted Thu October 24, 2019 02:51 AM

     

    Hello,

    You could try running the repair utility without using the Db2 Admin Tool. There is some risk in running this as it could create inconsistencies.

    Since this is not a ZD&T issue, you might try posting this question on a Db2 forum, or if you are able try opening a call with Db2 support.

     

    Regards,

    Greg

    gkeuken


  • 15.  Re: Issue with Mainframe z Development and Test Environment server(INDEX creating error)

    Posted Thu October 24, 2019 09:42 PM

    Hi.

     

    I executed REPAIR LEVELID by JCL. And I could resolve this issue.

    Please look at the attached file.

     

    By the way, do you know when this issue happens? If I know it I can do some permanent solution.

     

    Best Regards.

    shigeto.iwata

    Attachments

    DB2 index create successfully.xlsx


  • 16.  Re: Issue with Mainframe z Development and Test Environment server(INDEX creating error)

    Posted Mon October 28, 2019 07:11 AM

    Great .. glad things worked out.  I'm not sure what conditions would cause this error, there are likely many possibilities. Ensure you shutdown Db2 cleanly prior to stopping the ZD&T emulator (this could be one cause). 

    If you know when the error happened the system logs might be a place to look. 

     

    Regards,

    Greg

    gkeuken


  • 17.  Re: Issue with Mainframe z Development and Test Environment server(INDEX creating error)

    Posted Tue October 29, 2019 09:21 PM

    Hi.

     

    OK. I'll close this case. Thank you for replying.

    shigeto.iwata


Related Content