HP AutoSYNC User’s Guide Abstract HP NonStop™ AutoSYNC™ software is a reliable, fault-tolerant, and automatic subsystem for replicating files through synchronization. This manual describes the uses, installation, and all other operational aspects of AutoSYNC. Product Version AutoSYNC AAW Supported Release Version Updates (RVUs) This manual supports all J-series RVUs, all H-series RVUs, and all G-series RVUs, until otherwise indicated in a replacement publication.
Document History Part Number Product Version Published 522580-016 NonStop AutoSYNC AAR (Update 15) June 2011 522580-017 NonStop AutoSYNC AAT (Update 16) February 2012 522580-018 NonStop AutoSYNC AAU (Update 17) November 2012 522580-019 NonStop AutoSYNC AAV (Update 18) March 2013 522580-020 NonStop AutoSYNC AAW (Update 19) November 2013
Legal Notices Copyright 2012 Hewlett-Packard Development Company L.P. Legal Notice Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor’s standard commercial license. The information contained herein is subject to change without notice.
HP AutoSYNC User’s Guide Index Tables . Legal Notices 1.
3. One-time Synchronization Contents Authorize AutoSYNC 2-7 Update the System Coldload and Shutdown Procedures 2-8 Install the AutoSYNC EMS templates 2-8 Shutting Down AutoSYNC 2-8 Installing a New Version of AutoSYNC 2-9 Running Different Versions of AutoSYNC 2-9 Special Cases: Privileged Synchronization Processes 2-10 3.
4.
5.
7. Synchronization Over TCP/IP Contents TRIGGERONFILESET 6-3 TRIGGERONFILESET Arguments Trigger Output 6-3 Triggers and TIMEEXACT 6-3 Troubleshooting triggers 6-4 Examples 6-4 TRIGGER examples 6-4 TRIGGERONFILESET Example 6-7 Note on Triggers that invoke SQLCI 6-7 6-3 7.
8.
9. Reporting Function Contents OUT 8-85 PURGEDATA 8-85 RENAME 8-85 RESET 8-86 RESET GLOBAL 8-86 RESET LOCAL 8-87 REPORT 8-88 RUN[D] 8-91 START MONITOR 8-92 STATS 8-93 STATUS AUTOSYNC 8-93 STATUS BATCHID 8-94 STATUS MONITOR 8-95 STATUS SYNC 8-96 STATUS SYNCFILESET 8-97 STOP MONITOR 8-98 ABEND MONITOR 8-99 SUSPEND BATCHID 8-99 SUSPEND SYNCFILESET 8-99 SUSPEND SYNCUSER 8-100 SYNCHRONIZE 8-100 TIME 8-117 UPDATE 8-118 UPGRADE MAPDB 8-121 VOLUME 8-121 9.
B.
C. Examples Contents A synchronization process does not start B-1 Scheduled Synchronization Problems B-2 The source synchronization process creation fails with security violation B-2 The destination synchronization process creation fails with a security violation B-2 The destination synchronization process starts but fails to log down to the sync user ID B-2 Errors replacing destination files B-2 Synchronization of OSS files fails with error 4001 or error 4013.
Tables Contents Tables Table 2-1. Table 2-2. Table 8-1. Table 8-2. Table 8-3. Table A-1. Table A-2.
What’s New in This Manual Manual Information HP AutoSYNC User’s Guide Abstract HP NonStop™ AutoSYNC™ software is a reliable, fault-tolerant, and automatic subsystem for replicating files through synchronization. This manual describes the uses, installation, and all other operational aspects of AutoSYNC.
New and Changed Information What’s New in This Manual The new command INFO TCPIP has been added to display TCP/IP settings as configured on the system. AutoSYNC has been enhanced to prevent synchronizations into the current active SysDB and MapDB subvolumes.Also, the current active destination SYSDB and MapDB subvolumes are now automatically excluded from being purged through the use of the PURGE and SUBVOLPURGE options. See AutoSYNC Configuration Database on page A-1.
About This Manual This manual describes the uses, installation, and all other operational aspects of HP AutoSYNC. AutoSYNC is a reliable, fault-tolerant, and automatic subsystem for replicating files through synchronization. File synchronization is a complementary alternative to data replication for disaster recovery. Data replication is used primarily for database files; it replicates each record update that occurs in a database transaction.
General Syntax Notation About This Manual each side of the list, or horizontally, enclosed in a pair of brackets and separated by vertical lines. For example: FC [ num ] [ -num] [ text] K [ X | D ] address-1 { } Braces. A group of items enclosed in braces is a list from which you are required to choose one item. The items in the list may be arranged either vertically, with aligned braces on each side of the list, or horizontally, enclosed in a pair of braces and separated by vertical lines.
Notation for Messages About This Manual Line Spacing. If the syntax of a command is too long to fit on a single line, each continuation line is indented three spaces and is separated from the preceding line by a blank line. This spacing distinguishes items in a continuation line from items in a vertical list of selections. For example: ALTER [ / OUT file-spec / ] LINE [ , attribute-spec ]... !i and !o.
Notation for Messages About This Manual Nonitalic text. Nonitalic letters, numbers, and punctuation indicate text that is displayed or returned exactly as shown. For example: Backup Up. lowercase italic letters. Lowercase italic letters indicate variable items whose values are displayed or returned. For example: p-register process-name [ ] Brackets. Brackets enclose items that are sometimes, but not always, displayed.
Notation for Management Programming Interfaces About This Manual Notation for Management Programming Interfaces The following list summarizes the notation conventions used in the boxed descriptions of programmatic commands, event messages, and error lists in this manual. UPPERCASE LETTERS. Uppercase letters indicate names from definition files; enter these names exactly as shown. For example: ZCOM-TKN-SUBJ-SERV lowercase letters.
Change Bar Notation About This Manual HP AutoSYNC User’s Guide—522580-020 xviii
1 AutoSYNC Overview Introduction HP NonStop AutoSYNC software (AutoSYNC) provides automatic synchronization for HP NonStop server disk files. File synchronization is a complementary alternative to data replication for disaster recovery. Data replication is used primarily for database files; it replicates each record update that occurs in a database transaction.
Product Overview AutoSYNC Overview Product Overview This section gives a brief overview of AutoSYNC; a more complete description can be found in later sections. File Sets AutoSYNC synchronizes Enscribe files and SQL tables between pairs of source and destination locations. These locations are described by file set patterns, such as $DATA.APP*.*OBJ.
Fault Tolerance and File Recovery AutoSYNC Overview To configure a scheduled synchronization, a user must be added to the AutoSYNC system. An AutoSYNC administrator enables users to schedule synchronizations and can specify a maximum priority and select CPUs that the user should use. The AutoSYNC administrator can also suspend and activate a user without changing the user’s configuration. Fault Tolerance and File Recovery Scheduled synchronizations are managed by a fault-tolerant process pair.
Reporting AutoSYNC Overview Reporting It is often difficult to measure how dynamic your processing environment really is. The reporting function allows you to evaluate the amount of change that occurs on the file sets you wish to synchronize, without performing the actual data movement. Reporting is useful for planning system migrations and for configuring the frequency of scheduled synchronizations, either for disaster recovery or for data distribution purposes.
System and Map Databases AutoSYNC Overview communicate efficiently to compare file information and pass a stream of data containing the files that need to be copied. System and Map Databases Each system that has AutoSYNC installed has a single system database (SysDB) either in the subvolume $SYSTEM.ESCSYSDB or in the ESCSYSDB subvolume on some other disk volume. This database is a central reference point for other AutoSYNC components.
AutoSYNC Overview AutoSYNC in a Network of Systems HP AutoSYNC User’s Guide—522580-020 1-6
2 Installation This section discusses the procedure to follow for the initial installation of AutoSYNC. The topics covered are organized as follows: Prerequisites Installing AutoSYNC Installing a New Version of AutoSYNC Running Different Versions of AutoSYNC Special Cases: Privileged Synchronization Processes Prerequisites The AutoSYNC (SysDB and MapDB) configuration is stored in a set of audited SQL tables. The HP NonStop TMF product must be installed and configured.
Move Files from the Product Media to the Installation Subvolume Installation Privileged Synchronization Processes on page 2-10 for details. The entire process should take only a few minutes. In addition to the installation instructions contained in this manual, you should have your AutoSYNC system licensing instructions available. Move Files from the Product Media to the Installation Subvolume The AutoSYNC product media contains the files listed in Table 2-1.
Start an EMS Distributor Installation Then execute the INSTALL macro as follows:. VOLUME $.ZAUTOSYC RUN INSTALL You may specify a subvolume in which to install the AutoSYNC operational files. In a network of systems, where application software might be copied from one system to another, choose a volume and subvolume that can be specified on all systems. The example below shows the installation to subvolume $UTIL.AUTOSYNC: volume $system.zautosyc $SYSTEM ZAUTOSYC 3> install $util.
Create the AutoSYNC System Database Installation Create the AutoSYNC System Database Each system running AutoSYNC maintains system-level parameters stored in a small set of tables to control the overall operation of the product. This set of tables is referred to as the System Database (SysDB). If you have already installed HP NonStop AutoTMF software, the SysDB has already been created and will be used by AutoSYNC.
License AutoSYNC Installation SYSDB on page 8-68 for details on the command. AutoSYNC 1? create sysdb on $data; --- SQL Catalog $DATA.ESCCATLG is being created. --- SQL Catalog $DATA.ESCCATLG has been created. --- SysDB table $DATA.ESCSYSDB.MAPDBS created. --- SysDB table $DATA.ESCSYSDB.REGISTRY created. * Error * The monitor process $ZASY is not executing. * 652 * To start a monitor, issue the START MONITOR command. *Warning* Process $ZASY is not configured as a monitor process.
Start the Monitor Process Installation The CREATE MAPDB command creates the SYNCUSER table, to store user information and the REGISTRY table to store global parameters. The scheduled synchronization configuration tables and log files are added later, as sync file sets are configured for each syncuser. See Appendix A, Operations and Management, for details on the additional MapDB tables. AutoSYNC 3? create mapdb; --- MapDB table $DATA.ASYMAPDB.REGISTRY created. --- MapDB table $DATA.ASYMAPDB.
Authorize AutoSYNC Installation For example: 26> autosync HP Nonstop(tm) AutoSYNC(tm) Command Interpreter(T2713H01) - System \BLPROD (C)2010 Hewlett Packard Development Company, L.P. (C)2010 Carr Scott Software Incorporated * Error * The monitor process $ZASY is not executing. * 652 * To start a monitor, issue the START MONITOR command. AutoSYNC 1? start monitor; --- Starting Monitor process $ZASY AutoSYNC Monitor 1.9.
Update the System Coldload and Shutdown Procedures Installation designating a user ID as the Authorizer. Only users that are “under” the Authorizer can schedule synchronizations. See The AutoSYNC Authorizer on page 4-2 for details. By default, the Authorizer is the user ID of the monitor process. To designate the Authorizer explicitly, log on as the desired user ID and use the AUTHORIZE command. The command sets the ownership of the ASYSYNCP process to the Authorizer through the PROGID file attribute.
Installing a New Version of AutoSYNC Installation 1. Use the SUSPEND SYNCUSER command to suspend all AutoSYNC users. 2. Wait for active synchronizations to complete. Use the STATUS SYNC command to display the active synchronizations. 3. Stop the AutoSYNC monitor process with the AUTOSYNC command STOP MONITOR. Note that there are no ill effects resulting from stopping the monitor without first suspending the syncusers.
Installation Special Cases: Privileged Synchronization Processes Using an Alternate AutoSYNC Environment on page A-8. Special Cases: Privileged Synchronization Processes Certain synchronization file sets may require the use of a privileged ASYSYNC or ASYSYNCP process: If, on the source system, the AutoSYNC Authorizer does not have the privileges to “log down” as another user ID, one of the options is to license the local ASYSYNCP process.
3 One-time Synchronization This section presents a basic overview of AutoSYNC processing and the various options available for performing a one-time synchronization of Guardian files. AutoSYNC also supports the synchronization of OSS files, as described in Section 5, OSS File Synchronization. Most of the features described in this section also apply to scheduled synchronization, described in Section 4, Scheduled Synchronization.
File Sets One-time Synchronization File Sets The file sets describe the collection of files to be synchronized. A file set is a standard file pattern, such as \MYSYS.$DATA*.OBJ*.SERV*. There are a few restrictions on the source and destination file sets. Source file set Destination file set Source File Set to Destination File Set File Set Comparison Source file set The source file set must describe only local files.
File Set Comparison One-time Synchronization File Set Comparison AutoSYNC creates a list of all file names in the source file set. Some files are not eligible for synchronization; these files include: Files that are opened exclusively. AutoSYNC cannot gain access to such files. Files that are opened for update. Copying files that are being updated often results in corrupt files. You can request such files to be synchronized by using the OPENUPDATE option. Broken or corrupt files.
Data Transfer and File Replacement One-time Synchronization A corrupt or broken destination file is always replaced, even if it is newer than the source file. Files that do not have the same modification times are synchronized if the TIMEEXACT option is specified. Data Transfer and File Replacement Once the list of files to be synchronized is complete, AutoSYNC transfers the files using an efficient data-streaming protocol.
Ownership and Security One-time Synchronization synchronized files on the destination system. Thus, you can change security attributes as follows: Source file security Remote destination file security “A” or “N” “N” “G” or “C” “C” “O” or “U” “U” “-” “-” You may use the SECURE or NO NETWORKSECURE option to override the default security setting. Default PURGE Security To be replaced by AutoSYNC, existing destination files must be secured for purge access.
Alternate Key Files One-time Synchronization does not change the security string of the destination file and it remains the same as the source file. If the user chooses to preserve security attributes on the destination system, subsequent synchronizations could fail. For example a PURGE security of “O” preserved on the destination system will prevent further synchronizations because the file can only be replaced by the local (destination) owner of the file.
SQL Tables and Catalogs One-time Synchronization Example 1 File $DATA.DB.ACCT has one alternate key, $DATA.DB.ACCTAK. The following command synchronizes both the file ACCT and its alternate key ACCTAK to $BACKUP.DBBACK on the destination system: SYNC $DATA.DB.ACCT* to \DEST.$BACKUP.DBBACK.*; Note that no MAPNAMES file is required. Example 2 File $DATA.DB.ACCT has its alternate key ACCTAK on subvolume $KEYS.DBKEYS.
SQL Views One-time Synchronization If the index tables reside in a different subvolume than the base table in the source file set, use the MAPNAMES option to specify the mapping of the source names to the destination names. The destination file set must be defined using a filename that has the wild-card character asterisk (*); otherwise SQL tries to restore indexes and base table to the same filename. SYNC $DATA.SQLTBL.MYTBL TO \DEST.$DATA.SQLTBL.
SQL Collations One-time Synchronization When a shorthand view is synchronized, it is marked as corrupted if a table it references is not present on the destination system. This can create a problem if the view name alphabetically precedes the name(s) of the base tables. SQL Collations SQL collations are backed up as a combination of a collation file label and an immediately-following temporary edit file. AutoSYNC treats this pair of items as a single unit for recovery, OPENUPDATE and trigger processing.
Partitioned Files and Tables One-time Synchronization command. AutoSYNC does not see the mapnames-file entry and assumes the destination file is on $DATA01, and the following command will yield incorrect results: SYNC $DATA01.DB.PARTFILE TO \DEST.*.*.*, MAPNAMES mapnames-file;... where mapnames-file has entry: $DATA01.*.* TO $BACK01.*.* Instead, first specify: SYNC $DATA01.DB.PARTFILE TO \DEST.$BACK01.*.*, MAPNAMES mapnames-file...
Partitioned Files and Tables One-time Synchronization File name mapping The mapnames-file entries are similar to, but not exactly the same as, the MAP NAMES option of RESTORE. Each line of the MAPNAMES file contains a single mapping of the form: source-file-pattern TO destination-file-pattern The file name can be partially qualified; AutoSYNC replaces the missing portion of the name with the wild card asterisk(*). For example, the following entries: $DATA TO $BACK \NEWYORK.$DATA*.DB TO $BACK.
Synchronization Options One-time Synchronization Catalog mapping The information supplied by MAPNAMES is also used to perform SQL catalog volume mapping. You should include mapnames-file entries if catalogs are located on different volumes or subvolumes on the destination system. Note that SQL catalogs are never synchronized by AutoSYNC, but synchronized SQL objects have references to SQL catalogs that might require name mapping.
Making Exact Copies One-time Synchronization Changing File Security Compression Process Priority and Throttling Recovery Making Exact Copies By default, AutoSYNC does not synchronize a file if the destination file was modified more recently than the source file. This behavior allows you to customize the destination file for local use. When AutoSYNC synchronizes a file, the two files are exactly the same, including the modification time stamp.
Purging Extra Subvolumes in the Destination File Set One-time Synchronization extra subvolumes, specify the SUBVOLPURGE option in addition to the PURGE option, as described in the paragraph Purging Extra Subvolumes in the Destination File Set below. PURGE also applies to patterns such as $DATA.MYSUB*.SRV*. For each source subvolume that has files that match the pattern, AutoSYNC purges extra destination files that match the source file set pattern.
Files Opened for Update One-time Synchronization Exceptions: If the AUDIT option is specified and the destination file is audited, the rename operation cannot succeed. AutoSYNC issues a warning message, the file is skipped and the destination file is not replaced. A synchronized file, table, index or view does not replace an existing object of a different type. Files Opened for Update By default, AutoSYNC does not synchronize a file from the source file set if the file is opened for update.
Changing File Ownership One-time Synchronization Changing File Ownership By default, the ownership of each synchronized file is preserved. You may specify the OWNER option to give the files to any user ID, including your own user ID. Note that for OSS files, only SUPER.SUPER can change the ownership of a file on the destination. Moreover, using the OWNER option does not change the group id of the file. To change the group id, the user must also specify the OWNERGROUP option.
Changing File Security One-time Synchronization By default however, AutoSYNC always replaces an object file that has been SQL compiled on the source after it was last synchronized, because it compares source and destination MODIFICATION timestamps and they will always be different after the source has been SQL compiled.
Process Priority and Throttling One-time Synchronization throughput. In most environments, the increase in CPU usage outweighs the savings in data volume. The use of compression can be set globally through the global parameter [AUTO]SYNCCOMPRESS or, for a specific synchronization, through the COMPRESS option. Process Priority and Throttling You may specify a process PRIORITY for a synchronization to ensure that synchronization does not impact higher priority work.
BACKUP and RESTORE Programs One-time Synchronization BACKUP and RESTORE Programs Private Copies of BACKUP and RESTORE AutoSYNC makes use of the NonStop server’s BACKUP and RESTORE system utilities. BACKUP is executed on the source system; RESTORE is executed on the destination system. In some operational environments, access to these programs is restricted. To use AutoSYNC, you may need to obtain, license, and secure separate copies of BACKUP and RESTORE.
Keeping NOPURGEUNTIL Attribute One-time Synchronization Only the local Super user ID can set the LICENSE attribute. Only a file’s local owner, local group manager, or the local Super user can set the PROGID attribute. No remote user, even the Super user, can set the LICENSE or PROGID attributes. If you synchronize a LICENSEd or PROGIDed object file to a destination on the same system, the attributes are preserved if you have the authority to set those attributes in the first place.
Running the Destination Synchronization Process as a Local Process One-time Synchronization Running the Destination Synchronization Process as a Local Process below for instructions. Running the Destination Synchronization Process as a Local Process To enable ASYSYNC or ASYSYNCP to become a local process on a remote system, perform the following operations on the ASYSYNC or ASYSYNCP program on the destination system: 1.
One-time Synchronization Running the Destination Synchronization Process as a Local Process HP AutoSYNC User’s Guide—522580-020 3-22
4 Scheduled Synchronization As mentioned previously, most one-time synchronization features described in Section 3, One-time Synchronization also apply to scheduled synchronizations. This section describes features and concepts that are specific to scheduled synchronizations.
The AutoSYNC Authorizer Scheduled Synchronization Scheduled synchronizations, however, are managed by the AutoSYNC monitor process. The AutoSYNC monitor acts as an agent for the AutoSYNC users, but also must ensure that each user has access rights to the files that are to be synchronized. The following pages describe how AutoSYNC is granted sufficient authority to act as an agent for multiple users, but in a way that prevents granting enhanced access rights to those users.
AutoSYNC Users Scheduled Synchronization SUSPEND SYNCUSER ACTIVATE SYNCUSER Caution. The AutoSYNC administrator can manipulate the AutoSYNC configuration to gain access to files that may not be secured for access to the administrator user ID. Thus, the AutoSYNC authorizer must exercise discretion when designating the administrator. AutoSYNC Users To configure file sets to be synchronized, you must be a AutoSYNC user; the administrator makes you a user through the ADD SYNCUSER command.
Data Access Control Scheduled Synchronization Data Access Control Users of AutoSYNC, especially the authorizer, should understand how multiple users are managed by AutoSYNC, a non-privileged subsystem. The monitor process reads the SYNCUSER table to determine which users are configured to use AutoSYNC. The SYNCUSER table should be secured to prevent unauthorized access. For each AutoSYNC user, the monitor accesses the SFggguuu table to fetch the synchronizations configured by the user.
Interval, Start, and Stop Times Scheduled Synchronization Interval, Start, and Stop Times The basic scheduling control is the INTERVAL between synchronizations. The default interval is 5 minutes, but you can specify another interval. In addition, you can specify both START and STOP times. If you specify only START, AutoSYNC performs a daily synchronization at the specified time and the INTERVAL, if specified, is ignored.
ALTER SYNCFILESET (and ALTER BATCHID) Scheduled Synchronization ALTER SYNCFILESET (and ALTER BATCHID) You can change any of the file set options, including the source and destination file sets. See ALTER SYNCFILESET on page 8-37 and ALTER BATCHID on page 8-28. Altering a SYNCFILESET will cause it to be rescheduled and performed at the first opportunity. DELETE SYNCFILESET (and DELETE BATCHID) The synchronization is terminated and deleted from the schedule.
Checking the Outcome of Scheduled Synchronizations Scheduled Synchronization Checking the Outcome of Scheduled Synchronizations As mentioned above in the AutoSYNC Users paragraph, the outcomes of scheduled synchronizations performed on behalf of Syncuser ggg,uuu are logged in file SLggguuu. To display the content of the synchronization log file, use the LOG option of INFO BATCHID or INFO INFO SYNCFILESET. Security and Authorization A scheduled synchronization is managed by the AutoSYNC monitor process.
Scheduled Synchronization Flow Scheduled Synchronization Perform the following operations, on the source system, to make ASYSYNCP a privileged program that can log down. 1. In BIND, issue the following commands: ADD * FROM ASYSYNCP SET LIKE ASYSYNCP ALTER CALLABLE^LOG^DOWN, CALLABLE ON SET SAVEABEND ON BUILD ASYSYNCP! 2. At the TACL prompt, SQL compile ASYSYNCP: SQLCOMP/IN ASYSYNCP/NOREGISTER ON 3. At the TACL prompt, accelerate ASYSYNC AXCEL ASYSYNCP, ASYSYNCP or OCA ASYSYNCP 4. Then, as SUPER.
ASYSYNCP process Scheduled Synchronization For each user ID, uuu,ggg, there should be a file set configuration table named SFggguuu. All file sets in these tables are fetched to the monitor’s memory and sorted. Suspended file sets are discarded. The monitor starts a local ASYSYNCP process for each unique combination of user ID, known destination system, and batch ID.
ASYSYNC process Scheduled Synchronization ASYSYNC process The ASYSYNC process on the destination is started by the ASYSYNCP process on the source and thus automatically has the appropriate process-access ID. The ASYSYNC process receives a single file set description and a list of all files in the source file set. The ASYSYNC process then finds all files in the destination file set. If the PURGE or SUBVOLPURGE option is specified, extra files in the destination file set are purged.
5 OSS File Synchronization This section describes the features and options available for the synchronization of OSS files and directories. These features apply to both one-time synchronization and scheduled synchronization.
Source File Set OSS File Synchronization signify that the pathname was shortened. If the DETAIL or LOG options are specified with these commands, the complete OSS pathname is displayed. Pathnames wrap to the next line if necessary. AutoSYNC synchronizes the following OSS disk files: Directories Regular files Symbolic links Hard links Unlike an empty Guardian file system subvolume, an empty directory is synchronized.
Links OSS File Synchronization Purging Destination Files If a file, a link or a directory exists in the destination file set but does not exist in the source, it can be purged on the destination by specifying the PURGE option. If PURGE is specified, subordinate directories that do not exist in the source are purged. This differs from the purge processing for Guardian subvolumes. Entire Guardian subvolumes are purged only if the SUBVOLPURGE option is specified in addition to the PURGE option.
Links OSS File Synchronization By default, when ALLSYMLINKS is specified, a symbolic link is synchronized also when the symbolic link points outside the synchronization file set. In this case, the symbolic link may point to a file that does not exist. A message is written to the logfile: File not in source file set, synchronizing uncontained symbolic link. When NO ALLSYMLINKS is specified, AutoSYNC does not synchronize a symbolic link that points outside the synchronization file set.
Recovery OSS File Synchronization Another side effect of the source and destination timestamps inherent mismatch is that the TIMEEXACT option is ignored for symbolic links. Recovery The recovery function, controlled by the global parameter SYNCRECOVER, is by default enabled for all synchronizations. Recovery for Guardian file sets is discussed in paragraph Recovery on page 3-18.
Ownership and Security OSS File Synchronization As mentioned above in Modification Timestamp of Symbolic Links, TIMEEXACT is ignored for symbolic links. The RENAMEOPEN option is not supported for OSS files. If a destination file is open at the time of the synchronization, it will not be synchronized but a warning is written to the log file and synchronization continues with the next file or directory.
Ownership of Symbolic Links OSS File Synchronization If the user is not SUPER.SUPER (255,255), WRITE access is granted for the destination file. AutoSYNC applies the equivalent of Guardian purge security rules to OSS WRITE security. If the user is SUPER.SUPER (255,255), WRITE security is not upgraded and remains the same as the source file security setting because the SUPER.SUPER user always has the required WRITE access. You may use the SECURE option to override the default security setting.
Synchronization Options OSS File Synchronization 1. In BIND issue the following commands: ADD * FROM ASYSYNC SET LIKE ASYSYNC ALTER CALLABLE^LOG^DOWN, CALLABLE ON SET SAVEABEND ON BUILD ASYSYNC! 2. At the TACL prompt, SQL compile ASYSYNCP: SQLCOMP/IN ASYSYNCP/NOREGISTER ON 3. At the TACL prompt, accelerate ASYSYNC: AXCEL ASYSYNC, ASYSYNC or OCA ASYSYNC 4. Then, as SUPER.SUPER, issue the following command: FUP LICENSE ASYSYNC If synchronizing over TCP/IP, perform the same steps on ASYSYNCP. Note.
Synchronization Options OSS File Synchronization FROMOWNER HOSTNAME INTERVAL KEEPBACKUPINFILE KEEPSECURITY LISTALL OPENUPDATE OWNER PRI PURGE RATE percentage START hh:mm:ss STOP hh:mm:ss SUSPEND TIMEEX[ACT] TRIGGER TRIGGERONFILESET UNPROTECTED USEBINDERTIME The following options are not applicable to OSS files: AUDITED AUTOCREATECATALOG BACKUP CATALOG KEEPNOPURGEUNTIL MAPNAMES MAXBACKUP NETWORKSECURE NOSAFEGUARD RESTORE HP AutoSYNC User’s Guide
Synchronization Options OSS File Synchronization SQLREDEF SYNCVIEWS SUBVOLPURGE ZZINCLUDE The following options are not supported: COMPRESS RECOVERY RENAMEOPEN HP AutoSYNC User’s Guide—522580-020 5-10
6 Triggers This section gives a basic overview of AutoSYNC triggers. Triggers allow a user to run a TACL or OSS shell command for each synchronized file that was successfully moved to the destination system (TRIGGER) or run a TACL or OSS shell command after a complete file set has been successfully synchronized (TRIGGERONFILESET).
Commands Triggers The feature is invoked by specifying TRIGGER or TRIGGERONFILESET option in the SYNCHRONIZE, ADD SYNCFILESET, or ALTER SYNCFILESET commands: SYNCHRONIZE … TRIGGER “command-text”; or SYNCHRONIZE … TRIGGERONFILESET “command-text”; ADD SYNCFILESET … TRIGGER “command-text”; or ADD SYNCFILESET … TRIGGERONFILESET “command-text”; Commands TRIGGER Specify a complete TACL or OSS command line that includes built-in arguments that are replaced by appropriate file names.
TRIGGERONFILESET Triggers If no archive name is found, AutoSYNC will pass the placeholder question mark (?). For OSS, files the absolute pathname is specified. Recovery files have a name chosen by AutoSYNC. Such files are usually purged by AutoSYNC when the replacement file has been synchronized, but triggers may preserve these files by renaming them #MAPNAMES is replaced by the mapnames-file that is configured for the syncfileset using the MAPNAMES option.
Troubleshooting triggers Triggers source file modification timestamp and specifying TIMEEXACT will cause the files to be synchronized needlessly at every synchronization interval. Troubleshooting triggers For problem resolution and debugging, you can run the trigger command on a terminal at a TACL prompt. If the destination is on a remote system, the user must have security privileges sufficient to run a remote TACL process. Examples TRIGGER examples 1. SQL-compile the synchronized object file myslqprg.
TRIGGER examples Triggers 4. Compare the old destination file with the new destination file: discrepancies will be reported to the log file: SYNC /home/dev/sales/appl TO /E/paris/home/sales/appl/, LISTALL, LOGFILE triglog, CLEAR, TRIGGER "/home/sales/scripts/cpsyrcv #SYNCFILE #RECOVERFILE "; cpsyrcv: cp $1 /home/sales/bckupnew/; cp $2 /home/sales/bckupold/; 5. Conditionally SQL compile objects depending on the file code of the object file. Only objects that can run on the destination are SQLCOMP’ed.
TRIGGER examples Triggers where the TRIGCOND macro is: ======================================================== == Name: TRIGCOND == Purpose: Sample conditional sqlcomp depending on file == code and OS version == Usage: == SYNC $data.test.sqobj TO \paris.$datab.testb.
TRIGGERONFILESET Example Triggers TRIGGERONFILESET Example Change the library pointer in object files GETME and GETMETOO to GETUL after synchronizing the entire object subvolume to a location with a different name:y SYNC $data.objd.* TO \paris.$datab.objp.
Note on Triggers that invoke SQLCI Triggers Instead, the user should use the following command: SYNC $data.test.sqacct TO \paris.$datab.testb.
7 Synchronization Over TCP/IP AutoSYNC supports the use of a direct TCP/IP network connection to communicate between the source and destination AutoSYNC processes. This section describes how to setup synchronizations over TCP/IP and how AutoSYNC establishes and manages the connection. The topics covered are organized as follows: Overview Configuring a TCP/IP connection On both Source and Destination Systems On the Destination System On the Source System .
On both Source and Destination Systems Synchronization Over TCP/IP On both Source and Destination Systems Set the TCP/IP port numbers for AutoSYNC A TCP/IP SERVICES file is used to specify the port number for use by defined services. The name of the service is ASYSYNC-ZASY where ZASY is the name of the AutoSYNC monitor process $ZASY that is used on both systems to coordinate the TCP/IP connections.
On the Destination System Synchronization Over TCP/IP On the source system, the ASYSYNC process for a scheduled synchronization inherits the define from the monitor process. For a one-time synchronization, the ASYSYNC process inherits the define directly from the AUTOSYNC CI process. There is no default port number; if you do not configure a port number, synchronization over TCP/IP is not possible. Consult your local networking specialist to choose an appropriate port number.
On the Source System Synchronization Over TCP/IP Thus, you must specify all TCPIP, TCPSAM or TCP6SAM processes that correspond to those addresses, or the synchronization will fail to make the connection. Consult a networking specialist to determine the names of the TCPIP, TCPSAM, and TCP6SAM processes. Use the following SCF commands to understand your local networking configuration: LISTDEV TCPIP and INFO PROCESS $, DETAIL.
Connection Setup over TCP/IP Synchronization Over TCP/IP HOST name. If the destination is on a remote system, the destination file set must include the Expand node name of the remote system. SYNC[HRONIZE] src-fileset TO \sysname.dest-fileset, HOST { name | IP address } [, sync-options]; 2. Configure scheduled synchronization file sets using ADD SYNCFILESET or ALTER SYNCFILESET, specifying the HOST of the destination system in addition to the source and destination file sets.
Logging Synchronization Over TCP/IP SQL Executor accesses the SQL object in the ASYSYNCP object file. The SQL Executor uses "EXECUTE security" to access this SQL data. As mentioned above, the ASYSYNCP on the destination runs under the access ID of the Syncuser that requests the synchronization. If the owner of ASYSYNCP is SUPER.SUPER and ASYSYNCP execute access is set to "U", only SUPER.SUPER can access the SQL object in ASYSYNCP.
8 Command Interpreter The AUTOSYNC command interpreter is the primary interface for invoking utility functions and for controlling and monitoring the AutoSYNC. This chapter describes the AutoSYNC command interpreter and is organized as follows: Running the Command Interpreter Command Syntax Command Summary Command Descriptions Running the Command Interpreter AUTOSYNC is invoked through the TACL run command or equivalent. The TACL syntax is: [RUN] $SYSTEM.AUTOSYNC.
Command Syntax Command Interpreter Command Syntax AUTOSYNC is a conversational-mode command interpreter. Most commands can be continued over many lines with no need for a continuation character; as a consequence, each command must be terminated with a semi-colon (;). A few commands, such as FC and RUN, are single-line commands and are terminated by the end of line; such commands can be continued by placing an ampersand (&) at the end of the line.
Command Summary Command Interpreter Table 8-1. AutoSYNC Commands (continued) Command Name Description ALTER LOCAL Changes the value of a AutoSYNC local parameter ALTER MAPDB Changes attributes of MapDB and the monitor. ALTER MONITOR Changes attributes of a monitor process. ALTER SYNCFILESET Modifies configuration of scheduled synchronization by file set. ALTER SYNCUSER Modifies configuration of an AutoSYNC user. AUTHORIZE Sets the AutoSYNC authorizing user ID.
Command Summary Command Interpreter Table 8-1. AutoSYNC Commands (continued) Command Name Description STATUS AUTOSYNC Displays status information from the AutoSYNC scheduler. STATUS BATCHID Displays status information for a specific batchid. STATUS MONITOR Displays the status of a monitor process. STATUS SYNC Displays status for a synchronization process. STATUS SYNCFILESET Displays status information for a specific syncfileset. STOP MONITOR Stops the monitor process.
Command Descriptions Command Interpreter Table 8-2. General Purpose Commands Command Name Description LOG Outputs a copy of AUTOSYNC command input and output to a file. OBEY Executes a sequence of AUTOSYNC commands from a file. OUT Directs all AUTOSYNC command output to a file. PURGEDATA Clears all data from a file. RENAME Renames an Enscribe file RESET Resets completion code. RUN[D] Executes an external process during an AUTOSYNC session. STATS Examines an Enscribe structured file.
ACTIVATE SYNCFILESET Command Interpreter * | batchid | batchid - batchid a collection of file sets by BATCHID or a range of BATCHIDs. Up to 32 ranges can be entered. A BATCHID is an integer and is of the same format as an alternate key tag, that is, two characters in quotes or a number between 1 to 32767. If batchid-batchid is specified, the second batchid must be greater than the first. * designates all configured batchids for the user.
ADD SYNCFILESET Command Interpreter ADD SYNCFILESET Adds a file set to the scheduled synchronizations. See the Synchronization Options on page 3-12 for an overview of synchronization.
ADD SYNCFILESET Command Interpreter common-options (continued) { TRIGGER { tacl-command | oss-shell-command } } { TRIGGERONFILESET { tacl-command | oss-shell-command } } { UNPRO[TECTED] } { USERBINDERTIME } guardian-only-options: { AUDITED } { AUTOCREATECAT[ALOG] } { BACKUP backup-program } { CATALOG SQL-catalog } { COMPRESS } { KEEPNOPURGEUNTIL } { MAPNAMES mapnames-file } { MAXBACKUP num-of-files } { NETWORKS[ECURE] | NO NETWORKS[ECURE] } { NOSAFEGUARD | NO NOSAFEGUARD } { RE
ADD SYNCFILESET Command Interpreter OSS-only-options: { ALLHARDLINKS | NO ALLHARDLINKS } { ALLSYMLINKS | NO ALLSYMLINKS } { OWNERG[ROUP] { group-id | group-user } } { SECURE “rwxrwxrwx” } src-file-set a file set on the local system that is the source of the synchronization operation. If a system name is specified, it must be the local Expand node name. dest-file-set the location of the file set that is to be updated.
ADD SYNCFILESET Command Interpreter OSS file set definition The source and destination file sets must be specified with the absolute pathname. Wild-card characters are not supported; specify an absolute directory name or an absolute file name. If the source file set is a single file, the file is moved to the destination specified. If the directory does not exist at the destination location, the directory is created.
ADD SYNCFILESET Command Interpreter instructs AutoSYNC to exclude the files listed in exclude-file from synchronization. exclude-file an edit file that contains names of the files, subvolumes or disk volumes in the syncfileset that are to be excluded from the synchronization. An exclude file can be shared among syncfilesets. When starting a new synchronization ASYSYNC rereads the exclude list if the exclude file has been updated. Each entry must be on a separate line.
ADD SYNCFILESET Command Interpreter instructs AutoSYNC to exclude the files listed in the excludep-file from being purged on the destination, if the files do not exist on the source. EXCLUDEPURGE only applies when PURGE or SUBVOLPUREGE are also specified. Otherwise, EXCLUDEPURGE is ignored. excludep-file an edit file that contains the names of the files, subvolumes or disk volumes in the destination syncfileset that are excluded from being purged.
ADD SYNCFILESET Command Interpreter instructs Autosync to synchronize only the source files owned by the specified user ID. By default the whole source fileset is synchronized, regardless of the ownership of the files, as long as security settings do not prevent it. An OSS directory that is not owned by the specified owner is skipped, along with all its files and subdirectories, even if some of the subordinate files or subdirectories are owned by the specified user ID.
ADD SYNCFILESET Command Interpreter For OSS file sets, the BACKUP input files is an entry-sequenced file that contains the names of the files and directories to be synchronized, in addition to internal file information. KEEPS[ECURITY] that the Guardian security settings "rwep" of the source file are retained on the destination file. KEEPSECURITY overrides the SECURE and NETWORKSECURE options. LISTA[LL] includes all file names that are processed by BACKUP and RESTORE in the log.
ADD SYNCFILESET Command Interpreter the owner of the destination file set. If OWNER is omitted, the owner of the source file is retained. Note for OSS file sets. If OWNER is specified and OWNERGROUP is omitted, the OWNERGROUP of the file set is set to the group of the source file, not the group specified by OWNER. PRI[ORITY] priority the process priority at which the ASYSYNC process is to run when processing this syncfileset.
ADD SYNCFILESET Command Interpreter OSS files and directories: If PURGE is specified, subordinate directories not present in the source file set are purged on the destination. Note that this is different than the processing of Guardian subvolumes. Guardian subvolumes are not purged unless the SUBVOLPURGE is specified. An entry is written into the log file for each file or OSS directory that is purged as a result of the synchronization. PURGE is not supported for SQL tables.
ADD SYNCFILESET Command Interpreter that a file is synchronized if the modification timestamp of the source does not exactly match the modification timestamp of the destination file. By default, a file is synchronized only when the source file has been modified after the destination file was last modified. The comparison of timestamps accounts for differences in system clocks and time zones.. Note on symbolic links.
ADD SYNCFILESET Command Interpreter specifies a TACL or OSS shell command that is executed by AutoSYNC after the complete file set has been successfully synchronized. This is in contrast with the TRIGGER option that executes the TACL or shell command for each file that is synchronized. The trigger is executed if files have been replaced or purged during the synchronization, or if a file error has occurred that did not cause the synchronization to fail.
ADD SYNCFILESET Command Interpreter The destination object file is replaced if the binder or linker timestamps of the source and destination objects do not match exactly; the comparison operates as if TIMEEXACT were specified. The default is that object files are replaced based on a comparison of modification timestamps. guardian-only-options AUDITED instructs AutoSYNC to synchronize audited files. By default, audited files are not synchronized.
ADD SYNCFILESET Command Interpreter This option overrides the global parameter [AUTO]SYNCCOMPRESS Note: Compression is CPU-intensive and can reduce total throughput unless the connection between source and destination systems is slow. KEEPNOPURGEUNTIL specifies that the NOPURGEUNTIL attribute of a source SQL table or alternate index is preserved on the destination.
ADD SYNCFILESET Command Interpreter The entries follow file mapping entries and are preceded by the keyword "CATALOGS:", including the colon (:), as follows: $DATA TO $BACK \NEWYORK.$DATA*.DB TO $BACK.BACKUPDB $DATA*.DB.PARTFILE TO \TOKYO.* CATALOGS: $CATS.BACKCAT FOR $BACK.*.* $CATS.DBCAT FOR $BACK.BACKUPDB.* \TOKYO.$CATS.DBCAT for \TOKYO.*.*.* CATALOGS entries are checked for proper syntax, and passed along to the RESTORE process.
ADD SYNCFILESET Command Interpreter written to the logfile to notify the user that the Safeguard setting for the source file has been turned off on the destination. The default is NO NOSAFEGUARD and the ACL for a source file is propagated to the synchronized destination file. RECOVERY | NO RECOVERY enables or disables the recovery option. If recovery is enabled, AutoSYNC saves a copy of an existing destination file to an archive subvolume before it restores a later copy of the file.
ADD SYNCFILESET Command Interpreter the security of destination files. If this option is omitted, the security of a destination file is the same as that of the source file unless NETWORKSECURE is on and the destination files are on a destination system. SQLREDEF instructs AutoSYNC to synchronize SQL tables based on differences in the redefinition timestamps, in addition to differences in modified timestamps.
ADD SYNCFILESET Command Interpreter The default is SYNCVIEWS. ZZINC[LUDE] instructs AutoSYNC to synchronize ZZ* files (saveabend, binder temporary files, axcel temporary files, so on) and system swap files. By default, ZZ* files and system swap files are not synchronized.
ADD SYNCUSER Command Interpreter If OWNERGROUP is omitted, the group ID is one of: the group ID specified in the OWNER option, if it is entered the group ID of the source file otherwise. SECURE “rwxrwxrwx” the security of the destination file set. "rwxrwxrwx" settings are for user, group and others. The accepted values are: "r" grants read access "w" grants write access "x" grants execute access "-" denies access for read, write and execute setting.
ADD SYNCUSER Command Interpreter The log file is used by AutoSYNC to display messages pertaining to the synchronization operations it performs on behalf of this user. ADD SYNCU[SER] { user-id | user-name } [ [,]option... ]; option is: { BACKUP backup-program } { CPU n | (n1, n2, n3...
ADD SYNCUSER Command Interpreter logs an event to the EMS log when a syncfileset is synchronized to completion but contains one or more files that were not synchronized. The event does not necessarily signal an error condition. For example, a event is generated when a file in a syncfileset configured with OPENUPDATE is being updated during a synchronization. Setting the global parameter or SYNCUSER option EMSSUPPRESS overrides EMSFILENOTSYNCED.
ALTER BATCHID Command Interpreter If RESTORE is omitted, the default $SYSTEM.SYSnn.RESTORE program is used. SUSPEND that this user is not activated as a SYNCUSER until the ACTIVATE SYNCUSER command is issued. TRACE instructs AutoSYNC to trace the activity of the ASYSYNC process to the log file SLggguuu created in the MapDB for this user. Tracing is a diagnostic function that is likely to be requested by a support specialist in order to identify the source of a problem.
ALTER FILE Command Interpreter ALTER FILE Similar to the FUP ALTER (or SQLCI ALTER TABLE) commands, changes certain attributes of Enscribe files or mapped tables. ALTER FILE file-set {, option...
ALTER FILE Command Interpreter BUFFERED | NO BUFFERED turns buffering on or off. CLEARONPURGE | NO CLEARONPURGE erases disk free space when files are purged. CODE numeric file code of the file. file-code is an integer between 0 and 65535. Codes 100 to 999 are reserved for use by HP. LOCKLENGTH length the byte count of the key for generic locks. length is between 0 and the primary key length of the file. MAXEXTENTS size the maximum disk allocation extents.
ALTER GLOBAL Command Interpreter sets the mode of file writes: verified or not verified. The default is NO VERIFYWRITES. ALTER GLOBAL Sets or changes global AutoSYNC values. Global values are stored in the SYSDB table called REGISTRY and affect all processes executed using the SYSDB.
ALTER GLOBAL Command Interpreter If recovery is enabled, AutoSYNC saves a copy of a destination file to an archive subvolume before it restores a later copy of the file. If a failure occurs during the synchronization and the file is corrupted, the archived copy is recovered and replaces the corrupted file. This setting can be overridden by setting the syncfileset attribute or one-time sync option RECOVERY. The default is ON.
ALTER LOCAL Command Interpreter ALTER LOCAL Sets or changes a local parameter value. Local parameters are the same as global parameters and have the same purpose, but they are in effect for the current Monitor (MapDB) only. Local parameter values are stored in the MapDB table REGISTRY. Setting a local parameter value overrides the global (default) value.
ALTER MAPDB Command Interpreter ALTER MAPDB Modifies attributes of an existing MapDB; the alterable attributes mostly affect the associated monitor process, not MapDB itself. The changes take effect when the monitor process is restarted. These attributes can also be changed using ALTER MONITOR. ALTER MAPDB subvol { , option...
ALTER MONITOR Command Interpreter The default is $ZASY. PRIMARY cpu-number the CPU number (in the range of 0 to 15) of the primary monitor process. PRIORITY process-priority a process priority (in the range of 1 to 199) for the monitor process The PRIMARY, BACKUP, and PRIORITY options specify process creation parameters that are used when starting the monitor process. ALTER MONITOR Modifies attributes of an existing monitor process. The changes take effect when the monitor process is restarted.
ALTER MONITOR Command Interpreter Functionally however, the home terminal for the monitor process is the default EMS collector, as shown by the Autosync STATUS MONITOR command. If NONE is specified or file-name is omitted, the hometerm is re-set to the default described above. PRIMARY cpu-number the CPU number (in the range of 0 to 15) of the primary monitor process. PRIORITY process-priority a process priority (in the range of 1 to 199) for the monitor process.
ALTER SYNCFILESET Command Interpreter ALTER SYNCFILESET Modifies the options of the syncfilesets in the specified fset-id range. ALTER SYNCF[ILESET] fset-range [, fset-range ], ... {, options...
ALTER SYNCFILESET Command Interpreter common-options: (continued) { RATE percentage | NO RATE } { START hh:mm:ss | NO START } { STOP hh:mm:ss | NO STOP } { SUSPEND } { TRIGGER { tacl-command | oss-shell-command }| NO TRIGGER } { TRIGGERONFILESET { tacl-command | oss-shell-command } | NO TRIGGERONFILESET } { TIMEEX[ACT] | NO TIMEEX[ACT] } { TO file-set } { UNPRO[TECTED] | NO UNPRO[TECTED] } { USEBINDERTIME | NO USEBINDERTIME } guardian-only-options: { AUDITED | NO AUDITED } { AUTOCREA
ALTER SYNCFILESET Command Interpreter guardian-only-options: (continued) { RENAMEO[PEN] | NO RENAMEO[PEN] } { RESTORE restore-program | NO RESTORE } { SECURE "rwep" | NO SECURE } { SQLREDEF | NO SQLREDEF } { SUBVOLPURGE | NO SUBVOLPURGE } { SYNCVIEWS | NO SYNCVIEWS } { ZZINC[LUDE] | NO ZZINC[LUDE] } OSS-only-options: { ALLHARDLINKS | NO ALLHARDLINKS } { ALLSYMLINKS | NO ALLSYMLINKS } { OWNERG[ROUP] {{ group-id | group-user } | NO OWNERG[ROUP] } { SECURE “rwxrwxrwx” | NO SECURE } * | fs
ALTER SYNCFILESET Command Interpreter BATCHID batchid | NO BATCHID a batch identifier for the file set. The batchid is an unsigned integer and can be specified as a number between 0 and 65535 or as two ASCII characters in quotes. The default batchid is 0. All file sets that have the same batchid for a given user and destination system are synchronized in sequence by a single ASYSYNC process. To have more than one ASYSYNC process for the same destination system, use different BATCHIDs.
ALTER SYNCFILESET Command Interpreter Entries in the exclude-file can specify a pattern but the file and directory names must be fully qualified with absolute pathnames.
ALTER SYNCFILESET Command Interpreter does not exclude directory: /home/group/user/destdir/A/KA/ while exclude-file entry: /home/group/user/destdir/A/KA* or /home/group/user/destdir/A/KA/ excludes directory: /home/group/user/destdir/A/KA/ Note. Some performance degradation can occur if an exclude file that is shared by multiple files ets contains a long list of exclude names, because the synchronization process has to detect exclude names that do not apply to the specific file set.
ALTER SYNCFILESET Command Interpreter The interval value is ignored if a START option is specified without a STOP option; then synchronization occurs once a day at START time. Note that the interval is the time to delay from the completion of one synchronization until the start of the next synchronization. KEEPB[ACKUPINFILE] | NO KEEPB[ACKUPINFILE] instructs AutoSYNC to retain (or stop retaining) BACKUP and RESTORE input files.
ALTER SYNCFILESET Command Interpreter The time elapsed is computed from the last time the file was modified. The candidate files can be opened for WRITE or READ-WRITE access. The exclusion mode must be SHARED or PROTECTED. Recovery must be enabled for the file set. If a file is being updated at the time AutoSYNC attempts to synchronize it, it is skipped. To force the synchronization of a file as it is being modified, specify the UNPROTECTED option described below on page 8-48.
ALTER SYNCFILESET Command Interpreter specifies that any file that is in the destination file set but is not in the source file set will be (or will not be) purged. By default AutoSYNC does not purge any file in the destination file set. To exclude files from being purged on the destination, use the EXCLUDEPURGE option. Guardian file sets: If PURGE is specified, the subvolume portion of the source and destination file sets must be fully qualified (no wild-card characters or "*").
ALTER SYNCFILESET Command Interpreter Using back slash asterisk (\*) as the destination system is not supported for OSS file sets or for file sets configured for synchronization over TCP/IP. For file-set format definitions, see Guardian file set definition and OSS file set definition on page 8-10. START hh:mm:ss | NO START the start time of a synchronization window or a once-a-day synchronization. The time is entered in the format hour:minute:seconds between 00:00:00 and 23:59:59.
ALTER SYNCFILESET Command Interpreter TRIGGER { tacl-command | oss-shell-command } | NO TRIGGER a TACL command or OSS shell command that is executed by AutoSYNC for each file in the synchronized file set after the file has been moved to the destination. The command line contains four built-in arguments. Each argument starts with a pound sign (#) and is terminated by a TACL delimiter character such as a space or a comma, or by a OSS shell delimiter such as a space or a semicolon.
ALTER SYNCFILESET Command Interpreter #DESTFSET is replaced with the destination file set name. #FSETCOUNT is the number of files in the source file set. #SYNCCOUNT is the number of files replaced on the destination. #COUNTNOTBKUP is the number of files not backed up. #COUNTNOTREST is the number of files that were not restored.
ALTER SYNCFILESET Command Interpreter The security of the newly created destination catalog is set to the syncuser's default Guardian security. If the catalog already exists, the option is ignored. To register the object in a different catalog, use the CATALOG option in addition to AUTOCREATECATALOG. BACKUP backup-program | NO BACKUP the name of the BACKUP object program to use on the source system when a file set is synchronized.
ALTER SYNCFILESET Command Interpreter The mapnames-file is an edit or entry-sequenced file located on the destination system. File name mapping: The mapnames-file entries are similar to, but not exactly the same as, the MAP NAMES option of RESTORE. Each line of the MAPNAMES file contains a single mapping of the form. source-file-pattern TO destination-file-pattern The file name can be partially qualified; AutoSYNC replaces the missing portion of the name with the wild card asterisk (*).
ALTER SYNCFILESET Command Interpreter When processing large file sets, AutoSYNC divides the synchronized files into subsets, each processed by a separate BACKUP process. BACKUP performance decreases significantly with the number of files it processes. To avoid performance degradation, AutoSYNC starts multiple BACKUP processes, in sequence, and assigns to each no more than the configured num-of-files. The default is 1000.
ALTER SYNCFILESET Command Interpreter specifies (or disables the option) that destination unaudited files that are opened for shared READ access or running object files are to be renamed to allow AutoSYNC to replace them. The syncuser must have PURGE privileges to the destination file for the RENAME to succeed. Both the old and new file names are recorded in an AutoSYNC index file called AAINDEX, located in the MapDB subvolume.
ALTER SYNCFILESET Command Interpreter instructs AutoSYNC to process (or not) subvolumes in the destination file set even if the subvolumes do not exist on the source file set. All other synchronization options specified apply to the selection of files to purge in the destination file set. For example, if the AUDIT option is specified, the audited files in the extra destination subvolumes are purged. The REPORT function also lists the extra subvolumes if both PURGE and SUBVOLPURGE are specified.
ALTER SYNCFILESET Command Interpreter file is created in the destination file set and all contained links to the same inode are linked to this file. A warning is written into the log file when an uncontained hard link has been synchronized. If NO ALLHARDLINKS is specified, uncontained hard links are not synchronized. The default in ALLHARDLINKS. ALLSYMLINKS | NO ALLSYMLINKS synchronizes all symbolic links in the specified syncfileset, including uncontained symbolic links.
ALTER SYNCUSER Command Interpreter write access is granted in the destination file to allow subsequent synchronizations. Write access is only upgraded when the syncuser is the owner of the file and not SUPER.SUPER. When the super ID is used, the owner write security setting is not upgraded. ALTER SYNCUSER Modifies the parameters that were specified for a AutoSYNC user through the ADD SYNCUSER command. ALTER SYNCU[SER] { user-id | user-name } [ [,] option...
ALTER SYNCUSER Command Interpreter specifies that any synchronization error related to a specific file (for example, error 48, error 45, so on) will be logged in the EMS log. The EMS message specifies the name of the log file SLggguuu, the key of the log record, the SYNCfileset ID, the file error and the filename portion of the file. The user should then refer to the log file for details. The default is NO EMSFILEEVENTS.
AUTHORIZE Command Interpreter If this parameter is omitted, the maximum priority is set to the priority of AUTOSYNC minus 20. RESTORE restore-program | NO RESTORE the object file name of the RESTORE program to use on the destination system when a file set is synchronized. If RESTORE is omitted or if NO RESTORE is specified, the default $SYSTEM.SYSnn.RESTORE program is used. SUSPEND this user is not activated as a SYNCUSER until the ACTIVATE SYNCUSER command is issued.
CALC Command Interpreter ASYSYNCP process changes its access ID to the user ID who configured the synchronization. This operation succeeds only if the authorizer is (1) the Super ID, (2) the user’s group manager, or (3) the user itself; otherwise the synchronization is aborted. The ownership of the SYNCUSER table is set to the authorizer or, if specified, to the administrator. This command also sets the write and purge security of the SYNCUSER table to the owner (“xOxO”).
COMMENT Command Interpreter designates all systems that have this system as a destination. USER user-ID resumes synchronizations from system-name for this specific user-ID. If a user ID was specified in the DISABLE AUTOSYNC command, the user ID must be specified in CLEAR AUTOSYNC. For example, if synchronizations from system \remsys were disabled for user.sally and for user.joe, each must be cleared in a separate clear command: CLEAR AUTOSYNC FROM \remsys, USER user.
COPY Command Interpreter COPY Copies records or rows from an input file to an output file or displays them to an output device. It is analogous in function to the FUP COPY command. At this time, some of the FUP options pertaining to tape devices are not supported.
COPY Command Interpreter { SKIPMATCH } { TRIM trim-character } { UNLOADIN | NO UNLOADIN } { UNSTRUCTURED } { VARIN } out-options is: { BLOCKOUT <1 to 32767> } { BUFFERED } { EBCDICOUT } { FOLD } { PAD pad-character } { RECOUT <1 to 4096> } { REWINDOUT | NO REWINDOUT } { UNLOADOUT | NO UNLOADOUT } { UNSTROUT } { UPDATE } { VAROUT } display-options is { O[CTAL] } { D[ECIMAL] } { H[EX] } { A[SCII] } { BYTE[S] } { NO HEAD } in-file HP AutoSYNC User’s Guide—522580-0
COPY Command Interpreter the name of the file that is input to the copy command. It can be a process, a tape, terminal, or disk file. Supported disk files include edit files, spooler files, Enscribe structured and unstructured files. out-file the name of the file that is destination of the copy command. It can be a process, a tape, terminal, a printer or disk file. Supported disk files include edit files, spooler files, Enscribe structured and unstructured files.
COPY Command Interpreter key-spec is the alternate key tag (1 or 2 bytes) designating the alternate key to be used for positioning. ALTKEY key-value [, key-value] the alternate key of the starting record or row. The format of key-value is described above. UPSHIFT converts lowercase characters to uppercase. in-options BLOCKIN the number of bytes in an input block that is requested in a single physical read operation. When BLOCKIN is not specified, the RECIN value is used.
COPY Command Interpreter REVERSE the input file is to be READ from the starting record in reverse order. REWINDIN | NO REWINDIN (magnetic tapes only) the tape is rewound (or not rewound) when the EOF is read from the tape. If NO REWINDIN is specified, the tape remains positioned without rewinding.The default is REWINDIN. This option also applies to labeled tapes. SHARE the file is to be opened in shared-exclusion mode. The default is protected.
COPY Command Interpreter EBCDICOUT the output characters are translated from ASCII to their EBCDIC equivalents. FOLD the input records or rows that are longer than the output record length are divided into as many output records as needed to copy the entire input record or row. PAD pad-character the input record containing fewer bytes than the output record length is padded with pad-character. Specify pad-character as a single byte character in quotation marks or as an integer in the range of 0 to 255.
CPUS Command Interpreter display-options AUTOSYNC display options differ from FUP display options. AUTOSYNC applies all output data transformations (RECOUT, BLOCKOUT, PAD, and so on) before converting the data to display format, whereas FUP does it the other way around. As a result, AUTOSYNC only formats the data itself and displays it as it would be written to a disk file. Entry-sequenced record keys are displayed in the 64-bit format. O[CTAL] the output is in octal and ASCII format.
CREATE MAPDB Command Interpreter Since the MapDB is a set of SQL tables, the volume on which it is created must be TMF protected. CREATE MAPDB subvol [ , option... ]; or CREATE MAPDB ON volume [ , option... ]; option is { BACKUP cpu-number } { CATALOG SQL-catalog } { HOMETERM file-name } { MONITOR process-name } { PRIMARY cpu-number } { PRIORITY process-priority } { SECURE “rwep” } subvol the subvolume where the MapDB tables are created.
CREATE SYSDB Command Interpreter Functionally however, the home terminal for the monitor process is the default EMS collector, as shown by the Autosync STATUS MONITOR command.. MONITOR process-name the name of the monitor process to be associated with the MapDB. The name must have 4 characters. Each MapDB is associated with a unique monitor process name. Monitor process names must have exactly 4 characters in addition to the “$”; the default name is $ZASY.
DELAY Command Interpreter the SQL catalog subvolume where the SysDB tables are to be registered. If this parameter is omitted, AUTOSYNC creates a SQL catalog in subvolume ESCCATLG on the volume specified in the command. Following the creation of the system database, you should comply with the AutoSYNC registration instructions. If you create SYSDB on a subvolume other than $SYSTEM.
DELETE SYNCFILESET Command Interpreter DELETE SYNCFILESET Deletes syncfilesets in the specified fset range. DELETE SYNCF[ILESET] fset-range [, fset-id ],...; fset-range is { * | fset-id | fset-id - fset-id } * | fset-id | fset-id - fset-id identifies a synchronization file-set ID or a range of file-set IDs. Up to 32 ranges can be entered. If fset-id - fset-id is specified, the second fset-id must be greater than the first. * designates all configured syncfilesets for the syncuser.
DISABLE AUTOSYNC Command Interpreter The DEQUEUE command terminates if the queue is empty. It times out after two seconds if a read on the queue can't find a record. DEQUEUE in-file, out-file [, dequeue-options ] dequeue-options is: { { { { control-options in-options out-options display-options } } } } in-file an Enscribe queue file. out-file an Enscribe queue file, entry-sequenced file, the terminal or $NULL (or equivalent). dequeue-options See command options for COPY on page 8-60.
ENV Command Interpreter subvolume an existing MapDB subvolume. ENV The ENV command displays the current setting of all environmental variables. ENV; EXIT Terminates the AUTOSYNC session. A CTRL–Y has the same effect. The EXIT command does not require a semi-colon and cannot be followed by any text. EXIT FACTOR Accepts any numeric expression and calculates the prime factors of the integer part of the expression.
FILEINFO (FI) Command Interpreter The FC and ! command are not multiline commands and are not terminated with a semicolon. FILEINFO (FI) Displays information about Enscribe files. The information displayed is similar to the TACL FILEINFO display. FI[LEINFO] file-set [, DETAIL ]; or FID file-set; file-set TACL-style file name pattern specifying a collection of files. If no file-set is specified, the current subvolume is assumed. DETAIL displays detailed information.
HELP Command Interpreter HELP Describes the AUTOSYNC commands, monitor process commands and AutoSYNC specific DEFINEs. HELP [ help-option ]; help-option is { ALL } { AUTOSYNC-COMMANDS } { autosync-command [ DETAIL | EXAMPLE ] } { AUTOSYNC-DEFINES } { define [ USAGE ] } { ESCZIP } { MONITOR [ monitor-command ] } ALL displays the list of all commands. AUTOSYNC-COMMANDS requests the display of the list of all AUTOSYNC commands available.
HISTORY Command Interpreter is the name of the DEFINE. HELP displays the syntax and a description of the DEFINEs. USAGE displays information about the usage of the DEFINE, otherwise it displays it as a list of possible subtopics. MONITOR [ monitor-command ] displays the syntax and description of commands that can be sent to the monitor process via AUTOSYNC. If no monitor command is specified, HELP displays a list of the commands as subtopics.
INFO BATCHID Command Interpreter INFO BATCHID plays the synchronization parameters for the syncfilesets in the specified BATCHID ranges. This command is analogous in functionality to INFO SYNCFILESET. INFO BATCH[ID] [ batchid-range [, batchid-range ],...
INFO LOCALS Command Interpreter INFO LOCALS Displays a complete list of global and local values. Global parameter values are the default values in effect for all configured monitors in the system. LOCAL parameter values are the default values in effect for the current monitor. INFO LOCALS [, OBEYFORM ]; OBEYFORM displays a list of the ALTER LOCAL commands that were entered to modify the default global values. See ALTER GLOBAL above for a list of valid AutoSYNC global parameters and values.
INFO SYNCFILESET Command Interpreter * | fset-id | fset-id - fset-id identifies a synchronization file-set ID or a range of file-set IDs. Up to 32 ranges can be entered. If fset-id - fset-id is specified, the second fset-id must be greater than the first. * designates all configured syncfilesets for the syncuser. If fset-range is omitted, all syncfilesets for the current user are displayed. info-option DETAIL displays all parameter values for the file set.
INFO SYNCUSER Command Interpreter If FILESETID is specified, the file set ID is added to the OBEYFORM output. USER [ user-id | user-name ] | ALLUSERS a Guardian user ID or user name. ALLUSERS displays syncfileset information for all configured syncusers. If this option is omitted, the current user ID is assumed. INFO SYNCUSER Displays information pertaining to the synchronization privileges of a specified user.
LABELDISPLAY (LD) Command Interpreter Hostid (if any) for the TCP/IP process $Znnn Hostname (gethostname): hostname-from-gethostname IPv4 address(getaddrinfo): xx.xxx.xx.xx IPv6 address(getaddrinfo): ::ffff:xx.xxx.xx.xx getipnodebyname( IPV4 ) returns: Hostname = hostname-from-getipnodebynameI IPv4 address: xx.xxx.xx.xx getipnodebyname( IPV6 ) returns: Hostname = hostname-from-getipnodebyname IPv6 address: ::ffff:xx.xxx.xx.xx INFO TCPIP does not display any information about the AutoSYNC TCP/IP status.
LISTFILEOPENS (LFO) Command Interpreter LISTFILEOPENS (LFO) Displays all file opens like the FUP LISTOPENS command, with additional options. The command can be abbreviated to LFO. L[IST]F[ILE]O[PENS] file-set , options options is: { BYF[ILE] } { BYO[PENER] } { OUTP[UT] | WRIT[E] } file-set a TACL-style file name pattern specifying a collection of files. If file-set is omitted, all the opens for the local system are displayed ($* is assumed).
LIST SYNCPROCESS Command Interpreter This command helps to manage the AutoSYNC environment. LIST SYNCP[ROCESS] [ process-name | * ], info-option info-option is: { DES[TINATION] } { DETAIL } { MONITOR monitor-name } { SOURCE } { USER user-ID } process-name | * the Guardian process name of an ASYSYNC or ASYSYNCP process, or all running ASYSYNC processes. The default is all ASYSYNC and ASYSYNCP running from the current product subvolume for all users.
LOG Command Interpreter SOURCE displays the synchronization processes that are running as source synchronization processes. USER user-ID displays the synchronization processes for the specified syncuser. LOG Displays a history of the AUTOSYNC terminal session on another device, which may be a disk file, a printer, or another terminal. LOG TO starts the logging process, and LOG STOP terminates the logging. LOG { TO filename [CLEAR] | STOP }; TO filename identifies the current log file and starts logging.
MONITOR Command Interpreter displays the mode, number of links, group.owner, size, time of last modification for each file, and pathname. If the file is a special file, the size field instead contains the major and minor device numbers. If the file is a symbolic link, the pathname of the linked-to file is also printed preceded by ->. The attributes of the symbolic link are displayed.
OPEN Command Interpreter OPEN Select a current monitor process and associated MapDB. OPEN process-name; process-name the name of a configured monitor process. It is not necessary for the monitor process to be executing to update or display information for the corresponding MapDB. OUT Directs the output of an AUTOSYNC terminal session to another file. Interactive terminal prompts continues to appear on the original input device.
RESET Command Interpreter the new name for the file. RESET Changes all of the environmental variables to their original settings.It is most often used to change the condition code. RESET; RESET GLOBAL Removes a previously set global value from the configuration and reset the parameter to the default value.
RESET LOCAL Command Interpreter RESET LOCAL Removes a previously set local value from the configuration and resets the parameter to the default value of the corresponding global parameter. RESET LOCAL { parameter | * }; parameter is: { AUTOSYNC } { [AUTO]SYNCCOMPRESS } { [AUTO]SYNCOVERIP } { [AUTO]SYNCRECOVER } { EMSCOLLECTOR } { SYNCTCPPROC[ESSES] } * all global parameters are set to their original default value.
REPORT Command Interpreter REPORT Generates a report that compares source files and destination files. For additional information on the reporting function, consult Section 9, Reporting Function.
REPORT Command Interpreter fset-id identifies a synchronization file-set ID or a range of file-set IDs. Up to 32 ranges can be entered. If fset-id - fset-id is specified, the second fset-id must be greater than the first. * designates all configured syncfilesets for the current syncuser. USER user-ID | ALLU[SERS] [, USER user-ID | ALLU[SERS] USER user-ID a configured syncuser. REPORT creates a report for the syncuser file sets that are in the fset-range specified.
REPORT Command Interpreter displays the file name, file attributes and selection criteria of each selected file. If DETAIL is omitted, the report shows only summary statistics for the file set, but it does not report on specific files. ALL short form to specify all DETAIL options described below. INSYNC displays all files from the source and destination file set that have already been synchronized and are still in sync at the time the report is generated.
RUN[D] Command Interpreter NEWERINDEST displays all files in the destination file set where the destination file is newer than the source file. It overrides the other DETAIL options INSYNC, NOTINSYNC and EXCLUDED. The option is ignored if TIMEEXACT has also been specified. The sync options are applied at the time the files are compared.
START MONITOR Command Interpreter CPU EXTSWAP LIB NOWAIT PRI DEBUG IN MEM OUT SWAP DEFMODE INSPECT NAME PFS TERM command any command line to be passed to the process in the startup message. The RUN[D] command is not a multiline command and is not terminated with a semicolon. Any semicolon is passed to the process as part of the startup command. Refer to Table 8-3 for a list of standard programs, such as EDIT and FUP, that can be executed by simply typing the program name.
STATS Command Interpreter If omitted, the home terminal is set to the default EMS collector. The default EMS collector is $0, or the EMS collector configured by setting the global parameter EMSCOLLECTOR. Note that internally, the default hometerm of the monitor is $ZHOME, as displayed by the TACL command STATUS $, because an EMS collector cannot be specified as the hometerm of a process when the process is launched.
STATUS BATCHID Command Interpreter STATUS BATCHID Obtains and displays status information from the synchronization processes configured in the specified batchid. The command is functionally equivalent to STATUS SYNC with the BATCHID option. STATUS BATCH[ID] [ batchid-range [, batchid-range ],...
STATUS MONITOR Command Interpreter SYSTEM system-name specifies the Expand node name of a system for which the information is displayed. This option is useful for file set that have the destination system specified as a wildcard "*". If omitted, the status for all systems in the fileset that meet the criteria is displayed. USER { user-id | user-name } | ALLUSERS displays status information for any batchid running under the specified Guardian user ID or user name.
STATUS SYNC Command Interpreter STATUS SYNC Obtains and displays status information from the specified ASYSYNC process. It displays information pertaining to the file sets scheduled for synchronization. STATUS [ASY]SYNC [ process-name | * ] [, option... ] option is { ACTIVE} { BATCH[ID] batchid} { BRIEF} { DETAIL} { { [ FSET[ID] | ID ] syncf-id }} { SYSTEM system-name } { USER { user-id | user-name } | ALLUSERS} process-name the Guardian process name of a ASYSYNC process.
STATUS SYNCFILESET Command Interpreter displays status information for the specified synchronization file set. The same information can be displayed using STATUS SYNCFILESET. SYSTEM system-name specifies the Expand node name of a system for which the information is displayed. This option is useful for file sets that have the destination system specified as a wildcard "*". If omitted, the status for all systems in the fileset that meet the criteria is displayed.
STOP MONITOR Command Interpreter If fset-range is omitted, all syncfilesets for the current user are displayed. status-option: ACTIVE displays status information for ASYSYNC processes that are currently in the process of synchronizing file sets. BRIEF displays the synchronization process name, the destination system, the number of active file sets in the batchid and status of the synchronization process. DETAIL displays detailed status information.
SUSPEND BATCHID Command Interpreter ABEND MONITOR A variation on the STOP MONITOR command is the ABEND MONITOR command. ABEND MONITOR [ * | process-name | mapdb ]; ABEND MONITOR causes the monitor process to stop and produce a saveabend file. This command should be used when instructed to do so by HP or to supply information to report a monitor process problem. SUSPEND BATCHID Stops the synchronization for a given file set.
SUSPEND SYNCUSER Command Interpreter * designates all configured syncfilesets for the syncuser. To display the file set ID’s and BATCHIDs, use INFO SYNCFILESET. SUSPEND SYNCUSER Stops synchronization activity for the specified user. Active synchronization is stopped after the current file set is synchronized. SUSPEND SYNCU[SER] { user-id | ALLUSERS }; user-id a Guardian user ID or user name of a configured user. ALLUSERS designates all users. SYNCHRONIZE Executes a one time synchronization.
SYNCHRONIZE Command Interpreter Section 3, One-time Synchronization discusses synchronization options in greater detail.
SYNCHRONIZE Command Interpreter guardian-option: { AUDITED } { AUTOCREATECAT[ALOG] } { BACKUP backup-program } { CATALOG SQL-catalog } { COMPRESS | NO COMPRESS } { EXCLUDE exclude-file } { KEEPNOPURGEUNTIL } { MAPNAMES mapnames-file } { MAXBACKUP num-of-file } { NETWORKS[ECURE] | NO NETWORKS[ECURE] } { NOSAFEGUARD | NO NOSAFEGUARD } { RECOVERY | NO RECOVERY } { RENAMEO[PEN] } { RESTORE restore-program } { SECURE "rwep" } { SQLREDEF } { SUBVOLPURGE } { SYNCVIEWS | NO SYNCV
SYNCHRONIZE Command Interpreter oss-option: { ALLHARDLINKS | NO ALLHARDLINKS } { ALLSYMLINKS | NO ALLSYMLINKS } { OWNERG[ROUP] { group-id | group-user } } { SECURE "rwxrwxrwx” } source-file-set a guardian or OSS file set that is to be synchronized. If a system name is specified, it must be the local Expand node name. dest-file-set the location of the file set that is to be updated.
SYNCHRONIZE Command Interpreter If a system is specified, it must be the local system; exclusion pertains only to source files, not destination files. If the PURGE option is specified, to exclude files from being purged on the destination, use the EXCLUDEPURGE option. Without EXCLUDEPURGE: A file on the exclude list is purged on the destination (it is not excluded from purging), if it does not exist on the source.
SYNCHRONIZE Command Interpreter Each entry must be on a separate line. If a line starts either with the word "COMMENT", or the characters "--", the line is treated as a comment and is ignored. Note that exclusion applies only to destination files; it does not apply to files on the source. Consequently, if a system name is specified, it must be the name of the destination system. Guardian file sets: The exclude file supports all legal disk file patterns.
SYNCHRONIZE Command Interpreter KEEPB[ACKUPINFILE] instructs AutoSYNC to retain the BACKUP and RESTORE input files. By default, these files are temporary and they are purged after the synchronization has completed. This option is used for troubleshooting only. The name of the input file is in the format of ZBKnnnnn for BACKUP and ZRSnnnnn for RESTORE, where nnnnn is a serial number. The files are placed in the MapDB subvolume. The exact file name is displayed in the LOGFILE.
SYNCHRONIZE Command Interpreter the interval during which the source file must remain unchanged to be considered for synchronization. The default unit of time is MINUTES. If omitted, the openupdate interval is 5 minutes. The time elapsed is computed from the last time the file was modified. The candidate files can be opened for WRITE or READ-WRITE access. The exclusion mode must be SHARED or PROTECTED. Recovery must be enabled for the file set.
SYNCHRONIZE Command Interpreter Guardian file sets: If PURGE is specified, the subvolume portion of the source and destination file sets must be fully qualified (no wild-card characters or "*"). Purging of files occurs on a subvolume by subvolume basis. A destination file is not purged if it does not exist in a corresponding source subvolume, unless the SUBVOLPURGE option is also specified. Extra SQL objects in the destination like tables, views and indexes are purged.
SYNCHRONIZE Command Interpreter Note on SQL Shorthand Views. A SQL view has no modification timestamp. Instead AutoSYNC uses creation timestamps. This prevents a shorthand view from being synchronized every time the file set is synchronized. However if TIMEEXACT is specified, the shorthand view will always be synchronized because the creation time of the destination is always newer than the creation time of the source. For further details on SQL View synchronization, see paragraph SQL Views on page 3-8.
SYNCHRONIZE Command Interpreter The command supports a set of built-in arguments. Each argument starts with a pound sign (#) and is terminated by a TACL delimiter character such as space, comma (,), or by a OSS shell delimiter such as space, semicolon (;), and so on. Arguments are not case-sensitive. The built-in arguments are the following: #SOURCEFSET is replaced with the original source file set name. #DESTFSET is replaced with the destination file set name.
SYNCHRONIZE Command Interpreter instructs AutoSYNC to create (or not to create) a SQL catalog when a SQL object that requires a catalog is moved to a destination where the catalog does not exist. The catalog is created in the same location as the catalog on the source system. If the source catalog volume does not exist on the destination system, the catalog is placed on the volume of the destination tables.
SYNCHRONIZE Command Interpreter specifies the mapping of a source fileset to a destination file set and catalog name mapping. The mapnames-file is an edit or entry-sequenced file located on the destination system. File name mapping: The mapnames-file entries are similar to, but not exactly the same as, the MAP NAMES option of RESTORE. Each line of the MAPNAMES file contains a single mapping of the form.
SYNCHRONIZE Command Interpreter the maximum number of files to be processed by one BACKUP process. When processing large file sets, AutoSYNC divides the synchronized files into subsets, each processed by a separate BACKUP process. BACKUP performance decreases significantly with the number of files it processes. To avoid performance degradation, AutoSYNC starts multiple BACKUP processes, in sequence, and assigns to each no more than the configured num-of-files. The default is 1000.
SYNCHRONIZE Command Interpreter RENAMEO[PEN] specifies that destination unaudited files that are opened for shared READ access or running object files are to be renamed to allow AutoSYNC to replace them. The syncuser must have PURGE privileges to the destination file for the RENAME to succeed. Both the old and new file names are recorded in an AutoSYNC index file called AAINDEX, located in the MapDB subvolume.
SYNCHRONIZE Command Interpreter instructs AutoSYNC to process subvolumes in the destination file set even if the subvolumes do not exist on the source file set. All other synchronization options specified apply to the selection of files to purge in the destination file set. For example, if the AUDIT option is specified, the audited files in the extra destination subvolumes are purged. The REPORT function also lists the extra subvolumes if both PURGE and SUBVOLPURGE are specified.
SYNCHRONIZE Command Interpreter file is created in the destination file set and all contained links to the same inode are linked to this file. A warning is written into the log file when an uncontained hard link has been synchronized. If NO ALLHARDLINKS is specified, uncontained hard links are not synchronized. The default in ALLHARDLINKS. ALLSYMLINKS | NO ALLSYMLINKS synchronizes all symbolic links in the specified syncfileset, including uncontained symbolic links.
TIME Command Interpreter write access is granted in the destination file to allow subsequent synchronizations. Write access is only upgraded when the syncuser is the owner of the file and not SUPER.SUPER. When the super ID is used, the owner write security setting is not upgraded. TIME Displays the current local time of day as obtained from the local Guardian timekeeping function. You may also request the local time as seen by another system on your Expand network.
UPDATE Command Interpreter UPDATE Modifies field values in records from an Enscribe file. Most of the parameters are identical to COPY.
UPDATE Command Interpreter file the name of the Enscribe file that is to be modified by the command. selection-options COMParelen <1-to-255 > sets the compare length for generic positioning on the record key (primary or alternate) specified in the FIRST KEY option. The compare length must be less than or equal to the key specified. COUNT num-records is the number of records or rows to be copied. If omitted, all records are copied.
UPDATE Command Interpreter ALTKEY key-value [, key-value ] the alternate key of the starting record or row. The format of key-value is described above. EXACT requests exact positioning on the record key (primary or alternate) specified in the FIRST KEY option. FROMLAST positions on the last record in the key range specified in the FIRST KEY option. REVERSE the input file is to be READ from the starting record in reverse order. SHARE the file is to be opened in shared-exclusion mode.
UPGRADE MAPDB Command Interpreter UPGRADE MAPDB Creates additional tables in a configured MapDB (that is, the MapDB subvolume and monitor process are registered in the SysDB). AUTOSYNC prompts the user to issue the command if and when necessary. UPGRADE MAPDB subvol; subvol the name of a MapDB to upgrade. VOLUME Changes the default volume and/or subvolume for filename expansion. It can be abbreviated to V. Volume [ volume | subvolume | volume.
VOLUME Command Interpreter HP AutoSYNC User’s Guide—522580-020 8-122
9 Reporting Function This section describes the AutoSYNC reporting function. The topics covered are organized as follows: Overview REPORT Command Report Output Format Overview The AutoSYNC reporting function compares source and destination file sets and reports on the status of source and destination locations. It can aid in system migration by providing ad-hoc reports on migrated subvolumes, volumes or systems during the migration process.
REPORT Command Reporting Function The report can be written to a disk file. If no report file is specified, the report is displayed at the terminal.
Report Output Format Reporting Function Report Output Format The default REPORT output displays statistics of the files in sync, not in sync and excluded files; the list of potential entries generated are formatted as follows: Autosync Report timestamp Report Summary fileset: Source: source-fset, Destination: destination-fset n Files in source fileset n Subvolumes in source fileset n Volumes excluded n Subvolumes excluded n Files excluded from sync n Audited n Corrupt n Excluded specified n
Report Output Format Reporting Function If DETAIL is specified, the filename, file attributes, status indicator and the selection criteria are displayed for each file; in addition, the summary statistics are displayed at the end of the report. Filenames are grouped by subvolume. The extra files in the destination subvolume (files that are not in the source file set) are displayed first, in alphabetical order; for OSS file sets, extra files are listed last in alphabetical order.
Report Output Format Reporting Function The following example shows a sample report for a Guardian file set, where the EXCLUDE, PURGE and EXCLUDEPURGE options are specified: : AutoSYNC 1? report sync testdata.* to \dest.$data.testdata.*, purge, AutoSYNC 1+ excludep \dest.$data.jojoexcl.excludep, exclude jojoexcl.exclude; Starting SYNCfset $SDATA.testdata.* ($X1KLD) File $SDATA.testdata.RCRDEXIT excluded from synchronization. File $SDATA.testdata.RDEMP excluded from synchronization. File $SDATA.testdata.
Report Output Format Reporting Function The following example shows a sample report for a OSS file set, where the PURGE option is specified: AutoSYNC 5? AutoSYNC 31? report sync /home/cssw/johanne to /E/YOSPRD/home/cssw/johanne,purge; Starting SYNCfset /home/cssw/johanne ($X0YP8) -- Report completed for fileset -- /home/cssw/johanne -- to -- /E/YOSPRD/home/cssw/johanne. --- REPORT completed successfully. Autosync Report 8/24/07 12:37:44.
A Operations and Management This appendix describes the management of AutoSYNC. The topics covered are the following: AutoSYNC Configuration Database The AutoSYNC Monitor Monitor Commands Configuring and Using an Alternate AutoSYNC Environment AutoSYNC Defines Takeover Procedures Migrating the Configuration Database AutoSYNC Configuration Database The configuration information is stored in two subvolumes: 1. SysDB: global parameters and licensing information 2.
SysDB Operations and Management You need write access to the SysDB to create or alter MapDB, to specify the product license, or alter global configuration parameters. You need read access to execute some commands, especially to start the monitor process. When AutoSYNC needs to access the SysDB, it looks first for SysDB tables in $SYSTEM.ESCSYSDB. If the tables do not exist, it then searches all disks for a SysDB in the ESCSYSDB subvolume.
MapDB Operations and Management MapDB MapDB stores configuration parameters for scheduled synchronizations. The tables in the MapDB subvolume are: A REGISTRY table to store local parameters. Local parameters are analogous to global parameters stores in the SysDB REGISTRY table, but they apply only to a specific MapDB/monitor pair.
The AutoSYNC Monitor Operations and Management In FUP, rename the current log file and create the new file: RENAME SLggguuu, OLDLOG SET LIKE OLDLOG SET EXT (primary-extent, secondary-extent) MAXEXTENTS maxextents CREATE SLggguuu EXIT In AutoSYNC CI, reactivate the synchronizations for the syncuser: ACTIVATE SYNCUSER userID; The log file is opened once, when the synchronization process starts up. SUSPEND stops the synchronization process and ACTIVATE restarts the synchronization process.
Configuring the Monitor Process Operations and Management Configuring the Monitor Process The monitor is configured and started when the MapDB is created through the CREATE MAPDB command. The monitor has an assigned default process name, $ZASY, reserved for AutoSYNC. The monitor configuration can be changed by using the ALTER MONITOR command. You can configure process priority, process CPUs, and the monitor event-logging device.
Stopping a Monitor Operations and Management Stopping a Monitor The monitor process should be available for scheduled synchronizations to occur. If the monitor is stopped, synchronizations in progress will continue, but none are started. In normal situations, however, the monitor process should be stopped only when the system is being shut down. Use the STOP MONITOR command to stop the monitor. Monitor Commands The monitor accepts interactive command requests from AUTOSYNC.
LOG Operations and Management LOG The LOG command starts (and stops) the logging of monitor activity. LOG { TO file [CLEAR] | STOP } TO file [CLEAR] the name of a log file. CLEAR empties the file before logging commences. If file already exists, information is appended to the end of the file unless CLEAR is specified. If the file name ends with a number (for example, LOG001), additional files will be allocated with incrementing numbers when the first file becomes full. STOP stops logging.
SECURITY Operations and Management LICENSE requests information about the AutoSYNC license for the current system. TCPIP requests information about the configured listener processes. SECURITY The SECURITY command instructs the monitor to accept further commands only from a specific set of process access ids. SECURITY { N | C | U | A | G | O | - } The command option is a single character and is a Guardian security specifier.
Installing an Alternate Version of AutoSYNC Operations and Management AutoSYNC can use the same SysDB concurrently. See Configuring an Alternate SysDB below for details. Installing an Alternate Version of AutoSYNC If you wish to run different versions of AutoSYNC on your system, you first must install the alternate version in its own product subvolume. Run the INSTALL macro from the installation subvolume that contains the desired version, specifying the alternate product subvolume of your choice.
Configuring an Alternate Monitor Process Operations and Management Create an alternate MapDB Create the alternate MapDB using the CREATE MAPDB command, specifying the alternate monitor process name. This command starts the monitor process. In the example below, the user creates a test MapDB in $DATA.ASZMAPDB with monitor $ZASZ, from the same alternate product subvolume $data.asyaakts created as an example above in Installing an Alternate Version of AutoSYNC. 1> $data.asyaakts.
Configuring an Alternate Monitor Process Operations and Management In the example below, the user wishes to disable synchronization over TCP/IP for the new environment, for testing purposes and does so by setting the local SYNCoverip parameter: AutoSYNC 2? info globals; AutoSYNC Global Settings AutoSYNC SYNCcompress SYNCrecover SYNCoverIP SYNCTCPPROCesses EMSCollector ON OFF ON ON $ZTC0,$ZTC1 $0 AutoSYNC 3? alter local syncoverip off; --- AutoSYNC Local AUTOSYNCOVERIP updated.
Configuring an Alternate SysDB Operations and Management 3. Specify the monitor process name on the AUTOSYNC run command: 3> $data.asyaakts.autosync $ZASZ HP Nonstop(tm) AutoSYNC(tm) Command Interpreter(T2713H01) - System \ATOM (C)2006 Hewlett Packard Development Company, L.P. (C)2006 Carr Scott Software Incorporated 4. In AUTOSYNC, use the OPEN monitor-process command. 4> $data.asyaakts.
Configuring an Alternate SysDB Operations and Management Add the SysDB define Use the =_AUTOSYNC_SYSDB class catalog define to specify an alternate SysDB subvolume. Do not use the ESCSYSDB subvolume name. 1> add define =_autosync_sysdb,class catalog,subvol $data1.mysysdb 2> autosync HP Nonstop(tm) AutoSYNC(tm) Command Interpreter(T2713H01) - System \ATOM (C)2006 Hewlett Packard Development Company, L.P. (C)2006 Carr Scott Software Incorporated *Warning* The SysDB cannot be found.
AutoSYNC Defines Operations and Management define is the only way to specify an alternate SysDB. Use the ENV command to verify which SysDB and MapDB you are currently accessing. Autosync 1? env; ---------------------------------------CI Session Environment ---------------------------------------Process: $Z6LD (7,163) (priority 145) Volume $RWC.AUTOSYNC Dictionary None SQL catalog None SysDB $DATA1.MYSYSDB (9607180a) MapDB $DATA.
Takeover Procedures Operations and Management The =_AUTOSYNC_SYSDB DEFINE is class CATALOG and specifies a subvolume for the SysDB tables. If this DEFINE is present when AUTOSYNC is started, it does not look for the normal SysDB, but uses the one specified. Thus, it operates only with MapDBs and monitor processes that are created under the specified SysDB. A typical =_AUTOSYNC_SYSDB DEFINE is added by using the following TACL command: ADD DEFINE =_AUTOSYNC_SYSDB,CLASS CATALOG,SUBVOL $vol.
Unplanned Takeover Operations and Management SUSPEND SYNCUSER ALLUSERS; SUSPEND SYNCFILESET *; / SUSPEND BATCHID *: 3. Re-issue the STATUS SYNC, DETAIL command to confirm that there are no ASYSYNC processes that are still active. Note that SUSPEND will terminate a scheduled synchronization at the end of the current file being synchronized, so there may still be synchronization activity for a short period. 4. Proceed with the usual shutdown procedures, which will stop the AutoSYNC monitor.
Migrating the Configuration Database Operations and Management 3. When primary processing has been switched back to \P and \B becomes the destination system again, re-allow \B to accept synchronizations from \P on \B:. CLEAR AUTOSYNC FROM \P; Migrating the Configuration Database The AutoSYNC configuration files and tables are described above in paragraph AutoSYNC Configuration Database. The information stored in database tables references local file names, system names and system numbers.
Migrating an AutoSYNC Source System Operations and Management 3. If synchronizations are performed over TCP/IP, configure the TCP/IP connection as described in Synchronization Over TCP/IP on page 7-1 and as instructed by the network administrator. 4. At this point, issue the STATUS MONITOR command to verify the new environment is correctly configured. 5. Configure the AutoSYNC GLOBAL and LOCAL parameters, using infog as the command file. 6.
Migration Steps for an AutoSYNC Destination System Operations and Management Migration Steps for an AutoSYNC Destination System On the Existing Source System Moving a destination system requires updates to the syncfileset definitions on the source system. 1. Capture the syncfileset configuration information for each syncuser as described in Steps 4 described in paragraph On the Existing Source System on page A-17 above. 2.
Operations and Management Migration Steps for an AutoSYNC Destination System HP AutoSYNC User’s Guide—522580-020 A-20
B Problem Resolution This appendix discusses how to diagnose AutoSYNC problems, how to use the tools and how to report problems. The topics covered are: Common Security Problems Troubleshooting Tools Submitting Problems Common Security Problems Security related problems are common when first configuring AutoSYNC and performing synchronizations. Security rules enforced by SafeGuard and Guardian must be taken into consideration when planning and installing AutoSYNC.
Scheduled Synchronization Problems Problem Resolution Scheduled Synchronization Problems The source synchronization process creation fails with security violation Verify that the ASYSYNCP object file in the source product subvolume is PROGID’ed to the Authorizer. Verify that the Authorizer has permission to log down to the sync user ID. If not, make ASYSYNCP callable, to bypass the restriction. See Bypassing Disabled Log Down on page 4-7 for details.
Errors executing triggers Problem Resolution Synchronization of OSS files fails with error 4001 or error 4013. Check the owner of the source file. If the user is not the owner of the source file, only SUPER.SUPER can synchronize the file or directory. Moreover, if the destination is on a remote system, the remote synchronization process must be configured to run as a local process. See Running the Destination Synchronization Process as a Local Process on page 3-21 for configuration instructions.
Troubleshooting Tools Problem Resolution As mentioned in the paragraph above, verify that the MapDB log file SLgggnnn is secured to allow write access from both source and destination synchronization processes. Troubleshooting Tools AUTOSYNC Commands Synchronization Logs Events in the EMS Log AutoSYNC Tracing AUTOSYNC Commands Checking the Environment The overall processing environment can be checked using the CI command ENV.
Synchronization Logs Problem Resolution A character identifying the process that logged the entry: C— AutoSYNC configuration changes s— ASYSYNC-S - source system d— ASYSYNC-D - destination system t— trigger command output b— BACKUP r— RESTORE p— Report output line A text message If the synchronization is over EXPAND, both source and destination synchronization processes open the log file on the source system and write their respective messages into the log file.
Synchronization Logs Problem Resolution Autosync 1? info syncf 2,log last 1; Autosync User: 100,1 (sysman.user1) ID Source fileset Destination fileset Batch Intvl --- ------------------------ --------------------------------- ----- ----2 $DATA.STUFF* \SYSB.$DATA.STUFF.* 0 2 Log Starting Time: 2001-02-09 14:46:53.
Synchronization Logs Problem Resolution One-Time Synchronizations One-time synchronizations are launched using the SYNCHRONIZE command. AUTOSYNC logs the output of a such synchronizations in a temporary log file that is purged after the synchronization has completed. To retain the log file, use the LOGFILE option of the SYNCHRONIZE command. The format and content of the log file are identical to the SLggguuu log for scheduled synchronizations.
Events in the EMS Log Problem Resolution Events in the EMS Log The AutoSYNC monitor and the synchronization processes report informational and critical events to the EMS log on the source system. The Monitor events are sent to the Monitor’s home terminal. To direct all AutoSYNC events (from ASYSYNC processes and the Monitor) to the same collector, configure the Monitor’s home terminal to the local collector.
AutoSYNC Tracing Problem Resolution AutoSYNC Tracing For cases where a problem is not diagnosed by looking at the synchronization log, support personnel may request that the synchronization sessions be traced. Tracing is enabled for all syncfilesets belonging to a syncuser. To start tracing, use the TRACE option of the ALTER SYNCUSER command. The syncuser must be suspended and re-activated to start tracing. Tracing generates a large amount of data.
Submitting Problems Problem Resolution The following example traces a synchronization attempt where no files require synchronization. Autosync 3? info syncf 1,log last 1; Autosync User: 100,1 (SYSMAN.USER1) ID Source fileset Destination fileset Batch Intvl ---- ------------------------- --------------------------------- ----- --1 $DATA2.STUFF.* \SYSB.$DATA2.STUFF.* "JC" 1 Log Starting Time: 2001-02-09 16:39:11.373 s-PROCESS_CREATE_(\SYSB.$DATA2.JCC153.ASYSYNC,\SYSB.$Y2769:24726817) s-FILE_OPEN_(\SYSB.
AutoSYNC Component Failures Problem Resolution AutoSYNC Component Failures When the monitor process, AUTOSYNCCI or a synchronization process abend, they produce a saveabend file. The monitor displays a message on its hometerm or the configured EMS collector process and the command interpreter displays a message on its out file.
Scheduled Synchronization Failures Problem Resolution The log of the synchronization, either by PAKíng the log file (SLnnnggg) or by sending the output of the INFO SYNCF fset-ID, LOG command A VPROC listing of the ASYSYNC(P) process When the log does not yield sufficient diagnostic information, trace the syncfileset and send the trace along with the remaining supporting data.
C Examples These examples are intended to assist you in becoming acquainted with the use of the AutoSYNC product. These examples assume that the product has been successfully installed, licensed and that the monitor process is running. One-Time Synchronization Guardian file set SYNCHRONIZE the source file set $DATA.JOJOX*.* to the destination file set \DEST.$DATA.*.
OSS file set Examples OSS file set To synchronize the local directory tree home/dev/jojo to the destination node NSK2:i AutoSYNC 10? sync /home/dev/jojo to /E/NSK2/home/dev/jojo, timeexact; Starting SYNCfset /home/dev/jojo Source Directory: /home/dev/jojo/ ( .
Scheduled Synchronization Examples Scheduled Synchronization Single-User Environment In the single-user AutoSYNC environment, you install and configure AutoSYNC. The following commands show how to configure a single-user scheduled synchronization: Autosync 1? ADD SYNCUSER 110,125, MAXPRIORITY 130; --------- MapDB table $F08.ASYMAPDB.SF110125 created. MapDB table $F08.ASYMAPDB.SL110125 created. AutoSYNC user 110,125 (OPER.JOE) added. Monitor $ZASY cache refreshed.
Multiple-User Environment Examples Autosync 8? DELETE SYNCFileset 1; --- AutoSYNC fileset ID 1 deleted. --- Monitor $ZASY cache refreshed. Autosync 9? INFO SYNCFileset; AutoSYNC User: 110,125 (OPER.JOE) ID Source fileset Destination fileset Batch Intvl ---- ------------------------- --------------------------------- ----- ----0 $DATA.GROUP0.* \PROD.$DATA.GROUP0.* 0 5 Autosync 10? STATUS SYNC; SYNCuser: 110,255 (OPER.
Multiple-User Environment Examples configure a multiple-user environment where SUPER.SUPER is the AUTHORIZER. After logging on as SUPER.SUPER: Autosync 1? AUTHORIZE AUTOSYNC, ADMINistrator 110,255; User 110,255 (OPER.MGR) has been authorized as AutoSYNC administrator. The AutoSYNC monitor process must be started by user 255,255 (SUPER.SUPER). --- Monitor $ZASY cache refreshed. Log on as OPER.MGR: Autosync 2? ADD SYNCUSER OPER.JOE, PRIORITY 140; --------- MapDB table $F08.ASYMAPDB.SF110125 created.
Multiple-User Environment Examples Autosync 7? INFO SYNCFileset 0, DETAIL; AutoSYNC User: 110,125 (OPER.JOE) SyncID: 0 Source fileset: $DATA.GROUP1.* Destination fileset: \PROD.$DATA.GROUP1.
D Error Messages This appendix describes the EMS messages generated by AutoSYNC.
Informational messages Error Messages Effect. The monitor stops. Recovery. Restart the monitor. 103 Monitor takeover Cause. The monitor primary process or its CPU has failed. Effect. The monitor backup process has taken over. The monitor is ready to service requests. Recovery. Informational message. No action is required. 104 Monitor backup created Cause. The monitor primary process has created a backup process. Effect. The monitor process is fault tolerant. Recovery. Informational message.
Informational messages Error Messages 107 Monitor status info Cause. The monitor process has displayed status information. Effect. Status information is placed in the EMS log. Recovery. Informational message only; no corrective action is needed. 108 Monitor started ASYSYNC process Cause. The monitor process has started an ASYSYNC process to perform AutoSYNC synchronization. The message contains the user id that configured the synchronization, the destination node, and the process name. Effect.
Informational messages Error Messages 111 ASYSYNC process lost Cause. An ASYSYNC process has stopped or abended, but no process-stop message was received. This may be caused by a CPU failure. Effect. Informational message only; no corrective action is needed. Recovery. No action is required. The ASYSYNC process is restarted automatically. 112 Monitor cache refreshed Cause. Cached configuration information has been refreshed from the MapDB tables. Effect.
Informational messages Error Messages 115 ASYSYNC process failed Cause. The monitor process has attempted to start an ASYSYNC process to perform AutoSYNC synchronization, but the operation failed. The message contains PROCESS_CREATE_ error and error detail code. Effect. AutoSYNC processing for the specified user id is not active. Recovery. Correct the cause of the failure and the process will be restarted automatically. 120 ASYSYNC process started via TCP/IP Cause.
Informational messages Error Messages 123 Trigger TACL or OSS shell process abended Cause. An ASYSYNC process performed the TRIGGER option; it started a TACL process or an OSS shell passing the trigger command. TACL or the OSS shell abended. The message contains the user ID, destination node name, BATCHID, the file-set ID, or a -1 if not available and an the error text or the error and error detail code. Effect. Effect.
Informational messages Error Messages 142 MAPDB access error Cause. Configuration could not be accessed from the MapDB tables. Effect. Configuration information is not available to the monitor; requested services will not be performed. Recovery. Correct the table access problem and issue the MONITOR REFRESH NOW command. 143 MAPDB inconsistent Cause. Configuration information in the MapDB tables is inconsistent. Effect. The configuration information is not available on request to the monitor. Recovery.
Critical event messages Error Messages Effect. An ASYSYNC process has failed and a synchronization may not be performed. Recovery. Check the log of the SYNC user for further information. 204 Fileset update Cause. An ASYSYNC process has initialized or updated its file sets. Effect. The ASYSYNC process performs an updated set of synchronizations. Recovery. Informational message only; no corrective action is needed. Critical event messages 402 Monitor intentionally abended Cause.
Critical event messages Error Messages 412 Resize segment error Cause. An attempt to resize the extended segment failed. Effect. The process abends. Recovery. The error number is provided in the message. Determine the reason for the failure and correct it. 413 Memory pool allocation error Cause. An attempt to allocate memory in the extended segment failed. Effect. The process abends. Recovery. Since the product usually resizes the segment to satisfy memory requests, this error should not occur.
Critical event messages Error Messages 423 Remote monitor down Cause. When an ASYSYNC process starts, it must obtain information from the AutoSYNC monitor process on the destination system. This error is generated if it was not possible to contact the monitor. Effect. The synchronization process terminates. No files are synchronized. Recovery. Start the AutoSYNC monitor on the destination system. 432 ASYSYNC version mismatch Cause. A source or destination ASYSYNC process detected a version mismatch.
Critical event messages Error Messages 701 Product object missing Cause. A required program object file is missing from the product subvolume. Effect. The process abends. Recovery. Install the missing object file and re-execute the program.
Critical event messages Error Messages HP AutoSYNC User’s Guide—522580-020 D-12
Index A Administrator 4-2 Alternate key files 3-6 ASYSYNC or ASYSYNCP privileged processes 2-10 ASYSYNCP process authorizing 2-7 Authorizer 4-2 AUTOSYNC command interpreter 8-1 AutoSYNC license 2-5, 3-1 B C Coldload procedures Updating 2-8 Completion Code in AUTOSYNC command interpreter 8-1 D Defines use in AUTOSYNC command interpreter 8-2 Destination file set 3-2 node name 4-4 Disabled log down Bypassing 4-7 EMS messages EMSFILEEVENTS B-8 EMSSUPPRESS B-8 ESCSYSDB see SysDB F Files Opened for Update 3-1
O Index O Partitioned files and tables 3-9 Purging Destination Subvolumes SUBVOLPURGE 3-14 Purging Files in Destination 3-13 Purging Subvolumes in Destination 3-14 over TCP/IP 4-10 Security Remote passwords 4-7 SFggguuu MapDB table A-3 Shutdown procedures Updating 2-8 SLggguuu MapDB file A-3 Resizing the file A-3 Source file set 3-2 SQL index tables 3-7 SQL tables 3-7 SQL views 3-8 SQL/MX tables 3-3 Symbolic Link Modification Timestamp 5-4 Synchronization Criteria 5-4 TIMEEXACT 5-5 SYNCUSER MapDB table
Z Index Users 4-3 Z ZASYTMPL EMS templates 2-8 ZYQ*.
Special Characters Index HP AutoSYNC User’s Guide—522580-020 Index-4
