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 AAQ 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-009 AutoSYNC AAJ August 2007 522580-011 AutoSYNC AAK June 2008 522580-012 AutoSYNC AAM March 2009 522580-013 AutoSYNC AAN January 2010 522580-014 AutoSYNC AAO August 2010 522580-015 AutoSYNC AAQ January 2011
Legal Notices © Copyright 2010 Hewlett-Packard Development Company L.P. 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 What’s New in This Manual ix Manual Information ix New and Changed Information About This Manual xi Notation Conventions ix xi 1.
3. One-time Synchronization Contents Installing AutoSYNC (continued) Update the System Coldload and Shutdown Procedures Install the NonStop AutoSYNC EMS templates 2-8 Installing a New Version of AutoSYNC 2-9 2-8 3.
4. Scheduled Synchronization Contents 4.
6. Triggers Contents 6. Triggers Overview 6-1 7. Synchronization Over TCP/IP Overview 7-1 Configuring a TCP/IP connection 7-1 On both Source and Destination Systems 7-1 On the Destination System 7-3 On the Source System 7-4 Synchronization over TCP/IP 7-4 8.
8.
8.
9. Reporting Function Contents Command Descriptions (continued) UPGRADE MAPDB 8-92 VOLUME 8-92 9. Reporting Function Overview 9-1 Output format 9-2 A.
C. Examples Contents C. Examples One-Time Synchronization C-1 Guardian Fileset C-1 OSS Fileset C-2 Scheduled Synchronization C-3 Single-User Environment C-3 Multiple-User Environment C-4 D. Error Messages Informational messages Critical event messages D-1 D-8 Index 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 HP AutoSYNC User’s Guide—522580-015 x
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-015 xvi
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 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. You should only update SysDB through the AutoSYNC command interpreter, which ensures consistency between it and the other AutoSYNC components.
AutoSYNC in a Network AutoSYNC Overview HP AutoSYNC User’s Guide—522580-015 1-6
2 Installation This section discusses the procedure to follow for the initial installation of AutoSYNC. It covers: Prerequisites Installing AutoSYNC Installing a New Version of AutoSYNC 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. Volumes containing the AutoSYNC configuration must be specified in the TMF configuration as audited data volumes.
Move Files from the Product Media to the Installation Subvolume Installation Also, if your system security is configured to prevent a user from performing a log down to another user ID without specifying a password, read the section “Bypassing Disabled Log Down” on page 4-7. Consult the softdoc file for any recent changes to the installation procedures. The entire process should take only a few minutes.
Install the AutoSYNC Product Files Installation Install the AutoSYNC Product Files Use the INSTALL macro to restore the product files from ZAUTOSYC to the operational subvolume; the default operational subvolume is $SYSTEM.AUTOSYNC. Do not install the files in $SYSTEM.SYSTEM or $SYSTEM.SYSnn. Then execute the INSTALL macro as follows:. VOLUME $.ZAUTOSYC RUN INSTALL You may specify a subvolume in which to install the AutoSYNC operational files.
Create the AutoSYNC System Database Installation templates and filter. To do this, enter the following commands in a separate window terminal window: ADD DEFINE =_EMS_TEMPLATES, CLASS MAP, FILE ZASYTMPL EMSDIST TYPE P, COLLECTOR $0, TEXTOUT $HOME, FILTER ASYFLTR 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).
License AutoSYNC Installation volume as the SysDB tables). You may also specify a particular catalog. See CREATE SYSDB on page 8-63 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.
Start the Monitor Process Installation tables are created. See Appendix A, Operations and Management, for details on the additional MapDB tables. AutoSYNC 4? create mapdb; --- AutoSYNC MapDB table $DATA.ASYMAPDB.SYNCUSER created. --- Map Database for AutoSYNC created. --- System Database updated --- Changes will take effect when the Monitor is restarted. --- Starting AutoSYNC Monitor $ZASY. Monitor 1.5.
Authorize AutoSYNC Installation The following is displayed in the EMS log: 15:55 10JUN04 128,04,355 AutoSYNC Monitor $ZASY Starting Version 1.6.
Update the System Coldload and Shutdown Procedures Installation If system security is set such that the Authorizer cannot log down to another user ID, the following options are available: 1. Configure all scheduled synchronizations with the same user id as the AutoSYNC Authorizer. All other users must request one-time synchronizations. 2. Configure multiple AutoSYNC environments, each with its own MAPDB and monitor process.
Shutting Down AutoSYNC Installation Shutting Down AutoSYNC For an orderly shutdown of AutoSYNC, the following steps are recommended: 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.
Running Different Versions of AutoSYNC Installation Running Different Versions of AutoSYNC If you need to run different versions of AutoSYNC on the same system, for example to test a new version of the product, you must configure an alternate AutoSYNC environment (Monitor and MapDB) and install the test software in a different location.
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 Set Comparison One-time Synchronization Specifying the destination node as a wild-card (“\*”) is supported for scheduled synchronizations (see command description of ADD SYNCFILESET on page 8-7) but is not supported for one-time synchronizations. AutoSYNC must be installed, licensed, and running on the destination nodes. The volume, subvolume, and filename portions of a destination file set must be either a simple an asterisk (*) or must be fully specified.
Data Transfer and File Writing One-time Synchronization • ZZ files and system swap files. Files whose name begin with the letters ZZ are usually temporary or abandoned work files that should be purged. By default, ZZ files are not synchronized. System swap files are also temporary files and are not synchronized. You can request such files to be synchronized by using the ZZINCLUDE option. The source file list that is created is compared to files in the destination file set.
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 \REMOTE.$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 \REMOTE.$DATA.SQLTBL.
Partitioned Files and Tables One-time Synchronization PARTONLY synchronization of single partitions is not supported. An error message is generated if a secondary partition is specifically selected to be synchronized. When selecting a partitioned file for synchronization, AutoSYNC retrieves the aggregate modification time to compare source and destination modification times.
Partitioned Files and Tables One-time Synchronization Changing Subvolume and File Name Mapping Non-partitioned file 1. To synchronize the single partitioned file $DATA01.DB.FILE to subvolume and file BACKDB.BACKFILE, use the following command: SYNC $DATA01.DB.FILE TO $DATA01.BACKDB.BACKFILE,...; Partitioned file To synchronize the partitioned file $DATA*.DB.PARTFILE to different subvolume and file names $DATA*.BACKDB.BACKFILE, the command must specify the primary partition mapping, SYNC $DATA01.DB.
Partitioned Files and Tables One-time Synchronization are equivalent to: \SOURCE.$DATA.*.* TO \DEST.$BACK.*.* \NEWYORK.$DATA*.DB.* TO \DEST.$BACK.BACKUPDB.* \SOURCE.$DATA*.DB.PARTFILE TO \TOKYO.*.*.* By default, name mapping is performed by RESTORE with the assistance of the default MAP NAMES clause provided by AutoSYNC. The default clause is: MAP NAMES ( source-file-set TO dest-file-set, source-system.*.*.
Synchronization Options One-time Synchronization mapping 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.
Purging Extra Destination Files One-time Synchronization from being purged if the corresponding source file does not exist and the PURGE option is specified. Caution. Some performance degradation could occur if an exclude file containing a long list of files is shared by multiple syncfilesets. Purging Extra Destination Files Specify the PURGE option to purge all destination files that do not exist in the source.
Files Opened for Update One-time Synchronization source, it is copied to the destination, but existing processes continue to use the renamed object file. Only files that are open for shared read access or execute access are renamed. Files open exclusively or for write access are not renamed or replaced. AutoSYNC deletes renamed files after they are closed.
Synchronizing Based on Ownership One-time Synchronization 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. Synchronizing Based on Ownership By default, source files owned by all user can be candidates for synchronization, provided the security settings allow it.
Changing File Security One-time Synchronization To avoid replacing object files that have not changed, configure AutoSYNC to compare source and destination binder or linker timestamps instead of comparing MODIFICATION timestamps by specifying the USEBINDERTIME option. The destination object file is replaced only if the binder or linker timestamps of the source and destination do not match exactly; the comparison operates as if TIMEEXACT were specified.
Process Priority and Throttling One-time Synchronization Process Priority and Throttling You may specify a process PRIORITY for a synchronization to ensure that synchronization does not impact higher priority work. Specifying the PRIORITY might be especially useful if you have enabled compression. Another way to reduce the impact on other work is to specify a throttling RATE, which limits AutoSYNC to being active for some percentage (1 percent to 100 percent) of the elapsed time.
Reporting Outcome of the Synchronization One-time Synchronization You specify the alternate program names through the BACKUP and RESTORE options. Number of Files per BACKUP Process BACKUP performance degrades significantly when the number of files is large. To avoid performance degradation and limits in the BACKUP program, AutoSYNC restricts the number of files it assigns to any one BACKUP process. AutoSYNC starts multiple BACKUP processes, in sequence, to process all the files it is synchronizing.
Preserving Security Attributes on Remote Destinations One-time Synchronization 1. Use an appropriate user ID 2. Make the remote ASYSYNC (or the ASYSYNCP if synchronizing over TCP/IP) a privileged program that can become a local process and have local access to files on the remote destination system. See Privileged Destination Synchronization Process below for instructions. As a local process, the synchronization process can set LICENSE and PROGID attributes if the proper user ID is used.
Preserving Security Attributes on Remote Destinations One-time Synchronization 3. At the TACL prompt, accelerate ASYSYNC: AXCEL ASYSYNC, ASYSYNC or OCA ASYSYNC 4. Then, as SUPER.SUPER, license ASYSYNC: FUP LICENSE ASYSYNC IF synchronizing over TCP/IP, perform the same steps for ASYSYNCP. Note. Once you have altered ASYSYNC or ASYSYNCP with the above Binder commands, ASYSYNC or ASYSYNCP must be licensed; otherwise, all synchronizations that use that program will fail. WARNING.
One-time Synchronization Preserving Security Attributes on Remote Destinations HP AutoSYNC User’s Guide—522580-015 3-20
4 Scheduled Synchronization AutoSYNC Roles For most customers, the power of AutoSYNC lies in its ability to keep source and destination file sets synchronized on a continuous basis, which requires synchronization operations to be performed at regular intervals.
The AutoSYNC Administrator Scheduled Synchronization The authorizer is determined as follows: • • If a user issues the AUTHORIZE command, it confers access authority to the ASYSYNCP program using the PROGID facility. AUTHORIZE also designates the administrator. If no AUTHORIZE command has been issued, the user ID that issues the START MONITOR command will start and confer authority to the ASYSYNCP program. If the AUTHORIZE command is issued, any user can start the monitor process.
AutoSYNC Users Scheduled Synchronization 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. Adding a user (ggg, uuu) performs three operations: • • • Adds a user record to the SYNCUSER table of the MapDB. Creates a user file set table, SFggguuu in the MapDB. Creates a user log file, SLggguuu in the MapDB.
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.
BATCHID Scheduled Synchronization 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. If you specify both START and STOP, the AutoSYNC performs the synchronization at each interval between the specified times. BATCHID If a user schedules multiple synchronizations to a destination system, they are executed serially.
DELETE SYNCFILESET (and DELETE BATCHID) Scheduled Synchronization DELETE SYNCFILESET (and DELETE BATCHID) The synchronization is terminated and deleted from the schedule. See DELETE SYNCFILESET on page 8-64 and DELETE BATCHID on page 8-64. SUSPEND SYNCFILESET (and SUSPEND BATCHID) The synchronization is terminated, but retained in the schedule in a suspended state. See SUSPEND SYNCFILESET on page 8-92 and SUSPEND BATCHID on page 8-91.
Bypassing Disabled Log Down Scheduled Synchronization The user must have appropriate remote passwords to any remote destination. AutoSYNC can only synchronize files that are secured for read access by the user ID. It can only replace files that are secured for purge access by the user ID. If the destination is remote, replaced files must be secured for remote purge access. The ownership of synchronized symbolic links is a special case.
Schedule Management Scheduled Synchronization Note. Disabling log down simply prevents use of another user ID by the Super user. The Super user still has unfettered access to all data on the system. Using a privileged ASYSYNCP to bypass disabled log down does not compromise data security. Schedule Management The following overview describes how AutoSYNC manages scheduled synchronizations.
ASYSYNC Scheduled Synchronization The file sets are arranged on a schedule time-list and are processed as they become ready. File sets in an ASYSYNCP are processed serially. When a file set is processed, the ASYSYNCP process starts an ASYSYNC process on the destination system. The ASYSYNCP process then gathers information about all the files of the source file set and forwards them to the ASYSYNC process. The ASYSYNC process responds with a list of files (or tables) to be synchronized.
ASYSYNC Scheduled Synchronization down on the destination system, both the source and destination synchronization processes are ASYSYNCP objects. Then the communication between source and destination ASYSYNCP is established and the synchronizations proceed as described above in paragraphs ASYSYNCP and ASYSYNC. See Synchronization Over TCP/IP on page 7-1 for details.
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. OSS File Sets AutoSYNC supports synchronization of OSS file sets. Each synchronization file set can be either a set of OSS files and directories or a set of Guardian files.
Source File Set OSS File Synchronization To protect the destination file set from loss of integrity in case of system or component outages, AutoSYNC performs the following steps when synchronizing a file or directory: 1. The file or directory is first created with the destination filename plus a temporary name extension ZASYnnnn where nnnn is a number. 2. Data is written to the file. 3.
Links OSS File Synchronization Links AutoSYNC provides synchronization options that control synchronization of hard links and symbolic links. Hard links AutoSYNC always synchronizes a hard link when all links to the same inode are inside the synchronization file set. The SYNCHRONIZE command option ALLHARDLINKS controls the synchronization of a hard link when some of the links to the same inode are outside the synchronization file set.
Displaying OSS files and directories OSS File Synchronization When a symbolic link is synchronized, the content of the link, which is the name of the linked object, is changed in the destination file set as follows: • • If the symbolic link points outside the synchronization file set, the content of the symbolic link is not changed If the symbolic link points inside the synchronization file set and the linked name is an absolute pathname, then the source file set name portion of the linked name is repla
File Set Comparison OSS File Synchronization File Set Comparison A source file or directory is synchronized if the source file or directory was modified after the destination file or directory was last modified. Timestamp comparisons account for differences in time zones and system clocks. Files that have the same modification timestamp are never synchronized.
Changing Default Ownership of Symbolic Links OSS File Synchronization or directory but did not have WRITE access to the source file set, WRITE access on the destination OSS files is set as follows: • • 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.
Synchronization Options OSS File Synchronization In BIND, issue the following commands: ADD * FROM ASYSYNC ALTER CALLABLE^LOG^DOWN, CALLABLE ON BUILD ASYSYNC! Then, as SUPER.SUPER, issue the following command: FUP LICENSE ASYSYNC Or if synchronizing over TCP/IP: ADD * FROM ASYSYNCP ALTER CALLABLE^LOG^DOWN, CALLABLE ON BUILD ASYSYNCP! Then, as SUPER.SUPER, issue the following command: FUP LICENSE ASYSYNCP Note.
Synchronization Options OSS File Synchronization • • • • • • • • • • OWNER PRI PURGE RATE percentage START hh:mm:ss STOP hh:mm:ss SUSPEND TIMEEX[ACT] TRIGGER TRIGGERONFILESET The following are not applicable to OSS files: • • • • • • • • • • AUTOCREATECATALOG BACKUP CATALOG KEEPNOPURGEUNTIL MAPNAMES MAXBACKUP NETWORKSECURE SUBVOLPURGE USEBINDERTIME ZZINCLUDE The following options are not supported: • • COMPRESS RENAMEOPEN HP AutoSYNC User’s Guide—522580-015 5-8
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 after a complete file set has been successfully synchronized (TRIGGERONFILESET). Overview The TACL command specified as a trigger may invoke a TACL macro, obey a script, or execute a program. An OSS shell command may invoke a script, or execute an OSS program.
Trigger Commands Triggers If command-text calls for a parameter that is specified between quotes, you need to use double quotes (““) to specify the parameter. For example: SYNC myfile TO yourfile, OWNER myID TRIGGER "FUP SECURE yourfile ,""NNNN"" "; TRIGGER Arguments • • • #SYNCFILE is replaced with the destination file that has just been created or replaced by AutoSYNC. For OSS files the absolute pathname is specified. #SOURCEFILE is replaced with the name of the original source file.
Trigger Examples Triggers Trigger Output The TACL trigger command and the output of the TACL or OSS session are captured in the log file: • • For scheduled synchronizations, the log file is the MapDB file SLggguuu. For a one-time synchronization, the user specifies the LOGFILE option in the SYNCHRONIZE command. Note.
Trigger Examples Triggers 3. Accelerate the synchronized object files in subvolume $data.tstobj: SYNC $data.object.* TO \tst.$data.tstobj.*, TRIGGER “AXCEL #SYNCFILE, #SYNCFILE”; 4.
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.
Triggers Note on Triggers that invoke SQLCI HP AutoSYNC User’s Guide—522580-015 6-8
7 Synchronization Over TCP/IP Overview AutoSYNC supports the use of a direct TCP/IP network connection to communicate between the source and destination AutoSYNC processes. Configuration and use of TCP/IP does not interfere with the concurrent use of Expand to synchronize files. A single AutoSYNC installation uses both networks as requested by the user. The advantages of TCP/IP are: • • • You may synchronize files between systems that have the same Expand system name or number.
On both Source and Destination Systems Synchronization Over TCP/IP You can either create a private SERVICES file or update the system SERVICES file (usually $SYSTEM.ZTCPIP.SERVICES) with lines such as ASYSYNC-ZASY /tcp # AutoSYNC and optionally ASYNCLOG-ZASY /tcp # AutoSYNC LOG A private SERVICES file is an edit file located in the same subvolume as the installed ASYMON object file. Refer to $SYSTEM.ZTCPIP.SERVICES for a sample file. Note.
On the Destination System Synchronization Over TCP/IP The ASYNCLOG-ZASY port The AutoSYNC logging port is used on the source system to accept a connection from the destination system. However, the choice of an unpredictable port number is often incompatible with a firewall configuration that only allows selected incoming ports to be accessed. If configured, the logging port number must be distinct from the ASYSYNC-ZASY port number or any other assigned port number on the system.
On the Source System Synchronization Over TCP/IP The syntax to configure TCP/IP names is: ALTER GLOBAL SYNCTCPPROC[ESSES] $ZTC0, $ZTC1,...; You may specify up to 6 processes. The process names together must not exceed 30 characters, not including commas and spaces. 2.
Synchronization over TCP/IP Synchronization Over TCP/IP In this case, the source ASYSYNCP does not directly start the destination synchronization process ASYSYNC. Instead, ASYSYNCP connects to the monitor process on the destination system using a user-configured port. The destination monitor is the LISTNER. The monitor then starts an ASYSYNCP process.
Synchronization over TCP/IP Synchronization Over TCP/IP HP AutoSYNC User’s Guide—522580-015 7-6
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 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. SUSPEND BATCHID Terminates and suspends scheduled synchronization for specified BATCHID.
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-11 for an overview of synchronization.
ADD SYNCFILESET Command Interpreter 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 } { RECOVER[Y] | NO RECOVER[Y] } { RENAMEO[PEN] } { RESTORE restore-program } { SECURE "rwep" } { SQLREDEF } { SUBVOLPURGE } { USERBINDERTIME } { ZZINC[LUDE] } OSS-only-
ADD SYNCFILESET Command Interpreter src-file-set a file set on the local system that is the source of the synchronization operation. If a node name is specified, it must be the local node. dest-file-set the location of the file set that is to be updated. The volume, subvolume, and filename portions of a destination file set must be either asterisk (*) or must be fully specified.
ADD SYNCFILESET Command Interpreter • ° ° the full directory tree with all its subdirectories is synchronized. ° if the source directory is empty or no files were selected for synchronization, an empty directory is created. if the directory tree does not exist at the destination location, the directory is created. Pathnames cannot exceed 128 bytes in length. common-options AUTOSUSPEND specifies that the configured fileset will execute once and then will automatically be suspended.
ADD SYNCFILESET 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, a file on the exclude list is not purged on the destination system, even if other files in the same source subvolume are synchronized. Note that some performance degradation could occur if an exclude file containing a long list of files is shared by multiple syncfilesets.
ADD SYNCFILESET Command Interpreter host-name is the name by which the destination system is known on the internet, specified as a character string of 49 or fewer characters (example: foxii.cac.cpqcorp.net). There is no default value for this option. If HOST is omitted, AutoSYNC performs the synchronization over the Expand link. INTERVAL interval [ MINUTES | HOURS | DAYS ] the frequency at which the destination file set is to be updated. The value of interval is between 1 minute and 366 days.
ADD SYNCFILESET Command Interpreter specifies that a source file that is opened for update is eligible for synchronization. By default, AutoSYNC does not synchronize files that are opened for update. OPENUPDATE overrides the default behavior. interval is the number of seconds, minutes, or hours during which the source file must remain unchanged to be considered for synchronization. The default unit of time is MINUTES.
ADD SYNCFILESET Command Interpreter specifies that any file that is in the destination file set but is not in the source file set will be purged. By default AutoSYNC does not purge any file in the destination file set. 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.
ADD SYNCFILESET Command Interpreter the ending time of the synchronization window. The time is entered in the format hour:minute:seconds between 00:00:00 and 23:59:59. The maximum window is 24 hours. If the stop time is smaller than the start time, then it is assumed the synchronization window crosses into the next day. If STOP is omitted but START is specified, synchronization happens once a day at the specified START time.
ADD SYNCFILESET Command Interpreter ° #SYNCFILE is replaced with the destination file that has been created or replaced by AutoSYNC. For OSS files, the absolute pathname is specified. ° #SOURCEFILE is replaced with the name of the original source file. For OSS files, the absolute pathname is specified. ° #RECOVERFILE is replaced with the name of the file that was recovered by AutoSYNC. If no archive name is found, AUTOSYNC substitutes the placeholder "?" for the file name.
ADD SYNCFILESET Command Interpreter AUTOCREATECAT[ALOG] 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.
ADD SYNCFILESET Command Interpreter KEEPNOPURGEUNTIL is not supported for Enscribe files, consistent with FUP and RESTORE behavior. MAPNAMES mapnames-file specifies the mapping of a source fileset to a destination fileset 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.
ADD SYNCFILESET Command Interpreter See discussion on the use of MAPNAMES in Alternate Key Files on page 3-5, SQL Tables and Catalogs on page 3-6, Partitioned Files and Tables on page 3-7 and File and Catalog Name Mapping using MAPNAMES on page 3-9 MAXBACKUP num-of-files 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.
ADD SYNCFILESET Command Interpreter By default, recovery is enabled. RENAMEO[PEN] specifies that remote 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 remote 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.
ADD SYNCFILESET Command Interpreter By default, AutoSYNC compares only modification timestamps of source and destination SQL tables. Note. A SQL view or index is synchronized automatically with the primary partition of the base table. If the redefinition date of an index or view in the source subvolume is newer than in the destination subvolume but the primary source partition is older than the primary destination partition, the view or index will not be synchronized.
ADD SYNCFILESET Command Interpreter ALLHARDLINKS | NO ALLHARDLINKS synchronizes all files that are hard links in the specified syncfileset, including uncontained heartlands. When synchronizing an uncontained hard link, a new 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.
ADD SYNCUSER Command Interpreter If this option is omitted, the security of the destination file set is the same as that of the source file set. The exception is write security for the owner: when a file or a directory is synchronized and the write access was denied for the owner in the source file, 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.
ADD SYNCUSER Command Interpreter the object file name of the BACKUP program to use on the source system when a file set is synchronized. If BACKUP is omitted, the default $SYSTEM.SYSnn.BACKUP program is used. EMSFILEEVENTS | NO EMSFILEEVENTS specifies that any synchronization error related to a specific file (for example, error 48, error 45, and so on) will be logged in the EMS log.
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 VERIFIEDWRITES | NO VERIFIEDWRITES 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 enables or disables the recovery option. 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 monitor process is restarted. These attributes can also be changed using ALTER MONITOR. ALTER MAPDB subvol { , option... } option is: { BACKUP cpu-number } { HOMETERM [ file-name | NONE ] } { MONITOR monitor-name } { PRIMARY cpu-number } { PRIORITY process-priority } subvol the name of the MapDB subvolume. If this command is used to change the name of the monitor, the current monitor process must first be stopped.
ALTER MONITOR Command Interpreter 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. These attributes can also be changed using ALTER MAPDB. ALTER MONITOR [ process-name ] {, option...
ALTER MONITOR Command Interpreter PRIORITY process-priority a process priority (in the range of 1 to 199) for the monitor process.
ALTER SYNCFILESET Command Interpreter ALTER SYNCFILESET HP AutoSYNC User’s Guide—522580-015 8-34
ALTER SYNCFILESET Command Interpreter 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) { TIMEEX[ACT] | NO TIMEEX[ACT] } { TO file-set } guardian-only-options: { AUDITED | NO AUDITED } { AUTOCREATECAT[ALOG] } { BACKUP backup-program | NO BACKUP } { CATALOG SQL-catalog | NO CATALOG } { COMPRESS | NO COMPRESS } { KEEPNOPURGEUNTIL | NO KEEPNOPURGEUNTIL } { MAPNAMES mapnames-file | NO MAPNAMES } { MAXBACKUP num-of-files | NO MAXBACKUP } { NETWORKS[ECURE] | NO NETWORKS[ECURE] } { NOSAFEGUARD | NO NOSAFEGUARD
ALTER SYNCFILESET Command Interpreter OSS-only-options: { ALLHARDLINKS | NO ALLHARDLINKS } { ALLSYMLINKS | NO ALLSYMLINKS } { OWNERG[ROUP] {{ group-id | group-user } | NO OWNERG[ROUP]} { SECURE “rwxrwxrwx” | NO SECURE } * | 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.
ALTER SYNCFILESET Command Interpreter 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.
ALTER SYNCFILESET Command Interpreter instructs Autosync to (or not 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.
ALTER SYNCFILESET Command Interpreter input file is created only when files are synchronized and the MAPNAMES option is specified. 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] | NO KEEPS[ECURITY] the Guardian security settings "rwep" of the source file are retained on the destination file. KEEPSECURITY overrides the SECURE and NETWORKSECURE options.
ALTER SYNCFILESET Command Interpreter 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 | NO PRI[ORITY] the process priority at which the ASYSYNC process is to run when processing this syncfileset.
ALTER SYNCFILESET Command Interpreter RATE percentage | NO RATE the percentage of elapsed time the synchronization process should be active. The default is 100%. TO file-set the destination the file set that is to be synchronized with the source file set. The destination node may be specified as back slash asterisk (\*) which means that the destination of the synchronization is every node that has AutoSYNC installed, licensed, and running.
ALTER SYNCFILESET Command Interpreter In all cases, the comparison of timestamps accounts for differences in system clocks and time zones.... Note on symbolic links. Because source and destination modification timestamps of symbolic links never match, TIMEEXACT is ignored if specified for symbolic links. For further details on symbolic link synchronization, see paragraph Modification Timestamp of Symbolic Links on page 5-4 Note on SQL Shorthand Views. A SQL view has no modification timestamp.
ALTER SYNCFILESET Command Interpreter The trigger is executed if all files have been synchronized or, if a file error has occurred during the synchronization, or if no files required synchronization. The trigger is not executed if an error other than a file error has occurred and caused the synchronization to fail. The command supports a set built-in arguments.
ALTER SYNCFILESET Command Interpreter This option overrides the BACKUP option specified in the ADD SYNCUSER or ALTER SYNCUSER command. If BACKUP is omitted, $SYSTEM.SYSnn.BACKUP is used. CATALOG SQL-catalog | NO CATALOG where to register SQL objects that are synchronized. If CATALOG is omitted, the source catalog name is used. If the needed catalog does not exist and AUTOCREATECATALOG is not specified, SQL table synchronization fails.
ALTER SYNCFILESET Command Interpreter The file name can be partially qualified; AutoSYNC replaces the missing portion of the name with the wild card asterisk (*). For example: $DATA TO $BACK \NEWYORK.$DATA*.DB TO $BACK.BACKUPDB $DATA*.DB.PARTFILE TO \TOKYO.* Are equivalent to: \SOURCE.$DATA.*.* TO \DEST.$BACK.*.* \NEWYORK.$DATA*.DB.* TO \DEST.$BACK.BACKUPDB.* \SOURCE.$DATA*.DB.PARTFILE TO \TOKYO.*.*.* Catalog name mapping: The information in MAPNAMES is also used to perform SQL catalog volume mapping.
ALTER SYNCFILESET Command Interpreter By default this option is enabled and file security is changed as follows: Source file security Destination file security “A” “N” “G” “C” “O” “U” “-” “-” The default is NETWORKSECURE, but the SECURE option overrides NETWORKSECURE. NOSAFEGUARD | NO NOSAFEGUARD specifies that the Safeguard ACL for a source Enscribe disk file is not propagated to the destination when the file is synchronized.
ALTER SYNCFILESET Command Interpreter in the destination fileset volume. Renamed partitions, alternate indexes and protection views are named ABnnnnnn, ACnnnnnn, and so on. Note. If the destination file is audited, AutoSYNC displays a warning message and the file is not synchronized. An audited file cannot be renamed and AutoSYNC cannot temporarily unaudit the file to rename it because the file is opened. Note.
ALTER SYNCFILESET Command Interpreter USEBINDERTIME | NO USEBINDERTIME selects object files (code 100, 700 and 800 files) for synchronization by comparing the binder or linker timestamps of the source and destination. For all other file types in the fileset, the usual modification timestamp is used. The destination object file is replaced if the binder or linker timestamps of the source and destination do not match exactly; the comparison operates as if TIMEEXACT were specified.
ALTER SYNCFILESET Command Interpreter If NO ALLSYMLINKS is specified, uncontained symbolic links are not synchronized. A warning is written into the log file when an uncontained symbolic link has been skipped. The default is ALLSYMLINKS. OWNERG[ROUP] { group-id | group-user } | NO OWNERG[ROUP] the group ID of the destination file set. 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.
ALTER SYNCUSER Command Interpreter 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... ]; option is: { BACKUP backup-program | NO BACKUP } { CPU { n | ( n1, n2, n3 ...
ALTER SYNCUSER Command Interpreter EMSSUPPRESS | NO EMSSUPPRESS suppresses the generation of a class of EMS events that are considered optional. Suppressing the optional messages reduces the volume of output sent to the EMS collector. The types of messages suppressed are the following: • • Synchronization process START and STOP messages. Messages reporting configuration changes made by the administrator to a file set or a batch ID.
AUTHORIZE Command Interpreter messages, operations such as starting and stopping processes, creating and purging files, opening and closing files, and so on. AUTHORIZE By default, the user that starts the AutoSYNC monitor process authorizes all sync users to perform scheduled synchronizations. Thus, in a multiuser environment, the monitor process must be started by the super user or the group manager (n, 255) of all sync users.
CLEAR AUTOSYNC Command Interpreter integer arithmetic. If any operand contains a decimal point, the expression is evaluated to four decimal places of accuracy. CALC expression; expression is { constant } { expression op const } { ( expression ) } op is { + | – | * | / } constant an ordinary decimal constant with or without a decimal point, or a binary, octal, or hexadecimal integer (prefixed by %b, %, or %h, respectively.
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> } { 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-015 8-56
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-specifier 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. O[CTAL] the output is in octal and ASCII format. D[ECIMAL] the output is in decimal 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 table is to be created.
CREATE SYSDB Command Interpreter The PRIMARY, BACKUP, and PRIORITY, and HOMETERM options specify process creation parameters to be used when starting the monitor process. MONITOR process-name the name of the monitor process to be associated with the MapDB. The name must have 4 characters. The default is $ZASY. See the note below. PRIMARY cpu-number the CPU number (in the range of 0 to 15) of the primary monitor process.
DELAY Command Interpreter If you create SYSDB on a subvolume other than $SYSTEM.ESCSYSDB, then some precautions must be taken, mainly to avoid creating more than one SYSDB, since AUTOSYNC searches all disks for the SYSDB subvolume and issues an error if more than one is found. SECURE “rwep” sets the security of the SYSDB tables. DELAY Suspends the execution of the AutoSYNC command interpreter for the specified interval.
DELETE SYNCUSER Command Interpreter * designates all configured syncfilesets for the syncuser. To display the file set ID’s and BATCHIDs, use INFO SYNCFILESET. DELETE SYNCUSER Removes synchronization authorization defined for a user. DELETE SYNCU[SER] user-id [ ,KEEP ]; user-id the Guardian user ID or user name to remove from the list of users authorized to perform synchronization. KEEP instructs AutoSYNC to retain the configuration files SFggguuu and SLggguuu associated with the user being deleted.
DISABLE AUTOSYNC Command Interpreter an Enscribe queue file, entry-sequenced file, the terminal or $NULL (or equivalent). dequeue-options See command options for COPY on page 8-55. DISABLE AUTOSYNC Instructs AutoSYNC to reject synchronizations originating from the specified system or from all systems. Use the CLEAR AUTOSYNC command to allow synchronization from the disabled source systems. CLEAR AUTOS[YNC] FROM [ \system-name | * ]; \system-name an Expand system name.
FACTOR Command Interpreter FACTOR Accepts any numeric expression and calculates the prime factors of the integer part of the expression. FACTOR constant; constant an ordinary decimal constant with or without a decimal point, or a binary, octal, or hexadecimal integer prefixed by %b, %, or %h, respectively. FC and ! Execute previous commands found in the command history. FC permits a command to be edited before execution, while ! executes a command without editing.
FILES Command Interpreter displays detailed information. If DETAIL is not specified, AUTOSYNC displays one line of information per file in the file-set. FID file-set is equivalent to FILEINFO file-set, DETAIL. FILES Displays the 8-character filename only, for the filename or filename pattern that is supplied. Note that the AUTOSYNC FILES command is not the same as the TACL or FUP FILES commands. FILES file-set; file-set TACL-style file name pattern specifying a collection of files.
HISTORY Command Interpreter is an AUTOSYNC command. Help displays the syntax and description of the command. Multi-word commands are entered with hyphens. For example, to obtain help on ADD SYNCFILESET, type: HELP add-syncfileset; If DETAIL is specified, a description of the command parameters is displayed in addition to the syntax. If EXAMPLES is specified, Help displays examples of the command. If neither DETAIL nor EXAMPLES is specified, Help displays both as possible subtopics.
INFO BATCHID Command Interpreter \system-name an Expand system name. * designates all systems that have this system as a destination. If FROM is omitted, AUTOSYNC displays the remote access control for all systems. 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 GLOBALS Command Interpreter INFO GLOBALS Displays a complete list of the AutoSYNC global parameter values. INFO GLOBALS [, OBEYFORM ]; OBEYFORM displays a list of the ALTER GLOBAL 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 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.
INFO SYNCFILESET Command Interpreter INFO SYNCFILESET Displays the synchronization parameters for one file set or all specified file sets. INFO SYNCF[ILESET] [ fset-range [, fset-range ],...
INFO SYNCUSER Command Interpreter SYSTEM \system-name the name of the destination system for the syncfileset. This option is only required if the destination system was configured using the asterisk (*) in ADD SYNCFILESET or ALTER SYNCFILESET. Otherwise, the option is ignored. If system-name is omitted, the output of the most recent synchronization is displayed. OBEYFORM displays the text of the ADD SYNCF[ILESET] command that was used to configure the attributes for the file set.
LABELDISPLAY (LD) Command Interpreter LABELDISPLAY (LD) Displays label information for the specified table, such as catalog name, audit compression, columns data types, primary and alternate key columns, partitions, allocated extents, and so on. The command can be abbreviated to LD. L[ABEL]D[ISPLAY] sql-table [ ALLP[ARTS] | ALLI[NDEXS] ] sql-table a SQL table or View. ALLP[ARTS] displays the labels of all partitions of the table. ALLI[NDEXES] displays the labels of all indexes of the table.
LIST SYNCPROCESS Command Interpreter displays files opened for write or update access only. LIST SYNCPROCESS Obtains and displays information for all ASYSYNC and ASYSYNCP processes that are running from the current Autosync product subvolume. The synchronization processes listed are source and destination processes. The current product subvolume is the subvolume of the autosync command interpreter on the local system. This command helps to manage the AutoSYNC environment.
LOG Command Interpreter If DETAIL is omitted, the items displayed are: User ID, program file name, and process creation time. MONITOR monitor-name lists the synchronization processes that are running under a specific monitor process. If MONITOR is omitted, all synchronization processes running in the AutoSYNC product subvolume are listed. SOURCE displays the synchronization processes that are running as source synchronization processes.
MONITOR Command Interpreter If oss-pathname is omitted, the root directory is assumed. -a lists all entries in the directory, including the "." (dot) and ".." (dot dot) and other files whose names begin with a ".". -i displays inode number for each file listed. -l 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.
OBEY Command Interpreter OBEY Reads and executes a sequence of AUTOSYNC commands from another device. The commands are executed serially until an end-of-file condition is detected. An OBEY file may not contain an OBEY command. OBEY filename; filename the file containing a sequence of AUTOSYNC commands. OPEN Select a current monitor process and associated MapDB. OPEN process-name; process-name the name of a configured monitor process.
RENAME Command Interpreter RENAME Renames a non audited Enscribe file, like the TACL RENAME command. RENAME old-file , new-file old-file the Enscribe file to rename. new-file 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 filesets 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 this option is not specified and not configured in the MapDB, the monitor process hometerm is set to the system console. The monitor process writes the messages that would normally go to its hometerm to the EMS collector $0 or the collector specified through the EMSCOLLECTOR global parameter. Also, AUTOSYNC prints a warning to this effect. See “ALTER GLOBAL” on page 8-28 for details about the EMSCOLLECTOR global.
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 BATCHID batchid, [, option ]; option is { ACTIVE } { BRIEF } { DETAIL } { SYSTEM system-name } { USER { user-id | user-name } | ALLUSERS } batch-id a batchid number.
STATUS MONITOR Command Interpreter STATUS MONITOR Determines the status of monitor processes by sending them an inquiry message. STATUS MONITOR [ * | process-name | mapdb ]; process-name the process name of the monitor process to be queried. The default is the current monitor process for the session. mapdb a MapDB subvolume. Since each MapDB has an associated monitor process, this option is simply an alternative method to specify the process to be queried.
STATUS SYNCFILESET Command Interpreter displays status information for ASYSYNC processes that are currently in the process of synchronizing file sets. BATCH[ID] batchid displays status information for the synchronization file sets in the specified batchid. The same information can be displayed using STATUS BATCHID. BRIEF displays the synchronization process name, the destination node, the number of active file sets in the batchid and status of the synchronization process.
STATUS SYNCFILESET Command Interpreter The command is functionally equivalent to STATUS SYNC with the FSETID option. STATUS SYNCFILESET fset-id, [, option ]; option is ACTIVE } { BRIEF } { DETAIL } { SYSTEM system-name } { USER { user-id | user-name } | ALLUSERS } fset-id a synchronization file set. ACTIVE displays status information for ASYSYNC processes that are currently in the process of synchronizing file sets.
STOP MONITOR Command Interpreter STOP MONITOR Performs an orderly shutdown of a monitor process. All scheduled synchronizations are stopped. STOP MONITOR [ process-name | mapdb ]; process-name the process name of the monitor process to be stopped. The default is the current monitor process for the session. mapdb a MapDB subvolume. Since each MapDB has an associated monitor process, this is simply an alternative method to specify the process to be stopped.
SUSPEND SYNCFILESET Command Interpreter SUSPEND SYNCFILESET Stops the synchronization for a given file set. The synchronization operations can be resumed by using the ACTIVATE SYNCFILESET command. Active synchronization is stopped after the current file set is synchronized. SUSPEND SYNCF[ILESET] fset-range [, fset-range ] ,...; 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.
SYNCHRONIZE Command Interpreter • • Files starting with ZZ and system swap files, unless ZZINCLUDE is specified Files in subvolumes $vol.ZYQ*, because they are OSS files If an eligible source file has a modification timestamp that is later than the corresponding destination file, the destination file is replaced. Timestamp comparisons account for differences in time zones and system clocks.
SYNCHRONIZE Command Interpreter Section 3, One-time Synchronization discusses synchronization options in greater detail.
SYNCHRONIZE Command Interpreter guardian-option: { 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 } { RECOVER[Y] | NO RECOVER[Y] } { RENAMEO[PEN] } { RESTORE restore-program } { SECURE "rwep" } { SQLREDEF } { SUBVOLPURGE } { USEBINDERTIME } { ZZINC[LUDE] } continued } HP Aut
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 node name is specified, it must be the local node. dest-file-set the location of the file set that is to be updated. The volume, subvolume, and filename portions of a destination file set must be either asterisk (*) or must be fully qualified.
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, a file on the exclude list is not purged on the destination system, even if other files in the same source subvolume are synchronized. Note that some performance degradation could occur if an exclude file containing a long list of files is shared by multiple syncfilesets.
SYNCHRONIZE Command Interpreter host-name is the name by which the destination system is known on the internet, specified as a character string of 49 or fewer characters (example: foxii.cac.cpqcorp.net). There is no default value for this option. If HOST is omitted, AutoSYNC performs the synchronization over the Expand link. 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.
SYNCHRONIZE Command Interpreter specifies that a source file that is opened for update is eligible for synchronization. By default, AutoSYNC does not synchronize files that are opened for update. OPENUPDATE overrides the default behavior. interval is the number of seconds, minutes, or hours during which the source file must remain unchanged to be considered for synchronization. The default unit of time is MINUTES. If interval omitted, the OPENUPDATE interval is 0.
SYNCHRONIZE Command Interpreter ° 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. Catalog files are not supported and they are not synchronized or purged by Autosync.
SYNCHRONIZE Command Interpreter 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. Arguments can be specified in either upper or lower case.
SYNCHRONIZE Command Interpreter ° ° #COUNTNOTBKUP is the number of files not backed up. #COUNTNOTREST is the number of files that were not restored. guardian-options: AUDITED instructs AutoSYNC to synchronize audited files in the file set. The default is to synchronize only non audited files. AUTOCREATECAT[ALOG] 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.
SYNCHRONIZE Command Interpreter specifies that the NOPURGEUNTIL attribute of a source SQL table or alternate index is preserved on the destination. If KEEPNOPURGEUNTIL is specified, no further synchronization of the table or index will be successful until the NOPURGEUNTIL period has elapsed. By default AutoSYNC does NOT propagate the NOPURGEUNTIL attribute to the destination table, to insure that future synchronizations will be possible.
SYNCHRONIZE 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.
SYNCHRONIZE Command Interpreter specifies that the Safeguard ACL for a source Enscribe disk file is not propagated to the destination when the file is synchronized. A warning is 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. RECOVER[Y] | NO RECOVER[Y] enables or disables the recovery option.
SYNCHRONIZE 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. SQLREDEF instructs AutoSYNC to synchronize SQL tables based on differences in the redefinition timestamps, in addition to differences in modified timestamps. This option allows AutoSYNC to be sensitive to certain DML changes performed on SQL tables, such as ADD COLUMN, which do not cause the modification timestamp to change.
SYNCHRONIZE Command Interpreter oss-options: When describing synchronization options for OSS files below, the phrase "uncontained links" refers to files that are hard links or symbolic links that have references to files that reside outside of the synchronization file set. An uncontained hard link is a link to an inode where another link to the same inode resides outside the synchronization file set. An uncontained symbolic link points to a file that resides outside the synchronization file set.
TIME Command Interpreter "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. If this option is omitted, the security of the destination file set is the same as that of the source file set.
UPDATE Command Interpreter UPDATE Modifies field values in records from an Enscribe file. Most of the parameters are identical to COPY.
UPDATE Command Interpreter display-options {, Octal } {, Decimal } {, Hex } {, Ascii } {, BYTEs } {, NO HEAD } 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.
UPDATE Command Interpreter key-value applies only to key-sequenced files and specifies the approximate position of the starting record; key-value is specified as a string or as integer byte values in the range of 0 to 255. The key-value is entered as follows: “[“ { string } [, { string } ] “]” { 0:255 } [ { 0,255 } ] where the integers represent the byte values. To specify a list of strings, enclose each string in quotation marks separated by a comma and enclose the list in square brackets.
UPDATE Command Interpreter tape-options 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. UNLOADIN | NO UNLOADIN (magnetic tapes only) the tape is unloaded (or not unloaded) after the tape has been rewound. The default is UNLOADIN. This also applies to labelled tapes.
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-015 8-114
9 Reporting Function Overview The AutoSYNC REPORT 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. It is also useful to check the results of scheduled or one-time synchronizations.
Output format Reporting Function 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 Newer in des
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.
Output format Reporting Function The following examples show sample reports for a Guardian and a OSS file set, where specifying the PURGE option causes the display of the entry for extra files in the destination: AutoSYNC 1? report sync jo*.* to \yosprd.$data.*.*,purge; Starting SYNCfset $PRPC.JO*.* ($X0YHH) -- Report completed for fileset -- $PRPC.JO*.* to \YOSPRD.$DATA.*.*. --- REPORT completed successfully. Autosync Report 8/24/07 12:16:29.332 Report summary fileset: Source: $PRPC.JO*.
Output format Reporting Function 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.
Output format Reporting Function HP AutoSYNC User’s Guide—522580-015 9-6
A Operations and Management This appendix describes aspects of managing AutoSYNC, presenting the following topics: 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.
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 • 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 • 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.
Migrating the Configuration Database Operations and Management followed, the old primary system will immediately start synchronizing possibly out-ofdate files to the new primary system. To prevent older files on the original primary system from replacing newer files on the current primary system, the user must disable synchronization from the old primary system using the DISABLE AUTOSYNC command:.
Migrating an AutoSYNC Source System Operations and Management On the New Source System 1. Install AutoSYNC as described in Installing AutoSYNC on page 2-1. When creating the new MapDB, use the INFO MAPDB output collected in infom as a reference. 2. Authorize Autosync, using the STATUS MONITOR output collected in infom as a reference. 3.
Migration Steps for an AutoSYNC Destination System Operations and Management • • Validate the new configuration using the INFO GLOBAL, INFO SYNCUSER and INFO SYNCFILESET commands. Proceed with your usual testing suites, using one time syncs, the REPORT command and activating syncfilesets progressively. 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.
Operations and Management Migration Steps for an AutoSYNC Destination System HP AutoSYNC User’s Guide—522580-015 A-18
B Problem Resolution This appendix discusses how to diagnose AutoSYNC problems, how to use the tools and how to report problems.This appendix covers the following topics: Common Security Problems Troubleshooting Tools AUTOSYNC Commands Synchronization Logs AutoSYNC Events in the EMS Log AutoSYNC Tracing Submitting Problems Common Security Problems Security related problems are common when first configuring AutoSYNC and performing synchronizations.
Scheduled Synchronization Problems Problem Resolution Scheduled Synchronization Problems The local 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 • 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. Errors executing triggers • • Verify that the user has sufficient privileges to execute the trigger commands on the destination. Before configuring a trigger, log on as the user on the source system and run the trigger commands from a TACL prompt.
Troubleshooting Tools Problem Resolution Troubleshooting Tools AUTOSYNC Commands Checking the Environment The overall processing environment can be checked using the CI command ENV. It displays the names of the current MapDB and SysDB, along with the Guardian OS RVU, the serial number of the NonStop system, and so on. Checking the Configuration To list the values of system wide parameters, use INFO GLOBALS. To change any global parameter, use ALTER GLOBAL.
Synchronization Logs Problem Resolution • ° ° ° 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. If the synchronization is over TCP/IP, only the source synchronization process opens the log file. The destination synchronization process sends its messages to the source synchronization process.
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.
AutoSYNC Events in the EMS Log Problem Resolution AutoSYNC 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 In both one time and scheduled synchronizations, the output of the trace is written to the synchronization log file. Every operation performed by the sending and receiving ASYSYNC process is recorded in the trace.
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... LOG option ° 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 \REMOTE.$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. In each message description, the following information appears: • • • • • Message number Message text Cause—the condition or error that produced the message Effect—the effect of the condition or error on the system Recovery—the steps required to recover from a reported error Informational messages 100 Monitor initialization Cause. The monitor process is initializing itself. Effect.
Informational messages Error Messages 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. No action is required. 105 Monitor backup failed Cause.
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 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. Correct the configuration information and issue the MONITOR REFRESH NOW command. 200 ASYSYNC log access error Cause. An ASYSYNC process detected an error accessing a SYNC user logfile. Effect. The error number and the nature of the problem is described in the message. Recovery.
Critical event messages Error Messages Critical event messages 402 Monitor intentionally abended Cause. The monitor process has been intentionally abended to produce a saveabend file for problem diagnosis. Effect. The primary monitor process abends. The backup process takes over and continues processing. Recovery. Send the saveabend file to product support. 403 Invalid license Cause. An operation was attempted, but no license for that service has been installed. Effect. The operation is rejected.
Critical event messages Error Messages 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. Report this error to product support. 414 Allocate segment error Cause. Allocation of the extended segment failed. Effect. The process abends. Recovery. The error number is provided in the message.
Critical event messages Error Messages 432 ASYSYNC version mismatch Cause. A local or remote ASYSYNC process detected a version mismatch. The process that failed and the starting process, either the AutoSYNC monitor or the local ASYSYNC process if the remote ASYSYNC process failed, have different versions. Effect. The ASYSYNC process that detected the version mismatch abends. Recovery. Install the same AutoSYNC version on the local and remote systems.
Index A Administrator 4-2 Alternate key files 3-5 ASYSYNC or ASYSYNCP privileged processes 2-8 ASYSYNCP process authorizing 2-7 Authorizer 4-1 AUTOSYNC command interpreter 8-1 AutoSYNC license 2-5, 3-1 B BATCHID 4-5 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-1 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
P Index Destination file set 5-2 empty directory 5-1 hard links 5-3 pathname length 5-1 purging extra destination files 5-2 Source file set 5-2 Symbolic link 5-3 ZASYnnnn name extension 5-2 OSS pathname /E directory 5-1 Ownership Changing in symbolic links 5-6 OSS file sets 5-5 P Partitioned files and tables 3-7 Purging Destination Subvolumes SUBVOLPURGE 3-12 Purging Files in Destination 3-12 Purging Subvolumes in Destination 3-12 R REGISTRY MapDB table A-2 SysDB table A-1 S Scheduling ASYSYNC process
Special Characters Index Special Characters #MAPNAMES built-in argument in triggers #RECOVERFILE buil-tin argument in triggers #SOURCEFILE built-in argument in triggers #SYNCFILE built-in argument in triggers 6-2 6-2 6-2 6-2 HP AutoSYNC User’s Guide—522580-015 Index-3
Special Characters Index HP AutoSYNC User’s Guide—522580-015 Index-4
Content Feedback First Name: __________________ Phone: _____________________ Company: ___________________ Last Name: _________________ e-mail address: ______________ (All contact information fields are required.) If you’re reporting an error or omission, is your issue: Minor: I can continue to work, but eventual resolution is requested. Major: I can continue to work, but prompt resolution is requested. Critical: I cannot continue to work without immediate response.
