Messages

1

iSeries / Re: changing to single table stragegy deletes (empy) old table on creating new one

« on: September 10, 2021, 07:57:24 AM »

Thanks Justin.

And I only see 3 topics from 2021 in this iSeries forum, of which 2 on today by me, but I guess that's all

2

iSeries / changing to single table strategy deletes (empy) old table on creating new one

« on: September 10, 2021, 05:34:11 AM »

Hello,

We should add some fields to an application group and that will create new segment tables, as we experienced.
In the meantime, we changed the strategy from "maximum number of rows" to "single table"
At the moment we did an ARSLOAD, a new segment table was created, but the current table is gone.
This only seems to happen when the current table is empty, and not when the current table contains documents.

Example:
Current table is BBA3.
We added a field to the application group and loaded a document with ARSLOAD.
In the joblog, we see that BBA3 was copied (1 record, however it was empty) and deleted (many files BBA3_##).
This happened at the moment we added a new field to the application group, according to the timestamp.
BBA4 was created at the moment we did the ARSLOAD.
BBA4 only contained 1 document, because BBA3 was empty.

All our other tables with the new "single table" strategy still contained documents.
These were not deleted when new segment tables were created.
Is this the way it works: deleting empty ones and leave the other ones as is?

We have to do the same changes in production soon and want to be sure the combination "single table" and adding new fields to the AG (creating new tables) will not have side-effects with deleted data.

Thanks,
Henri

(What happened to this forum? Are topics gone from the iSeries forum?)

3

iSeries / new segment table not created because of missing current table

« on: September 10, 2021, 05:06:02 AM »

Hello,

We should add a new field to an existing application group and that will create new segment tables, as we experienced in the past.
But for 1 application group, the old/current table was missing, and on loading the first document, we got problems.
We got some error messages like ARS0013E that a column was missing and ARS0088E that the loading failed.
Meanwhile in the ARSAG table, the SEG_ID was incremented by 1, but the new table for this segment was not created.
I guess that this is because the current table could not be copied into a new one with the extra field.
We restored the missing table, which was empty anyway, and retried the load.
But since the SEG_ID was already incremented, the ARSAG record still points to a missing table.
Everytime we retry a load, the SEG_ID is incremented, without creating a new table, making data in ARSAG corrupt (maybe a suggestion to solve).

With specific names:
AGID_NAME is called NBA and the latest SEG_ID was 2, but NBA2 was missing.
After doing an ARSLOAD to store the first document, SEG_ID was incremented to 3, but NBA3 was not created.
NBA2 was restored by us, but SEG_ID is already pointing to segment 3.
So the next load was still failing, incrementing SEG_ID to 4.
At the moment SEG_ID is 6 after some retries, but the latest existing table is still NBA2.

The question is:
Can we safely do an SQL UPDATE to reset the SEG_ID number in ARSAG to the latest table in order to let this be copied on the next load? So can I update SEG_ID to 2 by SQL?
Will this solve the problem on the next load, copying NBA2 into NBA3?
Or should we do something else to synchronise the SEG_ID with the current table number.
Bonus question: Could there be a plausible reason why tables of emtpy archives get deleted somehow?

Best regards,
Henri

4

Windows Client / Re: Merging query restriction permissions for multiple usergroups on same app.group?

« on: February 25, 2021, 09:03:54 AM »

Unfortunately my client (ARSGUI.EXE) is not starting since a few weeks due to a Windows security issue according to the event log.

I'd like to try out the combination of usergroups with different SQL, but the documentation does not give me much hope:
"If the user is a member of more that one group, the groups are checked in ascending group ID number."

But what about exit points? I just read about it.

Thanks anyway,
Henri

5

Windows Client / Merging query restriction permissions for multiple usergroups on same app.group?

« on: February 25, 2021, 06:57:04 AM »

Hi,

I have a challenge in the OD-administrator to configure permissions for users in multiple groups.
In the documentation, I already found things like: "the user normally obtains the permissions of all of the groups"
That seems valid when permissions do not overlap (like on different folders or application groups), but when permissions overlap:
"When two (or more) groups provide permissions for the same folder, the user obtains the permissions of the group with the lowest GID"

For compliance with GDPR, some documents with a DocumentType (metadata / indexfield) may or may not be seen in the results of a search action.
We use the query restriction option for usergroups in application groups to get this result.

Some users belong to different usergroups. The usergroups have different permissions on the same application group using query restrictions on the DocumentType.
So even when permissions like "view" or "add" may not differ for those groups on the same AG, permissions will differ in combination with a query restriction.
I need to let a user retrieve a selection of documents through one usergroup, and a selection of other documents through another usergroup, using another query restriction.
This concerns the same application group, in which different query restrictions apply to different usergroups where the same user belongs to.

Simplified example:

User X may retrieve DocumentType 1
User Y may retrieve DocumentType 2
User Z may retrieve DocumentType 1+2

User X in UserGroup A
User Y in UserGroup B
User Z in UserGroup A+B

1 Application Group with permissions for UserGroup A and B, having Query Restrictions on DocumentType 1 and DocumentType 2 respectively.

So is this possible: One user in multiple groups, merging the outcome of multiple Query Restrictions that return separate documents?
In other words: Can the permissions for document retrieval be merged based on Query Restriction, for users in multiple usergroups on the same application group?
Or is it still the case that the usergroup with the lowest GID determines all permissions for the application group, overruling any AG permission setting from the other usergroup?
If so, any idea how to accomplish this without creating new usergroups for users with these combined permissions.

Thanks,
Henri