Sponsored Content
Full Discussion: Prophet 21 acclaim system
Operating Systems AIX Prophet 21 acclaim system Post 302999346 by bakunin on Saturday 17th of June 2017 11:23:02 PM
Old 06-18-2017
Quote:
Originally Posted by vbe
You said nothing about your OS ( I resume AIX) and version
I think i can answer that at least partially: the 43P-140 is a single-processor PowerPC 603e system (Power 3) and therefore the latest AIX version it could run would be AIX 5.1.

Regarding the question: these seem to be both messages of the application, not the OS, so i suppose the problem is with the application. ULIMITs might be a factor, though, at least regarding the first message.

I hope this helps.

bakunin
 

9 More Discussions You Might Find Interesting

1. Solaris

rsh commands not getting executed from Solaris 10 System to AIX System

Hi Friends, I am trying to execute rsh commands from Solaris 10 system to AIX system. When I give; Solaris10# rsh <hostname> ls -l , it gives me an error rshd : 0826-826 The host name for your address is not known At the same time, Solaris10# rsh <hostname> ---- gives me remote shell of... (25 Replies)
Discussion started by: jumadhiya
25 Replies

2. SCO

file system not getting mounted in read write mode after system power failure

After System power get failed File system is not getting mounted in read- write mode (1 Reply)
Discussion started by: gtkpmbpl
1 Replies

3. Shell Programming and Scripting

how to delete files at booting of system (system startup)

hi all I have a problem how to write a shell script which delete files/folder form directory whenever system boot and copy last updated folder/file in the specified directory.pse help me ASAP. i write a script which copy files in directory.I want when system boot up using script it check whether... (1 Reply)
Discussion started by: shubhig15
1 Replies

4. UNIX for Advanced & Expert Users

how to make a full system backup excluding data and restoring it to a new system

Hi, In order to have a sand box machine that I could use to test some system changes before going to production state, I'd like to duplicate a working system to a virtual one. Ideally, I'd like to manage to do it this way : - Make a full system backup excluding the user file system (this... (7 Replies)
Discussion started by: pagaille
7 Replies

5. Solaris

System hangs (freezes) on system bell/beep

I am running OpenIndiana development version oi_148 32-bit on a seven-year-old Dell Inspiron 8600. Seems to be running fine except for one particular annoyance: It freezes whenever a system bell/beep plays. I have mitigated this by turning the system bell off in gnome-terminal, which I use... (3 Replies)
Discussion started by: DeadBadger
3 Replies

6. HP-UX

how to mount a file system from a solaris server into an hp-ux system

Hi all I wonder if its possible to mount on a hp-ux server a file system that was previously mounted on a solaris 10 server. The LUN is on NetApp stoarge. The problem on hp-ux I cannot do pvcreate on the lun (disk) because contains data. Any help will be appreciated FR (2 Replies)
Discussion started by: fretagi
2 Replies

7. AIX

Accessing files on AIX system from Linux system

I have a following requirement in production system 1 : LINUX User: abcd system 2: AIX (it is hosting a production DB) Requirement user abcd from system 1 should have read access on archive log files created by DB on system 2. The log files are created with permissions 540 by user ora ,... (2 Replies)
Discussion started by: amitnm1106
2 Replies

8. AIX

Cloning a system via mksysb backup from one system and restore to new system

Hello All, I am trying to clone an entire AIX virtual machine to a new virtual machine including all partitions and OS.Can anyone help me on the procedure to follow? I am not really sure on how it can be done.Thanks in advance. Please use CODE tags for sample input, sample output, and for code... (4 Replies)
Discussion started by: gull05
4 Replies

9. UNIX for Beginners Questions & Answers

Migrating jobs from COBOL Mainframe system to UNIX system

In a nutshell requirement is to migrate the system from mainframe environment to UNIX environment (MF cobol would be used I guess). I have not much of idea in this field. I need to do some investigation on following points - - Ease of conversion - Known Data compatibility issue - Issue in... (9 Replies)
Discussion started by: Tjsureboy4me
9 Replies
Prophet::Replica(3pm)					User Contributed Perl Documentation				     Prophet::Replica(3pm)

NAME
Prophet::Replica DESCRIPTION
A base class for all Prophet replicas. METHODS
get_handle Determines what replica class to use and instantiates it. Returns the new replica object. store_local_metadata KEY => VALUE Takes a key and a value. Store some bit of metadata in a durable local datastore. Metadata isn't propagated when replicas are synced. Returns true or false. fetch_local_metadata KEY Takes a scalar key. Fetches a bit of metadata from the local metadata store. Returns the value of the key found in the local metadata store. Returns undef if there's no value for the key in the local metadata store. _url_to_replica_class Returns the replica class for the given url based on its scheme. import_changesets { from => Prophet::Replica ... } Given a Prophet::Replica to import changes from, traverse all the changesets we haven't seen before and integrate them into this replica. This routine calls traverse_changesets on the 'from' replica, passing in the most recent changeset the current replica has seen and a callback routine which calls integrate_changeset on the local replica. That callback itself takes a callback, after_integrate_changeset , which a replica implementation can use to perform some action after a changeset is integrated into a peer. after_integrate_changeset takes a paramhash, currently with only a single key, 'changeset'. import_resolutions_from_remote_replica { from => Prophet::Replica ... } Takes a Prophet::Replica object (and possibly some optional arguments) and imports its resolution changesets into this replica's resolution database. Returns immediately if either the source replica or the target replica lack a resolution database. integrate_changeset Prophet::ChangeSet Given a Prophet::ChangeSet, integrate each and every change within that changeset into the handle's replica. If there are conflicts, generate a nullification change, figure out a conflict resolution and apply the nullification, original change and resolution all at once (as three separate changes). If there are no conflicts, just apply the change. This routine also records that we've seen this changeset (and hence everything before it) from both the peer who sent it to us AND the replica which originally created it. record_changeset_and_integration Prophet::ChangeSet Given a Prophet::ChangeSet, integrate each and every change within that changeset into the handle's replica. If the state handle is in the middle of an edit, the integration of this changeset is recorded as part of that edit; if not, it is recorded as a new edit. last_changeset_from_source $SOURCE_UUID Returns the last changeset id seen from the replica identified by $SOURCE_UUID. has_seen_changeset { source_uuid => <uuid>, sequence_no => <int> } Returns true if we've previously integrated this changeset, even if we originally received it from a different peer. changeset_will_conflict Prophet::ChangeSet Returns true if any change that's part of this changeset won't apply cleanly to the head of the current replica. conflicts_from_changeset Prophet::ChangeSet Returns a Prophet::Conflict object if the supplied Prophet::ChangeSet will generate conflicts if applied to the current replica. Returns undef if the current changeset wouldn't generate a conflict. should_accept_changeset { from => Prophet::Replica, changeset => Prophet::ChangeSet } Returns true if this replica hasn't yet seen the changeset "changeset". fetch_changesets { after => SEQUENCE_NO } Fetch all changesets from this replica after the local sequence number SEQUENCE_NO. Returns a reference to an array of Prophet::ChangeSet objects. See also traverse_changesets for replica implementations to provide streamly interface. methods to be implemented by a replica backend uuid Returns this replica's uuid. latest_sequence_no Returns the sequence # of the most recently committed changeset. find_or_create_luid { uuid => UUID } Finds or creates a LUID for the given UUID. find_uuid_by_luid { luid => LUID } Finds the UUID for the given LUID. Returns "undef" if the LUID is not known. _create_luid ( 'uuid' => 'luid' ) Given a UUID => LUID hash mapping, return a new unused LUID (one higher than the mapping's current highest luid). _do_userdata_read $PATH $DEFAULT Returns a reference to the parsed JSON contents of the file given by $PATH in the replica's userdata directory. Returns $DEFAULT if the file does not exist. _do_userdata_write $PATH $VALUE serializes $VALUE to JSON and writes it to the file given by $PATH in the replica's userdata directory, creating parent directories as necessary. _upstream_replica_cache_file A string representing the name of the file where replica URLs that have been previously pulled from are cached. _read_cached_upstream_replicas Returns a list of cached upstream replica URLs, or an empty list if there are no cached URLs. _write_cached_upstream_replicas @REPLICAS writes the replica URLs given by @REPLICAS to the upstream replica cache file. _guid2luid_file The file in the replica's userdata directory which contains a serialized JSON UUID => LUID hash mapping. _read_guid2luid_mappings Returns a UUID => LUID hashref for this replica. _write_guid2luid_mappings ( 'uuid' => 'luid' ) Writes the given UUID => LUID hash map to "/_guid2luid_file" as serialized JSON. _read_luid2guid_mappings Returns a LUID => UUID hashref for this replica. traverse_changesets { after => SEQUENCE_NO, until => SEQUENCE_NO, callback => sub { my %data = (changeset => undef, @_} } Walk through each changeset in the replica after SEQUENCE_NO, calling the "callback" for each one in turn. can_read_changesets Returns true if this source is one we know how to read from (and have permission to do so). can_write_changesets Returns true if this source is one we know how to write to (and have permission to write to). Returns false otherwise. record_resolutions Prophet::ChangeSet Given a resolution changeset, record all the resolution changesets as well as resolution records in the local resolution database. Called ONLY on local resolution creation. (Synced resolutions are just synced as records.) _record_resolution Prophet::Change Called ONLY on local resolution creation. (Synced resolutions are just synced as records.) routines dealing with integrating changesets into a replica record_changes Prophet::ChangeSet Inside an edit (transaction), integrate all changes in this changeset and then call the _after_record_changes() hook. integrate_changes Prophet::ChangeSet This routine is called by "record_changes" with a Prophet::ChangeSet object. It integrates all changes from that object into the current replica. All bookkeeping, such as opening and closing an edit, is done by "record_changes". If your replica type needs to play games to integrate multiple changes as a single record, this is what you'd override. integrate_change Prophet::Change <Prophet::ChangeSet> Integrates the given change into the current replica. Used in "integrate_changes". record_integration_of_changeset Prophet::ChangeSet This routine records the immediately upstream and original source uuid and sequence numbers for this changeset. Prophet uses this data to make sane choices about later replay and merge operations routines which need to be implemented by any Prophet backend store uuid Returns this replica's UUID. create_record { type => $TYPE, uuid => $UUID, props => { key-value pairs } } Create a new record of type $TYPE with uuid $UUID within the current replica. Sets the record's properties to the key-value hash passed in as the "props" argument. If called from within an edit, it uses the current edit. Otherwise it manufactures and finalizes one of its own. delete_record {uuid => $UUID, type => $TYPE } Deletes the record $UUID of type $TYPE from the current replica. Manufactures its own new edit if "$self-"current_edit> is undefined. set_record_props { uuid => $UUID, type => $TYPE, props => {hash of kv pairs }} Updates the record of type $TYPE with uuid $UUID to set each property defined by the props hash. It does NOT alter any property not defined by the props hash. Manufactures its own current edit if none exists. get_record_props { uuid => $UUID, type => $TYPE, root => $ROOT } Returns a hashref of all properties for the record of type $TYPE with uuid $UUID. 'root' is an optional argument which you can use to pass in an alternate historical version of the replica to inspect. Code to look at the immediately previous version of a record might look like: $handle->get_record_props( type => $record->type, uuid => $record->uuid, root => $self->repo_handle->fs->revision_root( $self->repo_handle->fs->youngest_rev - 1 ) ); record_exists {uuid => $UUID, type => $TYPE } Returns true if the record in question exists and false otherwise. list_records { type => $TYPE } Returns a reference to a list of all the records of type $TYPE. list_records Returns a reference to a list of all the known types in your Prophet database. type_exists { type => $type } Returns true if we have any records of type $TYPE. routines which need to be implemented by any _writable_ prophet backend store optional routines which are provided for you to override with backend-store specific behaviour _after_record_changes Prophet::ChangeSet Called after the replica has integrated a new changeset but before closing the current transaction/edit. The SVN backend, for example, used this to record author metadata about this changeset. _set_original_source_metadata_for_current_edit Sets "original_source_uuid" and "original_sequence_no" for the current edit. helper routines log $MSG Logs the given message to "STDERR" (but only if the "PROPHET_DEBUG" environmental variable is set). log_fatal $MSG Logs the given message and dies with a stack trace. changeset_creator The string to use as the creator of a changeset. display_name_for_replica [uuid] If the user has a "friendly" name for this replica, then use it. Otherwise, display the replica's uuid. If you pass in a uuid, it will be used instead of the replica's uuid. perl v5.10.1 2009-12-22 Prophet::Replica(3pm)
All times are GMT -4. The time now is 10:54 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy