IBM i Access Client Solutions

I have ACS installed and everything works well except for Schemas.  When I click on Schemas, I get this error

Our system admin said it appears to be a problem with the naming of the system. The name in the DNS server isn't exactly the same as the name in the i .

Has anyone had this problem and found a way around it?

Hi,

I don't think it's related to DNS, here we have several partitions with different DNS entry, or none.

When you launch "Run SQL Scripts", then "Connect to Database" in Connection menu, what is displayed (you may have to refresh databases list)?

I have ACS installed and everything works well except for Schemas.  When I click on Schemas, I get this error

Our system admin said it appears to be a problem with the naming of the system. The name in the DNS server isn't exactly the same as the name in the i .

Has anyone had this problem and found a way around it?

It shows connected to the system in the Run SQL Scripts window.  If I run a script, it works.  If I try to use Content Assist to display a list of columns/fields, all I get is this

Hi,

I don't think it's related to DNS, here we have several partitions with different DNS entry, or none.

When you launch "Run SQL Scripts", then "Connect to Database" in Connection menu, what is displayed (you may have to refresh databases list)?

I have ACS installed and everything works well except for Schemas.  When I click on Schemas, I get this error

Our system admin said it appears to be a problem with the naming of the system. The name in the DNS server isn't exactly the same as the name in the i .

Has anyone had this problem and found a way around it?

It shows connected to the system in the Run SQL Scripts window.  If I run a script, it works.  If I try to use Content Assist to display a list of columns/fields, all I get is this

Hi,

I don't think it's related to DNS, here we have several partitions with different DNS entry, or none.

When you launch "Run SQL Scripts", then "Connect to Database" in Connection menu, what is displayed (you may have to refresh databases list)?

I have ACS installed and everything works well except for Schemas.  When I click on Schemas, I get this error

Our system admin said it appears to be a problem with the naming of the system. The name in the DNS server isn't exactly the same as the name in the i .

Has anyone had this problem and found a way around it?

I have ACS installed and everything works well except for Schemas.  When I click on Schemas, I get this error

Our system admin said it appears to be a problem with the naming of the system. The name in the DNS server isn't exactly the same as the name in the i .

Has anyone had this problem and found a way around it?

I have ACS installed and everything works well except for Schemas.  When I click on Schemas, I get this error

Our system admin said it appears to be a problem with the naming of the system. The name in the DNS server isn't exactly the same as the name in the i .

Has anyone had this problem and found a way around it?

"Database" is NOT always the name of the system.  Check the entries in WRKRDBDIRE.  Generally you are looking for the one marked *LOCAL.  There are exceptions.  In a H/A environment you may have a primary system named PROD1 and a h/a system named PROD2.  And there may be a WRKRDBDIRE for each on each.  Then there will be another entry, in this example PROD.  Generally you're supposed to connect to PROD so that it works on either machine when they do a switch.  There are a few exceptions:  BRMS and sysadmins like me who really are trying to get to a specific machine.

I didn't see a Navigator way to get to this.

I have ACS installed and everything works well except for Schemas.  When I click on Schemas, I get this error

Our system admin said it appears to be a problem with the naming of the system. The name in the DNS server isn't exactly the same as the name in the i .

Has anyone had this problem and found a way around it?

That message you received seems to indicate that you need to click the joblog icon in Run SQL Scripts and see why the attempt to add the database entry failed.  Perhaps it tried to do a ADDRDBDIRE and you do not have authority, or a *LOCAL exists or...

"Database" is NOT always the name of the system.  Check the entries in WRKRDBDIRE.  Generally you are looking for the one marked *LOCAL.  There are exceptions.  In a H/A environment you may have a primary system named PROD1 and a h/a system named PROD2.  And there may be a WRKRDBDIRE for each on each.  Then there will be another entry, in this example PROD.  Generally you're supposed to connect to PROD so that it works on either machine when they do a switch.  There are a few exceptions:  BRMS and sysadmins like me who really are trying to get to a specific machine.

I didn't see a Navigator way to get to this.

I have ACS installed and everything works well except for Schemas.  When I click on Schemas, I get this error

Our system admin said it appears to be a problem with the naming of the system. The name in the DNS server isn't exactly the same as the name in the i .

Has anyone had this problem and found a way around it?

Is the *LOCAL a problem.  I have authority to do the ADDRDBDIRE.

That message you received seems to indicate that you need to click the joblog icon in Run SQL Scripts and see why the attempt to add the database entry failed.  Perhaps it tried to do a ADDRDBDIRE and you do not have authority, or a *LOCAL exists or...

"Database" is NOT always the name of the system.  Check the entries in WRKRDBDIRE.  Generally you are looking for the one marked *LOCAL.  There are exceptions.  In a H/A environment you may have a primary system named PROD1 and a h/a system named PROD2.  And there may be a WRKRDBDIRE for each on each.  Then there will be another entry, in this example PROD.  Generally you're supposed to connect to PROD so that it works on either machine when they do a switch.  There are a few exceptions:  BRMS and sysadmins like me who really are trying to get to a specific machine.

I didn't see a Navigator way to get to this.

I have ACS installed and everything works well except for Schemas.  When I click on Schemas, I get this error

Our system admin said it appears to be a problem with the naming of the system. The name in the DNS server isn't exactly the same as the name in the i .

Has anyone had this problem and found a way around it?

Not generally.  I would find the joblog first.  Let's see exactly what it is concerned with.

Is the *LOCAL a problem.  I have authority to do the ADDRDBDIRE.

That message you received seems to indicate that you need to click the joblog icon in Run SQL Scripts and see why the attempt to add the database entry failed.  Perhaps it tried to do a ADDRDBDIRE and you do not have authority, or a *LOCAL exists or...

"Database" is NOT always the name of the system.  Check the entries in WRKRDBDIRE.  Generally you are looking for the one marked *LOCAL.  There are exceptions.  In a H/A environment you may have a primary system named PROD1 and a h/a system named PROD2.  And there may be a WRKRDBDIRE for each on each.  Then there will be another entry, in this example PROD.  Generally you're supposed to connect to PROD so that it works on either machine when they do a switch.  There are a few exceptions:  BRMS and sysadmins like me who really are trying to get to a specific machine.

I didn't see a Navigator way to get to this.

I have ACS installed and everything works well except for Schemas.  When I click on Schemas, I get this error

Our system admin said it appears to be a problem with the naming of the system. The name in the DNS server isn't exactly the same as the name in the i .

Has anyone had this problem and found a way around it?

The system auto creates a DBRDIRE of  EBRD  *LOCAL if the base settings are removed.

While that entry is in there, the Schemas function fails trying to create a new *LOCAL entry of SYSBAS *LOCAL.

If I manually delete the EBRD *LOCAL RDBDIRE on the iSeries and then run the Schemas function in ACS quickly, it will create a DBRDIRE of SYSBAS *LOCAL and work properly to bring up the Schemas one time.     Any subsequent attempts to use the Schemas function off the ACS menu fails again as it's still trying to Replace the *local entry and failing because there already is one.  The dumped joblog just refers to the exception, Cannot create *local DBRDIRE  (because there already is one)

We have this same issue on an older V7R2 system, an older V7R3 system and a brand new Power 10 running V7R4M0

(And yes, I work with MaryAnn)

------------------------------
Gary Martin

Original Message:
Sent: Wed March 20, 2024 02:10 PM
From: Robert Berendt
Subject: Problem Accessing Schemas

Not generally.  I would find the joblog first.  Let's see exactly what it is concerned with.

Is the *LOCAL a problem.  I have authority to do the ADDRDBDIRE.

That message you received seems to indicate that you need to click the joblog icon in Run SQL Scripts and see why the attempt to add the database entry failed.  Perhaps it tried to do a ADDRDBDIRE and you do not have authority, or a *LOCAL exists or...

"Database" is NOT always the name of the system.  Check the entries in WRKRDBDIRE.  Generally you are looking for the one marked *LOCAL.  There are exceptions.  In a H/A environment you may have a primary system named PROD1 and a h/a system named PROD2.  And there may be a WRKRDBDIRE for each on each.  Then there will be another entry, in this example PROD.  Generally you're supposed to connect to PROD so that it works on either machine when they do a switch.  There are a few exceptions:  BRMS and sysadmins like me who really are trying to get to a specific machine.

I didn't see a Navigator way to get to this.

I have ACS installed and everything works well except for Schemas.  When I click on Schemas, I get this error

Our system admin said it appears to be a problem with the naming of the system. The name in the DNS server isn't exactly the same as the name in the i .

Has anyone had this problem and found a way around it?

Ok.  I have an lpar named GDI.

DSPNETA shows the system name as GDI.

My Windows DNS server has an entry for GDI.

In iACS, Management, System Configurations, this lpar appears as System name:  GDI.dekko.com

In WRKRDBDIRE  I have GDI                 *LOCAL with

Relational database  . . . . . . :   GDI   
Remote location:                           
  Remote location  . . . . . . . :   *LOCAL
    Type . . . . . . . . . . . . :   *IP   
  Port number or service name  . :   *DRDA 

That SYSBAS name you displayed is confusing.  This leads me to believe that maybe you are using iASPs and something in that configuration is bewildering iACS' Schemas.

I believe each iASP should have it's own entry in WRKRDBDIRE but it should be assigned to LOOPBACK as per https://www.ibm.com/support/pages/accessing-objects-independent-asp-using-ddm-connections

For more information check out the subtopics regarding this at https://www.ibm.com/docs/en/i/7.5?topic=directory-working-relational-database

I am NOT a Power H/A user and do not pretend to know how to set all that up for such a scenario.  I use software replication (Quick-EDD) instead.  I also do not use any iASPs.

The system auto creates a DBRDIRE of  EBRD  *LOCAL if the base settings are removed.

While that entry is in there, the Schemas function fails trying to create a new *LOCAL entry of SYSBAS *LOCAL.

If I manually delete the EBRD *LOCAL RDBDIRE on the iSeries and then run the Schemas function in ACS quickly, it will create a DBRDIRE of SYSBAS *LOCAL and work properly to bring up the Schemas one time.     Any subsequent attempts to use the Schemas function off the ACS menu fails again as it's still trying to Replace the *local entry and failing because there already is one.  The dumped joblog just refers to the exception, Cannot create *local DBRDIRE  (because there already is one)

We have this same issue on an older V7R2 system, an older V7R3 system and a brand new Power 10 running V7R4M0

(And yes, I work with MaryAnn)

------------------------------
Gary Martin

Original Message:
Sent: Wed March 20, 2024 02:10 PM
From: Robert Berendt
Subject: Problem Accessing Schemas

Not generally.  I would find the joblog first.  Let's see exactly what it is concerned with.

Is the *LOCAL a problem.  I have authority to do the ADDRDBDIRE.

That message you received seems to indicate that you need to click the joblog icon in Run SQL Scripts and see why the attempt to add the database entry failed.  Perhaps it tried to do a ADDRDBDIRE and you do not have authority, or a *LOCAL exists or...

"Database" is NOT always the name of the system.  Check the entries in WRKRDBDIRE.  Generally you are looking for the one marked *LOCAL.  There are exceptions.  In a H/A environment you may have a primary system named PROD1 and a h/a system named PROD2.  And there may be a WRKRDBDIRE for each on each.  Then there will be another entry, in this example PROD.  Generally you're supposed to connect to PROD so that it works on either machine when they do a switch.  There are a few exceptions:  BRMS and sysadmins like me who really are trying to get to a specific machine.

I didn't see a Navigator way to get to this.

I have ACS installed and everything works well except for Schemas.  When I click on Schemas, I get this error

Our system admin said it appears to be a problem with the naming of the system. The name in the DNS server isn't exactly the same as the name in the i .

Has anyone had this problem and found a way around it?

We are not using an iASP.   Good old basic ASP, single partition machine here.

Navigator for I is the one that wants to ADDDBRDIRE of SYSBAS.    

If I clear the DBRDIRE on the iSeries and give it a minute, the one it puts in place is EBRD *LOCAL, which is our DSPNETA node name.

That's the run, the Schemas button in ACS keeps wanting to replace the DBRDIRE with that SYSBAS thing.

Ok.  I have an lpar named GDI.

DSPNETA shows the system name as GDI.

My Windows DNS server has an entry for GDI.

In iACS, Management, System Configurations, this lpar appears as System name:  GDI.dekko.com

In WRKRDBDIRE  I have GDI                 *LOCAL with

Relational database  . . . . . . :   GDI   
Remote location:                           
  Remote location  . . . . . . . :   *LOCAL
    Type . . . . . . . . . . . . :   *IP   
  Port number or service name  . :   *DRDA 

That SYSBAS name you displayed is confusing.  This leads me to believe that maybe you are using iASPs and something in that configuration is bewildering iACS' Schemas.

I believe each iASP should have it's own entry in WRKRDBDIRE but it should be assigned to LOOPBACK as per https://www.ibm.com/support/pages/accessing-objects-independent-asp-using-ddm-connections

For more information check out the subtopics regarding this at https://www.ibm.com/docs/en/i/7.5?topic=directory-working-relational-database

I am NOT a Power H/A user and do not pretend to know how to set all that up for such a scenario.  I use software replication (Quick-EDD) instead.  I also do not use any iASPs.

The system auto creates a DBRDIRE of  EBRD  *LOCAL if the base settings are removed.

While that entry is in there, the Schemas function fails trying to create a new *LOCAL entry of SYSBAS *LOCAL.

If I manually delete the EBRD *LOCAL RDBDIRE on the iSeries and then run the Schemas function in ACS quickly, it will create a DBRDIRE of SYSBAS *LOCAL and work properly to bring up the Schemas one time.     Any subsequent attempts to use the Schemas function off the ACS menu fails again as it's still trying to Replace the *local entry and failing because there already is one.  The dumped joblog just refers to the exception, Cannot create *local DBRDIRE  (because there already is one)

We have this same issue on an older V7R2 system, an older V7R3 system and a brand new Power 10 running V7R4M0

(And yes, I work with MaryAnn)

------------------------------
Gary Martin

Original Message:
Sent: Wed March 20, 2024 02:10 PM
From: Robert Berendt
Subject: Problem Accessing Schemas

Not generally.  I would find the joblog first.  Let's see exactly what it is concerned with.

Is the *LOCAL a problem.  I have authority to do the ADDRDBDIRE.

That message you received seems to indicate that you need to click the joblog icon in Run SQL Scripts and see why the attempt to add the database entry failed.  Perhaps it tried to do a ADDRDBDIRE and you do not have authority, or a *LOCAL exists or...

"Database" is NOT always the name of the system.  Check the entries in WRKRDBDIRE.  Generally you are looking for the one marked *LOCAL.  There are exceptions.  In a H/A environment you may have a primary system named PROD1 and a h/a system named PROD2.  And there may be a WRKRDBDIRE for each on each.  Then there will be another entry, in this example PROD.  Generally you're supposed to connect to PROD so that it works on either machine when they do a switch.  There are a few exceptions:  BRMS and sysadmins like me who really are trying to get to a specific machine.

I didn't see a Navigator way to get to this.

I have ACS installed and everything works well except for Schemas.  When I click on Schemas, I get this error

Our system admin said it appears to be a problem with the naming of the system. The name in the DNS server isn't exactly the same as the name in the i .

Has anyone had this problem and found a way around it?

We are not using an iASP.   Good old basic ASP, single partition machine here.

Navigator for I is the one that wants to ADDDBRDIRE of SYSBAS.    

If I clear the DBRDIRE on the iSeries and give it a minute, the one it puts in place is EBRD *LOCAL, which is our DSPNETA node name.

That's the run, the Schemas button in ACS keeps wanting to replace the DBRDIRE with that SYSBAS thing.

Ok.  I have an lpar named GDI.

DSPNETA shows the system name as GDI.

My Windows DNS server has an entry for GDI.

In iACS, Management, System Configurations, this lpar appears as System name:  GDI.dekko.com

In WRKRDBDIRE  I have GDI                 *LOCAL with

Relational database  . . . . . . :   GDI   
Remote location:                           
  Remote location  . . . . . . . :   *LOCAL
    Type . . . . . . . . . . . . :   *IP   
  Port number or service name  . :   *DRDA 

That SYSBAS name you displayed is confusing.  This leads me to believe that maybe you are using iASPs and something in that configuration is bewildering iACS' Schemas.

I believe each iASP should have it's own entry in WRKRDBDIRE but it should be assigned to LOOPBACK as per https://www.ibm.com/support/pages/accessing-objects-independent-asp-using-ddm-connections

For more information check out the subtopics regarding this at https://www.ibm.com/docs/en/i/7.5?topic=directory-working-relational-database

I am NOT a Power H/A user and do not pretend to know how to set all that up for such a scenario.  I use software replication (Quick-EDD) instead.  I also do not use any iASPs.

The system auto creates a DBRDIRE of  EBRD  *LOCAL if the base settings are removed.

While that entry is in there, the Schemas function fails trying to create a new *LOCAL entry of SYSBAS *LOCAL.

If I manually delete the EBRD *LOCAL RDBDIRE on the iSeries and then run the Schemas function in ACS quickly, it will create a DBRDIRE of SYSBAS *LOCAL and work properly to bring up the Schemas one time.     Any subsequent attempts to use the Schemas function off the ACS menu fails again as it's still trying to Replace the *local entry and failing because there already is one.  The dumped joblog just refers to the exception, Cannot create *local DBRDIRE  (because there already is one)

We have this same issue on an older V7R2 system, an older V7R3 system and a brand new Power 10 running V7R4M0

(And yes, I work with MaryAnn)

------------------------------
Gary Martin

Original Message:
Sent: Wed March 20, 2024 02:10 PM
From: Robert Berendt
Subject: Problem Accessing Schemas

Not generally.  I would find the joblog first.  Let's see exactly what it is concerned with.

Is the *LOCAL a problem.  I have authority to do the ADDRDBDIRE.

That message you received seems to indicate that you need to click the joblog icon in Run SQL Scripts and see why the attempt to add the database entry failed.  Perhaps it tried to do a ADDRDBDIRE and you do not have authority, or a *LOCAL exists or...

"Database" is NOT always the name of the system.  Check the entries in WRKRDBDIRE.  Generally you are looking for the one marked *LOCAL.  There are exceptions.  In a H/A environment you may have a primary system named PROD1 and a h/a system named PROD2.  And there may be a WRKRDBDIRE for each on each.  Then there will be another entry, in this example PROD.  Generally you're supposed to connect to PROD so that it works on either machine when they do a switch.  There are a few exceptions:  BRMS and sysadmins like me who really are trying to get to a specific machine.

I didn't see a Navigator way to get to this.

I have ACS installed and everything works well except for Schemas.  When I click on Schemas, I get this error

Our system admin said it appears to be a problem with the naming of the system. The name in the DNS server isn't exactly the same as the name in the i .

Has anyone had this problem and found a way around it?