Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

Distributed Security Control

IP.com Disclosure Number: IPCOM000108966D
Original Publication Date: 1992-Jul-01
Included in the Prior Art Database: 2005-Mar-23
Document File: 1 page(s) / 42K

Publishing Venue

IBM

Related People

Hanson, KC: AUTHOR [+2]

Abstract

Disclosed is a technique for maintaining replicated information up-to-date in a distributed AS/400* network environment. The master copy of the information is stored in one AS/400 node (the master), and the same information is replicated in multiple AS/400 nodes (shadows). This technique makes use of existing AS/400 facilities (i.e., Distributed Data Manager (DDM) and AS/400 Command Language (CL) commands) to keep the master copy and the replicated copies of information in sync. No application code is required in the AS/400 node that has the replicated information in receiving and applying the updates to the replicated information. This technique also provides customers the capability of controlling the frequency of updates based on their business needs.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 81% of the total text.

Distributed Security Control

       Disclosed is a technique for maintaining replicated
information up-to-date in a distributed AS/400* network environment.
The master copy of the information is stored in one AS/400 node (the
master), and the same information is replicated in multiple AS/400
nodes (shadows).  This technique makes use of existing AS/400
facilities (i.e., Distributed Data Manager (DDM) and AS/400 Command
Language (CL) commands) to keep the master copy and the replicated
copies of information in sync.  No application code is required in
the AS/400 node that has the replicated information in receiving and
applying the updates to the replicated information.  This technique
also provides customers the capability of controlling the frequency
of updates based on their business needs.

      In creating an object (e.g., an authorization list or a user
profile, etc.), the system administrator can optionally specify a
shadow list which determines "where" a shadow copy of the object is
required.  Every time an object is created/updated/deleted, the CL
commends used to create/update/delete the object are saved in a
database file. Periodically, an asynchronous process will be started
to propagate these changes to each affected shadow node.  The
asynchronous process reads the database file that contains all the CL
commands accumulated and issues the AS/400 Submit Remote Command
(SBMRMTCMD) to submit the CL command via the Distributed Data Manager
(DDM) for r...