Documente Academic
Documente Profesional
Documente Cultură
Using MIMIX
Product conventions.................................................................................................... 9 Menus and commands .......................................................................................... 9 Accessing online help............................................................................................ 9 Publication conventions............................................................................................... 9 Formatting for displays and commands .............................................................. 10 Sources for additional information............................................................................. 11 How to contact us...................................................................................................... 12 Chapter 1 MIMIX overview 13 MIMIX concepts......................................................................................................... 15 MIMIX AutoGuard overview ...................................................................................... 18 Key concepts for MIMIX AutoGuard .................................................................... 18 Auditing overview ................................................................................................ 19 What are MIMIX AutoGuard best practices? ....................................................... 20 How do I get started with MIMIX AutoGuard? ..................................................... 20 New MIMIX installations ................................................................................ 21 MIMIX policies ........................................................................................................... 22 Considerations when choosing policy values ...................................................... 22 When not to use MIMIX AutoGuard .................................................................... 23 Setting policies - general ..................................................................................... 24 To change existing installation policies ......................................................... 24 To change policies for a data group .............................................................. 25 To reset a data group-level policy to use the installation level value............. 25 Disabling MIMIX AutoGuard for data groups using the MIMIX CDP feature ....... 26 Policy descriptions............................................................................................... 27 Policies for recovery during replication...................................................................... 33 Errors handled by automatic database recovery ................................................. 33 Errors handled by automatic object recovery ...................................................... 34 Logging in to MIMIX Availability Manager ................................................................. 37 Your location is remembered .............................................................................. 37 Areas of the window in MIMIX Availability Manager.................................................. 37 Additional navigation and selection aids ............................................................. 39 Other useful tips .................................................................................................. 41 Accessing the MIMIX Main Menu from a 5250 emulator........................................... 42 Working with status 44 Becoming acquainted with status.............................................................................. 45 Status in MIMIX Availability Manager .................................................................. 45 The Enterprise View - your status shortcut.................................................... 45 Status on the navigation bar.......................................................................... 46 Monitoring status with MIMIX Availability Manager ................................................... 48 Checking replication status with MIMIX Availability Manager.............................. 48 Checking audit status with MIMIX Availability Manager ...................................... 48 Checking status of supporting services with MIMIX Availability Manager ........... 49 Monitoring status with MIMIX Availability Status ....................................................... 50 Checking replication status - 5250 emulator ....................................................... 52 Checking audit and notification status - 5250 emulator....................................... 52 Checking for status of supporting services - 5250 emulator ............................... 53 The Work with Data Groups display - 5250 emulator................................................ 54 Problems reflected in the Audits/Recov./Notif. field ............................................ 56
Chapter 2
Problems reflected in the Data Group column .................................................... 56 Resolving problems highlighted in the Data Group column........................... 57 Replication problems reflected in the Source and Target columns ..................... 59 Setting the automatic refresh interval .................................................................. 60 Working with the detailed status of data groups........................................................ 61 Displaying data group detailed status with MIMIX Availability Manager.............. 61 Variations of the Data Group Details - Activity window ................................. 64 Displaying data group detailed status from a 5250 emulator .............................. 64 Merged view .................................................................................................. 65 Object detailed status views .......................................................................... 69 Database detailed status views ..................................................................... 71 Identifying replication processes with backlogs......................................................... 76 Chapter 3 Working with audits and rules 79 What are rules and how they are used by auditing ................................................... 80 Requirements for using audits and rules................................................................... 81 Guidelines and recommendations for auditing .......................................................... 81 Considerations and recommendations for rules .................................................. 82 Replacement variables .................................................................................. 83 Rule-generated messages and notifications ................................................. 84 Where audit status and compliance status is reported.............................................. 85 Working with audits ................................................................................................... 87 Displaying audit status ........................................................................................ 90 Running audits immediately ................................................................................ 91 Ending audits....................................................................................................... 91 Displaying audit level differences ........................................................................ 92 Resolving audit problems - MIMIX Availability Manager ..................................... 93 Resolving audit problems - 5250 emulator .......................................................... 95 Checking the job log of an audit .......................................................................... 96 Working with audit compliance.................................................................................. 98 Determining whether auditing is within compliance........................................... 100 Working with audit schedules.................................................................................. 102 How audits are scheduled automatically ........................................................... 104 Shipped default audit schedules ....................................................................... 104 Considerations for changing audit scheduling................................................... 105 When to run the #DGFE audit ..................................................................... 106 Changing when audits are scheduled ............................................................... 106 Schedule parameter notes .......................................................................... 107 Changing the system where audits are performed............................................ 108 Considerations for using a different job scheduler for audits ............................ 108 Policies for auditing ................................................................................................. 109 Preventing audits from running ......................................................................... 110 To restrict audit activity in an installation based on data group state .......... 110 To restrict audit activity for a specific data group based on its state ........... 111 To disable auditing for an installation .......................................................... 112 To disable auditing for a data group ............................................................ 113 To disable automatic scheduling of an audit ............................................... 113 Running rules and rule groups manually................................................................. 115 Running rules or rule groups from within MIMIX Availability Manager .............. 115 Running rules or rule groups from the Rules window.................................. 115
Running rules or rule groups from the Data Groups window....................... 116 Running rules from the 5250 emulator .............................................................. 116 Running rule groups from the 5250 emulator .................................................... 117 Checking results of a user-defined rule................................................................... 118 Chapter 4 Working with notifications and recoveries 119 What are notifications and recoveries ..................................................................... 119 Displaying notifications............................................................................................ 120 What information is available for notifications ................................................... 121 Detailed information..................................................................................... 122 Options for working with notifications ................................................................ 122 Notifications for newly created objects .................................................................... 124 Displaying recoveries .............................................................................................. 125 What information is available for recoveries...................................................... 126 Detailed information..................................................................................... 127 Options for working with recoveries .................................................................. 127 Orphaned recoveries ......................................................................................... 128 Determining whether a recovery is orphaned.............................................. 128 Removing an orphaned recovery ................................................................ 129 Starting and ending replication 131 Choices when starting replication............................................................................ 133 What is started with the STRMMX command.................................................... 133 Considerations for starting data groups .................................................................. 135 When to clear pending entries and entries in error ........................................... 136 Clear pending and clear error processing ................................................... 136 Clearing pending entries when open commit cycles exist ................................. 139 Checking for open commit cycles................................................................ 139 Resolving open commit cycles to enable a clear pending start................... 140 Setting the audit level when starting a data group ............................................ 140 Choices when ending replication............................................................................. 141 What is ended by the ENDMMX command ....................................................... 142 Ending immediately or controlled ...................................................................... 143 Controlling how long to wait for a controlled end to complete ..................... 144 Ending all or selected processes....................................................................... 144 When to end the RJ link .................................................................................... 144 Considerations for ending data groups ................................................................... 146 Starting MIMIX......................................................................................................... 147 Ending MIMIX.......................................................................................................... 147 Ending with default values................................................................................. 147 Ending by prompting the ENDMMX command.................................................. 148 After you end MIMIX products ........................................................................... 148 STRMMX and ENDMMX messages ....................................................................... 149 Starting selected data group processes .................................................................. 150 Ending selected data group processes ................................................................... 151 Ending a data group in a controlled manner ........................................................... 152 Preparing for a controlled end of a data group .................................................. 152 Performing the controlled end ........................................................................... 152 Confirming the end request completed without problems ................................. 153 What replication processes are started by the STRDG command.......................... 155
Chapter 5
What replication processes are ended by the ENDDG command .......................... 159 Chapter 6 Resolving common replication problems 163 Working with MIMIX managers ............................................................................... 164 Resolving status problems with system and journal managers......................... 164 Starting a system manager or a journal manager ............................................. 165 Ending a system manager or a journal manager .............................................. 165 Working with message queues ............................................................................... 167 Working with the message log ................................................................................ 168 Working with user journal replicated files ................................................................ 170 Working with files in error .................................................................................. 170 Working with journal transactions for files in error....................................... 173 Placing a file on hold ......................................................................................... 174 Ignoring a held file ............................................................................................. 174 Releasing a held file at a synchronization point ................................................ 175 Releasing a held file .......................................................................................... 176 Releasing a held file and clearing entries.......................................................... 176 Correcting file-level errors ................................................................................. 176 Correcting record-level errors............................................................................ 177 Record written in error ................................................................................. 177 Working with tracking entries .................................................................................. 179 Working with tracking entries from MIMIX Availability Manager........................ 179 Accessing the Data Group Details - Activity window ................................... 179 Working with tracking entries from a 5250 emulator ......................................... 180 Accessing the appropriate tracking entry display ........................................ 180 Holding journal entries associated with a tracking entry.............................. 182 Ignoring journal entries associated with a tracking entry............................. 182 Waiting to synchronize and release held journal entries for a tracking entry .... 183 Releasing held journal entries for a tracking entry ...................................... 183 Releasing and clearing held journal entries for a tracking entry.................. 184 Removing a tracking entry........................................................................... 184 Working with objects in error ................................................................................... 185 Using the Work with DG Activity Entries display ............................................... 186 Retrying data group activity entries ................................................................... 188 Retrying a failed data group activity entry ................................................... 188 Determining whether an activity entry is in a delay/retry cycle .......................... 189 Removing data group activity history entries........................................................... 190 Starting, ending, and verifying journaling 191 What objects need to be journaled.......................................................................... 192 Authority requirements for starting journaling.................................................... 193 MIMIX commands for starting journaling................................................................. 194 Journaling for physical files ..................................................................................... 195 Displaying journaling status for physical files .................................................... 195 Starting journaling for physical files ................................................................... 195 Ending journaling for physical files .................................................................... 196 Verifying journaling for physical files ................................................................. 197 Journaling for IFS objects........................................................................................ 198 Displaying journaling status for IFS objects ...................................................... 198
Chapter 7
Starting journaling for IFS objects ..................................................................... 198 Ending journaling for IFS objects ...................................................................... 199 Verifying journaling for IFS objects.................................................................... 200 Journaling for data areas and data queues............................................................. 201 Displaying journaling status for data areas and data queues............................ 201 Starting journaling for data areas and data queues .......................................... 201 Ending journaling for data areas and data queues............................................ 202 Verifying journaling for data areas and data queues ......................................... 203 Chapter 8 Switching 204 About switching ....................................................................................................... 204 MIMIX Model Switch Framework....................................................................... 205 Planned Switch.................................................................................................. 205 Unplanned switch .............................................................................................. 206 Setting policies for switching ............................................................................. 208 Specifying a default switch framework in policies........................................ 208 Setting polices for MIMIX Switch Assistant ................................................. 208 Setting policies for switch compliance for a specific data group.................. 209 Setting policies when MIMIX Switch Assistant is not used.......................... 210 Changing the audit level policy for switching..................................................... 210 Switching using MIMIX Switch Assistant................................................................. 212 Switching from the MIMIX Basic Main Menu........................................................... 212 Switching to the backup system ........................................................................ 213 Synchronizing data and starting MIMIX on the original production system ....... 214 Switching to the production system ................................................................... 214 Determining when the last switch was performed ................................................... 215 Checking the last switch dates from MIMIX Availability Manager ..................... 215 Checking the last switch date from a 5250 emulator......................................... 216 Problems checking switch compliance.................................................................... 216 Performing a data group switch............................................................................... 217 Performing a data group switch from MIMIX Availability Manager .................... 217 Performing a data group switch from a 5250 emulator ..................................... 217 Switch Data Group (SWTDG) command................................................................. 219 Less common operations 221 Starting the TCP/IP server ...................................................................................... 222 Ending the TCP/IP server........................................................................................ 223 Working with objects ............................................................................................... 224 Displaying long object names............................................................................ 224 Considerations for working with long IFS path names ................................ 224 Displaying data group spooled file information.................................................. 224 Viewing status for active file operations .................................................................. 226 Displaying a remote journal link .............................................................................. 227 Displaying status of a remote journal link................................................................ 228 Identifying data groups that use an RJ link ............................................................. 230 Identifying journal definitions used with RJ ............................................................. 231 Disabling and enabling data groups ........................................................................ 232 Procedures for disabling and enabling data groups .......................................... 233 Determining if non-file objects are configured for user journal replication............... 234 Determining how IFS objects are configured .................................................... 234
Chapter 9
Determining how data areas or data queues are configured ............................ 235 Using file identifiers (FIDs) for IFS objects .............................................................. 236 Operating a remote journal link independently........................................................ 237 Starting a remote journal link independently ..................................................... 237 Ending a remote journal link independently ...................................................... 237 Chapter 10 Troubleshooting - where to start 239 Gathering information before reporting a problem .................................................. 241 Obtaining MIMIX and IBM i information from your system ................................ 241 Reducing contention between MIMIX and user applications................................... 242 Data groups cannot be ended ................................................................................. 243 Verifying a communications link for system definitions ........................................... 244 Verifying the communications link for a data group................................................. 245 Verifying all communications links..................................................................... 245 Checking file entry configuration manually.............................................................. 246 Data groups cannot be started ................................................................................ 248 Cannot start or end an RJ link................................................................................. 249 Removing unconfirmed entries to free an RJ link.............................................. 249 RJ link active but data not transferring .................................................................... 250 Errors using target journal defined by RJ link.......................................................... 251 Verifying data group file entries............................................................................... 252 Verifying data group data area entries .................................................................... 252 Verifying key attributes ............................................................................................ 252 Working with data group timestamps ...................................................................... 254 Automatically creating timestamps .................................................................... 254 Creating additional timestamps ......................................................................... 254 Creating timestamps for remote journaling processing ..................................... 255 Deleting timestamps .......................................................................................... 256 Displaying or printing timestamps ..................................................................... 256 Removing journaled changes.................................................................................. 257 Performing journal analysis ..................................................................................... 258 Removing journal analysis entries for a selected file ........................................ 260
Appendix A Interpreting audit results - supporting information 262 Interpreting results for configuration data - #DGFE audit........................................ 263 Interpreting results of audits for record counts and file data ................................... 265 What differences were detected by #FILDTA.................................................... 265 What differences were detected by #MBRRCDCNT ......................................... 267 Interpreting results of audits that compare attributes .............................................. 268 What attribute differences were detected .......................................................... 269 Where was the difference detected................................................................... 271 What attributes were compared ........................................................................ 272 Attributes compared and expected results - #FILATR, #FILATRMBR audits.... 273 Attributes compared and expected results - #OBJATR audit ............................ 278 Attributes compared and expected results - #IFSATR audit ............................. 286 Attributes compared and expected results - #DLOATR audit ........................... 288 Comparison results for journal status and other journal attributes .................... 290 How configured journaling settings are determined .................................... 293 Comparison results for auxiliary storage pool ID (*ASP)................................... 294 Comparison results for user profile status (*USRPRFSTS) .............................. 297
How configured user profile status is determined........................................ 298 Comparison results for user profile password (*PRFPWDIND)......................... 300 302 Appendix B IBM Power Systems operations that affect MIMIX MIMIX procedures when performing an initial program load (IPL) .......................... 302 MIMIX procedures when performing an operating system upgrade........................ 303 Prerequisites for performing an OS upgrade on either system ......................... 304 MIMIX-specific steps for an OS upgrade on the backup system....................... 305 MIMIX-specific steps for an OS upgrade on the production system with switching 307 MIMIX-specific steps for an OS upgrade on the production system without switching............................................................................................................................ 308 MIMIX procedures when upgrading hardware without a disk image change .......... 310 Considerations for performing a hardware system upgrade without a disk image change..................................................................................................................... 310 MIMIX-specific steps for a hardware upgrade without a disk image change..... 311 Hardware upgrade without a disk image change - preliminary steps .......... 311 Hardware upgrade without a disk image change - subsequent steps ......... 312 MIMIX procedures when performing a hardware upgrade with a disk image change... 313 Considerations for performing a hardware system upgrade with a disk image change..................................................................................................................... 313 Handling MIMIX during a system restore ................................................................ 314 Prerequisites for performing a restore of MIMIX ............................................... 314 Index 316
Product conventions
Product conventions
The conventions described here apply to all MIMIX products unless otherwise noted.
Publication conventions
This book uses typography and specialized formatting to help you quickly identify the type of information you are reading. For example, specialized styles and techniques distinguish information you see on a display from information you enter on a display or command line. In text, bold type identifies a new term whereas an underlined word highlights its importance. Notes and Attentions are specialized formatting techniques that are used, respectively, to highlight a fact or to warn you of the potential for damage. The following topics illustrate formatting techniques that may be used in this book.
UPPERCASE
monospace font
Text that you enter into a 5250 emulator command line. In instructions, the conventions of italic and UPPERCASE also apply. Examples showing programming code.
10
The following information may also be helpful if you use advanced journaling: DB2 UDB for iSeries SQL Programming Concepts DB2 Universal Database for iSeries SQL Reference IBM redbook AS/400 Remote Journal Function for High Availability and Data Replication, SG24-5189
11
How to contact us
For contact information, visit our Contact CustomerCare web page. If you are current on maintenance, support for MIMIX products is also available when you log in to Support Central. It is important to include product and version information whenever you report problems. If you use MIMIX Availability Manager, you should also include the version information provided at the bottom of each MIMIX Availability Manager window.
12
CHAPTER 1
MIMIX overview
This book provides operational information and procedures for using MIMIX ha1 and MIMIX ha Lite. For simplicity, this book uses the term MIMIX to refer to the functionality provided by either product unless a more specific name is necessary. MIMIX version 6 provides high availability for your critical data in a production environment on IBM PowerTM Systems through real-time replication of changes. MIMIX continuously captures changes to critical database files and objects on a production system, sends the changes to a backup system, and applies the changes to the appropriate database file or object on the backup system. The backup system stores exact duplicates of the critical database files and objects from the production system. MIMIX uses two replication paths to address different pieces of your replication needs. These paths operate with configurable levels of cooperation or can operate independently. The user journal replication path captures changes to critical files and objects configured for replication through a user journal. When configuring this path, shipped defaults use the remote journaling function of the operating system to simplify sending data to the remote system. In previous versions, MIMIX DB2 Replicator provided this function. The system journal replication path handles replication of critical system objects (such as user profiles, program objects, or spooled files), integrated file system (IFS) objects, and document library object (DLOs) using the system journal. In previous versions MIMIX Object Replicator provided this function.
Configuration choices determine the degree of cooperative processing used between the system journal and user journal replication paths when replicating database files, IFS objects, data areas, and data queues. One common use of MIMIX is to support a hot backup system to which operations can be switched in the event of a planned or unplanned outage. If a production system becomes unavailable, its backup is already prepared for users. In the event of an outage, you can quickly switch users to the backup system where they can continue using their applications. MIMIX captures changes on the backup system for later synchronization with the original production system. When the original production system is brought back online, MIMIX assists you with analysis and synchronization of the database files and other objects. You can view the replicated data on the backup system at any time without affecting productivity. This allows you to generate reports, submit (read-only) batch jobs, or perform backups to tape from the backup system. In addition to real-time backup capability, replicated databases and objects can be used for distributed processing, allowing you to off-load applications to a backup system. Typically MIMIX is used among systems in a network. Simple environments have one production system and one backup system. More complex environments have
13
MIMIX overview
multiple production systems or backup systems. MIMIX can also be used on a single system. MIMIX automatically monitors your replication environment to detect and correct potential problems that could be detrimental to maintaining high availability. MIMIX also provides a means of verifying that the files and objects being replicated are what is defined to your configuration. This can help ensure the integrity of your MIMIX configuration. The topics in this chapter include: MIMIX concepts on page 15 summarizes key concepts that you need to know about MIMIX. MIMIX AutoGuard overview on page 18 describes concepts related to automatic detection and recovery of problems with MIMIX AutoGuard and provides an introduction to auditing. MIMIX policies on page 22 describes polices used by MIMIX and how to set them. Policies for recovery during replication on page 33 identifies the policies associated with automatic error detection and correction during replication and identifies the common object and file error situations that can be automatically recovered. Logging in to MIMIX Availability Manager on page 37 describes what to expect the first time you log in to MIMIX Availability Manager. Areas of the window in MIMIX Availability Manager on page 37 describes the layout of the MIMIX Availability Manager window, what each area is for, and useful tips for working with this user interface. Accessing the MIMIX Main Menu from a 5250 emulator on page 42 describes the MIMIX Basic Main menu and the MIMIX Intermediate Main Menu. The MIMIX Basic Main menu is used to access the MIMIX Availability Status (WRKMMXSTS) display.
14
MIMIX concepts
MIMIX concepts
The basic concepts associated with MIMIX are identified below. More detailed information is available in the MIMIX Reference book. MIMIX installation - The network of IBM PowerTM Systems systems that transfer data and objects among each other using functions of a common MIMIX product. A MIMIX installation is defined by the way in which you configure the MIMIX product for each of the participating systems. A system can participate in multiple independent MIMIX installations. MIMIX Availability Manager - This browser-based user interface to MIMIX supports operational tasks with significant improvements over their 5250 emulator equivalents. With MIMIX Availability Manager, you are guided directly to the highest severity problem in an installation and presented with suggested resolutions for each unique problem. MIMIX AutoGuard - This set of functions within MIMIX provide the ability to automatically detect and correct problems in a MIMIX installation during replication processes and during automatically scheduled audits. Additional concepts associated with MIMIX AutoGuard are described in Key concepts for MIMIX AutoGuard on page 18. Replication path - A replication path is a series of processes used for replication that represent the critical path on which data to be replicated moves from its origin to its destination. MIMIX uses two replication paths to accommodate differences in how replication occurs for user journal and system journal entries. These paths operate with configurable levels of cooperation or can operate independently. Data group - A MIMIX construct that is used to control replication activities. A data group is a logical grouping of database files, data areas, objects, IFS objects, DLOs, or a combination thereof that defines a unit of work by which MIMIX replication activity is controlled. A data group may represent an application, a set of one or more libraries, or all of the critical data on a given system. Application environments may define a data group as a specific set of files and objects. Data group entries - A data group entry is a configuration construct that identifies a source of information to be replicated by or excluded from replication by a data group. Each entry identifies at least one object and its location on the source system. Classes of data group entries are based on object type. MIMIX uses data group entries to determine whether a journal entry should be replicated. Data groups that replicate from both the system journal and a user journal can have any combination of data group entries. Tracking entries - Tracking entries identify objects that can be replicated using advanced journaling techniques and assist with tracking the status of their replication. A unique tracking entry is associated with each IFS object, data area, and data queue that is eligible for replication using advanced journaling. IFS tracking entries identify eligible, existing IFS objects while object tracking entries identify eligible, existing data areas and data queues. Definitions - MIMIX uses several types of named definitions to identify related configuration choices.
15
System definitions identify a systems that participate in a MIMIX installation. Each system definition identifies one system. Transfer definitions identify the communications path and protocol to be used between systems. Journal definitions identify journaling environments that MIMIX uses for replication Each journal definition identifies a system and characteristics of the journaling environment on that system. Data group definitions identify the characteristics of how replication occurs between two systems. Each data group definition determines the direction in which replication occurs between the systems, whether that direction can be switched, and the default processing characteristics for replication processes.
Remote journal link (RJ link) - An RJ link is a MIMIX configuration element that identifies an IBM i remote journaling environment used by user journal replication processes. An RJ link identifies the journal definitions that define the source and target journals, primary and secondary transfer definitions for the communications path used by MIMIX, and whether the IBM i remote journal function sends journal entries asynchronously or synchronously. System manager - The system manager is a pair of communications jobs between the management system and a network system which must be active to enable replication. The system manager monitors for configuration changes and automatically moves any configuration changes to the network system. Dynamic status changes are also collected and returned to the management system. The system manager also gathers messages and timestamp information from the network system and places them in a message log and timestamp file on the management system. In addition, the system manager performs periodic maintenance tasks, including cleanup of the system and data group history files. Journal manager - The journal manager is a job on each system that MIMIX uses to maintain the journaling environment on that system. By default, MIMIX performs both change management and delete management for journal receivers used by the replication process. MIMIX Model Switch Framework - The MIMIX Model Switch Framework is a set of programs and commands that are designed to provide a consistent framework to be used when performing planned or unplanned switches. Typically, a model switch framework is customized to your environment through its exit programs. MIMIX Switch Assistant uses your model switch framework to perform switching MIMIX Switch Assistant - Available within MIMIX Availability Manager, the MIMIX Switch Assistant is a guided user interface that guides you through switching using your default MIMIX Model Switch Framework. Production system and backup system - These terms describe the role of a system relative to the way applications are used on that system. A production system is the system currently running the production workload for the applications. In normal operations, the production system is the system on which the principal copy of the data and objects associated with the application exist. A backup system is the system that is not currently running the production workload for the applications. In normal operations, the backup system is the system on which you maintain a copy of the data
16
MIMIX concepts
and objects associated with the application. These roles are not always associated with a specific system. For example, if you switch application processing to the backup system, the backup system temporarily becomes the production system. Typically, for normal operations in basic two-system environment, replicated data flows from the system running the production workload to the backup system. Source system and target system - These terms identify the direction in which an activity occurs between two participating systems. A source system is the system from which MIMIX replication activity between two systems originates. In replication, the source system contains the journal entries. Information from the journal entries is either replicated to the target system or used to identify objects to be replicated to the target system. A target system is the system on which MIMIX replication activity between two systems completes. Management system and network system - These terms define the role of a system relative to how the products interact within a MIMIX installation. These roles remain associated with the system within the MIMIX installation to which they are defined. One system in the MIMIX installation is designated as the management system and the remaining one or more systems are designated as network systems. A management system is the system in a MIMIX installation that is designated as the control point for all installations of the product within the MIMIX installation. The management system is the location from which work to be performed by the product is defined and maintained. Often the system defined as the management system also serves as the backup system during normal operations. A network system is any system in a MIMIX installation that is not designated as the management system (control point) of that MIMIX installation. Work definitions are automatically distributed from the management system to a network system. Often a system defined as a network system also serves as the production system during normal operations. Journal - An IBM i system object that identifies the objects being journaled and the journal receivers associated with the journal. The system journal is a specialized journal on the system which MIMIX uses. Journaling and object auditing - Journaling and object auditing are techniques that allow object activity to be logged to a journal. Journaling logs activity for selected objects of specific object types to a user journal. Object auditing logs activity for all objects to the security audit journal (QAUDJRN, the system journal), including those defined to a user journal. MIMIX relies on these techniques and the entries placed in the journal receivers for replicating logged activity. Journal receiver - An IBM i system object that is associated with a journal and contains the log of all activity for objects defined to the journal. Journal entry - A record added to a journal receiver that identifies an event that occurred on a journaled object. MIMIX uses file and record level journal entries to recreate the object on a designated system. Log space - A MIMIX object that provides an efficient storage and manipulation mechanism for replicated data that is temporarily stored on the target system during the receive and apply processes.
17
18
Compliance - Compliance is an indication of whether best practices are being followed in the MIMIX environment. Compliance is checked for auditing and for switching. MIMIX determines compliance by verifying whether successfully completed audits or regular switches occur within a time range defined in policies. The default policy values are set at what is considered the best practice for maintaining switchreadiness. Policies - A policy is a mechanism used to enable, disable, or provide input to a function such as replication, MIMIX AutoGuard, or MIMIX Switch Assistant. For most policies, the initially shipped values apply to an installation. However, policies can be changed and can also be overridden for individual data groups. Some policies, such as audit schedule, apply only to individual data groups. Notifications - Notifications are a secondary mechanism used to report when the activities performed by MIMIX AutoGuard complete or end in error. (The primary mechanism is to report errors through replication processes and the audit summary.) Shipped values for policies result in notifications for successful completion of audits. Through policies, you have options for controlling whether successful recoveries send notifications and for controlling the severity level of notifications used to report MIMIX rules ending in error. Recoveries - The term recovery is used in two ways. The most common use refers to the recovery action taken by MIMIX AutoGuard to correct a detected difference when automatic recovery polices are enabled. The second use refers to a temporary report that provides details about a recovery action in progress that is created when the recovery action starts and is removed when it completes.
Auditing overview
Multiple audits exist for each data group. Each audit identifies a data group to be checked and the MIMIX rule used to check it. MIMIX rules are the mechanism by which audits are defined and invoked. Each shipped MIMIX rule pre-defines a compare command to be invoked and the possible actions that can be initiated, if needed, to correct detected problems. MIMIX ships with default scheduling information associated with each MIMIX rule. MIMIX uses this scheduling information to automatically schedule audit requests on a regular basis. Scheduling can be adjusted for individual audits through policies. When MIMIX submits an audit request, a job is run on both systems associated with the data group being checked. MIMIX first checks the Run rule on system policy to determine where the audit should run and immediately ends the request that is not on the appropriate system. The process of auditing consists of a compare phase and a recovery phase. In the compare phase of an audit, the identified MIMIX rule initiates a specific compare command against the data group. The audit level policy determines how aggressively an audit checks your environment during its compare phase. Each MIMIX rule has the capability of providing multiple audit levels. If a MIMIX rule provides more than one audit level, each level provides increasingly more checking
19
capability.Through policies, you have control over the audit level used for rules that provide more than one level. If there are detected differences when the compare phase completes, the audit enters its recovery phase to start automatic recovery actions as needed. MIMIX attempts to correct the differences and sends generated reports, called recoveries, to the user interface. MIMIX removes these generated reports when the recovery action completes successfully. If the recovery job fails to correct the problem, MIMIX removes the recovery and sends an error notification to the user interface. Most MIMIX rules support a recovery phase. MIMIX is shipped with defaults that enable audits to enter the recovery phase automatically when needed.The recovery phase can be optionally disabled. The information available about each audit identifies the status of actions performed by its MIMIX rule, its compliance status, policy values which affect the actions of each phase, and scheduling information. When a phase completes, its timestamps and statistics are also available. When audit recoveries are enabled, you can specify the severity level of the notifications that are returned when the rule ends in error. This is controlled by the Notification severity policy. You can also view job logs associated with notifications and recoveries. Job logs are accessible from the system on which the audit comparison or recovery job ran.
20
turn starts a job that automatically schedules and submits audits a regular basis. The Start MIMIX command also starts replication processes, which invoke recovery processes as needed.
21
MIMIX policies
MIMIX policies control whether functions provided by MIMIX AutoGuard and MIMIX Switch Assistant are enabled and specify when and how you are notified about problems that may occur. The shipped default settings for policies apply to all systems and data groups within an installation. With the Set MIMIX Policy (SETMMXPCY) command, you can change the values in effect for the installation as well as specify policies for an individual data group. When a policy is set for a data group, it takes precedence over the installation policy. Policies must be changed from the management system. Changing policies requires that you have management-level authority to the Set MIMIX Policy (SETMMXPCY) command. When policies apply to an area in MIMIX Availability Manager, an option to change them is available as an action. From a 5250 emulator, you can set policies from a command line or from the Work with Audits, the MIMIX Availability Status, and the Work with DG Definitions displays.
22
MIMIX policies
opposite direction. For example, data groups AB and BA are configured for bidirectional replication between system A and system B. Data group AB replicates from system A to system B and data group BA replicates the opposite direction. System B is also the management system for this installation. You chose system A as the winning system and want to permit auditing in the direction from A to B. The Audit level policy for data group AB must be set to a level that permits audits to run (level 10 or higher). The Audit level policy for data group BA must be set to disable audits. The results of audits of data group AB will be available on system B, because system B is the management system and default policy values cause rules to be run from the management system. In environments with three or more systems in the same installation, you need to evaluate each pair of systems. For each pair of systems, evaluate the directions in which replication is permitted. If any pair of systems supports simultaneous bidirectional replication, determine the winning system in each pair and determine the direction to be audited. Set the audit level policy to permit auditing for the data group that replicates in the chosen direction. Disable auditing for the data group which replicates in the other direction. You may also want to consider changing the values of the Run rule on system policy for the installation or the audited data groups to balance processing loads associated with auditing. In environments that permit multiple management systems in the same installation, in addition to evaluating the direction of replication permitted within each pair of systems, you must also consider whether the systems defined by each data group are both management systems. If any pair of systems supports simultaneous bi-directional replication, choose the winning system and change the Audit level policies for each data group so that only one direction is audited. You may need to change the Run rule on system policy to prevent certain data groups from being audited from specific management systems.
23
Applications - At times, data groups for some applications will encounter problems if the application cannot acquire locks on objects that are defined to MIMIX. These data groups may need to be excluded from auditing. MIMIX acquires locks occasionally to save and restore objects within the replication environment. Some applications may fail when they cannot acquire a lock on an object. Refer to our Support Central for FAQs that list specific applications whose data groups should be excluded from auditing. For those excluded data groups, you can still run compares to determine if objects are not synchronized between source and target systems. Care must be taken to recover from these unsynchronized conditions.The applications may need to be ended prior to manually synchronizing the objects. To exclude a data group from audits, use the instructions in Disabling MIMIX AutoGuard for data groups using the MIMIX CDP feature on page 26.
2. You will see Installation Policy near the top of the window. The current values of policies are displayed. Specify a value for the policy you want to change. 3. To accept the changes, click OK. From a 5250 emulator, do the following from the management system: 1. From the command line type SETMMXPCY and press F4 (Prompt). 2. Verify that the value specified for Data group definition is *INST.
24
MIMIX policies
3. Press Enter to see all the policies and their current values. 4. Specify a value for the policy you want. Use F1 (Help) to view descriptions of possible values. 5. To accept the changes, press Enter.
2. The selected data group is listed near the top of the window and current values of its policies are displayed. Select a value for the policy you want to change. 3. To accept the changes, click OK. From a 5250 emulator, do the following from the management system: 1. From the command line type SETMMXPCY and press F4 (Prompt). 2. For the Data group definition, specify the full three-part name. 3. Press Enter to see all the policies and their current values. 4. Specify a value for the policy you want defined for the data group. Use F1 (Help) to view descriptions of possible values. 5. To accept the changes, press Enter.
2. The selected data group is listed near the top of the window and current values of its policies are displayed. For the policy you want to change, select Use installation default. 3. To accept the changes, click OK. From a 5250 emulator, do the following from the management system: 1. From the command line type SETMMXPCY and press F4 (Prompt). 2. For the Data group definition, specify the full three-part name. 3. Press Enter to see all the policies and their current values. 4. For the policy you want to reset, specify *INST. 5. To accept the changes, press Enter.
25
Disabling MIMIX AutoGuard for data groups using the MIMIX CDP feature
The functions provided by the MIMIX CDP feature1 create an environment in which source system changes have been transferred to the target system but have not been applied. Any data group which uses this feature must disable automatic comparisons and automatic recovery actions for the data group From MIMIX Availability Manager, the action to change policies for a data group is only available when the system you are viewing is the management system. Do the following: 1. Ensure that you have the management system selected in the navigation bar. If you are not certain which system is the management system, you can select Services to check. 2. Select Data Groups from the navigation bar. From the list of data groups, select the data group that uses the MIMIX CDP feature. 3. From within the Summary area, select the Change Policies action and click .
4. Verify that the expected data group is listed near the top of the window. If you see Installation Policy, close the window and start again. 5. For Automatic system journal recovery, select Disable. 6. For Automatic user journal recovery, select Disable. 7. For Automatic audit recovery, select Disable. 8. For Audit level, select Disable. 9. To accept the changes, click OK. From a 5250 emulator, do the following from the management system: 1. From the command line type SETMMXPCY and press F4 (Prompt). 2. For the Data group definition, specify the full three-part name of the data group that uses the MIMIX CDP feature. 3. Press Enter to see all the policies and their current values. 4. For Automatic object recovery, specify *DISABLED. 5. For Automatic database recovery, specify *DISABLED. 6. For Automatic audit recovery, specify *DISABLED. 7. For Audit level, select *DISABLED. 8. To accept the changes, press Enter.
26
Policy descriptions
There are minor differences in the names of policies between MIMIX Availability Manager and the 5250 emulator. The names shown here are those used in MIMIX Availability Manager. For a complete description of all policy values, see online help for the command. Data group definition - Select the scope of the policies to be set. When the value *INST is specified, the policies being set by the command apply to all systems and data groups in the installation, with the exception of any policy for which a data grouplevel override exists. When a three-part qualified name of a data group is specified, the policies being set by the command apply to only that data group and override the installation-level policy values. Audit rule - Select the MIMIX rule for which an audit schedule will be set for the specified data group definition. The Audit schedule policy determines when this rule will audit the data group. The audit rule must specify the value *NONE when changing any policy except the audit schedule. Automatic system journal recovery - Select whether to enable functions that automatically check for common object errors that occur during replication from the system journal and automatically start recovery actions to correct detected errors. Automatic user journal recovery - Select whether to enable functions that automatically check for common file errors that occur during replication from the user journal and automatically start recovery actions to correct detected errors. Automatic audit recovery - Select whether to enable audits to start automatically recovery actions to correct differences detected during their compare phase. System journal recovery notify on success - Select whether automatic object recovery actions send an informational (*INFO) notification upon successful completion. This policy is only valid when the Automatic system journal recovery policy is enabled. User journal recovery notify on success - Select whether automatic database recovery actions send an informational (*INFO) notification upon successful completion. This policy is only valid when the Automatic user journal recovery policy is enabled. Audit notify on success - Select whether activity initiated by audits, including recovery actions, should automatically send an informational (*INFO) notification upon successful completion. If an audit is run when the Automatic audit recovery policy is disabled, successful notifications are sent only for the compare phase of the audit. Notification severity - Select the severity level of the notifications sent when a rule ends in error. This policy determines the severity of the notification that is sent, not the severity of the error itself. The policy is in effect whether the rule is invoked manually or automatically. This policy is useful for setting up an order precedence for notifications at the data group level. For example, if you set this policy for data group CRITICAL to be *ERROR when the value for the installation-level policy is *WARNING, any error
27
notifications sent from data group CRITICAL will have a higher severity than those from other data groups. Object only on target action - Select how the recovery action for specific audits should handle objects that are configured for replication but exist only on the target system. The following rules check for the only-on-target error: #OBJATR, #IFSATR, #DLOATR, #FILATR, and #FILATRMBR. When the Automatic audit recovery (AUDRCY) policy is enabled, these rules use the value from this policy to attempt recovery for this error. See Considerations when choosing policy values on page 22 for additional information. Journaling attribute difference action - Specify the recovery action to take for scenarios in which audits have detected differences between the actual and configured values of journaling attributes for objects journaled to a user journal. This type of difference can occur for the Journal Images attribute and the Journal Omit Open/Close attribute. Differences found on either the source or target object are affected by this policy. MIMIX configured higher - Specify the recovery for correcting a difference in which the MIMIX configuration specifies an attribute value that results in a higher number of journal transactions than the object's journaling attribute. MIMIX configured lower - Specify the recovery action for correcting a difference in which the MIMIX configuration specifies an attribute value that results in a lower number of journal transactions than the object's journaling attribute. User journal apply threshold action - Select what action to pass to the Compare File Data (CMPFILDTA) command or the Compare Record Count (CMPRCDCNT) command when it is invoked with *DFT specified for its DB apply threshold (DBAPYTHLD) parameter. The commands parameter determines what to do if the database apply session backlog exceeds the threshold warning value configured for the database apply process. This policy applies whenever these commands are used and the backlog exceeds the threshold. The shipped default for this policy causes the requested command to end and may cause the loss of repairs in progress or inaccurate counts for members. You can also set this policy to allow the request to continue despite the exceeded threshold. Maximum rule runtime - Select a value or specify the maximum number of minutes a MIMIX rule can run when the Automatic audit recovery policy is enabled. When the time elapsed since the rule started exceeds the value specified, any recovery actions in progress will end. The compare phase of the rule is always allowed to complete regardless of this policys value. The shipped default for this policy of 1440 minutes (24 hours) prevents running multiple instances of the same MIMIX rule within the same day. Valid values are 60 minutes through 10080 minutes (1 week). The time is checked when the audit starts, when the recovery phase starts, and periodically during the recovery phase. Audit warning threshold - Select a value or specify how many days can elapse after an audit was last performed before an indicator is set. When the number of days that have elapsed exceeds the threshold, the indicator is set to inform you that auditing needs your attention. The shipped default value of 7 days is at the limit of best practices for auditing.
28
In MIMIX Availability Manager, this indicator appears as an Attention icon next to Compliance in the Details section of the navigation bar and next to the audit in the Audit Compliance window. In the 5250 emulator, the indicator appears as the Audits and notifications activity on the MIMIX Availability Status (WRKMMXSTS) window. Note: It is recommended that you set this value to match the frequency with which you perform audits. It is possible for an audit to be prevented from running for several days due to environmental conditions or the Action for running audit policy. You may not notice that the audit did not run when expected until the Audit warning threshold is exceeded, potentially several days later. If you run all audits daily, specify 1 for the Audit warning threshold policy. If you do not run audits daily, set the value to what makes sense in your MIMIX environment. For example, if you run the #FILDTA audit once a week and run all other audits daily, the default value of 7 would cause all audits except #FILDTA to have exposure indicated. The value 1 would be appropriate for the daily audits but the #FILDTA audit would be identified as approaching out of compliance much of the time. Audit action threshold - Select a value or specify how many days can elapse after an audit was last performed before an indicator is set. When the number of days that have elapsed exceeds the threshold, the indicator is set to inform you that action is required because the audit is out of compliance. The shipped default of 14 days is the suggested value for this threshold, which is 7 days beyond the limit of best practices for auditing. In MIMIX Availability Manager, this indicator appears as an Action Required icon next to Compliance in the Details section of the navigation bar and next to the audit in the Audit Compliance window. In the 5250 emulator, the indicator appears as the Audits and notifications activity on the WRKMMXSTS window. Note: It is recommended that you set this value to match the frequency with which you perform audits. It is possible for an audit to be prevented from running for several days due to environmental conditions or the Action for running audit policy. You may not notice that the audit did not run when expected until the Audit action threshold is exceeded, potentially several days later. If you run all audits daily, specify 1 for the Audit action threshold policy. If you do not run audits daily, set the value to what makes sense in your MIMIX environment. For example, if you run the #FILDTA audit once a week and run all other audits daily, the default value of 14 would cause all audits except #FILDTA to have exposure indicated. The value 2 would be appropriate for the daily audits but the #FILDTA audit would be identified as approaching out of compliance much of the time. Audit level - Select the level of comparison that an audit will perform when a MIMIX rule which supports multiple levels is invoked against a data group. The policy is in effect regardless of how the rule is invoked. The amount of checking performed increases with the level number. This policy makes it easy to change the level of audit performed without changing the audit scheduling or rules. No auditing is performed if this policy is set to *DISABLED. Note: Best practice is to use level 30 to perform the most extensive audit. If you use a lower level, consider its effect on how often you need to be certain that data
29
is synchronized between source and target systems. For additional information, see Changing the audit level policy for switching on page 210. Run rule on system - Select the system on which to run audits. This policy is used when audits are invoked with *YES specified for the value of the Use run rule on system policy (USERULESYS) parameter on the Run Rule (RUNRULE) or Run Rule Group (RUNRULEGRP) command. When *YES is specified in these commands, this policy determines the system on which to run audits. The policys shipped default is to run audits from the management system. You can also set the policy to run audits from the network system, the source or target system, or from a list of system definitions. When both systems of a data group are in the specified list, the target system is used. While this policy is intended for audits, any rule that meets the same criteria will use this policy. Action for running audits - Select a value for each condition1. This policy determines the type of audit actions permitted when certain conditions exist in the data group. If a condition exists at the time of an audit request, audit activity is restricted to the specified action. If multiple conditions exist and the values specified are different, only the most restrictive of the specified actions is allowed. If none of the conditions are present, the audit requests are performed according to other policy values in effect. Inactive data group - Specify the type of auditing actions allowed when any replication process required by the data group is inactive. For example, a data group of TYPE(*ALL) is considered inactive if any of its database or object replication processes is in a state other than active. Apply in threshold - Specify the type of auditing actions allowed when any of the database apply or object apply processes used by the data group have reached their configured warning threshold. Synchronize threshold size - Select a value or specify the threshold, in megabytes (MB), to use for preventing the synchronization of large objects during recovery actions. When any of the Automatic system journal recovery, Automatic user journal recovery, or Automatic audit recovery policies are enabled, all initiated recovery actions use this policy value for the corresponding synchronize command's Maximum sending size (MB) parameter. This policy is useful for preventing performance issues when synchronizing large objects. Number of third delay retry attempts - Select a value or specify the number of times to retry a process during the third delay/retry interval. This policy is used when the Automatic system journal recovery policy is enabled. Object replication processes use this policy value when attempting recovery of an in-use condition that persists after the data groups configured values for the first and second delay/retry intervals are exhausted. The shipped default is 100 attempts. This policy and its related policy, Third delay retry interval, can be disabled so that object replication does not attempt the third delay/retry interval but still allow recoveries for other errors. Third delay retry interval - Select a value or specify the delay time (in minutes) before retrying a process in the third delay/retry interval. This policy is used when the
1. Users will see this policy only on systems running version 5 service pack 5.0.06.00 or higher.
30
Automatic system journal recovery policy is enabled. Object replication processes use this policy value when attempting recovery of an in-use condition that persists after the data groups configured values for the first and second delay/retry intervals are exhausted. The shipped default is 15 minutes. Switch warning threshold - Select a value or specify how many days can elapse after the last switch was performed before an indicator is set for the installation. When the number of days that have elapsed exceeds this threshold, the indicator is set to inform you that switching may need your attention. In MIMIX Availability Manager, an icon appears next to Switching in the Details area of the navigation bar and next to the Last switch date field on the MIMIX Switch Assistant window. In the 5250 emulator, the indicator appears as the Last switch field on the WRKMMXSTS window. The shipped default is 90 days, which is considered at the limit of best practices for switching. Switch action threshold - Select a value or specify how many days can elapse after the last switch was performed before an indicator is set for the installation. When the number of days that have elapsed exceeds this threshold, the indicator is set to inform you that action is required. In MIMIX Availability Manager, an icon appears next to Switching in the Details area of the navigation bar and next to the Last switch date field on the MIMIX Switch Assistant window. In the 5250 emulator, the indicator appears as the Last switch field on the WRKMMXSTS window. The shipped default of 180 days is the suggested value for this threshold, which beyond the limit of best practices for switching. Default model switch framework - Select a value or specify the default MIMIX Model Switch Framework to use for switching. This value is used by MIMIX Switch Assistant from within MIMIX Availability Manager or from the MIMIX ha Lite Main Menu (option 5). The shipped default value is MXMSFDFT, which is the default model switch framework name for the installation. If the default name is not being used, this value should be changed to the name of the MIMIX Model Switch Framework used to switch the installation. Independent ASP library ratio - Select a value or specify a number for n in a ratio (n:1) of independent ASP libraries (n) on the production system to SYSBAS libraries on the backup system1. For each switchable independent ASP defined to MIMIX by a device resource group, a monitor with the same name as the resource group checks this ratio. When the number of independent ASP libraries falls to a level that is below the specified ratio, the monitor sends a notification to inform you that action may be required. This signals that your recovery time objective could be in jeopardy because of a prolonged independent ASP switch time. CMPRCDCNT commit threshold - Select a value or specify a number that identifies the threshold at which a request to compare record counts (CMPRCDCNT command or #MBRRCDCNT audit) will not perform the comparison due to commit cycle activity on the source system2. The value specified is the maximum number of uncommitted record operations that can exist for files waiting to be applied at the time the compare request is invoked. Each database apply session is evaluated against the threshold
1. The library ratio monitor and the policy it uses require an access code for the MIMIX Cluster product. 2. Users will see this policy only on systems running version 5 service pack 5.0.14.00 or higher.
31
independently. As a result, it is possible that record counts will be compared for files in one apply session but will not be compared for files in another apply session. For additional information see the MIMIX Reference book. Audit schedule - Select the scheduling information that MIMIX uses to automatically submit audit requests for the specified data group and rule. In order to be scheduled, a value other than *NONE must be specified for Frequency, and values must be specified for Scheduled time and either Scheduled date or Scheduled day. Scheduled dates are entered and displayed in job date format. When the job date format is Julian, the equivalent month and day are used to determine when to schedule audit requests. For detailed information about this policy, see Working with audit schedules on page 102.
32
MIMIX AutoGuard Object Replication Yes Yes2 Yes Yes Yes Yes Database Replication Yes Yes2 Yes Yes
Data Groups Name1 *INST1 *INST *INST *INST *INST *INST *INST
A data group definition value of *INST indicates the policy is installation-wide. A name indicates the policies are in effect only for the specified data group. When this policy is enabled, the other policies in the same column are in effect unless otherwise noted.
When automatic recovery policies are enabled, MIMIX will attempt to recover errors it detects during the replication process. The following topics identify what errors can be recovered in this way: Errors handled by automatic database recovery on page 33 Errors handled by automatic object recovery on page 34
33
The recovery action also sends a report of a recovery in progress to the user interface. In MIMIX Availability Manager, these reports are located on the Recoveries page. In a 5250 emulator, the reports are on the Work with Recoveries display (WRKRCY command). When the recovery action completes, the report is removed. The DB rcy. notify on success policy determines whether a successful recovery generates an informational notification. Only when all recovery options are exhausted without success is a file placed in hold error (*HLDERR) status. Recovery actions that end in an error do not generate a separate error notification because the error is already reflected in MIMIX status.
Table 3. Error File level errors - and Unique-key record level error Record level errors Errors detected and corrected during database replication when automatic database recovery is enabled. Description Typically invoked when there is a missing library, file, or member. Also invoked when an attempt to write a record to a file results in a unique key violation. Without database autonomics, these conditions result in the file being placed in *HLDERR status. Invoked when the database apply process detects a data-level issue while processing record-level transactions. Without database autonomics, any configured collision resolution methods may attempt to correct the error. Otherwise, these conditions result in the file being placed in *HLDERR status. Invoked during the priming of IFS tracking entries when replicated IFS objects are determined to be missing from the target system. Priming of tracking entries occurs when a data group is started after a configuration change or when the request to start a data group specifies to clear pending entries. Invoked during the priming of object tracking entries when replicated data area and data queue objects are determined to be missing from the target system. Priming of tracking entries occurs when a data group is started after a configuration change or when the request to start a data group specifies to clear pending entries. Invoked when a temporary lock condition or an operating system condition exists that prevents the database apply process (DBAPY) from opening the file or applying transactions to the file. Without database autonomics, users typically have to release the file so the database apply process (DBAPY) can continue without error.
Errors on IFS objects configured for advanced journaling Errors on data area and data queue objects configured for advanced journaling Errors when DBAPY cannot open the file or apply transactions to the file
34
Unless the object is explicitly excluded from replication for a data group, the autonomic recovery action will synchronize the object to ensure that it is on the target system. Note: Object autonomics does not detect or correct the following problems: Missing spooled files on the target system. Files and objects that are cooperatively processed. Although the files and objects are not addressed, problems with authorities for cooperatively processed files and objects are addressed. Activity entries that are stuck in a perpetual pending status (PR, PS, PA, or PB). The recovery action also sends a report of a recovery in progress to the user interface. In MIMIX Availability Manager, these reports are located on the Recoveries page. In a 5250 emulator, the reports are on the Work with Recoveries display (WRKRCY command). When the recovery action completes, the report is removed. The Obj. rcy. notify on success policy determines whether a successful recovery generates an informational notification. Only when all recovery options are exhausted without success is an activity entry placed in error status. Recovery actions that end in an error do not generate a separate error notification because the error is already reflected in MIMIX status.
Table 4. Error Missing objects on target system1 Errors detected and recoveries attempted by object autonomics during object replication Description An object (library-based, IFS, or DLO) exists on the source system and is within the name space for replication, but MIMIX detects that the object does not exist on the target system. Without object autonomics, this results in a failed activity entry. Notes: Missing spooled files are not addressed. Missing objects that are configured for cooperative processing are not synchronized. However, any problems with authorities (*AUTL or *USRPRF) for the missing objects are addressed. Any operation against an object whose parent object is missing on the target system. Without object autonomics, this condition results in a failed activity entry due to the missing parent object. Any operation that requires a user profile object (*USRPRF) that does not exist on the target system. Without object autonomics, this results in authority or object owner issues that cause replication errors. Any operation that requires a authority list (*AUTL) that does not exist on the target system.Without object autonomics, this results in authority issues that cause replication errors.
Missing parent objects on target system1 Missing *USRPRF objects on target system1 Missing *AUTL objects on target system1
35
Errors detected and recoveries attempted by object autonomics during object replication Description Applications which hold persistent locks on objects can result in object replication errors if the configured values for delay/retry intervals are exceeded. Default values in the data group definition provide approximately 15 minutes during which MIMIX attempts to access the object for replication. If the object cannot be accessed during this time, the result is activity entries with errors of Failed Retrieve (for locked objects on the source system) and Failed Apply (for locked objects on the target system) and a reason code of *INUSE. Notes: 1. The Number of third delay/retries policy and the Third retry interval policy determine whether automatic recovery is attempted for this error. 2. Automatic recovery for this error is not attempted when the objects are configured for cooperative processing.
1.
The synchronize command used to automatically recover this problem during replication will correct this error any time the command is used.
36
For many windows, you can adjust the amount of information displayed by changing preferences. You can change preferences at any time. Many tasks can be performed in the main window. Some tasks launch a new window while leaving the main window active. You can easily close the new window by using the Close button.
37
Note: Some windows may not have the bar or selected areas of the navigation bar. Content area - The content area changes based on your selections in the navigation bar. Typically, your location is identified in the summary at the top and corresponds to selected items in the navigation bar. Many windows display information in list form below the Toolbar. The Toolbar, when available, provides access to functions that are relevant to the displayed information.
Figure 1. Basic window layout
The content area of the Data Group Status window has a unique layout, shown in Figure 2. For this window, a portion of the content area is used as a selection list. The
38
data group selected is highlighted in gray and its summary status is displayed to its right in the gray-highlighted area.
Figure 2. Unique content area layout for the Data Group Status window.
39
and the action that will occur when clicked. The following provides an overview of common status icons: Status icons - overview
Status Action required Unknown Partially Active Ended Switching Description An error occurred. Immediate user action is required. Some or all status information is unavailable. Immediate user action is required. Processes are changing state or some processes are active while others are ended. User action may be required. All processes have ended normally due to a user request. User action is necessary to restart the processes. One or more data groups is in the process of switching which system is used as the source for replication. User action may be necessary. A warning condition exists that is either automatically correctable or is a non-critical condition. User action may be necessary. The status is unknown because collector services is not active. User action is necessary to start collector services. Processes are active. The process has been disabled.
Underlined text - Text that is underlined when you hover over it can be used to navigate to a predetermined area. Flyover help indicates the action. Clicking on underlined text can take a predefined action, display additional selection criteria, such as another navigation area, or change the content in the content area. Selecting listed items with checkboxes - Several windows contain lists from which you can select multiple items to act upon with actions available in the toolbar. Checkboxes next to each item allow selection. A checkbox at the top of a list next to a heading allows selection or deselection of all items in the list at once. Once items are selected, you can use any of the Selected buttons from the toolbar. Selecting actions from drop-down lists - Drop-down lists provide available actions for an item. The location of the drop-down list determines the scope of its available actions. In summary area - When a drop-down list appears in the summary area at the top of a window, its actions apply to all the items on the window. With some notable exceptions, such as starting all or ending all data groups, the actions can affect data groups that may not be visible from MIMIX Availability Manager. Online help notes these exceptions. Next to an item - When a drop-down list appears next to an item, its actions apply to only that item. These drop-down lists cannot be used in conjunction with checkboxes. In some cases, the recommended best action is the default action for the item and can vary from item to item in the list. In a toolbar - Drop-down lists available in toolbars are for filtering. The available
40
actions can be used to filter the content displayed. Ellipses - Actions that will prompt a command in another window or confirmation box before occurring are always followed by an ellipsis (...). Filtering - Filter buttons on the toolbar and not associated with a drop-down list offer a larger set of filtering criteria. Clicking the Filter button displays a Filter window, from which you can specify filter criteria for items within the current window.
41
42
Main Menu. We recommend you use the MIMIX Basic Main Menu unless you must access the MIMIX Intermediate Main Menu.
Figure 3. MIMIX Basic Main Menu
MIMIX Basic Main Menu System: MIMIX Select one of the following: 1. Availability status 2. Start MIMIX 3. End MIMIX 5. Start or complete switch 11. Configuration menu 12. Work with monitors 13. Work with messages 31. Product management menu WRKMMXSTS SYSTEM1
Selection or command ===>__________________________________________________________________________ ______________________________________________________________________________ F3=Exit F4=Prompt F9=Retrieve F21=Assistance level F12=Cancel (C) Copyright Vision Solutions, Inc., 1990, 2008.
Figure 4.
MIMIX Select one of the following: 1. 2. 3. 4. Work Work Work Work with with with with data groups systems messages monitors WRKDG WRKSYS WRKMSGLOG WRKMON
11. Configuration menu 12. Compare, verify, and synchronize menu 13. Utilities menu 31. Product management menu LAKEVIEW/PRDMGT
Selection or command ===>__________________________________________________________________________ ______________________________________________________________________________ F3=Exit F4=Prompt F9=Retrieve F21=Assistance level F12=Cancel (C) Copyright Vision Solutions, Inc., 1990, 2008.
43
CHAPTER 2
This chapter describes common MIMIX operations that help keep your MIMIX environment running. In order for MIMIX to provide a hot backup of your critical information, all processes associated with replication must be active at all times. Supporting service jobs must also be active. MIMIX allows you to display and monitor the statuses of these processes. While you can perform common operations, such as monitoring status, from either MIMIX Availability Manager or a 5250 emulator, MIMIX Availability Manager is preferred. MIMIX Availability Manager provides significant benefits over a 5250 emulator, including: Enterprise view of all installations and systems using MIMIX Ability to take you directly to the highest severity problem per installation Suggested resolution for each unique problem
The topics included in this chapter are: Becoming acquainted with status on page 45 describes how status bubbles up within MIMIX Availability Manager to include the highest severity errors. Monitoring status with MIMIX Availability Manager on page 48 describes how to check status of replication processes and supporting services from MIMIX Availability Manager. Monitoring status with MIMIX Availability Status on page 50 describes how to check status of replication processes and supporting services from a 5250 emulator. The Work with Data Groups display - 5250 emulator on page 54 describes the errors reported on this 5250 emulator display and provides procedures for resolving them. Working with the detailed status of data groups on page 61 describes how to access detailed status for a data group from either user interface. Identifying replication processes with backlogs on page 76 describes what fields to check in each user interface for detailed status of a data group.
44
45
Figure 7 shows how the severity of the problem is reflected in the content area as well as the navigation bar. The data group with the problem is identified in the list. Also, the Summary area identifies the cause of the problem and an appropriate action for
46
resolving it. Displaying details from the Summary area provides access to additional information about replication activity and problems.
Figure 7. A problem reflected on the Data Group Status window.
47
48
a. Use the flyover to determine the recommended action for the selected audit rule. b. From the Actions drop-down menu, select the appropriate action and click Note: You can also click the audit rule to see a detailed description of the audit status. The Rule status field in the Rule Details area contains the message and appropriate action for the specified audit rule. Select the appropriate action and click . For more information, see Working with audits on page 87. .
49
Additional fields - In the upper right corner of the display, additional fields report information that is relevant to maintaining the installation. Recoveries - Identifies the total number of recoveries in progress for the installation. Active recoveries represent problems detected and being corrected by MIMIX AutoGuard. Before certain activity, such as ending MIMIX, it is important that there are no recoveries in progress in the installation. If more than 9999 recoveries exist, the field displays ++++. Last switch - This field is only displayed when there is a value specified for the Default model switch framework policy. The date indicates when the last completed switch was performed using the switch framework specified in the policy. If you have not yet performed a switch using the switch framework defined in policies, this date is when the MIMIX environment was first started or when the
50
system managers were started and explicitly reset the configuration. Activity/Status - The main area of the display provides a reporting area for status of activity in key areas. Replication, Audits and notifications, and Services. For each activity area, status represents a summation of multiple processes. The text shown within each activity area changes to identify the most severe problem within its processes. Text, as well as background color, also identify the summarized status and indicate what action is appropriate. Blue indicates there are no problems with the activity and that no action is required. Yellow indicates warnings that may need your attention. Red indicates errors or inactive processes that require immediate action. Options - On this display, the activity you select with an option and the status of the activity determines what you see as the result of using the option. This behavior is unlike that of options on other MIMIX displays. The following subtopics describe the results of using the available options. Option 5 (Display details) from the MIMIX Availability Status display results in a display showing detailed status for the selected activity. Take option 5 next to the item to access detailed information for the activity. For Replication, the result is the Work with Data Groups display. For Audits and notifications, the result is the Summary view of the Work with Audits display. (To see details for notifications, press F20 (Command line), then enter the command WRKNFY.) For Services, the result is the Work with Systems display for status of the MIMIX managers. (To see details for monitors, press F4 (MIMIX Menu), then use option 12 (Work with monitors).)
Option 9 (Troubleshoot) from the MIMIX Availability Status display results in the appropriate display to use as a starting point for troubleshooting the stated problem for the selected activity. The stated problem reflects the highest severity problem present. Other less severe problems may exist, they may be reflected on the subsequent display but will not be reflected on the MIMIX Availability Status display until higher severity problems are resolved.Take option 9 next to the item to access detailed information for the activity. For Replication, the result is the Work with Data Groups display. For Audits and notifications, the result is dependent on the severity of the stated problem. All auditing conditions are prioritized before any notifications. For audits with status conditions, the result is the Summary view of the Work with Audits display. For audits with compliance conditions, the result is the Compliance view of the Work with Audits display. For notifications with errors, the result is the Work with Notifications display. For Services, the result is dependent on the severity of the stated problem. All system manager and journal manager errors are prioritized before any monitor errors. For system manager and journal manager errors, the result is the Work
51
with Systems display. For monitor errors, the result is the Work with Monitors display.
Red - Conditions exist that require immediate action or a switch is in progress. Possible scenarios that require immediate action include: Error conditions Processes required for replication are not active Some objects are not journaled and therefore cannot be replicated Journal state or cache is not as expected.
Status may change due to warnings or problems with any of the replication processes, with replication errors associated with data group entries (file, object, IFS tracking, and object tracking), or with a change in switch status. To begin resolving problems, use option 9 (Troubleshoot) to access the Work with Data Groups display, from which you can view detailed information and take action. See The Work with Data Groups display - 5250 emulator on page 54 for more information. Note: Replication status can indicate action required (red) while a switch is in progress. When you are ready to switch from the backup system to the production system, press F4 (MIMIX Menu). From there, use option 5 to continue switching.
52
Status values are shown by color while message text within the highlighted area indicates the nature of any problem. Blue - No action is required. No audits are active, have differences, or are out of compliance, and there are no new error or warning notifications. Yellow - An audit or notification may need your attention. An out-of-compliance audit is running its compare phase, an audit is approaching an out-of-compliance state, or a new warning notification exists. Red - A condition exists that requires immediate action. An audit has failed, had unresolved differences, is out-of-compliance, was prevented from running because of policy values, or a new error notification exists. Status may change due to the highest severity condition with audits, audit results, audit compliance, or new notifications. To begin resolving problems, use option 9 (Troubleshoot) to access the appropriate display for the indicated problem. For audit status problems, see Resolving audit problems - 5250 emulator on page 95. To resolve audit compliance problems, the audits must be run. See Running audits immediately on page 91 and Working with audit compliance on page 98. For additional information about notifications see Displaying notifications on page 120.
53
Figure 9. Sample Work with Data Groups display. The display uses letters and colored highlighting to call your attention to warning and problem conditions. This example shows items in color which would appear with color highlighting on the display. If you are viewing this page in printed form, the color may not be shown.
CHICAGO 11:02:05 Type options, press Enter. Audits/Recov./Notif.: 001 / 002 / 003 5=Display definition 8=Display status 9=Start DG 10=End DG 12=Files not active 13=Objects in error 14=Active objects 15=Planned switch 16=Unplanned switch ... ---------Source----------------Target--------ErrorsOpt Data Group System Mgr DB Obj DA System Mgr DB Obj DB Obj __ APP1 LONDON A I CHICAGO A I __ APP2 LONDON A A A CHICAGO A A A __ APP3 LONDON A I CHICAGO A I 2 __ CRITICALAP LONDON A R A A CHICAGO A A A 1 4 __ RJAPP4 LONDON A L CHICAGO A I Work with Data Groups
F3=Exit F10=Legend
F5=Refresh F13=Repeat
Bottom F7=Audits F8=Recoveries F9=Automatic refresh F16=DG definitions F23=More options F23=More keys
For each data group listed, you can see the current source system and target system processes, and the number of errors reported. The following fields and columns are available. Audit/Recov./Notif. -This field is located in the upper right corner of the Work with Data Groups display. The first number is the total number of audits that require action to correct a problem or that require your attention to prevent a situation from becoming a problem. The second number indicates the number of active recoveries, including those resulting from audits.The third number indicates the number of new notifications that require action or attention. If more than 999 items exist in any field, the field will display +++. When a field is highlighted in red, a problem exists. When a field is
54
highlighted in yellow, at least one out-of-compliance audit is currently active or an audit is approaching out of compliance. For details, see Problems reflected in the Audits/Recov./Notif. field on page 56. Data group - When a data group name is highlighted, a problem exists. For details, see Problems reflected in the Data Group column on page 56 Source - The following columns provide summaries of processes that run on the source system. For details about status values, see Replication problems reflected in the Source and Target columns on page 59. Mgr - Represents a summation of the system manager and the journal manager. DB - Represents the status of the remote journal link. It is possible to have an active status in this column even though the data group has not been started. When the RJ link is active, database changes will continue to be sent to the target system. MIMIX can read and apply these changes once the data group is started. For data groups configured for source-send replication, this represents the status of the database send process. Obj - Represents a summation of the object processes that run on the source system. These include the object send, object retrieve and container send processes. DA - This column represents the status of the data area polling process when the data group replicates data areas through the data area poller. This column does not contain data when data areas are replicated through the user journal with advanced journaling or through the system journal. Target - The following columns provide summaries of processes that run on the target system. For details about status values, see Replication problems reflected in the Source and Target columns on page 59. Mgr - Represents a summation of the system manager and the journal manager. DB - Represents the summation of the database reader process and the database apply processes. For data groups configured for source-send replication, this column represents the summation of the status of database apply processes. Obj - Represents the object apply processes. Errors - When any errors are indicated in the following columns (DB and Object), they are highlighted in red. DB - Represents a combination of file entries, IFS tracking entries, and object tracking entries in error for the data group. To work with a subsetted list of errors, use option 12 (Files not active), option 51 (IFS tracking entries not active), or option 53 (Object tracking entries not active). For additional information, see Working with files in error on page 170 and Working with tracking entries on page 179. Obj - Represents a count of the number of objects for which at least one activity entry is in a failed state. To work with a subsetted list, use option 13 (objects in error). For additional information, see Working with objects in error on page 185.
55
Yellow
56
2. To start journaling for a file or a tracking entry, use option 9 (Start journaling) to start journaling. 3. You can use option 11 (Verify journaling) to verify that journaling has started. Journal cache or journal state problems: If the data group name is highlighted in red or yellow, do the following to check for and resolve problems: 1. From the Work with Data Groups display, use option 8 (Display status). 2. From the Data Group Status display, press F8 (Database). 3. The Jrn State and Cache Src and Tgt fields are located In the upper left corner of the Data Group Database Status display. For each system (Src or Tgt) status of the journal state is shown first, followed by the status of the journal cache. The example below shows v for value in all for status positions. Based on the status displayed in these fields, you can take the actions described in the following steps to correct the problem:
Jrn State and Cache Src: v v Tgt: v v
4. Source system journal state (first Src: value) - If the source system state is red and the value for the journal state is standby (S) or inactive (I), the journal state must be changed and all data replicated through the user journal must be synchronized. Do the following: a. Press F12 (Cancel) to return to the Work with Data Groups display. Note which system is specified as the source system for the data group. b. Use option 45 (Journal Definitions) to view the journal definitions used for the data group in error. c. On the Work with Journal Definitions display, determine the journal name and library specified for the system that is the source system for the data group. d. Specify the name and library of the source system journal in the following command:
CHJRN CHGJRN JRN(library/name) JRNSTATE(*ACTIVE)
57
e. All data replicated through the user journal must be synchronized. For detailed information about synchronizing a data group, refer to your Runbook or to the MIMIX Reference book. 5. Source system journal cache (second Src: value) - If the source system cache is yellow, the actual status does not match the configured value in the journal definition used on the source system. Do the following: a. Press F12 (Cancel) to return to the Work with Data Groups display. Note which system is specified as the source system for the data group. b. Use option 45 (Journal Definitions) to view the journal definitions used for the data group in error. c. On the Work with Journal Definitions display, use option 5 (Display next to the journal definition listed for the source system. d. Check the value of the Journal caching (JRNCACHE) parameter. e. Determine which value is appropriate for journal cache, the configured value or the actual status value. Once you have determined this, either change the journal definition value or change the journal state (CHGJRN command) so that the values match. 6. Target system state (first Tgt: value) or Target system cache (second Tgt: value) - If the target system state or cache is yellow, the actual value for state or cache does not match the configured value. Do the following: a. Press F12 (Cancel) to return to the Work with Data Groups display. Note which system is specified as the target system for the data group. b. Use option 45 (Journal Definitions) to view the journal definitions used for the data group in error. c. On the Work with Journal Definitions display, use option 5 (Display next to the journal definition listed for the target system. d. Check the value of the following parameters, as needed: Target journal state (TGTSTATE) Journal caching (JRNCACHE) e. Determine why the actual status of the journal state or journal cache does not match the configured value of the journal definition used on the target system. f. Determine which values are appropriate for journal state and journal cache, the configured value or the actual status value. Once you have determined this, either change the journal definition value or change the journal state or cache (CHGJRN command) so that the values match.
58
A C
U J T
X P
Waiting at a recovery point (highlighted red) - The process is currently suspended at a recovery point.
Note: Use F10 (Legend) to view a pop-up window that displays the status values and colors. To remove the pop-up window, press Enter or F12 (Cancel).
59
60
If the view you want is not initially displayed, you can select it from the navigation bar. Online help is available for all views. From MIMIX Availability Manager, do the following to display a data group detailed status: 1. Select Data Groups from the Details area of the navigation bar. 2. From the list of data groups, select the data group you want. Status for this selected data group is displayed in the Summary area. 3. Select Display Details and click .
Note: The window displayed may be any of the following Data Group Details windows: Activity, Status, User Journal, or System Journal. MIMIX Availability Manager determines which window to display based on the severity of problems in the selected data group. Figure 10 shows an example of the Details - Status window. 4. If necessary, select Status from the Details area of the navigation bar. 5. To see additional details for this data group, use the left navigation bar to select
61
62
Figure 11. User journal detailed status for a data group within MIMIX Availability Manager
Figure 12. System journal detailed status for a data group within MIMIX Availability Manager
63
Object and File support actions which enable viewing additional detail for a specified file or object. Figure 13 shows an example of the window when File activity with replication problems is displayed.
Figure 13. Example of file information shown in the Data Group Details - Activity window
64
Replication activity and press Enter. 3. The Work with Data Groups display appears. Type an 8 (Display status) next to the data group you want and press Enter. 4. The Data Group Status display shows a merged view of data group activity on the source and target systems. (See Figure 14.) Only fields for the type of information replicated by the data group are displayed. For example, if the data group replicates only objects from the system journal, you will only see fields for system journal replication. If the data group replicates from both the system journal and the user journal, you will see fields for both. To see additional status information for object processes or database processes, do the following: If the data group contains object information, press F7 (Object) to view additional object status displays. The Data Group Object Status display appears. If the data group contains database information, press F8 (Database) to view additional database status displays. The Data Group Database Status display appears. Tracking entry information for advanced journaling is also available.
5. For object information, there are three views. For database information, there are four views available. Use F11 to change between views. Note: If the data group contains both database and object information, you can toggle between object details and database details by using the F7 and F8 keys.
Merged view
The initial view displayed is the merged view. This view summarizes status for the replication paths configured for the data group. The status of each process is represented by the color of the box surrounding the process and a status letter. Table 7 shows possible status values. Figure 14 shows a sample of the merged view of the Data Group Status display. The data group in this view is configured for user journal replication using remote journaling and for system journal replication.
Figure 14. Merged view of data group status. The inverse highlighted blocks are not shown in
65
this example.
Data Group Status 17:39:36 Data group . . . . : CRITICALAP Database errors . . . . : 1 Elapsed time . . . : 00:52:51 Objects in error/active : 4 / 0 Transfer definition: PRIMARY-A State. . . . . . . . . : *ASYNCPEND --------------------------- Source Statistics --------------------------System: LONDON-A Journal Manager-A RJLNK Monitor- A Receiver Sequence # Date Time Trans/Hour Database Source Jrn. LONDN0002 >0,000,002,591 4/20/08 11:02:35 Link-A RJ Tgt Jrn. LONDN0002 >0,000,002,591 4/20/08 11:02:35 Last Read . LONDN0002 >0,000,002,591 4/20/08 11:02:35 Entries not read: 0 Est. time to read: Object Current . . AUDRCV0108 22,314,732 4/22/08 17:37:13 748 Send-I Last Read . AUDRCV0103 22,175,464 4/21/08 11:05:56 Entries not read : 139,268 Est. time to read: --------------------------- Target Statistics --------------------------System: CHICAGO-A Journal Manager-A Reader-A RJLNK Monitor- A Last Received Unprocessed Entry Count Est Time Sequence # Entry Count Trans/Hour To Apply DB Apply-A >0,000,002,590 Obj Apply-A 22,023,868 4 F3=Exit F5=Refresh F10=Restart statistics F7=Object view F12=Cancel F8=Database F14=Start DG F9=Automatic refresh F15=End DG
Note: Journal sequence numbers shown in the Source Statistics and Target Statistics areas may be truncated if the journal supports *MAXOPT3 for the receiver size and the journal sequence number value exceeds the available display field. When truncation is necessary, the most significant digits (leftmost) are omitted. Truncated journal sequence numbers are prefixed by '>'. This is shown in Figure 14.
Table 7. Color and Status Red Red - I Red - W Yellow Yellow - P Turquoise - T Possible values for detailed status. Not all statuses are used by each process. Description When displayed on the Data group, Database errors, or Objects in error fields, a problem exists that requires action. The process is inactive. The process is suspended at a recovery point. This status is only available for apply processes. When displayed on the Data group field, a problem exists that may require attention. One or more of the processes is active but others are inactive. On the merged view, this status is only possible for the Object Send field. The process has a backlog which exceeds its configured threshold. On fields which summarize status for multiple processes, use F7 and F8 to view the specific threshold. The -T is not shown in statistical fields. If a threshold condition persists over time, refer to the MIMIX Reference book for information about possible resolutions. The status of the process is unknown
White - U
66
Possible values for detailed status. Not all statuses are used by each process. Description The process is active. The RJ Link is in catch-up mode.This status is only possible for the Database Link process in the merged view and the RJ link field in some database views. The data group is disabled. This also means the data group is currently inactive.
Green - D
Top left corner: The top left corner of the Data Group Status display identifies the data group, the elapsed time, and the status of the transfer definition in use. The elapsed time is the amount of time that has elapsed since you accessed this display or used the F10 (Restart statistics) key. Top right corner: The top right corner of the display identifies the number of errors identified by MIMIX. If the workstation supports colors, the number files and objects in error will be displayed in red. The Database errors field identifies the number of errors in user journal replication processes. This includes all file entries, IFS tracking entries, and object tracking entries in error. The Objects in error/active fields indicate the number of objects that are failed and the number of objects with pending activity entries. The first number in these fields indicates the number of objects defined to the data group that have a status of *FAILED. The second number indicates the number of objects with active (pending) activity entries. The State field identifies the state of the remote journal link. The values for the state field are the same as those which appear on the Work with RJ Links display. This field is not shown if the data group uses source-send processes for user journal replication.
Source statistics: The middle of the display shows status and summarized statistics for the journals being used for replication and the processes that read from them. The following process fields are possible: System - Identifies the current source system definition. The status value is an indication of the success in communicating with that system. Journal Manager - Displays the status of the journal manager process for the source system. DTAARA Poller - Displays the status of the data area poller. This field is present only if the data group replicates data areas using this process. RJLNK Monitor - Displays status of the RJLNK monitor on the source system. This field is present only for data groups that use remote journaling. Database (Link or Send) - Identifies the status of the process which transfers user
67
journal entries from the source system to the target system. Link - Displayed when the data group is configured for remote journaling. The status is that of the of the RJ link. Send -Displayed when the data group id configured for MIMIX source-send processes. The status is that of the database send process. Object Send - Displays a summation of status from the object send, object retrieve, and container send processes. The highest priority status from each process determines the status displayed. Use F7 (Object view) to see the individual processes. For the Database and Object processes, additional fields identify current journal information, the last entry that has been read by the process, and statistics related to arrival rate, entries not read, and estimating the time to read. Current - For the Database Send and Object Send processes, this identifies the last entry in the currently attached journal receiver. This information is used to show the arrival rate of entries to the journals. Note: If the data group uses remote journaling, current information is displayed in two rows, Source jrn and RJ tgt jrn. The source journal sequence number refers to the last sequence number in the local journal on the source system. The remote journaling target journal sequence number refers to the last sequence number in the associated remote journal on the target system. Transactions per hour - For current journal information, this is based on the number of entries to arrive on the journal over the elapsed time the statistics have been gathered. For last read information, this is based on the actual number of entries that have been read over the elapsed time the statistics have been gathered. Last Read - Identifies the journal entry that was last read and processed by the object send, database send, or database reader. Transactions per hour - For current journal fields, this is based on the number of entries to arrive on the journal over the elapsed time the statistics have been gathered. For last read fields, this is based on the actual number of entries that have been read over the elapsed time the statistics have been gathered and will change due to elapsed time and the rate at which entries arrive in the journal. Entries not read - This a calculation of the number of journal entries between the last read sequence number and the sequence number of the last entry in the current receiver for the source journal. An asterisk (*) preceding this field indicates that the journal receiver sequence numbers have been reset between the last entry in the current receiver and the last read entry. Estimated time to read - This is a calculation using the entries not read and the transactions per hour rate. This calculation is intended to provide an estimate of the length of time it may take the process (database reader, database send, or object send) to complete reading the journal entries. Target statistics: The lower part of the display shows status and summarized statistics for all target system processing. The following process fields are possible:
68
System - Identifies the current target system definition. The status value is an indication of the success in communicating with that system. Journal Manager - Displays the status of the journal manager process for the target system. Reader - Displays status of the database reader. This field is present only for data groups that use remote journaling. RJLNK Monitor - Displays status of the RJLNK monitor on the target system. This field is present only for data groups that use remote journaling. DB Apply and Obj Apply - Each field displays the combined status for the apply jobs in use by the process. For each process, additional fields show statistics for the last received journal sequence number, number of unprocessed entries, approximate number of transactions per hour being processed, and the approximate amount of time needed to apply the unprocessed transactions for all database or object apply sessions.
69
Objects in error . .
Send Process -I Jrn Manager -A Receiver Sequence # Date Time Trans/Hour Current . . AUDRCV0108 10,022,314,732 4/22/08 17:37:13 748 Last Read . AUDRCV0103 10,022,175,464 4/21/08 11:05:56 Entries not read: 139,268 Est. time to read: --------------------- Object Retrieve/Container Send ---------------------Retrievers Retrieve Senders Send Containers Containers Min Act Max Backlog Min Act Max Backlog Sent Per Hour 1 0 5 1 0 5 1,145 ------------------------------- Object Apply ------------------------------Applies Apply Active Entries Entries Min Act Max Backlog Objects Sequence # Applied Per Hour 1 1 5 4 >0,022,023,871 1,133 F3=Exit F5=Refresh F9=Automatic refresh F7=Merged view F11=View 2 F8=Database view F12=Cancel F24=More keys
Objects in error . .
Send Process -I Jrn Manager -A Receiver Sequence # Date Time Trans/Hour Current . . AUDRCV0108 10,022,314,732 4/22/08 17:37:13 748 Last Read . AUDRCV0103 10,022,175,464 4/21/08 11:05:56 Entries not read: 139,268 Est. time to read: --------------------- Object Retrieve/Container Send ---------------------Retrievers Retrieve Senders Send Containers Containers Min Act Max Backlog Min Act Max Backlog Sent Per Hour 1 0 5 1 0 5 1,145 ------------------------------- Object Apply ------------------------------Applies Apply ------------- Last Applied ------------Min Act Max Backlog Sequence # Type Object 1 1 5 0 >0,022,023,871 *DOC BVT#I/PBBDOCXX.002 F3=Exit F5=Refresh F9=Automatic refresh F7=Merged view F11=View 3 F8=Database view F12=Cancel F24=More keys
70
Target system: CHICAGO-A ------------------------------- Object Send ------------------------------Entry Sequence # Date Time Type Object Active TCO >0,022,023,868 4/20/08 13:59:23 *DOC BVT#I/PBBDOCXX.002 Processed TCO >0,022,023,868 4/20/08 13:59:23 *DOC BVT#I/PBBDOCXX.002 ------------------------------- Object Apply ------------------------------Entry Sequence # Date Time Type Object Processed TCA >0,022,023,871 4/20/08 13:59:23 *DOC BVT#I/PBBDOCXX.002
71
19, and Figure 20). Each session has its own status value. In these sample figures there is only one apply session (A) which is active (-A). The Jrn State and Cache (Src and Tgt) fields reflect journal standby state and journal caching actual values for the journals when the IBM high availability performance enhancements are installed on the systems defined to the data group. These fields appear on database views 1 and 2 (Figure 18 and Figure 19). The target journal state and cache values are set on the journal when the database apply session is started. Journal State - The status values indicate the actual state value for the source and target journals. Table 8 shows the possible values for each field. Journal Cache - The status indicate the actual cache value for the source and target journals. Table 9 shows the possible values for each field. For each system (Src or Tgt) status of the journal state is shown first, followed by the status of the journal cache. If a problem exists with journal state or journal cache, the data group name is also highlighted with the same color. For information about resolving journal cache or journal state problems, see Resolving problems highlighted in the Data Group column on page 57.
Table 8. Field Either system Possible status values for Journal State fields Color and Status White No color No color U A X Description Unknown. MIMIX was not able to retrieve values, possibly because the journal environment has not yet been built. Journal state is active The required IBM feature, IBM i option 42 - High Availability Journal Performance, is not installed on this system Journal is in standby state as expected Source journal is in standby state but that state is not expected. Source journal in inactive state but that state is not expected. Target journal state or cache is not as expected and the database apply session is active Target journal state is inactive but that state is not expected. The IBM feature is installed but the data group is configured to not journal on the target system.
S S I S I
blank blank
72
Table 9. Field
Possible status values for Journal Cache fields Color and Status White U X Description Unknown. MIMIX was not able to retrieve values, possibly because the journal environment has not yet been built The required IBM feature, IBM i option 42 - High Availability Journal Performance, is not installed on this system Caching is active Caching is not active. Source journal cache value is not as expected. Source journal cache value is not as expected. Target journal cache value not as expected and the database apply session is active. Target journal cache value not as expected and the database apply session is active. The IBM feature is installed but the data group is configured to not journal on the target system.
Either System
No color
Y N Y N Y N
blank blank
Figure 18. Data group detail statusdatabase view 1. In this example, the Link status of -A and the presence of the Reader status indicate that the data group uses remote journaling. The display also shows that journal standby state is active and journal caching is not active. The unprocessed entry count indicates that the final journal entry has not been applied. The > character preceding sequence numbers for the apply session indicate truncated sequence
73
F24=More keys
Figure 19. Data group database statusview 2. In this example, the Link status of A and the presence of the Reader status indicates that the data group uses remote journaling. The display also shows that journal standby state is active and journal caching is not active.
CHICAGO 16:07:03 Data group . . . . : CRITICALAP File and Tracking entries. : 12 Elapsed time . . . : 00:52:51 Not journaled on source . : 1 Jrn State and Cache Src: A N Tgt: A N Not journaled on target . : 1 RJ Link -A Held due to error . . . . : 2 Jrn Manager -A Reader -A Held for other reasons . . : 0 Receiver Sequence # Date Time Trans/Hour Source Jrn. LONDN0002 12,345,678,900,000,002,591 4/20/08 11:02:35 Rj Tgt Jrn. LONDN0002 12,345,678,900,000,002,591 4/20/08 11:02:35 Last Read . LONDN0002 12,345,678,900,000,002,591 4/20/08 11:02:35 Entries not read: 0 Est. time to read: ------------------------------- Database Apply --------------------------Apply Received Apply point Clock Time Hold MIMIX Log Open Status Sequence # Sequence # Difference Sequence # Commit Id A-A >0,000,002,590 >0,000,002,590 Data Group Database Status System:
F24=More keys
74
LONDON-A Entry Sequence # UMX 12,345,678,900,000,002,591 UMX 12,345,678,900,000,002,591 UMX 12,345,678,900,000,002,591 - 12,345,678,900,000,002,590
Target system: CHICAGO-A ------------------------------- Database Apply ----------------------------Apply Entry Sequence # Date Time Object Library Member A-A UMX >0,000,002,590 4/20/08 11:01:04
F24=More keys
Figure 21. Data group detail statusdatabase view 4. In this example, the combined number of file and tracking entries shown in Figure 18 and Figure 19 are separated into separate columns for file entries, IFS tracking entries, and object tracking entries.
File and Tracking Entry Status Data group . . . . : CRITICALAP File Entries 7 1 0 0 0 IFS Trk Entries 3 0 1 1 0 Obj Trk Entries 2 0 0 1 0 System: CHICAGO 16:07:03
Number of entries . . . . : Not journaled on source . : Not journaled on target . : Held due to error . . . . : Held for other reasons . .:
F24=More keys
75
In MIMIX Availability Manager, you may need to select User Journal or System Journal from the Details area of the navigation bar to access the appropriate window. In a 5250 emulator, use F7 or F8 on the Data Group Status display to locate the appropriate view.
Location of fields in each user interface which identify backlogs and threshold conditions for replication processes Description User Interface Window / View Fields to Check for Backlog Fields Highlighted when Threshold Exceeded
RJ Link
The backlog is the quantity of source journal entries that have not been transferred from the local journal on the source system to the remote journal on the target system. The time difference between the last entry in each journal can also be an indication of a backlog. MIMIX Availability Manager 5250 emulator Data Group Status Details -User Journal window Merged view, Database views 1 and 2 Not Sent Differences between transactions identified for Source and Target. Differences between journal entries identified by Source Jrn and RJ Tgt jrn for the database link. Not Sent 1
76
Location of fields in each user interface which identify backlogs and threshold conditions for replication processes Description User Interface Window / View Fields to Check for Backlog Fields Highlighted when Threshold Exceeded
DB Reader or DB Send
The backlog is the quantity of journal entries that are waiting to be read by the process. The time difference between the last entry that was read by the process and the last entry in the journal on the source system can also be an indication of a backlog. MIMIX Availability Manager 5250 emulator Data Group Status Details -User Journal window Merged view, Database views 1 and 2 Not Read Differences between transactions identified for Target (or Current) and Last Read. For remote journaling configurations, differences between journal entries identified by Source Jrn and Last read. For MIMIX source-send configurations, differences between journal entries identified by Current and Last Read. Not Read 1
DB Apply
The backlog is the number of entries waiting to be applied to the target system. Each apply session is listed as a separate entry with its own backlog. MIMIX Availability Manager 5250 emulator Data Group Status Details -User Journal window Database views 1, 2, and 3 Unprocessed Entries Unprocessed Entries 2
Object Send
The backlog is the quantity of journal entries that have not been read from the system journal. The time difference between the last entry that was read by the process and the last entry in the system journal can also be an indication of a backlog. MIMIX Availability Manager 5250 emulator Data Group Status Details -System Journal window Merged view, Object views 1, 2, and 3 Not Processed Differences between transactions identified for Current and Last Read. Differences between transactions identified for Object Current and Last Read Not Processed 1
77
Location of fields in each user interface which identify backlogs and threshold conditions for replication processes Description User Interface Window / View Fields to Check for Backlog Fields Highlighted when Threshold Exceeded
Object Retrieve
The backlog is the number of entries for which MIMIX is waiting to retrieve objects. MIMIX Availability Manager 5250 emulator Data Group Status Details -System Journal window Object views 1 and 2 Retrievers, Backlog column Retrievers, Backlog column
Retrieve Backlog
Container Send
The backlog is the number of packaged objects for entries that are waiting to be sent to the target system. MIMIX Availability Manager 5250 emulator Data Group Status Details -System Journal window Object views 1 and 2 Containers, Backlog column Containers, Backlog column
Object Apply
The backlog is the number of entries waiting to be applied to the target system. MIMIX Availability Manager 5250 emulator Data Group Status Details -System Journal window Object views 1 and 2 Apply, Backlog column Apply, Backlog column
Apply Backlog
Notes: 1. When the threshold is exceeded, the field also includes text which indicates whether the backlog was exceeded by time or by entries and by how much. 2. When the threshold is exceeded, the field also includes text which indicates the number of entries by which the threshold is exceeded. 3. When highlighted, the threshold journal entry quantity criterion is exceeded. 4. When highlighted the threshold time criterion is exceeded.
78
CHAPTER 3
Audits are defined by and invoked through rules and influenced by policies. Aspects of audits include schedules, status, reported results, and their compliance status. MIMIX is shipped so that auditing can occur automatically. For day-to-day operations, auditing requires minimal interaction to monitor audit status and results. MIMIX user interfaces separate audit runtime status, compliance status, and scheduling information onto different views to simplify working with audits. Compliance errors and runtime errors require different actions to correct problems. This chapter provides information and procedures to support day-to-day operations as well as to change aspects of the auditing environment. The following topics are included. What are rules and how they are used by auditing on page 80 defines the differences between MIMIX rules used for auditing and user-defined rules. Requirements for using audits and rules on page 81 identifies the policy required for automatic audit recovery and the authority levels needed for working with rules when additional product and command security functions provided through License Manager are used. Guidelines and recommendations for auditing on page 81 provides considerations for effectively auditing a replication environment and recommendations for using both MIMIX rules and user-defined rules. Where audit status and compliance status is reported on page 85 describes where audit runtime and compliance status information is reported in higher-level status in the user interfaces. Working with audits on page 87 identifies the Audit Summary interfaces and provides procedures for common activities with audits, such as running audits immediately and resolving reported problems. Working with audit compliance on page 98 identifies the Audit Compliance interfaces and describes how to determine if an audit has a compliance problem. Working with audit schedules on page 102 identifies the Audit Schedule interfaces and the shipped default schedule information for MIMIX rules, provides considerations and procedures for changing an audit schedule, changing the system on which audits are performed, and provides considerations for using a different job scheduling mechanism. Policies for auditing on page 109 identifies all of the policies that can influence audits and provides procedures to prevent audits from running in common scenarios. Running rules and rule groups manually on page 115 describes how to run rules and rule groups manually and how to check the results of a user-generated rule. Checking results of a user-defined rule on page 118 describes how to view the results of running a user-defined rule.
79
80
Audit level: Best practice for auditing is to run the most extensive comparison possible. Specifying level 30 for the Audit level policy enables this. If you choose to run daily audits at a lower audit level, you should be aware of the risks, especially when switching. The level you choose for daily audits depends on your environment, and especially on the data compared by the #FILDTA and #IFSATR audits. When choosing a value, consider how much data there is to compare, how frequently it changes, how long the audit runs, how often you run the audit, and how often you need to be certain that data is synchronized between source and target systems. The #FILDTA audit compares all file member data defined for file members defined to a data group only when audit level 30 is used. Level 10 and level 20 compare 5 percent and 20 percent of data, respectively. Lower audit levels may take days or
81
weeks to completely audit file data. New files created during that time may not be audited. The #IFSATR audit compares data when audit level 20 or 30 is used. At level 10, only attributes are compared. Regardless of the level you use for daily operations, Vision Solutions strongly recommends that you perform audits at audit level 30 before the following events to ensure that 100 percent of that data is valid on the target system: Before performing a planned switch to the backup system. Before switching back to the production system.
Recommendations when automatic audit recovery is enabled: You should also consider the following when you use audit recoveries: MIMIX rules support recoveries only when the automatic audit recovery policy is enabled. Automatic recovery is not supported for user-defined rules. It may take multiple iterations of running audits with recoveries before the results are clean. Recovering from one error may result in a different error surfacing the next time the audit is performed. For example, a recovery that adds data group file entries may result in detecting a database relationship difference (*DBRIND) error the next time the audit is performed, where the root problem is that a library of logical files is not identified for replication. Always review the results of the audits. Audit results reflect only what was actually compared. Some objects may not have been compared due to object activity or due to the audit level policy value in effect, even when no differences (*NODIFF) are reported. You may need to take actions other than running an audit to correct detected issues. For example, you may need to change a procedure so that target system objects are only updated by replication processes. Watch for trends in the audit results. Trends may indicate situations that need further investigation. For example, objects that are being recovered for the same reason every time you run an audit can be an indication that something in your environment is affecting the objects between audits. In this case, investigating the environment for the cause may determine that a change is needed in the environment, in the MIMIX configuration, or in both. Trends may also indicate a MIMIX problem, such as reporting an object as being recovered when it was not. Report these scenarios to MIMIX CustomerCare. You can do this by creating a new case using the Case Management page in Support Central.
82
General recommendations: Run MIMIX rules from a management system. For most environments, the management system is also the target system. If you cannot run rules from the management system due to physical constraints or because of complex configurations, you can change the Run rule on system policy to meet your needs. See Changing the system where audits are performed on page 108. When choosing the value for the Run rule on system policy, consider your switching needs. Run MIMIX rules on a scheduled basis. This will help you detect problems in a timely manner and when you have time to address them. When running a rule or rule group from MIMIX Availability Manager, you should ensure that you have selected the appropriate systems for viewing in the browser preferences. Otherwise, you will not see the message log entries, notifications, and possible recoveries from the rule.
Considerations for the run rule commands: The RUNRULE command allows you to run multiple rules concurrently, with each specified rule running in an independent process. A limit of 100 unique rules can be specified per RUNRULE request. The RUNRULEGRP command only allows you to specify one rule group at a time. Otherwise, this command is like the RUNRULE command. When prompting the RUNRULE or RUNRULEGRP commands, consider the following: For the Data group definition prompts, the default value, *NONE, means the rule will not be run against a data group. If *NONE is specified on the command when the rule uses the &DGDFN replacement variable, running the RUNRULE command results in an error condition in the audit status and a message log entry. When a data group name or *ALL is specified, any instance of the &DGDFN replacement variable is replaced with the data group name and each data group is run in a separate process. For the Job description and Library prompts, the default value, MXAUDIT, submits the request using the default job description, MXAUDIT.
Replacement variables
Replacement variables are used to simplify the configuration and management of rules by allowing rule actions to be used for multiple data groups. They can also simplify outfile generation and cleanup. Replacement variables begin with an ampersand (&) and are used to pass in a value when a rule action is run. Some commonly used replacement variables include: The &PRDLIB replacement variable passes in the library from which the command specified in the rule is initiated. The &DGDFN replacement variable identifies the data group the rule is to act upon. In order to run a rule that contains &DGDFN, you must specify the value for the data group definition on the RUNRULE command. The &OUTFILE replacement variable passes in the name of a MIMIX generated
83
output file (outfile). The outfile is placed in a library whose name is the name of the MIMIX installation library followed by the characters _0. The outfile is managed by MIMIX. When &OUTFILE is specified in a rule, you will be able to view the resulting outfile from the user interface.
84
In a 5250 emulator, audit status and compliance status are reflected on the MIMIX Availability Status display (WRKMMXSTS command), shown in Figure 23. The Audits and notifications area in the middle of this display provides a high-level indication of current status and the severity of any problem for a MIMIX installation. Color and the text of the message displayed indicate when problems exist that require immediate
85
attention (yellow) or action (red). When audit information is identified in the message, both options will access the Work with Audits display. The example in Figure 23 shows that attention may be required to prevent an audit from becoming out of compliance. In this example, using option 9 next to the Audits and notifications field will take you to the Compliance view of the Work with Audits display.
Figure 23. MIMIX Availability Status display highlighting a problem with audit compliance
Also, the Work with Data Groups display also provides an indication of the number of audits that require action or attention. Figure 24 shows the Audits/Recov./Notif. fields
86
in the upper right of the display. If more than 999 items exist in any field, the field will display +++.
Figure 24. Work with Data Groups display highlighting audits that require action (red)
CHICAGO 10:49:06 Type options, press Enter. Audits/Recov./Notif.: 015 / 000 /002 5=Display definition 8=Display status 9=Start DG 10=End DG 12=Files not active 13=Objects in error 14=Active objects 15=Planned switch 16=Unplanned switch ... ---------Source----------------Target--------ErrorsOpt Data Group System Mgr DB Obj DA System Mgr DB Obj DB Obj __ TESTDG34 LONDON A A A CHICAGO A A A __ TESTDG43 LONDON A A A CHICAGO A A A Work with Data Groups
F3=Exit F10=Legend
Bottom F5=Refresh F7=Audits F8=Recoveries F9=Automatic refresh F16=DG definitions F23=More options F24=More keys
The first number is the total number of audits that require action to correct a problem or that require your attention to prevent a situation from becoming a problem. The second number indicates the number of active recoveries, including those resulting from audits. The third number indicates the number of new notifications that require action or attention. When the Audits field is highlighted in reverse red, at least one audit has failed, has unresolved differences, or is out of compliance. When highlighted in reverse yellow, at least one out-of-compliance audit is currently active or an audit is approaching out of compliance. For additional information and to work with audits, use either F7 (Audits) or option 57 (Audits) to access the Work with Audits display. For additional information see Working with audits on page 87 and Working with audit compliance on page 98.
87
MIMIX Availability Manager - On the Audit Summary window you can quickly see the status of any audits in progress. The status of audits in progress is reflected with an icon in overall status in the navigation bar and in icons next to audits. When there is no icon present, as in Figure 25, there are no audits in progress and no known problems. When problems exist, the Action required field is highlighted and the audits requiring immediate attention or intervention have icons to draw your attention.
Figure 25. Audit Summary window in MIMIX Availability Manager.In this example, there are no problems with audit status. However, there is an audit compliance problem.
88
5250 emulator - The Summary view of the Work with Audits display (Figure 26) shows audit runtime status and audit results status in the Audit Status column.
Figure 26. Audit Summary View - data group definition view
Work with Audits System: Type options, press Enter 5=Display 6=Print 7=Notification 8=Recoveries 36=Change DG policies 37=Change audit schedule Audit Status *CMPACT *CMPACT *CMPACT *RCYACT *QUEUED *QUEUED *NOTRUN *NODIFF AS01
Opt __ __ __ __ __ __ __ __
---------Definition--------DG Name System 1 System 2 EMP AS01 AS02 EMP AS01 AS02 EMP AS01 AS02 EMP AS01 AS02 EMP AS01 AS02 EMP AS01 AS02 EMP AS01 AS02 EMP AS01 AS02
Bottom Parameters or command ===> _________________________________________________________________________ F3=Exit F4=Prompt F5=Refresh F9=Retrieve F10=Compliance summary F11=View 2 F16=Inst. policies F18=Subset F21=Print list F24=More keys
Note: If audit compliance problems exist, you may see a different view of the Work with Audits display. Use F10 to access the Summary view. Use F11 to view information about policies in effect when the audit was last run. The Last Run column in Figure 27 shows the values of policies in effect at the time the audit was last run through its compare phase. Recovery identifies the value of the automatic audit recovery policy. When this policy is enabled, after the comparison completes, MIMIX automatically starts recovery actions to correct differences detected by the audit. Recovery may also indicate a value of *DISABLED if a condition checked by the Action for running audits (RUNAUDIT) policy existed and the policy value for that condition specified *CMP, preventing audit recoveries from running. Level identifies the value of the audit level policy. The audit level determines
89
the level of checking performed during the compare phase of the audit. If an audit was never run, the value *NONE is displayed in both columns.
Figure 27. Audit Summary View - last run policies view
Work with Audits System: Type options, press Enter 5=Display 6=Print 7=Notification 8=Recoveries 36=Change DG policies 37=Change audit schedule Audit Status *CMPACT *CMPACT *CMPACT *RCYACT *QUEUED *QUEUED *NOTRUN *NODIFF ------Last Recovery *ENABLED *ENABLED *ENABLED *ENABLED *ENABLED *ENABLED *ENABLED *ENABLED AS01
Opt __ __ __ __ __ __ __ __
Bottom Parameters or command ===> _________________________________________________________________________ F3=Exit F4=Prompt F5=Refresh F9=Retrieve F10=Compliance summary F11=View 1 F12=Cancel F13=Repeat F18=Subset F21=Print list
Click Help to see descriptions of values for these fields and icons. 4. To view additional details, select the Details action and click From a 5250 emulator, do the following: 1. Doing one of the following to access the Summary view of the Work with Audits display: Enter the command: installation-library/WRKAUD VIEW(*AUDSTS) .
90
From the MIMIX Availability Status display, use option 5 (Display details) next to Audits and notifications. Then, if necessary, use F10 to access the Summary view.
2.Check the value shown in the Audit Status column. Press F1 (Help) for a description of status values. 3. To view additional information about an audit, use option 5 (Display).
For more information, see, Resolving audit problems - MIMIX Availability Manager on page 93. From a 5250 emulator, most users should perform these procedures form the management system. To run a rule immediately, do the following: 1. Enter the command: installation-library/WRKAUD 2. Type option 9 (Run rule) next to the audit you want and press Enter. For more information, see, Resolving audit problems - MIMIX Availability Manager on page 93.
Ending audits
Only active or queued audits can be ended. This includes audits with the following statuses: Currently comparing (*CMPACT), Currently recovering (*RCYACT), or Currently waiting to run (*QUEUED). You must end active or queued audits from the system that originated the audit. From MIMIX Availability Manager, you can end active or queued audits from the Audit Summary and Audit Compliance windows as well as from the Audit Details window when viewing an active or queued audit.
91
To end an active or queued audit, do the following: 1. Select Audit Summary or Audit Compliance from the navigation bar. 2. The list in the resulting window shows all audits for data groups selected for viewing for the installation. Check the following: Icons next to the Rule column indicate overall audit status. The State column indicates the current state of audit activity.
Click Help to see descriptions of values for these fields and icons. 3. For the active or queued audit you want, select the End Audit action and click .
4. For queued audits and audits in the compare phase at the time of the request, status is changed to their previous values. Status for audits in the recovery phase is set according to the completed comparison result as well as the results of any completed recovery actions. From a 5250 emulator, you can end active or queued audits from any view of the Work with Audits display. This procedure uses the Status view. To end an active or queued audit, do the following: 1. Enter the command: installation-library/WRKAUD VIEW(*AUDSTS) 2. Check the value shown in the Audit Status column. Press F1 (Help) for a description of status values. 3. Type option 10 (End) next to the active or queued audit you want to end and press Enter. 4. Audits in *CMPACT or *QUEUED status are set back to their previous status values. Audits in *RCYACT status are set according to the completed comparison result as well as the results of any completed recovery actions.
3. The MIMIX Rule Details window displays the available audit levels. For each audit level, the command used in the compare phase is shown. The Differences column identifies what parameters are different from the command used in the previous audit level.
92
Rule Failed
93
Addressing audit problems - MIMIX Availability Manager Results Differences detected, recovery disabled Action The detected differences must be manually resolved. Either the Automatic audit recovery policy is disabled or the Action for running audits policy prevented recovery actions while the data group was inactive or had an apply process which exceeded its threshold. To determine the cause, select Notifications from the action list and click . If the Automatic audit recovery policy is disabled, the differences must be manually resolved. If the Action for running audits policy was the cause, correct any problems with the data group status. You may need to start the data group and wait for threshold conditions to clear. Then run the audit again. To manually resolve differences, do the following: 1. Select Output File from the action list and click . 2. The detected differences are displayed. Look for items with a Difference Indicator value of *NC or *NE. You can display details about the error or attempt the possible recovery action available. 3. Select the action you want and click . To have MIMIX recover differences on subsequent audits, change the value of the automatic audit recovery policy. The remaining detected differences must be manually resolved.
Note: For audits using the #MBRRCDCNT rule, automatic recovery is not possible. Other audits, such as #FILDTA, may correct the detected differences.
Completed Successfully
Completed Successfully
Do the following: 1. Select Output File from the action list and click . 2. The detected differences are displayed. Look for items with a Difference Indicator value of *NE, *NC, or *RCYFAILED. If automatic audit recovery is disabled, you may see other values as well. For the #MBRRCDCNT results, also look for values of: *HLD, *LCK, *NF1, *NF2, *SJ, *UE, and *UN. You can display details about the error or attempt the possible recovery action available. 3. Select the action you want and click . Not run due to policy (any value) The audit was prevented from running by the Action for running audits policy. Either the data group was inactive or an apply process exceeded its threshold. This may be expected during periods of peak activity or when data group processes have been ended intentionally. However, if the audit is frequently not run due to this policy, action may be needed to resolve the cause of the problem.
For more information about the values displayed in the audit results, see Interpreting audit results - supporting information on page 262.
94
2. Check the Audit Status column for values shown in Table 12. Audits with potential problems are at the top of the list. Take the action indicated in Table 12.
Table 12. Status *FAILED Addressing audit problems - 5250 emulator Action The audit failed for these possible reasons. Reason 1: The rule called by the audit failed or ended abnormally. To run the rule for the audit again, select option 9 (Run rule). To check the job log, see Checking the job log of an audit on page 96. Reason 2: The #FILDTA audit or the #MBRRCDCNT audit which required replication processes that were not active. 1. From the MIMIX Availability Status display, check whether there are any problems indicated for replication processes. 2. If there are no problems with replication processes, use F20 to access a command line and type WRKAUD. Then skip to Step 6. 3. If there are replication problems, use option 9 (Troubleshoot) next to the Replication activity. 4. On the Work with Data Groups display, if processes for the data group show a red I, L, or P in the Source and Target columns, use option 9 (Start DG). 5. When processes are active, use F7 to view audits. 6. From the Work with Audits display, use option 9 (Run rule) to run the audit.
95
Addressing audit problems - 5250 emulator Action The comparison performed by the audit detected differences. No recovery actions were attempted. Either the Automatic audit recovery policy is disabled or the Action for running audits policy prevented recovery actions while the data group was inactive or had an apply process which exceeded its threshold. To determine the cause, use option 7 to view notifications for the audit. A subsetted list of the notifications for the audit appears. If the Automatic audit recovery policy is disabled, the differences must be manually resolved. If the Action for running audits policy was the cause, correct any problems with the data group status. You may need to start the data group and wait for threshold conditions to clear. Then run the audit again. To manually resolve differences, from the notification do the following: 1. Use option 8 to view the results in the output file. 2. Check the Difference Indicator column for values of *NC and *NE. For any of these differences, you will need manually resolve these problems. To have MIMIX recover differences on subsequent audits, change the value of the automatic audit recovery policy. The comparison performed by the audit detected differences. Some of the differences were not automatically recovered. The remaining detected differences must be manually resolved.
Note: For audits using the #MBRRCDCNT rule, automatic recovery is not possible. Other audits, such as #FILDTA, may correct the detected differences.
*DIFFNORCY
*NOTRCVD
Do the following: 1. Use option 7 to view notifications for the audit. 2. A subsetted list of the notifications for the audit appears. Use option 8 to view the results in the output file. 3. Check the Difference Indicator column for values of *NC, *NE, and *RCYFAILED. If automatic audit recovery is disabled, you may see other values as well. For the #MBRRCDCNT results, also look for values of: *HLD, *LCK, *NF1, *NF2, *SJ, *UE, and *UN. For any of these differences, you will need to manually resolve these issues. *NOTRUN The audit was prevented from running by the Action for running audits policy. Either the data group was inactive or an apply process exceeded its threshold. This may be expected during periods of peak activity or when data group processes have been ended intentionally. However, if the audit is frequently not run due to this policy, action may be needed to resolve the cause of the problem.
For more information about the values displayed in the audit results, see Interpreting audit results - supporting information on page 262.
96
From MIMIX Availability Manager, to check the job log for an audit, do the following: 1. For the audit in question, select the Job logs action and click only available when viewing audits from the sending system. . This choice is
2. The Job Log window opens. Look at the most recent messages to determine the cause of the audit failure. Note: If you see no data available instead, you may still be able to view the job log from the 5250 emulator as described below. From a 5250 emulator, you must display the notifications from an audit in order to view the job log. Do the following: 1. From the Work with Audits display, type 7 (Notification) next to the audit and press Enter. 2. The notifications associated with the audit are displayed on the Work with Notifications display. Use option 5 (Display) or F22 to view the description in the Notification column. 3. If the notification is not sufficient to determine the problem, use option 12 (Display job) next to the notification. 4. The Display Job menu opens. Select option 4 (Display spooled files). Then use option 5 (Display) from the Display Job Spooled Files display. 5. Look for a completion message from the rule with the text indicated from Step 2. Usually the most recent messages are at the bottom of the display.
97
5250 emulator - From a 5250 emulator, audit compliance status is reflected in the Audits and notifications row on the MIMIX Availability Status display (Figure 23). You can quickly see whether any audits have reached their compliance policies. The Audits and notifications row is highlighted when any audit reaches its warning or
98
action threshold policy. When a compliance problem exists, this row is highlighted in red or yellow. When audit compliance information is identified in the message, both options will access Compliance view of the Work with Audits display (Figure 29). Note: If other audit problems exist, you may see a different view of the Work with Audits display. Use F10 to access the Compliance view.
Figure 29. Audit Compliance View - data group definition view
Work with Audits System: Type options, press Enter 5=Display 6=Print 7=Notification 8=Recoveries 36=Change DG policies 37=Change audit schedule 9=Run rule AS01 10=End
Opt __ __ __ __ __ __ __ __
---------Definition--------DB Name System 1 System 2 EMP AS01 AS02 EMP AS01 AS02 EMP AS01 AS02 EMP AS01 AS02 EMP AS01 AS02 EMP AS01 AS02 EMP AS01 AS02 EMP AS01 AS02
---Compare End--Date Time 09/25/08 12:15:34 09/25/08 12:15:34 09/25/08 12:15:34 09/25/08 12:15:35 09/25/08 12:15:38 09/25/08 12:15:36 09/25/08 12:15:38 09/25/08 12:15:37
Bottom Parameters or command ===> _________________________________________________________________________ F3=Exit F4=Prompt F5=Refresh F10=Schedule summary F11=View 2 F16=Inst. policies F17=Sort sched. time F18=Subset F24=More keys
99
An audit with a compliance problem must be run to resolve the problem. Use F11 to view when the audits are next scheduled to run (Figure 30).
Figure 30. Audit Compliance View - scheduled time view.
Work with Audits System: Type options, press Enter 5=Display 6=Print 7=Notification 8=Recoveries 36=Change DG policies 37=Change audit schedule 9=Run rule AS01 10=End
Opt __ __ __ __ __ __ __ __
-Scheduled Time-Date Time 09/26/08 02:00:00 09/26/08 02:25:00 09/26/08 02:10:00 09/26/08 02:20:00 09/26/08 02:35:00 09/26/08 02:15:00 09/26/08 02:30:00 09/26/08 02:05:00
---Compare End--Date Time 09/25/08 12:15:34 09/25/08 12:15:34 09/25/08 12:15:34 09/25/08 12:15:35 09/25/08 12:15:38 09/25/08 12:15:36 09/25/08 12:15:38 09/25/08 12:15:37
Bottom Parameters or command ===> _________________________________________________________________________ F3=Exit F4=Prompt F5=Refresh F10=Schedule summary F11=View 2 F16=Inst. policies F17=Sort sched. time F18=Subset F24=More keys
In both views, the list is initially sorted by compliance status. To sort the list by scheduled time, use F17.
100
3. Click on the rule name to display additional details, including compliance information, when the audit last ran successfully, and when it is next scheduled to run. 4. Select the appropriate action and click .
5. To resolve a problem with audit compliance, the audit in question must be run and complete its compare phase. To run the audit now see Running audits immediately on page 91. From a 5250 emulator, do the following to check for compliance problems: 1. Do one of the following to access the Compliance view of the Work with Audits display: Enter the command: installation-library/WRKAUD VIEW(*COMPLY) From the MIMIX Availability Status display, use option 5 (Display details) next to Audits and notifications. Then, if necessary, use F10 to access the Compliance view.
2. Check the Compliance column for values of *ATTN and *ACTREQ. 3. To resolve a problem with audit compliance, the audit in question must be run and complete its compare phase. To see when the audit is next scheduled to run press F11. To run the audit now, see Running audits immediately on page 91.
101
Similar information is available from a 5250 emulator on the audit schedule view of the Work with Audits display (Figure 32).
102
Note: The Work with Audits display may open to a different view. Use F10 to access the Schedule view.
Figure 32. Audit Schedule View - scheduled time view
Work with Audits System: Type options, press Enter 5=Display 6=Print 7=Notification 8=Recoveries 36=Change DG policies 37=Change audit schedule ---------Definition--------DG Name System 1 System 2 EMP AS01 AS02 EMP AS01 AS02 EMP AS01 AS02 EMP AS01 AS02 EMP AS01 AS02 EMP AS01 AS02 EMP AS01 AS02 EMP AS01 AS02 9=Run rule AS01 10=End
Opt __ __ __ __ __ __ __ __
-Scheduled Time-Date Time 09/25/08 02:00:00 09/25/08 02:25:00 09/25/08 02:10:00 09/25/08 02:20:00 09/25/08 02:35:00 09/25/08 02:15:00 09/25/08 02:30:00 09/25/08 02:05:00
Bottom Parameters or command ===> _________________________________________________________________________ F3=Exit F4=Prompt F5=Refresh F10=Audit summary F11=View 2 F17=Sort sched. time F18=Subset F21=Print list F24=More keys
View 1 shows the date and time of the next scheduled audit. Use F11 to view the settings in the Schedule policy.
Figure 33. Audit Schedule View - schedule policy values
Work with Audits System: Type options, press Enter 5=Display 6=Print 7=Notification 8=Recoveries 36=Change DG policies 37=Change audit schedule 9=Run rule AS01 10=End
Opt __ __ __ __ __ __ __ __
Weekday SMTWTFS SMTWTFS SMTWTFS SMTWTFS SMTWTFS SMTWTFS SMTWTFS SMTWTFS SMTWTFS
Rel.Day 12345L
Bottom Parameters or command ===> _________________________________________________________________________ F3=Exit F4=Prompt F5=Refresh F10=Audit summary F11=View 1 F17=Sort sched. time F18=Subset F21=Print list F24=More keys
In both views, the list is initially sorted by rule and data group name.To sort the list by scheduled time, use F17.
103
#OBJATR
sdn_OBJATR
#FILATR
sdn_FILATR
104
Shipped MIMIX rules and schedule for corresponding shipped audit monitor Rule Name #IFSATR Description Compares IFS attributes. Uses the Compare IFS Attributes (CMPIFSA) command. Compares basic file attributes at the member level. Uses the Compare File Attributes (CMPFILA) command. Compares all DLO attributes. Uses the Compare DLO Attributes (CMPDLOA) command. Compares the number of current records (*CURRDS) and the number of deleted records (*NBRDLTRCDS) for physical files that are defined to an active data group. Uses the Compare Record Counts (CMPRCDCNT) command.
Note: Equal record counts suggest but do not guarantee that files are synchronized. This audit does not have a recovery phase. Differences detected by this audit appear as not recovered in the Audit Summary.
#FILATRMBR
sdn_MBRATR
#DLOATR
sdn_DLOATR
#MBRRCDCNT
sdn_RCDCNT
#FILDTA1
Compares file contents. Uses the Compare File Data (CMPFILDTA) command.
sdn_FILDTA
1.
The #FILDTA audit, and the Compare File Data (CMPFILDTA) command require TCP/IP communications.
Note: While you may decide to vary the scheduled times, it is recommended that you always run all audits every day and maintain the same order shown in Table 13.
105
From the MIMIX Availability Status display, use option 5 (Display details) next to Audits and notifications. Then, if necessary, use F10 to access the Schedule view.
2. Type 37 (Change audit schedule) next to the audit you want to change and press Enter. 3. The Set MIMIX Policies (SETMMXPCY) command appears, showing the current policy values for the selected audit rule and data group. Specify the values you want and press Enter.
106
107
108
How policies correlate to function Shipped Values Installation Data Groups Name Varies by rule *INST *INST *INST *INST *INST *INST *INST *INST *INST *INST *INST *INST *INST *INST *INST Yes Yes Yes Yes2 Yes2 Yes Yes Yes *NONE *NONE 9,999,999 Yes Yes Yes Yes Yes Yes Yes *CHGOBJ *NOCHG *END 1440 7 14 *LEVEL30 *MGT Auditing
Data group definition Audit rule Automatic audit recovery Audit notify on success Notification severity Object only on target action Journal attribute differences action1 MIMIX configured higher MIMIX configured lower User journal apply threshold action Maximum rule runtime Audit warning threshold Audit action threshold Audit level Run rule on system Action for running audits1 Inactive data group Apply in threshold Synchronize threshold size
109
How policies correlate to function Shipped Values Installation Data Groups *INST *WEEKLY *NONE *ALL Varies by rule Yes Yes Auditing
CMPRCDCNT commit threshold3 Audit schedule Frequency Scheduled date Scheduled day Scheduled time Relative day of month
1. 2. 3.
*NOMAX
Users will see this policy only on systems running version 5 service pack 5.0.06.00 or higher. These policies are not limited to recovery actions. Users will see this policy only on systems running version 5 service pack 5.0.14.00 or higher.
1. The Action for running audits policy is available on systems running version 5 service pack 5.0.06.00 or higher. Systems running earlier software levels will perform audits regardless of the data group state.
110
a data group has value other than *INST for this policy, that value remains in effect. From MIMIX Availability Manager, the action to change installation policies is only available when the system you are viewing is the management system. Do the following: 1. Ensure that you have the management system selected in the navigation bar. If you are not certain which system is the management system, you can select Services to check. 2. Select Data Groups from the navigation bar. At the top of the window, select the Change Installation Policies action and click . 3. You will see Installation Policy near the top of the window. The current values of policies are displayed. For Action for running audits, do the following: a. Select the value for Inactive data group that indicates the audit actions to permit when the data group is inactive. b. Select the value for Apply in threshold that indicates the audit actions to permit when an apply session reaches its configured warning threshold. 4. To accept the changes, click OK. From a 5250 emulator, do the following from the management system: 1. From the command line type SETMMXPCY and press F4 (Prompt). 2. Verify that the value specified for Data group definition is *INST. 3. Press Enter to see all the policies and their current values. 4. For Action for running audits, do the following: a. Specify the value you want for Inactive data group that indicates the audit actions to permit when the data group is inactive b. Specify the value you want for Apply in threshold that indicates the audit actions to permit when an apply session reaches its configured warning threshold. 5. To accept the changes, press Enter.
To restrict audit activity for a specific data group based on its state
From MIMIX Availability Manager, the action to change policies for a data group is only available when the system you are viewing is the management system. Do the following: 1. Ensure that you have the management system selected in the navigation bar. If you are not certain which system is the management system, you can select Services to check. 2. Select Data Groups from the navigation bar. 3. From the Data Group Status window, select the data group you want from the list. 4. From the Summary area of the display, select the Change Policies action and click .
111
5. The selected data group is listed near the top of the window and current values of its policies are displayed. For Action for running audits, do the following: a. Select the value for Inactive data group that indicates the audit actions to permit when the data group is inactive. b. Select the value for Apply in threshold that indicates the audit actions to permit when an apply session reaches its configured warning threshold. 6. To accept the changes, click OK. From a 5250 emulator, do the following from the management system: 1. From the command line type SETMMXPCY and press F4 (Prompt). 2. For the Data group definition, specify the full three-part name. 3. Press Enter to see all the policies and their current values. 4. For Action for running audits, do the following: a. Specify the value you want for Inactive data group that indicates the audit actions to permit when the data group is inactive b. Specify the value you want for Apply in threshold that indicates the audit actions to permit when an apply session reaches its configured warning threshold. 5. To accept the changes, press Enter.
4. For Audit level, select Disable. 5. For Automatic audit recovery, select Disable. 6. To accept the changes, click OK. From a 5250 emulator, do the following from the management system: 1. From the command line type SETMMXPCY and press F4 (Prompt).
112
2. Verify that the value specified for Data group definition is *INST. 3. Press Enter to see all the policies and their current values. 4. Specify *DISABLED for the Audit level policy. 5. To accept the changes, press Enter.
113
4. Verify that expected data group and rule are listed near the top of the window. If not, close the window and start again. 5. For Frequency, select None. 6. To accept the changes, click OK. From a 5250 emulator, do the following from the management system: 1. From the command line type SETMMXPCY and press F4 (Prompt). 2. For the Data group definition, specify the full three-part name. 3. For Audit rule, specify the name of the MIMIX rule. 4. Press Enter to see the current values for the Audit schedule policy. 5. Specify *NONE for the Frequency prompt. 6. To accept the changes, press Enter.
114
115
b. Select whether to send an informational notification when the rule completes successfully. This value overrides values specified in policies or in the rule itself. c. Select whether the rule should use the policy in effect to determine the system on which it will run. This value is only used when a data group is selected. d. Select a value or specify the name and library of the job description used to submit the request for batch jobs. Default values are to use the first MXAUDIT job description found in the library list. 5. To run the rule or rule group, click OK.
116
Typically, this procedure should be performed from the system and installation where you wan the rule to run. Do the following: 1. On a command line, type RUNRULE and press F4 (Prompt). The Run Rule (RUNRULE) display appears. 2. At the Rule name prompt, specify the rule names for the rules you want to run. You can specify up to 100 rules to run from the command. 3. At the Data group definition prompt, specify the value you want. The default is *NONE, but you can specify that rules be run against an individual data group or all data groups. 4. Press F10 for additional parameters. 5. At the Notification severity prompt, specify the severity level to assign to the notification that is sent if the rule ends in error. This value overrides values specified in policies or in the rule itself. For a MIMIX rule, the default value *DFT is the same as the value *POLICY, where the Notification severity policy in effect determines the severity of the notification. For a user rule, *DFT is the same as the value *RULE, where the rule determines the severity of the notification. 6. At the Notification on success prompt, specify whether you want the rule to generate a notification when the specified rule ends successfully. This value overrides values specified in policies or in the rule itself. For a MIMIX rule, the default value *DFT is the same as *POLICY, where the Audit notify on success policy in effect determines whether a notification is sent. If the policy is set for both the installation and for the data group, the data group value is used. For a user rule, *DFT is the same as the value *RULE, where the value specified in the rule determines whether a notification is sent. 7. At the Use run rule on system policy prompt, specify whether the rule should use the policy in effect when run.This value is only used when a data group is selected. The default value *NO will run the rule on the local system. 8. At the Job description and Library prompts, specify the name and library of the job description used to submit the batch request. The default value, MXAUDIT, submits the request using the default job description, MXAUDIT. 9. To run the rule, press Enter.
117
group or all data groups. 4. Press F10 for additional parameters. 5. At the Notification severity prompt, specify the severity level to assign to the notification that is sent if a rule in the group ends in error. This value overrides values specified in policies or in the rule itself. For a MIMIX rule group, the default value *DFT is the same as the value *POLICY, where the Notification severity policy in effect determines the severity of the notification. For a user rule, *DFT is the same as the value *RULE, where the rule determines the severity of the notification. 6. At the Notification on success prompt, specify whether you want the rule to generate a notification when the specified rules end successfully. This value overrides values specified in policies or in the rule itself. For a MIMIX rule, the default value *DFT is the same as *POLICY, where the Audit notify on success policy in effect determines whether a notification is sent. If the policy is set for both the installation and for the data group, the data group value is used. For a user rule, *DFT is the same as the value *RULE, where the value specified in the rule determines whether a notification is sent. 7. At the Use run rule on system policy prompt, specify whether each rule should use the policy in effect when run.This value is only used when a data group is selected. The default value *NO will run the rule on the local system. 8. At the Job description and Library prompts, specify the name and library of the job description used to submit the batch request. The default value, MXAUDIT, submits the request using the default job description, MXAUDIT. 9. To run the rule group, press Enter.
118
CHAPTER 4
Because the manner in which notifications are generated can vary, it is important to note that notifications can represent both real-time events as well as events that occurred in the past but, due to scheduling, are being reported in the present. For example, the ownership of a file is changed on the target system at 8:00 PM. If your
119
audit (CMPFILA) is scheduled to run at 1:00 AM, MIMIX will detect the change and push a notification to the user interface when the audit completes. Previously, detection of the change was contingent upon you viewing a report after the audit completed and noticing the difference. Recoveries - The term recovery is used in two ways. The most common use refers to the recovery action taken by MIMIX AutoGuard to correct a detected difference when automatic recovery polices are enabled. The second use refers to a temporary report that provides details about a recovery action in progress. The report is automatically created when the recovery action starts and is removed when it completes. While it exists, the report identifies what originated the action and what is being acted upon, and may include access to an associated output file (outfile) and the job log for the associated job. The action which generated a report may also generate a notification when the recovery action ends.
Displaying notifications
You can check for notifications from either user interface. Note: Notifications from audits are automatically set to a status of acknowledged. Audit status and results should be checked from the Audit Summary window or the Work with Audits (WRKAUD) display. From MIMIX Availability Manager, if there are any new notifications, an icon appears next to the Notifications item in the Details area of the navigation bar. To see a list of notifications or select a notification to view, do the following: 1. Select Notifications from the Details area in the navigation bar. 2. The upper right corner of the Notifications window contains fields showing the number of new and acknowledged notifications for the installation and system you are viewing. 3. Below the toolbar, the notifications are separated into two lists, New and Acknowledged. Expand or collapse the lists as needed. 4. To see details for a notification, select the Display Details action and click From a 5250 emulator, do one of the following: If there are no audit problems in the installation, the MIMIX Availability Status display will indicate whether there are any notifications requiring attention or immediate action that are from sources other than audits. From the MIMIX Availability Status display, type a 5 (Display details) next to Audits and notifications and press Enter. Notifications from all sources are listed on the Work with Notifications display. To access the Work with Notifications display, enter the command WRKNFY. The list is sorted so that new notifications appear at the top. To see details for a notification, type a 5 (Display) next to the notification you want and press Enter. The Work with Data Groups display includes the number of new notifications that require action or attention. From the MIMIX Availability Status display, type 5 (Display details) next to Replication. The Work with Data Groups display appears. The Audit/Recov./Notif. fields are located in the upper right corner. .
120
Displaying notifications
121
Detailed information
When you display a notification, you see its description, status, severity, data group, source, and sender as described above. You also have access to the following information: Details - When the source of the notification is a rule, this identifies the command that was initiated by the rule. When the source of the notification is user-generated, this indicates the notification detail text specified when the notification entry was added. When the source of the notification is a monitor, this describes the events that resulted in the notification. Output File - If available, this identifies an associated output file. Output file information associated with a notification is only available from the sender system. For user-generated notifications, output file information is available only if it was specified when the notification was added. Job - If available, this identifies the job that generated the notification. Job information associated with a notification is only available from the sender system. For usergenerated notifications, this information is available only if it was specified when the notification was added.
Display Details
5=Display 6=Print
Output File1
8=View results
Job Log1
12=Display job
122
Displaying notifications
Table 15.
Options available for notifications WRKNFY Option 46=Acknowledge 47=Mark as new Description Sets the selected notification status to *ACK (Acknowledged). Sets the selected notification status to *NEW (New). Displays details of the rule that generated the notification, including the substitution variables for the command the rule initiated. This action is only available for notifications generated by a rule.
1. 2.
This action may also be available for a notification from the Notification Details window. MIMIX manages an output file associated with a notification from an automatically recovery action or a MIMIX rule when the output file exists in a specific library. The format of the library name for such an output file is MIMIX-installation-library_0.
123
124
Displaying recoveries
Displaying recoveries
Active recoveries are an indication of problems detected and being corrected by MIMIX AutoGuard. Before certain activity, such as ending MIMIX, it is important that no recoveries are in progress in the installation. You can check for recoveries from either user interface. From MIMIX Availability Manager, if there are any recoveries in progress, an icon appears next to the Recoveries item in the Details area of the navigation bar. Recoveries are automatically generated and removed by a recovery action initiated by automatic functions within replication processes and audits. To see a list of recoveries or select a recovery to view, do the following: 1. Select Recoveries from the Details area in the navigation bar. 2. The upper right corner of the Recoveries window contains fields showing the number of active and held recoveries for the installation and system you are viewing. 3. To see details for a recovery, select the Display Details action and click .
From a 5250 emulator, you can see how many recoveries are in progress from the MIMIX Availability Status display or the Work with Data Groups display. The Work with Recoveries display lists recoveries and provides options for working with held recoveries associated with an audit or a MIMIX rule. To see a count of recoveries in progress, do one of the following To access the MIMIX Availability Status display, enter the command WRKMMXSTS. The Recoveries field in the upper right corner of the display shows the number of active recoveries in progress for the installation. To access the Work with Data Groups display, use option 5 (Display details) next to the Replication area.
Figure 34 shows the Audits/Recov./Notif. fields in the upper right corner of the Work with Data Groups display. The first number is the total number of audits that require action to correct a problem or require your attention to prevent a situation from becoming a problem. The second number indicates the number of active recoveries, including those resulting from audits. The third number indicates the number of new notifications that require action or attention. If more than 999 items exist in any field, the field will display +++. A consistently high number of recoveries suggests that there may be configuration issues with one or more data groups. To select a recovery to view or work with a held recovery, do the following: 1. To access the Work with Recoveries display, do one of the following: From the Work with Audits display, use option 8 (Recoveries) to see a list of recoveries associated with an audit. From the Work with Data Groups display, use F8 to see all recoveries. On a command line, enter the command WRKRCY.
2. To see details for a recovery, type a 5 (Display) next to the recovery you want and
125
press Enter.
Figure 34. Work with Data Groups display showing recoveries in progress
CHICAGO 10:49:06 Type options, press Enter. Audits/Recov./Notif.: 001 / 002 / 003 5=Display definition 8=Display status 9=Start DG 10=End DG 12=Files not active 13=Objects in error 14=Active objects 15=Planned switch 16=Unplanned switch ... ---------Source----------------Target--------ErrorsOpt Data Group System Mgr DB Obj DA System Mgr DB Obj DB Obj __ TESTDG34 LONDON A A A CHICAGO A A A __ TESTDG43 LONDON A A A CHICAGO A A A Work with Data Groups
F3=Exit F10=Legend
Bottom F5=Refresh F7=Audits F8=Recoveries F9=Automatic refresh F16=DG definitions F23=More options F24=More keys
126
Displaying recoveries
Date - Indicates the date the recovery process started. Time - Indicates the time the recovery process started. Source - Identifies the process, program, or command that generated the recovery. Names that begin with the character # are generated by automatic recovery actions for audits or database replication or by a MIMIX rule. Names that begin with the characters ## are generated by automatic recovery actions for object replication. Sender or From System - Identifies the system from which the recovery originated.
Detailed information
When you display a recovery, you see its description, status, data group, source, and sender as described above. You also have access to the following information. Details - When the source of the recovery is a rule, this identifies the command run by the rule in an attempt to recover from the detected error. Output File - If available, this identifies an associated output file that lists the detected errors the recovery is attempting to correct. Output file information associated with a recovery is only available from the sender system. Job - If available, this identifies the job that is performing the recovery action. Job information associated with a recovery is only available from the sender system.
Display Details
5=Display 6=Print
Output File1
8=View progress
127
Table 16.
Options available for recoveries WRKRCY Option 10=End job Description Ends an active recovery job. This action is valid for recoveries with names that begin with # and is only available from the system on which the recovery job is running. Displays the job log for the recovery job associated in progress. This option is only available from the system on which the recovery job is running. In MIMIX Availability Manager, the job is displayed in the Job Log window. Places an active recovery job on hold. This action is valid for recoveries with names that begin with # and is only available from the system on which the recovery job is running. Releases a held recovery job. This action is valid for recoveries with names that begin with # and is only available from the system on which the recovery job is held. Displays details of the rule that generated the recovery, including the substitution variables for the command the rule initiates. This action is available for recoveries generated by audit activity.
Job Log1
12=Display job
Hold Job
13=Hold job
Release Job
14=Release job
Rule Details1
1.
This action may also be available for a notification from the Recovery Details window.
Orphaned recoveries
There are times when recoveries exist but are no longer associated with a job. The following conditions could cause recoveries to become orphaned: An unplanned switch has occurred The MIMIX subsystem was ended unexpectedly A recovery job was ended unexpectedly
When automatic audit recovery is enabled, orphaned recoveries are converted to error notifications during system cleanup. If the orphaned recovery is older than the cleanup time specified in the system definition, it is deleted. When automatic database recovery or automatic object recovery is enabled, orphaned recoveries are deleted, when possible. Because recoveries are displayed on both systems, but jobs associated with them are only accessible from the originating system, you need to verify that the recovery is orphaned before removing it.
128
Displaying recoveries
identified in the Sender column on the Recoveries window. You may need to change Preferences to view the Sender column. 3. For the recovery in question, select the Display Details action and click .
4. From the Recovery Details window, locate the Job information. Then do the following as needed: If you see the message Job not available on the system. Job available on originating system only, select the correct system from the navigation bar. Then start this procedure again. If you see the message No job information available the recovery is orphaned. Go to Removing an orphaned recovery on page 129. If a job name is displayed, click on the name. The job information is displayed in the Job Log window. If the job is no longer available, you should see the message No data available, which confirms that the recovery is orphaned. Go to Removing an orphaned recovery on page 129
From a 5250 emulator, do the following to determine whether a recovery is orphaned: 1. From the iSeries command line, type WRKRCY and press Enter. 2. Press F11 to display the Timestamp view. This view allows you to see the From System column which lists the system from which the recovery originated. 3. Ensure you are operating from the originating system. Then type a 12 next to the recovery. 4. Do one of the following: If an error message is displayed indicating that the job associated with the recovery is not found, follow the steps in Removing an orphaned recovery on page 129. When the Display Job display appears, type a 10 in the Selection field and press Enter. The status of the job is displayed. If the job associated with the recovery is no longer valid, follow the steps in Removing an orphaned recovery on page 129.
129
From a 5250 emulator, do the following to remove an orphaned recovery: 1. From the originating system, type WRKRCY on the command line and press Enter. 2. After you have ensured that the recovery is orphaned, type a 4 next to the orphaned recovery you wish to remove and press Enter. 3. Press Enter to confirm your request to remove the recovery.
130
CHAPTER 5
MIMIX uses a number of processes to perform replication. These processes, along with a number of supporting processes must be active to enable MIMIX to function. All of these processes are usually started initially during configuration. Two sets of commands provide the ability to start and stop replication, as follows: The Start MIMIX (STRMMX) and End MIMIX (ENDMMX) commands will start or stop replication processes as well as all supporting processes for the products in a MIMIX installation library in a single operation. These commands are the preferred method for starting and ending MIMIX. The Start Data Group (STRDG) and End Data Group (ENDDG) commands will start or stop data group replication processes.
This chapter provides information about using either set of commands. The following topics are included: Choices when starting replication on page 133 describes the STRMMX and STRDG commands and considerations for using either command. Considerations for starting data groups on page 135 describes considerations and options for using the STRDG command, including setting a new synchronization point by clearing pending and error entries and setting the audit level on objects. Choices when ending replication on page 141 describes the ENDMMX and ENDDG commands and considerations that are common to both commands, such as when to perform a controlled end or when to end the RJ link. Considerations for ending data groups on page 146 describes general information you should know about the behavior of the ENDDG command. Starting MIMIX on page 147 provides a procedure for using the STRMMX command. Ending MIMIX on page 147 provides procedures for using the ENDMMX command and describes when you may also need to end the MIMIX subsystem. STRMMX and ENDMMX messages on page 149 describes the messages returned by these commands. Starting selected data group processes on page 150 provides a procedure using the STRDG command. Ending selected data group processes on page 151 provides a procedure using the ENDDG command. Ending a data group in a controlled manner on page 152 provides procedures for preparing to end, ending, and confirming that the end completed without problems. What replication processes are started by the STRDG command on page 155 describes which replication processes are started with each possible value of the Start processes (PRC) parameter. Both data groups configured for remote
131
journaling and data groups configured for MIMIX source-send processing are addressed. What replication processes are ended by the ENDDG command on page 159 describes what replication processes are ended with each possible value for the End Options (PRC) parameter. Both data groups configured for remote journaling and data groups configured for MIMIX source-send processing are addressed.
132
Considerations for either command: Before using either STRMMX or STRDG to start replication, consider the following: Before you start data group replication, the database files and objects must be synchronized between the systems defined to the data group. For more information about performing the initial synchronization, see the MIMIX Reference book. If you are using the MIMIX for MQ function, you must use the procedures in the MIMIX for IBM WebSphere MQ book for initial synchronization and initial start of data groups that replicate data for IBM WebSphere MQ. Data groups that are in a disabled state are not started. For more information, see Disabling and enabling data groups on page 232.
133
Master monitor - Starts the master monitor on each of the specified systems. Monitors - On each of the specified systems, the master monitor starts monitors that are not disabled and which are configured to start with the master monitor. Application groups - Starts Cluster Services for all specified systems that use clustering. Also starts any application groups and their associated data groups. Note: The STRMMX command does not start promoter group activity. Start promoter group activity using procedures in the Using MIMIX Promoter book.
134
Starting a data group may take longer if the remote journal function is operating in catchup mode. In addition to the considerations described in Choices when starting replication on page 133, the following considerations apply to using the STRDG command: MIMIX determines which data group replication processes to start based on the value you specify on the Start processes (PRC) parameter. This is fully described in What replication processes are started by the STRDG command on page 155. You can optionally specify the point at which to start replication in the journal receivers. The parameters for database and object journal receivers and sequence numbers provide this capability. You may need to use these parameters when starting data groups for the first time, or when starting a data group in which you have been using the MIMIX CDP feature. For user journal replication, the IBM i remote journal function controls where processing starts in the source journal receiver. The values specified for the Database journal receiver (DBJRNRCV) and Database large sequence number (DBSEQNBR2) identify the starting location for the database reader process and the database apply process. For system journal replication, the value specified for Object journal receiver (OBJJRNRCV) and Object large sequence number (OBJSEQNBR2) identify the starting location for the object send process and the object apply process. Note: The parameters Database sequence number (DBSEQNBR) and Object sequence number (OBJSEQNBR) continue to be valid for journal definitions which specify *MAXOPT2 for the Receiver size option (RCVSIZEOPT) and for values that do not exceed 10 digits. To ensure continued compatibility, the use of parameters DBSEQNBR2 and OBJSEQNBR2 is recommended.
135
There are times when you may need to establish a new synchronization point for a data group by clearing the backlog for the apply processes and clearing identified errors in processing. Topic When to clear pending entries and entries in error on page 136 describes when you may need to start a data group with a new synchronization point. The STRDG command provides the ability to change the object audit level of existing objects configured for replication before starting replication. For more information see Setting the audit level when starting a data group on page 140.
Reason for Resetting Data Group After synchronizing database files and objects between two systems.
After switching the direction of the data group, when starting replication on the system that now becomes the source system. After changing the Number of DB apply sessions (NBRDBAPY) parameter on the data group definition
Specify *YES for the Clear pending prompt. Specify *CLRPND or *YES for the Clear error prompt. Specify *YES for the Clear pending prompt.
136
stored in the journal log space. Clear pending resets the starting point for all data group file entries and object entries. Clear error clears the hold log spaces. MIMIX prevents a start request that specifies CLRPND(*YES) from running if there are open commit cycles present. Instead, message LVE387F is issued. Table 18 shows the processing that occurs based on the selection made for the Clear pending (CLRPND) and Clear error (CLRERR) prompts. The Clear pending and Clear error prompts work independently. For example, when CLRPND(*NO) is selected, no clear pending processing occurs.
Table 18. CLRPND *NO CLRPND and CLRERR processing CLRERR *NO Processing Description Data groups start with regular processing: Data group file entry status remains unchanged. Hold logs remain unchanged. The value selected for the CLRPND parameter is used for CLRERR. Same processing as CLRPND(*NO) CLRERR(*NO). Data group file entries in *HLDERR, *HLDRGZ, *HLDRNM, *HLDPRM, and *HLDRLTD status are cleared. Tracking entries in *HLDERR status are cleared. Hold log space is deleted.
Note: CLRPND(*YES) will not start a data group when there are open commit cycles on files defined to the data group.
Notes
*NO
*CLRPND
*NO
*YES
*YES
*NO
Data group file entries in *HLDRGZ, *HLDRNM, and *HLDPRM status are cleared and reset to active. Data group tracking entries in *HLDRNM are cleared and reset to active. Data group file entries and tracking entries in *HLDERR status remain unchanged. If there is a requested status at the time of starting, it is cleared. Journal, hold, tracking entry hold, and apply history log spaces are deleted. The apply session to which data group file entries are assigned may change.
See File entry apply session assignment See Single apply session processing See Log spaces
137
Notes See File entry states See File entry apply session assignment See Single apply session processing See Log spaces
Data group file entries in *HLDERR, *HLDRGZ, *HLDRNM, *HLDPRM, and *HLDRLTD status are cleared and reset to active. Tracking entries in *HLDERR and *HLDRNM status are cleared and reset to active. If there is a requested status at the time of starting, it is cleared. Journal, hold, and apply history log spaces are deleted. The apply session to which data group file entries are assigned may change. Data group file entry status in *HLDRTY remains unchanged. *YES *CLRPND
Note: CLRPND(*YES) will not start a data group when there are open commit cycles on files defined to the data group.
The value selected for the CLRPND parameter is used for CLRERR. Same processing as CLRPND(*YES) CLRERR(*YES).
See File entry states See File entry apply session assignment See Single apply session processing See Log spaces
File entry states: Files in specific states will not reset to active when you specify *YES on the Clear Error prompt. If you have set data group file entries to any of these states, the following process exception applies:
Note: The only states that can be set using the Set Data Group File Entry (SETDGFE) command are *HLD, *RLSWAIT, *ACTIVE, and *HLDIGN. All other states are the result of internal processing.
*HLD - Journal entries cached before *YES is specified are discarded. If *ALL or *ALLSRC is specified on the Start processes prompt, all subsequent entries from the specified starting point will be cached again. *RLSWAIT - Journal entries are discarded as they wait for the synchronization point to arrive in the journal stream. This occurs regardless of the value specified for Clear Error or Clear Pending. *HLDIGN - Journal entries are discarded until the file status is changed to something else. *HLDSYNC - Journal entries are ignored since an external process is actively synchronizing the file. When that event completes normally, the file is set to *RLSWAIT. File entry apply session assignment: Clear pending processing attempts to load balance the data group file entries among the defined apply sessions. If the requested apply session in the data group file entry definition is *ANY, or if it is *DGDFT and the requested apply session for the data group definition is *ANY, then the apply session to which the data group file entry is assigned may be changed when processing occurs. For data groups configured to replicate through the user journal, the requested apply session may be ignored to ensure that related files are handled by the same apply session.
138
Single apply session processing: In most situations, you will perform clear pending processing on all apply sessions belonging to a data group by specifying *ALL or *DBALL on the Start processes (PRC) prompt. MIMIX also supports the ability to perform clear pending processing on a single apply session, which is useful for recovery purposes in certain error situations. To perform clear pending processing on a single apply session, specify PRC(*DBAPY) and the specific apply session (APYSSN). Log spaces: Because they have not been applied, journal entries that exist in the journal log space are considered pending. Journal entries that exist in the hold log space, however, are considered in error. The Clear pending and Clear error prompts affect which log spaces are deleted (and recreated) when a data group is started.
139
Note: If you are upgrading from a previous version and you have user programs that use the STRDG command you should recompile those programs and specify an option for the SETAUD parameter. For example, you may have an automated switch program that uses the STRDG command. Refer to the STRDG command help text for assistance with setting the audit levels for objects that are replicated by MIMIX. You should be aware of how the processing order for data group entries can affect the auditing value of IFS objects. For examples and for information about manually specifying the audit level of objects, see the MIMIX Reference book.
140
The reason you need to end MIMIX activity determines which command is the best choice to use. Table 19 lists common reasons for ending and the appropriate command to use. Depending on why you are ending replication, you may need to choose values other than the defaults.
Table 19. Choosing the appropriate command to end replication Use Command ENDMMX ENDMMX The save request may not be able to save all the files or objects if they are opened or locked by MIMIX. See controlled end information in Ending immediately or controlled on page 143. Also end the RJ link Also end the RJ link Let MIMIX Switch Assistant or your MIMIX Model Switch Framework end replication. See Ending selected data group processes on page 151. The changes are not available to active replication processes until the data group processes are ended and restarted. Additional Information
Reason for Ending Replication Ending communications for any reason Performing a full save and restore of data that is defined to MIMIX
Preparing to update MIMIX software Performing an IPL of either system Upgrading the operating system release on either system Performing a switch in preparation for performing maintenance on either system Ending only a selected replication process Changing configuration, such as adding or changing data group entries
141
Table 19.
Choosing the appropriate command to end replication Use Command ENDDG Additional Information The save request may not be able to save all the files or objects if they are opened or locked by MIMIX. You may be able to end only processes on the target system. See Ending selected data group processes on page 151.
Considerations when choosing a command: Both ENDMMX and ENDDG commands support options for how processes are ended and for ending the remote journal link. Answering the following questions will help you determine which commands and options are appropriate. Do processes need to end in a controlled manner or can they be ended immediately? Both commands support these options. For more information, see Ending immediately or controlled on page 143 Do you need to end only a subset of the replication processes? Only ENDDG supports ending selected processes. For more information see Ending all or selected processes on page 144. Does the RJ link also need to end? For data groups that use remote journaling you may also choose whether to end the RJ link. In most cases, the RJ link can remain active. For more information, see When to end the RJ link on page 144.
142
the specified systems. Master monitor - Ends the master monitor on each of the specified systems. MIMIX Promoter - Ends promoter group activity on the specified systems. Audits and Recoveries - All queued audits, all audits in progress, and all recoveries in progress, that are associated with the specified systems are ended. This includes jobs with locks on the installation library. Queued audits and audits in comparison phase revert to their previous state. Audits in recovery phase reflect the state of processing at the time of the end request, which may be Not recovered. Note: Cluster services is not ended when MIMIX managers end because cluster services may be necessary for other applications.
143
A data group that is ended in a controlled manner is enabled for a more effective and safer start when the start request specifies to clear pending entries. The existence of commit cycles implies that there is application activity on the source system that should not be interrupted; replication should be allowed to continue through the end of the commit cycle. It is preferable to ensure that commit cycles are resolved or removed before ending a data group. When open commit cycles exist, a data group cannot be started with a request to clear pending entries. The open commit cycles must be resolved before pending entries can be cleared during a start request. If the request to perform a controlled end also includes ending the RJ link, the RJ link is ended after all requested processes end. Either type of end request may be ignored if the request is submitted just before the time that MIMIX jobs are restarted daily. For more information about restarting jobs, see Configuring restart times for MIMIX jobs in the MIMIX Reference book.
144
The RJ link can normally remain active unless you have a need to prevent data from being sent to the target system. Some situations where you need to end the RJ link include: Following a switch, to prevent data from returning to the system on which it originated (round-tripping), and to reduce communications and DASD usage Before performing an IPL on either the source system or target system Before upgrading the IBM i release on either the source system or the target system Before performing a hardware upgrade
145
146
Starting MIMIX
Starting MIMIX
To start all MIMIX products within an installation library, do the following: 1. If you are starting MIMIX for the first time or starting MIMIX after a system IPL, do the following: a. Use the command WRKSBSJOB SBS(MIMIXSBS)to verify that the MIMIX subsystem is running. If the MIMIXSBS is not already active, start the subsystem using the STRSBS SBS(MIMIXQGPL/MIMIXSBS)command. b. If MIMIX uses TCP/IP for system communication, the TCP/IP servers must be running. If TCP/IP is not already active, start TCP/IP using the port number defined in the transfer definitions and the procedures described in Starting the TCP/IP server on page 222. 2. Do one of the following: From the MIMIX Basic Main Menu, select option 2 (Start MIMIX) and press Enter. From the MIMIX Availability Status display, press F13 (Start MIMIX). From a command line type STRMMX and press Enter.
3. The Start MIMIX (STRMMX) display appears. Accept the default value for the System definition prompt and press Enter. 4. If you see a confirmation display, press Enter to start MIMIX.
Ending MIMIX
For most configurations, It is recommended that you end MIMIX products from the management system, which is usually the backup system. If your installation is configured so that the backup system is a network system, you should end MIMIX from the network system. Note: If you are ending MIMIX for a software upgrade or to install a service pack, use the procedures in the softwares ReadMe document. To end MIMIX, use the following procedures: 1. Use one of the following procedures: Ending with default values on page 147 Ending by prompting the ENDMMX command on page 148
2. Complete any needed follow-up actions using the information and procedures in After you end MIMIX products on page 148.
147
From the MIMIX Basic Main Menu, select option 3 (End MIMIX) and press Enter. You will see a confirmation display. From the MIMIX Availability Status display, press F17 (End MIMIX). You will see a confirmation display.
2. From the confirmation display, you can press F1 (Help) to see a description of the default values that will be used. To end MIMIX, press Enter,
To check for active entries, use the command WRKDGACTE STATUS(*ACTIVE). When to also end the MIMIX subsystem - You will also need to end the MIMIX subsystem when you need to IPL the system, when upgrading MIMIX software, and when installing a MIMIX software service pack. The MIMIX subsystem must be ended from the 5250 emulator. To end the subsystem, do the following: 1. Log out of MIMIX Availability Manager.
148
Note: Other MIMIX Availability Manager users should also be instructed to log out. 2. From the 5250 emulator, enter LAKEVIEW/ENDMMXAM. 3. Enter the command WRKSBS. The Work with Subsystems display appears. 4. Type an 8 (Work with subsystem jobs) next to subsystem MIMIXSBS and press Enter. 5. End any remaining jobs in a controlled manner. Type a 4 (End) next to the job and press F4 (Prompt). The How to end (OPTION) parameter should have a value of *YES. Press Enter. If you see a confirmation display, press Enter to continue. 6. Press F12 (Cancel) to return to the Work with Subsystems display. 7. Type a 4 (End subsystem) next to subsystem MIMIXSBS and press Enter.
149
To selectively start processes for a data group, do the following: 1. From the Work with Data Groups display, type a 9 (Start DG) next to the data group that you want to start and press Enter. 2. The Start Data Group (STRDG) display appears. At the Start processes prompt, specify the value for the processes you want to start. To see a list of values, press F4 (Prompt). Note: When you are starting a data group for the first time, specify *ALL. 3. Press Enter. 4. Additional prompts appear. For most situations, you should accept the default values. If you need to establish a new synchronization point, use Table 17 on page 136 to determine the correct values to specify for the Clear pending and Clear error prompts. If you are submitting this command for batch processing, you should specify *NO for the Show confirmation screen prompt.
150
To selectively end processes for a data group, do the following: 1. From the Work with Data Groups display, type a 10 (End DG) next to the data group that you want to end and press Enter. 2. The End Data Group (ENDDG) display appears. At the Process prompt, specify the value for the processes you want to end. To see a list of values, press F4 (Prompt). 3. At the End process prompt, specify the value you want. 4. If the data group uses remote journaling, verify that the value of the End remote journaling prompt is what you want. 5. If you want to end only a selected apply session, press F10 (Additional parameters). Then specify the value for the session you want to end at the Apply session prompt. 6. To end the selected processes, press Enter.
151
Note: Only information for the type of information replicated by the data group appears on the status displays. For example, if the data group does not contain database files, you will only see fields for object information. 3. For data groups which replicate from the user journal, you also need to check for any files that are held for other reasons. Press F8 (Database). The Held for other reasons field In the upper right of the Data Group Database Status display should also be 0 before you end the data group. A non-zero value may or may not prevent the end request from completing. For more information, see topics Working with files in error on page 170.
152
4. Because you specified *CNTRLD in Step 2, you can also use the Wait Time (WAIT) parameter to specify how long MIMIX should try to end the selected processes in a controlled manner. Use F1 (Help) to see additional information about the possible options. Specify *SBMRQS to submit a request to end the data groups. The appropriate actions are issued to end the specified processes and control is returned to the caller immediately. When you specify this value, the TIMOUTOPT parameter (Step 5) is ignored. Specify *NOMAX. When you specify this value, MIMIX will wait until all specified MIMIX processes are ended. Specify a numeric value (number-of-seconds). MIMIX waits the specified time for a controlled end to complete before using the option specified in the TIMOUTOPT parameter.
5. If you specified a numeric value for the WAIT parameter in Step 4, you can also use the Timeout Option (TIMOUTOPT) parameter. You can specify what action you want the ENDDG command to perform if the time specified in the WAIT parameter is reached: The current process should quit and return control to the caller (*QUIT). A new request should be issued to end all processes immediately (*ENDIMMED). When this value is specified, pending activity entries may still exist after the data group processes are ended. An inquiry message should be sent to the operator notifying of a possible error condition (*NOTIFY). If you specify this value, the command must be run from the target system.
153
Apply. If there are open commit cycles and you restart using CLRPND(*YES), you may lose these transactions. To verify commit cycles, do the following: a. Press F8 (Database) to view the Data Group Detail Status display. b. For each apply session listed, verify that the value shown in the Open Commit column at the right side of the display will be blank. c. If open commit cycles exist, restart the data group. You must take action to resolve the open commit cycles, such as ending or quiescing the application or closing the commit cycle. Then repeat the controlled end again.
154
Table 20 identifies the processes that are started when MIMIX RJ support is used for database replication for each of the possible values on the PRC parameter. An RJ link identifies the IBM i remote journal function, which transfers data to the target system. On the target system, the data is processed by the MIMIX database reader (DBRDR) before the database apply process (DBAPY) completes replication. For data groups that use MIMIX RJ support, it is standard practice to leave the RJ link active when the data groups are ended. If the RJ link is not already active when starting data groups, MIMIX starts the RJ link when the value specified for the PRC parameter includes database source system processes or all processes. The RJ Link column in Table 20 shows the result of each process when the RJ link is not active while the Notes column identifies behavior that may not be anticipated when the RJ link is already active.
155
Processes started by data groups configured for MIMIX Remote Journal support. This assumes that all replication processes are inactive when the STRDG request is made. Notes Source Processes DB replication RJ Link 1 Object replication OBJSND Starts Starts Inactive Inactive2 Starts Inactive2 Inactive2 Starts Inactive Inactive2 Inactive2 OBJRTV Starts Starts Inactive Inactive2 Starts Inactive2 Inactive2 Starts Inactive Inactive2 Inactive2 CNRSND Starts Starts Inactive Inactive2 Starts Inactive2 Inactive2 Starts Inactive Inactive2 Inactive2 STSRCV Starts Starts Inactive Inactive2 Starts Inactive2 Inactive2 Starts Inactive Inactive2 Inactive2 Target Processes DB replication DBRDR Starts Inactive Starts Starts Inactive3 Inactive Starts Inactive3 Inactive3 Starts Inactive3 DBAPY Starts Inactive Starts Starts Inactive 3 Inactive Starts Inactive3 Inactive3 Inactive Starts3 Object replication OBJRCV Starts Starts Inactive Inactive2 Starts Inactive2 Inactive2 Starts Inactive Inactive2 Inactive2 CNRRCV Starts Starts Inactive Inactive2 Starts Inactive2 Inactive2 Starts Inactive Inactive2 Inactive2 STSSND Starts Starts Inactive Inactive2 Starts Inactive2 Inactive2 Starts Inactive Inactive2 Inactive2 OBJAPY Starts Inactive Starts Inactive2 Starts Inactive2 Inactive2 Inactive Starts Inactive2 Inactive2
*ALL *ALLSRC *ALLTGT *DBALL *OBJALL *DBSRC *DBTGT *OBJSRC *OBJTGT *DBRDR *DBAPY Notes:
E A, E A, B A, E A, C A, C, E A, B A, C A, C A, D A, C
Starts1 Starts1 Inactive1 Starts1 Inactive1 Starts1 Inactive1 Inactive1 Inactive1 Inactive1 Inactive1
A. Data groups which use cooperative processing should have both database and object processes started to prevent objects and data on the target system from becoming not fully synchronized. B. When the RJ link is already active, database replication becomes operational. C. When the RJ link is already active, database journal entries continue to transfer to the target system over the RJ link D. When the RJ link is already active, database journal entries continue to transfer to the target system over the RJ link, where they will be processed by the DBRDR. E. If data group data area entries are configured, the data area polling process also starts when values which start database source processes are selected.
1. This column shows the effect of the specified value on the RJ link when the RJ link is not active. See the Notes for the effect of values when the RJ Link is already active, which is default behavior.
156
2. 3.
These object replication processes are not available in data groups configured for database-only replication. These database replication processes are not available in data groups configured for object-only replication.
Optionally, data groups can use source-send technology instead of remote journaling for database replication. Data groups created on earlier levels of MIMIX may still be configured this way. Table 21 identifies the processes that are started by each value for Start processes when source-send technology is used for database replication. The MIMIX database send (DBSND) process and database receive (DBRCV) process replace the IBM i remote journal function and the DBRDR process, respectively.
Table 21. Value for PRC Processes started by data groups configured for Source Send replication This assumes that all replication processes are inactive when the STRDG request is made. Notes Source Processes DB replication DBSND 1 *ALL *ALLSRC *ALLTGT *DBALL *OBJALL *DBSRC *DBTGT *OBJSRC *OBJTGT *DBRDR 4 *DBAPY Notes: A. Data groups which use cooperative processing should have both database and object processes started to prevent objects and data on the target system from becoming not fully synchronized. A A A A A A A A A Starts 1 Starts 1 Inactive Starts 1 Inactive 3 Starts 1 Inactive Inactive3 Inactive3 Inactive3 Object replication OBJSND Starts Starts Inactive Inactive2 Starts Inactive2 Inactive2 Starts Inactive Inactive2 Inactive2 OBJRTV Starts Starts Inactive Inactive2 Starts Inactive2 Inactive2 Starts Inactive Inactive2 Inactive2 CNRSND Starts Starts Inactive Inactive2 Starts Inactive2 Inactive2 Starts Inactive Inactive2 Inactive2 STSRCV Starts Starts Inactive Inactive2 Starts Inactive2 Inactive2 Starts Inactive Inactive2 Inactive2 Target Processes DB replication DBRCV Starts Starts Inactive Starts Inactive3 Starts Inactive Inactive3 Inactive3 Inactive3 DBAPY Starts Inactive Starts Starts Inactive3 Inactive Starts Inactive3 Inactive3 Starts 3 Object replication OBJRCV Starts Starts Inactive Inactive2 Starts Inactive2 Inactive2 Starts Inactive Inactive2 Inactive2 CNRRCV Starts Starts Inactive Inactive2 Starts Inactive2 Inactive2 Starts Inactive Inactive2 Inactive2 STSSND Starts Starts Inactive Inactive2 Starts Inactive2 Inactive2 Starts Inactive Inactive2 Inactive2 OBJAPY Starts Inactive Starts Inactive2 Starts Inactive2 Inactive2 Inactive Starts Inactive2 Inactive2
157
1. 2. 3. 4.
When the database send (DBSND) process starts, the data area polling process also starts. These object replication processes are not available in data groups configured for database-only replication. These database replication processes are not available in data groups configured for object-only replication The database reader (*DBRDR) process is not used by data groups configured for source-send replication.
158
Table 22 identifies the processes that are ended by each value for End options when MIMIX RJ support is used for database replication. An RJ link identifies the IBM i remote journal function, which transfers data to the target system. On the target system, the data is processed by the MIMIX database reader (DBRDR) before the database apply process (DBAPY) completes replication. The communications defined by the RJ link remains active and is not affected by any value for End options. In most cases, leaving the RJ link active is preferable. If necessary, you can end the RJ link by changing value for End remote journaling (ENDRJLNK parameter). When to end the RJ link on page 144 describes when you need to end the RJ link.
159
Processes ended by data groups configured for MIMIX Remote Journal support. This assumes that all replication processes are active when the ENDDG request is made and that the request does not specify to end the RJ link. Notes Source Processes DB replication RJ Link 1 Object replication OBJSND Ends Ends Active Active 2 Ends Active 2 Active 2 Ends Active Active 2 Active 2 OBJRTV Ends Ends Active Active 2 Ends Active 2 Active 2 Ends Active Active 2 Active 2 CNRSND Ends Ends Active Active 2 Ends Active 2 Active 2 Ends Active Active 2 Active 2 STSRCV Ends Ends Active Active 2 Ends Active 2 Active 2 Ends Active Active 2 Active 2 Target Processes DB replication DBRDR Ends Active Ends Ends Active 3 Active Ends Active 3 Active 3 Ends Active DBAPY Ends Active Ends Ends Active 3 Active Ends Active 3 Active 3 Active Ends Object replication OBJRCV Ends Ends Active Active 2 Ends Active 2 Active 2 Ends Active Active 2 Active 2 CNRRCV Ends Ends Active Active 2 Ends Active 2 Active 2 Ends Active Active 2 Active 2 STSSND Ends Ends Active Active 2 Ends Active 2 Active 2 Ends Active Active 2 Active 2 OBJAPY Ends Active Ends Active 2 Ends Active 2 Active 2 Active Ends Active 2 Active 2
*ALL *ALLSRC *ALLTGT *DBALL *OBJALL *DBSRC *DBTGT *OBJSRC *OBJTGT *DBRDR *DBAPY Notes:
E A, E B, E A, B A, B, E B A, B A, B B, C B, D
Active1 Active1 Active1 Active1 Active1 Active1 Active1 Active1 Active1 Active1 Active1
A. Has no effect on database-only replication. New database journal entries continue to transfer to the target system over the RJ link, where they will be processed. B. Data groups that use cooperative processing may be affected by the result of this value. Ending database processes while object processes remain active may result in object activity entries being placed on hold. Similarly, ending object processes while database processes remain active may result in files being placed on hold due to error. C. New database journal entries continue to transfer to the target system over the RJ link. Existing entries stored in the log space on the target system before the end request was processed will be applied. D. New database journal entries continue to transfer to the target system over the RJ link, where they will be processed by the DBRDR. E. The data area polling process ends when values which end database source processes are specified.
160
1. 2. 3.
The RJ link is not ended by the End options (PRC) parameter. New database journal entries continue to transfer to the target system over the RJ link. See the Notes column for additional details. These object replication processes are not available in data groups configured for database-only replication. These database replication processes are not available in data groups configured for object-only replication.
Optionally, data groups can use source-send technology instead of remote journaling for database replication. Data groups created on earlier levels of MIMIX may still be configured this way. Table 23 identifies the processes that are ended by each value for End options when source-send technology is used for database replication. The MIMIX database send (DBSND) process and database receive (DBRCV) process are replaced by the IBM i remote journal function and the DBRDR process, respectively.
Table 23. Value for PRC Processes ended by data groups configured for Source Send replication This assumes that all replication processes are active when the ENDDG request is made. Notes Source Processes DB replication DBSND 1 *ALL *ALLSRC *ALLTGT *DBALL *OBJALL *DBSRC *DBTGT *OBJSRC *OBJTGT Notes: A. Data groups that use cooperative processing may be affected by the result of this value. Ending database processes while object processes remain active may result in object activity entries being placed on hold. Similarly, ending object processes while database processes remain active may result in files being placed on hold due to error. 161 A A A A A A Ends 1 Ends 1 Active Ends 1 Active 3 Ends 1 Active Active 3 Active 3 Object replication OBJSND Ends Ends Active Active 2 Ends Active 2 Active 2 Ends Active OBJRTV Ends Ends Active Active 2 Ends Active 2 Active 2 Ends Active CNRSND Ends Ends Active Active 2 Ends Active 2 Active 2 Ends Active STSRCV Ends Ends Active Active 2 Ends Active 2 Active 2 Ends Active Target Processes DB replication DBRCV Ends Ends Active Ends Active 3 Ends Active Active 3 Active 3 DBAPY Ends Active Ends Ends Active 3 Active Ends Active 3 Active 3 Object replication OBJRCV Ends Ends Active Active 2 Ends Active 2 Active 2 Ends Active CNRRCV Ends Ends Active Active 2 Ends Active 2 Active 2 Ends Active STSSND Ends Ends Active Active 2 Ends Active 2 Active 2 Ends Active OBJAPY Ends Active Ends Active 2 Ends Active 2 Active 2 Active Ends
Processes ended by data groups configured for Source Send replication This assumes that all replication processes are active when the ENDDG request is made. Notes Source Processes DB replication DBSND 1 Object replication OBJSND Active 2 Active 2 OBJRTV Active 2 Active 2 CNRSND Active 2 Active 2 STSRCV Active 2 Active 2 Target Processes DB replication DBRCV Active 3 DBAPY Ends 3 Object replication OBJRCV Active 2 Active 2 CNRRCV Active 2 Active 2 STSSND Active 2 Active 2 OBJAPY Active 2 Active 2
Active 3
A. Data groups that use cooperative processing may be affected by the result of this value. Ending database processes while object processes remain active may result in object activity entries being placed on hold. Similarly, ending object processes while database processes remain active may result in files being placed on hold due to error.
1. 2. 3. 4. When the database send (DBSND) process ends, the data area polling process also ends. These object replication processes are not available in data groups configured for database-only replication. These database replication processes are not available in data groups configured for object-only replication The database reader (*DBRDR) process is not used by data groups configured for source-send replication.
162
CHAPTER 6
You may also need to use problem determination procedures in this chapter. Note: The procedures in this chapter are primarily for use with a 5250 emulator. The following topics are included in this chapter: Working with MIMIX managers on page 164 describes how to start, stop, and resolve problems with the system manager and journal manager. Working with message queues on page 167 describes how to use the MIMIX primary and secondary message queues from a 5250 emulator. Working with the message log on page 168 describes how to access the MIMIX message log from either user interface. Working with user journal replicated files on page 170 includes topics for how to resolve a file that is held due to an error. It also includes topics about options for placing a file on hold and releasing held files. Working with tracking entries on page 179 describes how to use tracking entries to resolve replication errors for IFS objects, data areas, or data queues that are replicated cooperatively with the user journal. It also includes topics about options for placing a tracking entry on hold and releasing held tracking entries. Working with objects in error on page 185 describes how to resolve objects in error by working with the data group activities used for system journal replication. This topic includes information about how to retry failed activity entries and how to determine whether MIMIX is automatically attempting to retry an activity. Removing data group activity history entries on page 190 describes how to manually remove completed entries for system journal replication activity. This may be necessary if you need to conserve disk space.
163
From a 5250 emulator, a problem with a system or journal manager is reflected on the MIMIX Availability Status display and the Work with Systems display. To troubleshoot, do the following: 1. Do one of the following to access the Work with Systems display: From the MIMIX Basic Main Menu, select option 1 (Availability status) and press Enter. If the Services area on the resulting Work with Availability Status display identifies a problem with a manager, use type a 9 (Troubleshoot) next to Services and press Enter. From MIMIX Intermediate Main Menu, select option 2 (Work with Systems) and press Enter.
2. The Work with Systems display appears. The first system definition in the list is for the local system. The status of the system manager and journal manager for the local system should be *ACTIVE. Most installations will not be licensed for Vision Cluster1 and should have *NONE for the Cluster Services status. Note: If the system manager status is *ACTREQ and you want to do more problem isolation, use option 7 (Display status) to view the status of each pair of jobs between systems. This is useful when resolving problems for a
164
management system. 3. Type a 9 (Start) next to the system definition you want and press Enter. 4. The Start MIMIX Managers display appears. Any managers that are not running on the system will be selected to start. To submit the request, press Enter.
3. The Start MIMIX Managers display appears. By default, any manager that is not running will be selected to start. Specify the value for the type of manager you want to start at the Manager prompt and press Enter. From a 5250 emulator, to selectively start a system manager or journal manager for a system, do the following 1. From the MIMIX Availability Status screen, use option 5 (Display details) next to the Services bar. 2. The Work with Systems display appears. Type a 9 (Start) next to the system definition you want and press Enter. 3. The Start MIMIX Managers display appears. By default, any manager that is not running will be selected to start. Specify the value for the type of manager you want to start at the Manager prompt and press Enter.
3. The End MIMIX Managers display appears. Specify the value for the type of manager you want to end at the Manager prompt and press Enter. The selected managers are ended. From a 5250 emulator, to end a system manager or journal manager, do the following: 1. From the MIMIX Availability Status screen, use option 5 (Display details) next to the Services bar. 2. The Work with Systems display appears with a list of the system definitions defined for the MIMIX installation. Type a 10 (End) next to the system definition you want and press Enter. 3. The End MIMIX Managers display appears. Specify the value for the type of manager you want to end at the Manager prompt and press Enter. The selected
165
166
167
2. The Work with Message Log appears with a list of the current messages. The initial view shows the message ID and text. 3. Press F11 to see additional views showing the message type, severity, the product and process from which it originated, whether it is associated with a group (for MIMIX, a data group), and the system on which it originated. 4. You can subset the messages shown on the display. A variety of subsetting options are available that allow you to manage the message log more efficiently. 5. To work with a message, type the number of the option you want and press Enter. The following options are available: 4=Remove - Use this option if you want to delete a message. When you select this option, a confirmation display appears. Verify that you want to delete the
168
messages shown and press Enter. The message is deleted only from the local system. 5=Display message - Use this option to view the full text of the first level message and gain access to the second level text. 6=Print - Use this option to print the information for the message. 8=Display details - Use this option to display details for a message log entry including its from and to program information, job information, group information, product, process, originating system, and call stack information. 9=Related messages - Use this option to display a list of messages that relate to the selected message. Related messages include a summary and any detail messages immediately preceding it. This can be helpful when you have a large message log list and you want to show the messages for a certain job. 12=Display job - If job information exists on the system, you can use this option to access job information for a message log entry. The Work with Jobs display appears from which you can select options for displaying specific information about the job.
169
3. The Data Group Details - Activity window opens to display file activity for the data group that is experiencing replication problems. Files that are held due to an error are highlighted in red. The preferred action is displayed in the Action list. Note: If additional errors with higher priorities exist for the file, the preferred action displayed in the Action list will be for the highest priority error. 4. Select the action you want from the Action list and click .
In a 5250 emulator, file replication errors are reported in the DB Errors column on the Work with Data Groups display.
170
To access a list of files in error for a data group, do the following: 1. From the MIMIX Basic Main Menu select option 1 (Availability status) and press Enter. The MIMIX Availability Status display appears. 2. Use option 5 (Display details) next to Replication. The Work with Data Groups display appears. 3. The DB Errors column identifies whether a data group has any files held due to errors, as well as any cooperatively processed IFS objects, data areas, and data queues that are on held due to errors. Files on hold for other reasons are not reflected in this column. Notes: To determine if there are files on hold for other reasons, use the procedure in Working with the detailed status of data groups on page 61. For information about cooperatively processed IFS objects, data areas, and data queues, see Working with tracking entries on page 179.
4. Type 12 (Files not active) next to the data group you want and press Enter. 5. The Work with DG File Entries display appears with a list of the file entries in error for the data group you selected. Significant capability is available for addressing common replication problems and journaling problems. Do the following: a. Use F10 to toggle between views showing status, journaling status, database apply session in use, and the journal entry and error code. b. Any entry with a status of *HLD, *HLDERR, *HLDIGN or *HLDRLTD indicates that action is required. Use Table 24 to identify choices based on the file entry status. c. Use options identified in Table 25 to address journaling or replication problems. 6. If necessary, take action to prevent the error from happening again. Refer to the following topics: Correcting file-level errors on page 176 Correcting record-level errors on page 177
Possible actions based on replication status of a file entry Preferred Action1 Unless an error has occurred, no action is necessary. Entries in the user journal for the file are replicated and applied. If necessary, any of the options to hold journal entries can be used. User action is required to release the file entry (option 26) so that held journal entries from the user journal can be applied to the target system. User action is required. Attempt to resolve the error by synchronizing the file (option 16).
*HLD *HLDERR
171
Possible actions based on replication status of a file entry Preferred Action1 User action is required to either synchronize the file (option 16) or to change the configuration if you no longer want to replicate the file. Journal entries for the file are discarded. Replication is not occurring and the file may not be synchronized. Depending on the circumstances, Release may also be an option. These are transitional states that should resolve to *ACTIVE. If these status persist, check the journaling status for the entry. MIMIX retains log spaces for the held journal entries for the duration of these temporary hold requests. The file entry is held because an entry could not be applied due to a condition which required waiting on some other condition (such as inuse). After a short delay, the database apply job will automatically attempt to process this entry again. The preferred action is to allow MIMIX to periodically retry the file entry. By default, the database apply job will automatically attempt to process the entry every 5 minutes for up to 1 hour. Manually releasing the file entry will cause MIMIX to attempt to process the entry immediately User action is required for a file in the same network. View the related files (option 35). A file that is related due to a dependency, such as a constraint or a materialized query table, is held. Resolving the problem for the related held file will resolve this status. The file is waiting to be released by the DB apply process and will be changed to *ACTIVE. If the status does not change to *ACTIVE, check the journaling status. If this status persists, you may need to synchronize (option 16). These are transitional states that should resolve automatically. The file entry represents a member that is being processed cooperatively between the CMPFILDTA command and the database apply process.
*HLDRLTD
*RLSWAIT
Options for working with file entries from the Work with DG FIle Entries display Additional Information See Starting journaling for physical files on page 195. See Ending journaling for physical files on page 196. See Verifying journaling for physical files on page 197. See topic Synchronizing database files in the MIMIX Reference book.
172
Options for working with file entries from the Work with DG FIle Entries display Additional Information See topic Working with journal transactions for files in error on page 173. See topic Placing a file on hold on page 174. See topic Ignoring a held file on page 174. See topic Releasing a held file at a synchronization point on page 175. See topic Releasing a held file on page 176. See topic Releasing a held file and clearing entries on page 176. Available for entries with a status of *HLDERR that identify a member. See topic Comparing and repairing file data - members on hold (*HLDERR) in the MIMIX Reference book.
20=Work with file error entries 23=Hold file 24=Ignore file 25=Release wait 26=Release 27=Release clear 31=Repair member data 35=Work with related files
173
b. Select the option (Table 26) you want to use on the journal transaction:
Table 26. 2=Change Options available from the Work with DG FE on Hold display. You can change the contents or characteristics of the journal entry. Use this option with caution. Any changes can affect the validity of data in the journal entry. You can delete the journal entry. You can display details for the specified journal entry associated with the data group file entry in question. You can immediately apply a transaction that has caused a file to go on hold. The entry you selected is immediately applied to the file outside of the apply process. If the apply is successful, the error/hold entry that was applied is removed from the error/hold log. However, if the apply fails, a message is issued and the entry remains in the error/hold log. This process does not release the file; it only applies the selected entry.
174
Note: Be certain that you want to use the ignore feature. Any ignored transactions cannot be retrieved. You must replace the object on the target system with a current version from the source system. If a file has been on hold for a long time or you expect that it will be, the amount of storage used by the error/hold log space can be quite large. If you anticipate that you will need to save and restore the file or replace it for any other reason, it may be best to just ignore all current transactions. Do the following: 1. From the MIMIX Basic Main Menu select option 1 (Availability status) and press Enter. The MIMIX Availability Status display appears. 2. Use option 5 (Display details) next to Replication. The Work with Data Groups display appears. 3. Type 17 (File entries) next to the data group you want and press Enter. 4. The Work with DG File Entries display appears. Type 24 (Ignore file) next to the entry you want and press Enter. The status of the file is changed to *HLDIGN. The file entry is ignored. Journal entries for the file entry, including any hold logs, are discarded.
175
176
A discrepancy in the file descriptions between the management and network systems An operational error.
This topic identifies the most common file-level errors and measures that you can take to prevent the problem from recurring. See also Correcting record-level errors on page 177. Once you diagnose and correct a file-level error, the problem rarely manifests itself again. Some of the most common file-level errors are: Authority: The MIMIXOWN user profile defined in the MIMIX job description does not have authority to perform a function on the target system. You can prevent this problem by ensuring that the MIMIXOWN user profile has all object authority (*ALLOBJ). This guarantees that the user profile has all the necessary authority to run IBM i commands and has the ability to access the library and files on the management system. Refer to the License and Availability Manager book for more information about the MIMIXOWN user profile and authority. Objects existence or corruption: MIMIX cannot run a function against a file on the target system because the file or a supporting object (such as logical files) does not exist or has become damaged. System security is the only way to prevent an object from being accidentally deleted from the target system. Make sure that only the correct personnel have the ability to remove objects from the target system where replicated data is applied. Also, ensure that application programs do not delete files on the target system when there are no apply sessions running. MIMIX subsystem ended: If the MIMIX subsystem is ended in an immediate mode while MIMIX processes are still active, files may be placed in a Held status. This is a result of MIMIX being unable to complete a transaction normally. After MIMIX is restarted, you only need to release the affected files.
177
entries) are skipped on the send system. Common reasons why records are written in error include the following: Journaling was ended: When journaling is ended, transaction images are not being collected. If users update the files while journaling is not running, no journal entries are created and MIMIX DB Replicator has no way of replicating the missing transactions. The best way to prevent this error is to restrict the use of the Start Journaling Physical File (STRJRNPF) and End Journaling Physical File (ENDJRNPF) commands. User journal replication was restarted at the wrong point: When you change the starting point of replication for a data group, it is imperative that transactions are not skipped. Apply session restarted after a system failure: This is caused when the target system experiences a hard failure. MIMIX always updates its user spaces with the last updated and sent information. When a system fails, some information may not be forced to disk storage. The data group definition parameter for database apply processing determines how frequently to force data to disk storage. When the apply sessions are restarted, MIMIX may attempt to rewrite records to the target system database. Unable to write/update a record: This error is caused when MIMIX cannot access a record in a file. This is usually caused when there are problems with the logical files associated with the file or when the record does not exist. The best way to prevent this error is to make sure that replication is started in the correct position. This error can also be due to one of the problems listed in topic Correcting file-level errors on page 176. Unable to delete a record: This is caused when MIMIX is trying to delete a record that does not exist or has a corrupted logical file associated with the physical file. This error can also be due to one of the problems listed in topic Correcting file-level errors on page 176.
178
5. The Data Group Details - Activity window opens for the type of tracking entry you selected. Only tracking entries that are experiencing replication problems are displayed.
179
MIMIX customizes the list of actions available for each tracking entry displayed so that only actions that are applicable can be selected. The preferred action is listed first in the available list. Online help provides additional information about the available actions.
Select Option 50=IFS trk entries 51=IFS trk entries not active 52=Obj trk entries 53=Obj trk entries not active
4. The tracking entry display you selected appears. Significant capability is available for addressing common replication problems and journaling problems. Do the following: a. Use F10 to toggle between views showing status, journaling status, and the database apply session in use. b. Any entry with a status of *HLD, *HLDERR or *HLDIGN indicates that action is required. The identified object remains in this state until action is taken. Statuses of *HLD and *HLDERR result in journal entries being held but not applied. Use Table 28 to identify choices based on the tracking entry status.
180
Possible actions based on replication status of a tracking entry Preferred Action1 Unless an error has occurred, no action is necessary. Entries in the user journal for the IFS object are replicated and applied. If necessary, any of the options to hold journal entries can be used. User action is required to release the entry (option 26) so that held journal entries from user journal can be applied to the target system. User action is required. Attempt to resolve the error by synchronizing the file (option 16). User action is required to either synchronize the object (option 16) or to change the configuration if you no longer want to replicate the object. Journal entries for the object are discarded. Replication is not occurring and the object may not be synchronized. Depending on the circumstances, Release may also be an option. This is a transitional state for IFS tracking entries that should resolve to *ACTIVE. If this status persists, check the journaling status for the entry. Object tracking entries cannot have this status. If the status does not change to *ACTIVE, you may need to synchronize (option 16)
*HLDRNM
*RLSWAIT
1.
Options for working with tracking entries Additional Information See Removing a tracking entry on page 184 Identifies an object, its replication status, journaling status, and the database apply session used. Creates a spooled file which can be printed See Starting journaling for IFS objects on page 198 and Starting journaling for data areas and data queues on page 201. See Ending journaling for IFS objects on page 199 and Ending journaling for data areas and data queues on page 202. See Verifying journaling for IFS objects on page 200 and Verifying journaling for data areas and data queues on page 203.
181
Options for working with tracking entries Additional Information Synchronizes the contents, attributes, and authorities of the object represented by the tracking entry between the source and target systems. For more information, see topic Synchronizing tracking entries in the MIMIX Reference book. See Holding journal entries associated with a tracking entry on page 182. See Ignoring journal entries associated with a tracking entry on page 182. See Waiting to synchronize and release held journal entries for a tracking entry on page 183. See Releasing held journal entries for a tracking entry on page 183. See Releasing and clearing held journal entries for a tracking entry on page 184.
16=Synchronize
182
anticipate that you will need to save and restore the object or replace it for any other reason, it may be best to just ignore all current transactions. Do the following: 1. Access the IFS or object tracking entry display as described in Accessing the appropriate tracking entry display on page 180. 2. Type 24 (Ignore) next to the tracking entry for the object you want and press Enter.
Waiting to synchronize and release held journal entries for a tracking entry
Use this procedure to wait for a synchronization point to release any held journal entries for an object identified by a tracking entry, then resume replication. The request changes the tracking entry status to *RLSWAIT. Any journal entries for the associated IFS object, data area, or data queue are discarded until an object saved journal entry is encountered. This is the synchronization point. The tracking entry status is then changed to *ACTIVE and all journal entries that were held after the synchronization point are applied. If the object saved journal entry is not in the log space, the tracking entry remains in *RLSWAIT status. If you are unsure as to how many save requests might accumulate for an object, you can synchronize the object associated with the tracking entry. The tracking entry status will become *ACTIVE. Do the following: 1. Access the IFS or object tracking entry display as described in Accessing the appropriate tracking entry display on page 180. 2. Type 25 (Release wait) next to the tracking entry for the object you want and press Enter.
183
184
Table 30.
4=Remove
For more information, see Removing data group activity history entries on page 190. 7=Display message 8=Retry Use this option to display any error message that is associated with the entry. Use this option to retry the data group activity. MIMIX changes the entry status to pending and attempts the failed operation again.
Note: It is possible to schedule the request for a time when the retry is more likely to be successful. For more information about retrying failed entries, see Retrying data group activity entries on page 188.
185
Table 30.
Options on the Work with Data Group Activity display for working with objects in error. Use this option to access the Work with DG Activity Entries display. From the display you can display additional information about replicated journal transactions for the object, including the journal entry type and access type (if available), as well as see whether the object is undergoing delay retry processing. You can also take options to display related entries, view error messages for a failure, and synchronize the object. For more information, see Using the Work with DG Activity Entries display on page 186. Use this option to remove an entry with a status of *FAILED and any related entries that have a status of *DELAYED. You may need to take action to synchronize the object associated with the entry.
14=Remove related
4=Remove
5=Display
Use this option display details about the individual entry. The information available about the object includes whether the object is undergoing delay retry processing, and journal entry information, including access type information for T-SF, T-YC, and T-ZC journal entry types. For more information, see Determining whether an activity entry is in a delay/retry cycle on page 189 Use this option to print the entry. Use this option to display the error message associated with the processing failure for the entry. Use this option to retry the data group activity entry. MIMIX changes the entry status to pending and attempts the failed operation again as soon as possible.
186
Table 31.
Options available on the Work with DG Activity Entries display. Displays entries related to the specified object. For example, use this option to see entries associated with a move or rename operation for the object. Displays the job that was processing the object when the error occurred, if the still job information exists and is on this system. Use this option to synchronize objects defined to MIMIX for system journal replication (objects that are not configured for cooperative processing). Activity entries with *ACTIVE or *COMPLETED status can be synchronized, as well as entries with a *FAILED status and with the following journal types: T-CO, T-CP, T-OR, T-SE, T-ZC (see notes), T-YC, and T-SF (see notes). A confirmation display allows you to confirm your choices before the request is processed. Entries are placed in a pending synchronization status. When the data group is active, the contents of the object, its attributes, and its authorities are synchronized between the source and target systems. The status of the activity entry is set to completed by synchronization. Notes: To synchronize files defined for cooperative processing, use the Synchronize DG File Entry (SYNCDGFE) command. Spooled files (T-SF journal entries) with the following access types can be synchronized: C = spooled file created; U = spooled file changed. Changed objects (T-ZC journal entries) with the following access types can be synchronized: 1 (Add); 7 (Change); 25 (Initialize); 29 (Merge); 30 (Open); 34 (Receive); 36 (Reorganize); 50 (Set); and 51 (Send).
9=Display related
187
3. On the Retry DG Activity Entries (RTYDGACTE) display, specify a value for the Time of day to retry prompt. Then press Enter. You can specify a specific time within 24 hours. The scheduled time is based on the time on the system from which the request is submitted regardless of the system on which the activity to retry occurs. When you submit a retry request for a scheduled time, MIMIX will make the entry active and will wait until the specified time before retrying the request. The scheduled time is the earliest the request will be processed. Be sure to consider any time zone differences between systems as you determine a scheduled time. For additional information and examples, press F1 (Help). 4. The Confirm Retry of DG Activity display appears. Press Enter. If failed activity entries occur frequently, consider using the third delay retry cycle. When the Automatic object recovery policy is enabled, a third retry cycle is performed
188
using the settings in effect from the Number of third delay/retries and Third retry interval (min.) policies. These policies can be set for the installation or for a specific data group.
189
3. To change the selection criteria, do the following as needed: To remove a subset of completed entries for the selected object based on the timestamp of the replicated journal entries, specify values for Starting date and time and Ending date and time prompts. To expand the set of objects for which completed entries will be removed, change the values of the following prompts as needed: For an expanded set of object types, use the Object type prompt. For a library based object, use the Object and Library prompts. For a DLO, use the Document and Folder prompts. For an IFS object use the IFS object prompt. For a spooled file, use the Spooled file name, Output queue, and Library prompts. 4. A confirmation display appears. Press Enter.
190
CHAPTER 7
191
192
TABLE statement is automatically journaled if the library in which it is created contains a journal named QSQJRN. New *FILE, *DTAARA, *DTAQ objects - The operating system will automatically journal a new object if it is created in a library that contains a QDFTJRN data area and the data area has enabled automatic journaling for the object type. The default value (*DFT) for the Journal at creation (JRNATCRT) parameter in the data group definition enables MIMIX to create the QDFTJRN data area in a library and enable the data area for automatic journaling for an object type. When the data group is started, MIMIX evaluates all data group object entries for each object type. (Entries for *FILE objects are only evaluated when the data group specifies COOPJRN(*USRJRN).) Entries properly configured to allow cooperative processing of the object type determine whether MIMIX will create the QDFTJRN data area. MIMIX uses the data group entry with the most specific match to the object type and library that also specifies *ALL for its System 1 object (OBJ1) and Attribute (OBJATR). When the QDFTJRN data area in a library is enabled for an object type, all new objects of that type are journaled, not just those which are eligible for replication. Note: MIMIX prevents the QDFTJRN data area from being created the following libraries: QSYS*, QRECOVERY, QRCY*, QUSR*, QSPL*, QRPL*, QRCL*, QRPL*, QGPL, QTEMP and SYSIB*. For example, if MIMIX finds only the following data group object entries for library MYLIB, it would use the first entry when determining whether to create the QDFTJRN data area because it is the most specific entry that also meets the OBJ1(*ALL) and OBJATR(*ALL) requirements. The second entry is not considered in the determination because its OBJ1 and OBJATR values do not meet these requirements.
LIB1(MYLIB) OBJ1(*ALL) OBJTYPE(*FILE) OBJATR(*ALL) COOPDB(*YES) PRCTYPE(*INCLD) LIB1(MYLIB) OBJ1(MYAPP) OBJTYPE(*FILE) OBJATR(DSPF) COOPDB(*YES) PRCTYPE(*INCLD)
193
If you use the IBM commands (STRJRNPF, STRJRN, STRJRNOBJ) to start journaling, the user ID that performs the start journaling request must have the appropriate authority requirements.
For journaling to be successfully started on an object, one of the following authority requirements must be satisfied: The user profile of the user attempting to start journaling for an object must have *ALLOBJ special authority. The user profile of the user attempting to start journaling for an object must have explicit *ALL object authority for the journal to which the object is to be journaled. Public authority (*PUBLIC) must have *OBJALTER, *OBJMGT, and *OBJOPR object authorities for the journal to which the object is to be journaled.
If you attempt to start journaling for a data group file entry, IFS tracking entry, or object tracking entry and the files or objects associated with the entry are already journaled, MIMIX checks that the physical file, IFS object, data area, or data queue is journaled to the journal associated with the data group. If the file or object is journaled to the correct journal, the journaling status of the data group file entry, IFS tracking or object tracking entry is changed to *YES. If the file or object is not journaled to the correct journal or the attempt to start journaling fails, an error occurs and the journaling status is changed to *NO.
194
3. The Start Journal Entry (STRJRNFE) display appears. The Data group definition prompts and the System 1 file prompts identify your selection. Accept these values or specify the values you want.
195
4. Specify the value you want for the Start journaling on system prompt. Press F4 to see a list of valid values. When *DGDFN, *SRC, or *TGT is specified, MIMIX considers whether the data group is configured for journaling on the target system (JRNTGT) and starts or prevents journaling from starting as required. 5. If you want to use batch processing, specify *YES for the Submit to batch prompt. 6. To start journaling for the physical file associated with the selected data group, press Enter. The system returns a message to confirm the operation was successful.
3. The End Journal File Entry (ENDJRNFE) display appears. If you want to end journaling for all files in the library, specify *ALL at the System 1 file prompt. 4. Specify the value you want for the End journaling on system prompt. Press F4 to see a list of valid values. When *DGDFN, *SRC, or *TGT is specified, MIMIX considers whether the data group is configured for journaling on the target system (JRNTGT) and ends or prevents journaling from ending as required. 5. If you want to use batch processing, specify *YES for the Submit to batch prompt. 6. To end journaling, press Enter.
196
3. The Verify Journaling File Entry (VFYJRNFE) display appears. The Data group definition prompts and the System 1 file prompts identify your selection. Accept these values or specify the values you want. 4. Specify the value you want for the Verify journaling on system prompt. When *DGDFN is specified, MIMIX considers whether the data group is configured for journaling on the target system (JRNTGT) when determining where to verify journaling. 5. If you want to use batch processing, specify *YES for the Submit to batch prompt 6. Press Enter.
197
198
4. The Start Journaling IFS Entries (STRJRNIFSE) display appears. The Data group definition and IFS objects prompts identify the IFS object associated with the tracking entry you selected. You cannot change the values shown for the IFS objects prompts1. 5. Specify the value you want for the Start journaling on system prompt. Press F4 to see a list of valid values. When *DGDFN, *SRC, or *TGT is specified, MIMIX considers whether the data group is configured for journaling on the target system (JRNTGT) and starts or prevents journaling from starting as required. 6. To use batch processing, specify *YES for the Submit to batch prompt and press Enter. Additional prompts for Job description and Job name appear. Either accept the default values or specify other values. 7. The System 1 file identifier and System 2 file identifier prompts identify the file identifier (FID) of the IFS object on each system. You cannot change the values2. 8. To start journaling on the IFS objects specified, press Enter.
3. The End Journaling IFS Entries (ENDJRNIFSE) display appears. The Data group definition and IFS objects prompts identify the IFS object associated with the tracking entry you selected. You cannot change the values shown for the IFS objects prompts1. 4. Specify the value you want for the End journaling on system prompt. Press F4 to see a list of valid values. When *DGDFN, *SRC, or *TGT is specified, MIMIX considers whether the data group is configured for journaling on the target system (JRNTGT) and ends or
1. When the command is invoked from a command line, you can change values specified for the IFS objects prompts. Also, you can specify as many as 300 object selectors by using the + for more values prompt. 2. When the command is invoked from a command line, use F10 to see the FID prompts. Then you can optionally specify the unique FID for the IFS object on either system. The FID values can be used alone or in combination with the IFS object path name.
199
prevents journaling from ending as required. 5. To use batch processing, specify *YES for the Submit to batch prompt and press Enter. Additional prompts for Job description and Job name appear. Either accept the default values or specify other values. 6. The System 1 file identifier and System 2 file identifier identify the file identifier (FID) of the IFS object on each system. You cannot change the values shown2. 7. To end journaling on the IFS objects specified, press Enter.
3. The Verify Journaling IFS Entries (VFYJRNIFSE) display appears. The Data group definition and IFS objects prompts identify the IFS object associated with the tracking entry you selected. You cannot change the values shown for the IFS objects prompts1. 4. Specify the value you want for the Verify journaling on system prompt. Press F4 to see a list of valid values. When *DGDFN is specified, MIMIX considers whether the data group is configured for journaling on the target system (JRNTGT) and verifies journaling on the appropriate systems as required. 5. To use batch processing, specify *YES for the Submit to batch prompt and press Enter. Additional prompts for Job description and Job name appear. Either accept the default values or specify other values. 6. The System 1 file identifier and System 2 file identifier identify the file identifier (FID) of the IFS object on each system. You cannot change the values shown2. 7. To verify journaling on the IFS objects specified, press Enter. Using file identifiers (FIDs) for IFS objects on page 236.
200
4. The Start Journaling Obj Entries (STRJRNOBJE) display appears. The Data group definition and Objects prompts identify the object associated with the
201
tracking entry you selected. Although you can change the values shown for these prompts, it is not recommended unless the command was invoked from a command line. 5. Specify the value you want for the Start journaling on system prompt. Press F4 to see a list of valid values. When *DGDFN, *SRC, or *TGT is specified, MIMIX considers whether the data group is configured for journaling on the target system (JRNTGT) and starts or prevents journaling from starting as required. 6. To use batch processing, specify *YES for the Submit to batch prompt and press Enter. Additional prompts for Job description and Job name appear. Either accept the default values or specify other values. 7. To start journaling on the objects specified, press Enter.
3. The End Journaling Obj Entries (ENDJRNOBJE) display appears. The Data group definition and IFS objects prompts identify the object associated with the tracking entry you selected. Although you can change the values shown for these prompts, it is not recommended unless the command was invoked from a command line. 4. Specify the value you want for the End journaling on system prompt. Press F4 to see a list of valid values. When *DGDFN, *SRC, or *TGT is specified, MIMIX considers whether the data group is configured for journaling on the target system (JRNTGT) and ends or prevents journaling from ending as required. 5. To use batch processing, specify *YES for the Submit to batch prompt and press Enter. Additional prompts for Job description and Job name appear. Either accept the default values or specify other values. 6. To end journaling on the objects specified, press Enter.
202
3. The Verify Journaling Obj Entries (VFYJRNOBJE) display appears. The Data group definition and Objects prompts identify the object associated with the tracking entry you selected. Although you can change the values shown for these prompts, it is not recommended unless the command was invoked from a command line. 4. Specify the value you want for the Verify journaling on system prompt. Press F4 to see a list of valid values. When *DGDFN is specified, MIMIX considers whether the data group is configured for journaling on the target system (JRNTGT) and verifies journaling on the appropriate systems as required. 5. To use batch processing, specify *YES for the Submit to batch prompt and press Enter. Additional prompts for Job description and Job name appear. Either accept the default values or specify other values. 6. To verify journaling on the objects specified, press Enter.
203
Switching
CHAPTER 8
Switching
Switching is when you temporarily reverse the roles of the systems. The original source system (production) becomes the temporary target system and the original target system (backup) becomes the temporary source system. When the scenario that required you to switch directions is resolved, you typically switch again to return the systems to their original roles. This chapter provides information and procedures to support switching. The following topics are included: About switching on page 204 provides information about switching with MIMIX including best practice and reasons why a switch should be performed. Subtopics describe: The role of MIMIX Model Switch Framework within switching What is a planned switch and requirements for a planned switch What is an unplanned switch and actions to be completed after the failed source system is recovered How to set policies associated with switching, including compliance thresholds and the default model switch framework How to change the audit level policy to ensure the most complete comparison is performed when auditing before switching Switching using MIMIX Switch Assistant on page 212 describes how to use this tool in MIMIX Availability Manager. Switching from the MIMIX Basic Main Menu on page 212. describes how to switch from a 5250 emulator. Determining when the last switch was performed on page 215 describes how to check the Last switch field which indicates the switch compliance status and provides the date when the last switch was performed. Problems checking switch compliance on page 216 describes problems that can occur with data for the Last switch field. Performing a data group switch on page 217 describes how to switch a single data group using the SWTDG command. Switch Data Group (SWTDG) command on page 219 provides background information about the SWTDG command, which is used in all switch interfaces.
About switching
Replication environments rarely remain static. Therefore, best practice is to perform regular switches to ensure that you are prepared should you need to perform one during an emergency.
204
About switching
MIMIX supports two methods for switching the direction in which replication occurs for a data group. These methods are known as a planned switch and an unplanned switch. You may need to perform a switch for any of the following reasons: The production system becomes unavailable due to an unplanned outage. A switch in this scenario is unplanned. You need to perform hardware or software maintenance on the production system. Typically, you can schedule this in advance so the switch is planned. You need to test your recovery plan. This activity is also a planned switch.
There are three phases to a complete switch: switch to the backup system, synchronize the systems when the production is ready to use, and switch back to the production system. Switching data groups is only a part of performing a switch. Best practice for switching includes performing regular switches. Best practice also includes performing all audits with the audit level set at level 30 immediately prior to a planned switch to the backup system and before switching back to the production system. For performing the switch, best practice is to use the MIMIX Switch Assistant within MIMIX Availability Manager or to switch using option 5 (start or complete switch) from the MIMIX Basic Main Menu.
Planned Switch
You can start a planned switch from either system. When using MIMIX Model Switch Framework, you start the switch from the system that MIMIX Model Switch
205
Switching
Framework is on. In a planned switch, MIMIX initiates a controlled shutdown of the data group. Both systems and the communications between them must be active. Before you start a planned switch of a data group, you should ensure that the following actions have been completed. Your enterprise may have additional requirements. Perform an full set of audits with the audit level policy set to level 30. Running the #FILDTA audit at this audit level checks 100 percent of file member data for the data group for synchronization between source and target systems and is strongly recommended. Shut down any applications that use database files or objects defined to the data group. If any users or other non-MIMIX processes remain active while the switch is being performed, the data can become not synchronized between systems and orphaned data may result. Ensure that there are no jobs other than MIMIX currently active on the source system. This may require ending all interactive and batch subsystems other than MIMIX and ending communications. Users should be prevented from accessing either system until after the switch is complete and the data group is restarted. If you use user journal replication processes, you should address any files, IFS tracking entries, or object tracking entries in error for your critical database files. If you use system journal replication processes, you should address any object errors.
You are not required to run journal analysis after a planned switch. MIMIX retains information about where activity ended so that when you restart the data group, it is started at the correct point. When the data group is started, the temporary target system (the production system) is now being updated with user changes that are being replicated from the temporary source system (the backup system). Do not allow users onto the production system until after the production system is caught up with these transactions and you run the switch process again to revert to the normal roles.
Unplanned switch
In an unplanned switch, the source system is assumed to be unavailable. An unplanned switch is generally required when the source system fails and, in order to continue normal operations, you must switch users to a backup system. (Typically MIMIX is configured so that the target for replication is your backup system.) You must run an unplanned switch from the target system. MIMIX performs a controlled shutdown of replication processes on the target system. The controlled shutdown allows all apply processing to catch up before the apply processes are ended. There are default (*DFT) values for several parameters on the SWTDG command that allow the switch operation to continue without intervention from the user. See Planned Switch on page 205 for additional details about these default values.
206
About switching
In an unplanned switch of a data group that uses remote journaling, the default behavior is to end the RJ link. Once the failed source system is recovered, the following actions should be completed: You should perform journal analysis on that system before restarting the data group or user applications. Journal analysis helps identify any possible loss of data that may have occurred when the source system failed. Journal analysis relies on status information on the source system about the last entry that was applied. This information will be cleared when the data group is restarted. Communication between the systems must be active before you restart the data group. The switch process is complete when you restart the data group. When the data group is restarted, MIMIX notifies the source system that it is now the temporary target system. New transactions are created on the temporary source system (the backup system) while the production system (the temporary target system) is unavailable for replication. After you have completed journal analysis, you can send these new transactions to the production system to synchronize the databases. Once the databases are synchronized, you must run the switch process again to revert to the normal roles before allowing users onto the production system.
When the data group is started after a switch, any pending transactions are cleared. The journal receiver is already changed by the switch process and the new journal receiver and first sequence number are used.
207
A data group definition value of *INST indicates the policy is installation-wide. A name indicates the policies are in effect only for the specified data group.
208
From MIMIX Availability Manager, the action to change installation policies is only available when the system you are viewing is the management system. Do the following: 1. Ensure that you have selected the management system for the installation you want from the navigation bar. If you are not certain which system is the management system, you can select Services to check. 2. From the management system, select Switching from the navigation bar. 3. Select Change Installation Policies from the MIMIX Switch Assistant window. 4. Specify values for the following fields: a. For Switch warning threshold, the value 90 is recommended. b. For Switch action threshold, the value 180 is recommended. c. For Default model switch framework, specify the name of your MIMIX Model Switch Framework. 5. To accept the changes, click OK. From a 5250 emulator, do the following from the management system: 1. From the command line type SETMMXPCY and press F4 (Prompt). 2. Verify that the value specified for Data group definition is *INST. 3. Press Enter to see all the policies and their current values. 4. Specify values for the following fields: a. For Switch warning threshold, the value 90 is recommended. b. For Switch action threshold, the value 180 is recommended. c. For Default model switch framework, specify the name of your MIMIX Model Switch Framework. 5. To accept the changes, press Enter.
209
3. Select Change Policies from the action list. 4. Specify values for the following fields: a. For Switch warning threshold, specify a value other than Disabled; 90 or Installation is recommended. b. For Switch action threshold, specify a value other than Disabled; 180 or Installation is recommended. 5. To accept the changes, click OK.
For more information about the risks associated with lower audit levels, see Guidelines and recommendations for auditing on page 81. From MIMIX Availability Manager, the action to change policies is only available when the system you are viewing is the management system. Do the following: 1. Ensure that you have selected the management system for the installation you want from the navigation bar. If you are not certain which system is the management system, you can select Services to check. 2. From the management system, select Policies from the navigation bar. 3. On the MIMIX Policies window, the first entry listed is the installation. Select the Details action and click . 4. On the Set MIMIX Policies window, specify 30 for Audit level and click OK. From a 5250 emulator, do the following from the management system: 1. From the command line type SETMMXPCY and press F4 (Prompt).
210
2. Verify that the value specified for Data group definition is *INST. 3. Press Enter to see all the policies and their current values. 4. For Audit level, specify *LEVEL30. Then press Enter.
211
For information about policies used by MIMIX Switch Assistant, see Setting policies for switching on page 208. Each step of the switch cycle must be performed from the system on which the MIMIX Model Switch Framework was created. Typically, this is the backup system. To perform a switch, do the following: 1. Select Switching from the Details area in the navigation bar. The MIMIX Switch Assistant window appears. 2. Perform the manual actions listed in the Step area of the MIMIX Switch Assistant window. Some actions include buttons for access to relevant locations. (You must re-select Switching from the navigation bar to return to MIMIX Switch Assistant.) 3. Consult your runbook for any additional required actions for the step. Perform them now. 4. To start the step, click on the button located at the bottom of the text. This will prompt the Run Switch Framework (RUNSWTFWK) command, where you can specify options for the switch. 5. When processing ends for the step, the Command History window opens to display any errors that occurred. For more information, use online Help.
212
Each phase will prompt the Run Switch Framework command (RUNSWTFWK) with your default switch framework and appropriate values for the phase. To change the default switch framework to a different implementation, see Setting policies for switching on page 208.
213
214
4. You will see the Confirm Switch to Production confirmation display. Press F16 to confirm your choice to switch MIMIX and specify switching options. 5. The Run Switch Framework (RUNSWTFWK) command appears. The default Switch framework and the value *PROD for the Switch framework process are preselected and cannot be changed. Do the following: a. You can change values for other parameters as needed. b. To start the switch, press Enter. 6. Consult your runbook to determine if any additional steps are needed.
215
Note: If the date is not listed for a data group, the data group policy may not be configured for switching. Compliance is only checked when you specify the data group policy for Switch warning threshold and Switch action threshold. For more information, see Setting policies for switching on page 208.
216
3. Some of the parameter values that you may want to consider when the Switch Data Group display appears are: If you specified Switch type of *PLANNED and have specified a number for the Wait time (seconds) parameter, you can specify a value for the Timeout Option parameter to specify what action you want the SWTDG command to perform if the time specified in the Wait time (seconds) parameter is exceeded. When
217
you are performing a planned switch you may want to specify the number of seconds to wait before all the active data group processes end. If you specify *NOMAX the switch process will wait until all data group processes are ended. This could delay the switch process. You can use the Conditions that end switch parameter to specify the types of errors that you want to end the switch operation. To ensure that the most comprehensive checking options are used, choose *ALL. For a planned switch, the default value, *DFT, is the same as *ALL. For an unplanned switch, *DFT will prevent the switch only when database apply backlogs exist. Verify that the value for the Start journaling on new source prompt is what you want. If necessary, change the value.
4. After the confirmation screen, press F16 to continue. 5. Press Enter. Messages appear indicating the status of the switch request. When you see a message indicating that the switch is complete, users can begin processing as usual on the temporary source system. 6. If you performed an unplanned switch, perform journal analysis on the original source system as soon as it is available, to determine if any transactions were missed. Use topic Performing journal analysis on page 258. 7. Start the data group, clearing pending entries, using the procedure in Starting selected data group processes on page 150. This starts replication in the new temporary direction.
Updated for 6.0.15.00.
218
219
receiver during the switch operation. If you have applications that are dependent on the receiver name for recovery purposes, It is recommended that you choose CHGUSRRCV(*NO) to prevent a new journal receiver from being created during a data group switch. The Change system journal receiver (CHGSYSRCV) parameter is used to specify whether or not you want MIMIX to create and attach a new journal receiver to the system (audit) journal (QAUDJRN) during the switch operation. If you have applications that are dependent on the receiver name for recovery purposes, it is recommended that you choose CHGSYSRCV(*NO) to prevent a new journal receiver from being created during a data group switch. The End if database errors (ENDDBERR) parameter has been obsoleted by the Conditions that end switch (ENDSWT) parameter. Previously, the ENDDBERR parameter was used to specify whether to switch the data group when data replication errors exist. Use the ENDSWT parameter and specify *DBERR to produce the equivalent of ENDDBERR(*YES), or *NONE to produce the equivalent of ENDDBERR(*NO). The Confirm (CONFIRM) parameter is used to specify if a confirmation panel is displayed. The default is *NO (the confirmation panel is not displayed). Note that options for switching on the Work with Data Groups display call the SWTDG command with *YES specified so that the confirmation panel is automatically displayed and the user must press F16 to continue.
220
CHAPTER 9
This chapter describes how to perform infrequently used operations that help keep your MIMIX environment running. The following topics are included: Starting the TCP/IP server on page 222 contains the procedure for starting the TCP/IP server. Ending the TCP/IP server on page 223 contains the procedure for ending the TCP/IP server. Working with objects on page 224 contains tips for working with long object and IFS path names. Viewing status for active file operations on page 226 describes how to check status when replicating database files that you are reorganizing or copying with MIMIX Promoter. Displaying a remote journal link on page 227 describes how to display information about he link between a source journal definition and a target journal definition. Displaying status of a remote journal link on page 228 includes procedures for determining whether a data group uses remote journaling and for checking the status of a remote journal link. Identifying data groups that use an RJ link on page 230 includes the procedure to determine which data groups use a remote journal link. Identifying journal definitions used with RJ on page 231 describes how to determine whether a journal definition is defined to one or more remote journal links. Disabling and enabling data groups on page 232 describes when it can be beneficial to disable and enable data groups. Procedures for these processes are included in this topic. Determining if non-file objects are configured for user journal replication on page 234 provides procedures for determining whether configured for IFS objects, data areas, and data queues are configured to be cooperatively processed through the user journal. Using file identifiers (FIDs) for IFS objects on page 236 describes file identifiers (FIDs) which are used by commands to uniquely identify the correct IFS tracking entries to process. Operating a remote journal link independently on page 237 describes how to configure, start, and end a remote journal link without defining data to be replicated by MIMIX processes.
221
222
223
To display the entire object name from any of these displays, position the cursor on an entry which indicates a long name and press F22 (Display entire field).
224
To access the spooled file information, do the following: 1. From the MIMIX Basic Main Menu, select option 1 (Availability status) and press Enter. The MIMIX Availability Status display appears. 2. Select option 5 (Display details) in the Replication bar and press Enter. The Work with Data Groups display appears. 3. Select option 14 (Active objects) for the data group you want to view and press Enter. The Work with Data Group Activity display appears.
4. From this display, press F16 (Spooled Files) to access the Display Data Group Spooled Files display. This display lists all of the current spooled files and shows the mapping of their names between the source and target systems.
225
3. From the MIMIX Utilities Menu, select option 63 (Work with copy status) and press Enter. 4. The Work with Copy Status display appears. From this display you can track the status of active copy or reorganize operations, including the replication of physical file data as specified by METHOD(*DATA) on the Synchronize Data Group File Entry (SYNCDGFE) command. Note: You can only see status for the system on which you are working.
226
227
The following states are considered to be inactive: *UNKNOWN *NOTAVAIL *NOTBUILT *SRCNOTBLT *TGTNOTBLT Neither journal defined to the remote journal link resides on the local system so the state of the link cannot be checked. The ASP where the journal is located is varied off. The remote journal link is defined to MIMIX but one of the associated journal environments has not been built. The remote journal link is defined to MIMIX but the associated source journal environment has not been built. The remote journal link is defined to MIMIX but the associated target journal environment has not been built.
228
Possible states for RJ links, shown in order starting with most severe. Description The remote journal cannot receive journal entries from the source journal due to an error condition. The remote journal link is processing a request for a controlled end. The remote journal link is not active.
*CTLINACT *INACTIVE
The following states are considered to be active: *INACTPEND An active remote journal link is in the process of becoming inactive. For asynchronous delivery, this is a transient state that will resolve automatically. For synchronous delivery, one system is inactive while the other system is inactive with pending unconfirmed entries. An active remote journal link is connected using synchronous delivery and is running in catch-up mode. The state will become *SYNC when catch-up mode ends. An active remote journal link is connected using asynchronous delivery and is running in catch-up mode. The state will become *ASYNC when catch-up mode ends. An active remote journal link is connected using synchronous delivery mode. An active remote journal link is connected using asynchronous delivery mode.
*SYNCPEND
*ASYNCPEND
*SYNC *ASYNC
229
5. Press F10 (View RJ links). Consider the following and contact your MIMIX administrator before taking action that will end the RJ link or remove the remote journaling environment. When *NO appears in the Use RJ Link column, the data group will not be affected by a request to end the RJ link or to end the remote journaling environment. Note: If you allow applications other than MIMIX to use the RJ link, they will be affected if you end the RJ link or remove the remote journaling environment. When *YES appears in the Use RJ Link column, the data group may be affected by a request to end the RJ link. If you use the procedure for ending a remote journal link independently in topic Ending a remote journal link independently on page 237, ensure that any data groups that use the RJ link are inactive before ending the RJ link.
230
231
232
by specifying a different value on the STATE parameter of the WRKDG command or by specifying preferences in MIMIX Availability Manager.
From a 5250 emulator the Change Data Group (CHGDG) command allows you to disable or enable a data group by changing its state. This command requires that the system manager is active and communication with the remote system is active. To disable or enable an individual data group, do the following: 1. On a command line, type CHGDG and press Enter. The Change Data Group display appears. 2. At the Data group definition prompts, fill in the values you want or press F4 for a valid list. 3. At the State prompt, do one of the following: To keep the state of the data group the same, specify the default, *SAME. To change the state of an active data group, you must first end the data group by running the End Data Group (ENDDG) command. See Ending selected data group processes on page 151. To disable an enabled data group, specify *DISABLE. When the state of the data group is changed to disabled, the status of the data group changes from *INACTIVE to *DISABLED. To enable a disabled data group, specify *ENABLE. When the state of the data group is changed to enabled, the status of the data group changes from *DISABLED to *INACTIVE.
233
To view additional information for a data group IFS entry, type 5 (Display) next to the entry and press Enter. 6. Press F12 (Cancel) to return to the Work with Data Groups display. Then type 50 (IFS trk entries) next to the data group you want and press Enter. 7. The Work with DG IFS Trk. Entries display appears with a list of tracking entries for the IFS objects identified for replication by the data group. If there are no tracking entries listed but Step 5 indicates that properly configured data group IFS entries exist, the tracking entries must be loaded. For more information about loading tracking entries, see the MIMIX Reference book.
234
235
236
To end a remote journal link separately from other MIMIX processes, do the following: 1. To access the Work with Journal Links display, type the command WRKRJLNK and press Enter. 2. From the Work with Remote Journal Links display, type a 10 (End) next to the link in the list that you want to end. 3. Do one of the following: To perform an immediate end from the source system, press Enter. This completes the procedure for an immediate end.
237
To perform a controlled end or to end from the target system, press F4 (Prompt), then continue with the next step.
4. The End Remote Journal Link (ENDRJLNK) display appears. Press F10 (Additional parameters). 5. To perform a controlled end, specify *CNTRLD at the End remote journal link prompt. If you need to end from the target system, specify *TGT at the End RJ link on system prompt. To process the request, press Enter.
238
CHAPTER 10
Occasionally, a situation may occur that requires user intervention. This section provides information to help you troubleshoot problems that can occur in a MIMIX environment. If you are using MIMIX Availability Manager, the best place to start is with the flyover text on the icons representing problems and status. Often, this will direct you to a course of action. If you are using 5250 emulator commands, start at the MIMIX Availability Status display.
Note: The procedures in this chapter are primarily for use with a 5250 emulator. You can also consult our website at www.mimix.com for the latest information and updates for MIMIX products. The following topics are included in this chapter: Gathering information before reporting a problem on page 241 describes the information you should gather before you report a problem. A procedure is included to help you gather this information. Reducing contention between MIMIX and user applications on page 242 describes a processing timing issue that may be resolved by specifying an Object retrieval delay value on the commands for creating or changing data group entries. Data groups cannot be ended on page 243 describes possible causes for a data group that is taking too long to end. Verifying a communications link for system definitions on page 244 describes the process to verify that the communications link defined for each system definition is operational. Verifying the communications link for a data group on page 245 includes a process to use before synchronizing data to ensure that the communications link for the data group is active. Checking file entry configuration manually on page 246 includes the process for checking that correct data group file entries exist with respect to the data group object entries. This process uses the Check DG File Entries (CHKDGFE) command. Data groups cannot be started on page 248 describes some common reasons why a data group may not be starting. Cannot start or end an RJ link on page 249 describes possible reasons that can prevent you from starting or ending an RJ link. This topic includes a procedure for removing unconfirmed entries to free an RJ link. RJ link active but data not transferring on page 250 describes why an RJ link may not be transferring data and how to resolve this problem.
239
Errors using target journal defined by RJ link on page 251 describes why errors when using a target journal defined by an RJ link can occur and how to resolve them. Verifying data group file entries on page 252 includes a procedure for verifying data group file entries using the Verify Data Group File Entries (VFYDGFE) command. Verifying data group data area entries on page 252 includes a procedure for verifying data group data area entries using the Verify Data Group Data Area Entries (VFYDGDAE) command. Data area entries are only used when data areas are replicated by the data area poller process, which is not preferred. Verifying key attributes on page 252 includes a procedure for verifying key attributes using the VFYKEYATR (Verify Key Attributes) command. Working with data group timestamps on page 254 describes timestamps and includes information for creating, deleting, displaying, and printing them. Removing journaled changes on page 257 describes the configuration conditions that must be met using the Remove Journaled Changes (RMVJRNCHG) journal entry. Performing journal analysis on page 258 describes and includes the procedure for performing journal analysis of the source system.
240
2. Next to the product you want, type a 6 (About version) and press Enter. The About pop-up appears, showing the Product, Library, Installed version, and the OS/400 level on this system. 3. Press F9 (Fixes) to see the Work with Installed Fixes display. From this display you can determine the latest level of the MIMIX cumulative fix package that is installed. Note: You should know the version and release level (VnRnMn) of the IBM i operating system that is on each system with which you are working. Use the process above on each system.
241
242
243
244
245
246
To submit the job for batch processing, accept *YES. Press Enter and continue with the next step.
9. At the Job description prompts, specify the name and library of the job description used to submit the batch request. Accept MXAUDIT to submit the request using the default job description, MXAUDIT. 10. At the Job name prompt, accept *CMD to use the command name to identify the job or specify a simple name. 11. To start the data group file entry check, press Enter.
247
248
To recover from this situation, you should run the Verify Communications Link (VFYCMNLNK) command to assist you in determining what may by wrong and why the RJ link will not start. If you are using an independent ASP, check the transfer definition to ensure the correct database name has been specified. You also need to end the remote journal link from the target system. Ending the link from the target system is a restriction of the IBM remote journal function.
249
250
4. Type a 2 (Change) next to the target journal definition and press Enter. 5. Press F9 (All parameters), then page down to locate the Threshold message queue and Library prompts. 6. Change the Threshold message queue prompt to *JRNDFN and the Library prompt to *JRNLIB, or to other acceptable values. 7. To accept the change, press Enter.
251
252
Do the following to verify that the attributes of a file are appropriate for keyed replication: 1. On a command line, type VFYKEYATR (Verify Key Attributes). The Verify Key Attributes display appears. 2. Do one of the following: To verify a file in a library, specify a file name and a library. To verify all files in a library, specify *ALL and a library. To verify files associated with the file entries for a data group, specify *MIMIXDFN for the File prompt and press Enter. Prompts for the Data group definition appear. Specify the name of the data group that you want to check.
3. Press Enter. 4. A spooled file is created that indicates whether you can use keyed replication for the files in the library or data group you specified. Display the spooled file (WRKSPLF command) or use your standard process for printing. You can use keyed replication for the file if *BOTH appears in the Replication Type Allowed column. If a value appears in the Replication Type Defined column, the file is already defined to the data group with the replication type shown.
253
Note: For data groups that use remote journaling, the created and sent timestamps will be set to the same value. The received timestamp will be set to the time when the record was read on the target system by the database reader process. After all four timestamps have been added, the journal entry is converted and placed into a file for viewing or printing. You can view timestamps only from the management system. The system manager must be active to return the timestamps to the management system.
254
2. The Work with DG Timestamps display appears. Type a 1 (Create) next to the blank line at the top of the display and press Enter. 3. The Create Data Group Timestamps display appears. Specify the name of the data group and the number of timestamps you want to create and press Enter. Note: You should generate multiple timestamps to receive a more accurate view of replication process performance.
255
Repeat this procedure for each RJ data group for which you want to generate timestamps.
Deleting timestamps
You can delete all timestamps or you can select a group of one or more timestamps to delete. To delete timestamps for a data group, do the following: 1. From the Work with Data Groups display, type 41 (Timestamps) next to the data group you want and press Enter. 2. The Work with DG Timestamps display appears. Type a 4 (Delete) next to the timestamps you want to delete and press Enter. 3. A confirmation screen appears. Press Enter. To selectively delete a range of timestamps, do the following: 1. Type the command DLTDGTSP and press F4 (Prompt). 2. The Delete Data Group Timestamps display appears. Specify values you want for the Data group definition prompt. 3. Specify the values you want for the Starting date and time prompt and for the Ending date and time prompt, then press Enter.
3. Press Enter. 4. If you selected to display, the Display Data Group Timestamps display appears. If you selected to print, a spooled file is created that you can print using your standard printing procedures.
256
257
4. If you did not see a pop-up window in Step 3 and you need to clear data from a previous run of journal analysis and collect new information, do the following: a. If you want to keep information from a previous run, make a copy of file DM6500P located in the installation library. b. Press F9 (Update display) to clear the screen and collect the new information. A pop-up confirmation window with the following message is displayed: WARNING! The journal analysis journal entries file will be cleared!
258
c. Press Enter to submit the update request. 5. The request to collect journal analysis information is submitted by job RTVFILANZ using the job description MIMIXQGPL/MIMIXDFT. When the job completes, LVI3855 Retrieval of affected files for journal analysis completed normally appears in the message log. Press F5 (Refresh) to see the collected information. It may take a short time to collect the information. 6. Retrieve journal entries. The journal entries for the files identified on the display must be retrieved before you can use options to display or print statistics (5 and 6) or display journal entries (11). Do one of the following: Press F14 (Retrieve all entries). A pop-up window stating Confirm retrieval of ALL analysis journal entries appears. Press Enter. (The retrieved information is placed in an internal file.This does not produce a spool file.) If there are a large number of files listed on the display, you may want to retrieve entries for only a selected file at a time. Type option 9 (Retrieve journal entries) next to the file to retrieve journal entries for and press Enter. The retrieved journal entries are placed in a spool file named MXJEANZL.
Message: LVI3856 Retrieval of journal entries for journal analysis completed normally appears in the message log. 7. Review the collected information using the following: Use option 11 (Display journal entries) to view the entries for each file. Use F21 (Print list) to print all entries for a file. You can use options 5 (Display statistics) and 6 (Print statistics) to see the statistical breakdown of journal entries for a selected file member identified by journal analysis. The statistics include the number of adds, deletes, and updates, along with the related file transactions and dates of the first and last journal entries.
Figure 35 shows an example of the information displayed by option 11 for one journal entry.
259
Journal header information (continued) Record length . . . . : 607 Record number . . . . : 838 Operation indicator . : 0 Commit cycle ID . . . : 0 Journal identification Journal name . . . . . : Library . . . . . . : Receiver identification Receiver name . . . . : Library . . . . . . : Sequence number . . . :
<JOURNAL> <JRNLIB>
8. Determine what action you need to take for each unprocessed entry. For example: You may need to run the original job again on the current source system to reproduce the entries. If a file has already been updated on the current source system (manually or otherwise), you may need to merge data from both files. If this is the case, do not synchronize the files. If there are write changes (R-PT entries), these changes should be made on the current source system before running the synchronization phase of the switch or starting data groups in order to maintain Relative Record Number consistency within the file. If this is done after the data group has been started, the relative record numbers could become unsynchronized between the two systems.
260
choices. When you continue with the confirmation, the journal entries for the selected file member are immediately removed from the journal analysis information that is displayed. It does not delete any other information contained in other MIMIX files.
Updated for 6.0.15.00.
261
262
*EXTRADGFE
An extra file entry exists. Delete the DGFE or change the DGOBJE to COOPDB(*YES)
Note: Changing the object entry affects all objects using the object entry. If you do not want all objects changed to this value, copy the existing DGOBJE to a new, specific DGOBJE with the appropriate COOPDB value.
No file exists for the existing file entry. Delete the DGFE, re-create the missing file, or restore the missing file. No file member exists for the existing file entry. Delete the DGFE for the member or add the member to the file. Automatic audit recovery actions were attempted but failed to correct the detected error. Run the audit again. Recovered by automatic recovery actions. No action is needed. File entries are in transition and cannot be compared. Run the audit again.
*RECOVERED *UA
The Option column of the report provides supplemental information about the comparison. Possible values are: *NONE - No options were specified on the comparison request. *NOFILECHK - The comparison request included an option that prevented an error from being reported when a file specified in a data group file entry does not exist. *DGFESYNC - The data group file entry was not synchronized between the source and target systems. This may have been resolved by automatic recovery
263
actions for the audit. One possible reason why actual configuration data in your environment may not match what is defined to your configuration is that a file was deleted but the associated data group file entries were left intact. Another reason is that a data group file entry was specified with a member name, but a member is no longer defined to that file. If you use the automatic scheduling and automatic audit recovery functions of MIMIX AutoGuard, these configuration problems can be automatically detected and recovered for you. Table 35 provides examples of when various configuration errors might occur.
Table 35. Result *NODGFE *EXTRADGFE *NOFILE *NOMBR CHKDGFE - possible error conditions File exists Yes Yes No Yes Member exists Yes Yes No No DGFE exists No Yes Yes Yes DGOBJE exists COOPDB(*YES) COOPDB(*NO) Exclude No entry
264
Each record in the output files for these audits or commands identifies a file member that has been compared and indicates whether a difference was detected for that member. MIMIX Availability Manager displays only detected differences found by each compare command using a subset of the fields from the output file. You can see the full set of fields in each output file by viewing it from a 5250 emulator. The type of data included in the output file is determined by the report type specified on the compare command. When viewed from a 5250 emulator, the data included for each report type is as follows: Difference reports (RPTTYPE(*DIF)) return information about detected differences. Difference reports are the default for these compare commands. Full reports (RPTTYPE(*ALL)) return information about all objects and attributes compared. Full reports include both differences and objects that are considered synchronized. Relative record number reports (RPTTYPE(*RRN)) return the relative record number of the first 1,000 records of a member that fail to compare. Relative record number reports apply only to the Compare File Data command.
265
Possible values for Compare File Data (CMPFILDTA) output file field Difference Indicator (DIFIND) Description Data matches. No differences were detected within the data compared. Global difference indicator. Member excluded from comparison because it was not changed or restored after the timestamp specified for the CHGDATE parameter. No difference was detected. However, fields with unsupported types were omitted. The file feature is not supported for comparison. Examples of file features include materialized query tables. Matching entry not found in database apply table. Unable to process selected member. File formats differ between source and target files. Either the record length or the null capability is different. Indicates that a member is held or an inactive state was detected. Unable to complete processing on selected member. Messages preceding LVE0101 may be helpful. Indicates a difference was detected. Member not found on system 1. Member not found on system 2. The file member is being processed for repair by another job running the Compare File Data (CMPFILDTA) command. The source file is not journaled, or is journaled to the wrong journal. Unable to process selected member. See messages preceding message LVE3D42 in job log. The file or member is being processed by the Synchronize DG File Entry (SYNCDGFE) command. Unable to process selected member. Reason unknown. Messages preceding message LVE3D42 in job log may be helpful. Indicates that the members synchronization status is unknown.
*EQ (DATE)
*HLD *IOERR *NE *NF1 *NF2 *REP *SJ *SP *SYNC *UE *UN
266
*EC *EQ *FF *FMC *HLD *LCK *NE *NF1 *NF2 *SJ *UE *UN
267
For difference and full reports of compare attribute commands, several of the attribute selectors return an indicator (*INDONLY) rather than an actual value. Attributes that return indicators are usually variable in length, so an indicator is returned to conserve space. In these instances, the attributes are checked thoroughly, but the report only contains an indication of whether it is synchronized. For example, an authorization list can contain a variable number of entries. When comparing authorization lists, the CMPOBJA command will first determine if both lists have the same number of entries. If the same number of entries exist, it will then determine whether both lists contain the same entries. If differences in the number of entries are found or if the entries within the authorization list are not equal, the report will indicate that differences are detected. The report will not provide the list of entriesit will only indicate that they are not equal in terms of count or content. MIMIX Availability Manager displays only detected differences found by Compare Attributes commands using a subset of the fields from the output file. MIMIX Availability Manager displays summary rows in the Summary List window and detail rows in the Details window for the Compare command type. You can see the full set of fields in the output file by viewing it from a 5250 emulator.
1. The Compare Attribute commands are: Compare File Attributes (CMPFILA), Compare Object Attributes (CMPOBJA), Compare IFS Attributes (CMPIFSA), and Compare DLO Attributes (CMPDLOA).
268
269
Possible values for output file field Difference Indicator (DIFIND) Description Unable to process selected member. See messages preceding message LVE3D42 in job log. Object status is unknown due to object activity. If an object difference is found and the comparison has a value specified on the Maximum replication lag prompt, the difference is seen as unknown due to object activity. This status is only displayed in the summary record.
Note: The Maximum replication lag prompt is only valid when a data group is specified on the command.
*UN
1. 2. 3.
Not all values may be possible for every Compare command. Priorities are used to determine the value shown in output files for Compare Attribute commands. The value *RECOVERED can only appear in an output file modified by a recovery action. The object was initially found to be *NE or *NC but MIMIX autonomic functions recovered the object.
For most attributes, when a detailed row contains blanks in either of the System 1 Indicator or System 2 Indicator fields, MIMIX determines the value of the Difference Indicator field according to Table 39. For example, if the System 1 Indicator is *NOTFOUND and the System 2 Indicator is blank (Object found), the resultant Difference Indicator is *NE.
Table 39. Difference Indicator values that are derived from System Indicator values. Difference Indicator System 1 Indicator Object *NOTCMPD *NOTFOUND *NOTSPT *RTVFAILED *DAMAGED Found (blank value) *NA Object Found *EQ / *EQ (blank value) (LOB) / *NE / *UA / *EC / *NC *NA *NE / *UA *NS *UN *NE *NE *NS *UN *NE
*NS
*UN
*NE / *UA *NE / *UA *NS *UN *NE *UN *UN *NE
270
For a small number of specific attributes, the comparison is more complex. The results returned vary according to parameters specified on the compare request and MIMIX configuration values. For more information see the following topics: Comparison results for journal status and other journal attributes on page 290 Comparison results for auxiliary storage pool ID (*ASP) on page 294 Comparison results for user profile status (*USRPRFSTS) on page 297 Comparison results for user profile password (*PRFPWDIND) on page 300
*RTVFAILED
1. 2.
The priority indicates the order of precedence MIMIX uses when setting the system indicators fields in the summary record. This value is not used in determining the priority of summary level records.
For comparisons which include a data group, the Data Source (DTASRC) field identifies which system is configured as the source for replication. In MIMIX Availability Manager Details windows, the direction of the arrow shown the data group field identifies the flow of replication.
271
272
Access path valid Access path size Allow delete operation Allow operations Allow read operation Allow update operation
273
Compare File Attributes (CMPFILA) attributes Description Allow write operation Auxiliary storage pool ID Returned Values (SYS1VAL, SYS2VAL) *YES, *NO 1-16 (pre-V5R2) 1-255 (V5R2) 1 = System ASP See Comparison results for auxiliary storage pool ID (*ASP) on page 294 for details. *NONE, *CHANGE, *ALL Group which checks attributes *AUTL, *PGP, *PRVAUTIND, *PUBAUTIND *NONE, list name 33 character name in the format: library/file(member)
Object audit value File authorities Authority list name Name of based-on physical file member Pre-determined set of basic attributes
*BASIC
Group which checks a pre-determined set of attributes. When *FILE is specified for the Comparison level (CMPLVL), these attributes are compared: *CST (group), *NBRMBR, *OBJATR, *RCDFMT, *TEXT, and *TRIGGER (group). When *MBR is specified for the Comparison level (CMPLVL), these attributes are compared: *CURRCDS, *EXPDATE, *NBRDLTRCD, *OBJATR, *SHARE, and *TEXT. 1-65535 Group which checks attributes *CSTIND, *CSTNBR No value, indicator only5 When this attribute is returned in output, its Difference Indicator value indicates if the number of constraints, constraint names, constraint types, and the check pending attribute are equal. For referential and check constraints, the constraint state as well as whether the constraint status is enabled or disabled is also compared. Numeric value 0-4294967295 *YES, *NO Group which checks *DBRIND, *OBJATR
274
Compare File Attributes (CMPFILA) attributes Description Database relations Returned Values (SYS1VAL, SYS2VAL) No value, indicator only5 When this attribute is returned in output, its Difference Indicator value indicates if the number of database relations and the dependent file names are equal. Blank for *NONE or date in CYYMMDD format, where C equals the century. Value 0 is 19nn and 1 is 20nn. Valid only for Comparison level of *FILE, this group compares the basic set of attributes (*BASIC) plus an extended set of attributes. The following attributes are compared: *ACCPTH, *AUT (group), *CCSID, *CST (group), *CURRCDS, *DBR (group), *MAXKEYL, *MAXMBRS, *MAXRCDL, *NBRMBR, *OBJATR, *OWNER, *PFSIZE (group), *RCDFMT, *REUSEDLT, *SELOMT, *SQLTYP, *TEXT, and *TRIGGER (group). 10 character name *NONE if the file has no members. *YES, *NO *NONE, 1-32767 0-32767 *YES, *NO Add, update, and delete authorities are not checked. Differences in these authorities do not result in an *NE condition. Group which checks *JOURNALED, *JRN, *JRNLIB, *JRNIMG, *JRNOMIT. Results are described in Comparison results for journal status and other journal attributes on page 290. *YES, *NO 10 character name, blank if never journaled *AFTER, *BOTH 10 character name, blank if never journaled *OPNCLO, *NONE 3 character ID 10 character name *NONE if the file has no members.
*DBRIND 3
*EXPDATE1 *EXTENDED
Name of member *FIRST Force keyed access path Records to force a write Increment number of records Join Logical file
*JOURNAL
Journal attributes
File is currently journaled Current or last journal Record images Current or last journal library Journal entries to be omitted Language ID Name of member *LAST
275
Compare File Attributes (CMPFILA) attributes Description Record format level check Access path maintenance Maximum increments Maximum key length Maximum members Max % deleted records allowed Maximum record length Current number of deleted records Number of members Initial number of records Object control level File owner File size attributes Primary group Private authority indicator Returned Values (SYS1VAL, SYS2VAL) *YES, *NO *IMMED, *REBLD, *DLY 0-32767 1-2000 *NOMAX, 1-32767 *NONE, 1-100 1-32766 0-4294967295 0-32767 *NOMAX, 1-2147483646 8 character user-defined value User profile name Group which checks *CURRCDS, *INCRCDS, *MAXINC, *NBRDLTRCD, *NBRRCDS *NONE, user profile name No value, indicator only5 When this attribute is returned in output, its Difference Indicator value indicates if the number of private authorities and private authority values are equal. No value, indicator only5 When this attribute is returned in output, its Difference Indicator value indicates if public authority values are equal. 1-32 *IPL, *AFTIPL, *NO *YES, *NO
*MAXKEYL1 *MAXMBRS1 *MAXPCT1 *MAXRCDL1 *NBRDLTRCD1 *NBRMBR1 *NBRRCDS1 *OBJCTLLVL1 *OWNER *PFSIZE *PGP *PRVAUTIND
*PUBAUTIND
Public authority indicator Number of record formats Access path recovery Reuse deleted records
276
Compare File Attributes (CMPFILA) attributes Description Select / omit file Share open data path SQL file type Text description Returned Values (SYS1VAL, SYS2VAL) *YES, *NO *YES, *NO PF Types - NONE, TABLE, LF Types - INDEX, VIEW, NONE 50 character value Group which checks *TRGIND, *TRGNBR, *TRGXSTIND Trigger equal indicator No value, indicator only5 When this attribute is returned in output, its Difference Indicator value indicates whether it is enabled or disabled, and if the number of triggers, trigger names, trigger time, trigger event, and trigger condition with an event type of update are equal. Numeric value No value, indicator only5 When this attribute is returned in output, its Difference Indicator value indicates if a trigger program exists on the system. 10 character user-defined value *IMMED, *CLS, 1-32767 *IMMED, *NOMAX, 1-32767
*TRIGGER *TRGIND 3
*TRGNBR 3 *TRGXSTIND 3
Number of triggers Trigger existence indicator User-defined attribute Maximum file wait time Maximum record wait time
2. 3. 4.
5.
Differences detected for this attribute are marked as *EC (equal configuration) when the compare request specified a data group and the object is configured for system journal replication with a configured object auditing value of *NONE. This attribute is only compared for logical file members by the #FILATRMBR audit. This attribute cannot be specified as input for comparing but it is included in a group attribute. When the group attribute is checked, this value may appear in the output. Differences detected for this attribute are marked as *EC (equal configuration) when the compare request specified a data group and the file is configured for system journal replication with a configured Omit content (OMTDTA) value of *FILE. If *PRINT is specified in the comparison, an indicator appears in the system 1 and system 2 columns. If *OUTFILE is specified, however, these values are blank.
277
*ASP
*ASPNBR
Number of defined storage pools. Valid for subsystem descriptions only. Attention key handling program Valid for user profiles only. Object audit value Authority attributes Authority to check. Valid for job queues only. Authority list name Pre-determined set of basic attributes
*ATTNPGM2
*NONE, *USRPRF, *CHANGE, *ALL Group which checks *AUTL, *PGP, *PRVAUTIND, *PUBAUTIND *OWNER, *DTAAUT *NONE, list name Group which checks a pre-determined set of attributes. These attributes are compared: *CRTTSP, *DOMAIN, *INFSTS, *OBJATR, *TEXT, and *USRATR.
278
Compare Object Attributes (CMPOBJA) attributes Description Character identifier control. Valid for user profiles only. Country ID Valid for user profiles only. Communications entries Valid for subsystem descriptions only. Returned Values (SYS1VAL, SYS2VAL) *SYSVAL, ccsid-value
*CNTRYID2
*SYSVAL, country-id
*COMMEIND
No value, indicator only3 When this attribute is returned in output, its Difference Indicator value indicates if the number of communication entries, maximum number of active jobs, communication device, communication mode, associated job description and library, and the default user entry values are equal. *SYSVAL, *CHANGE, *ALL, *USE, *EXCLUDE, *SYSVAL, *CHANGE, *ALL, *USE, *EXCLUDE
*CRTAUT2
Authority given to users who do not have specific authority to the object. Valid for libraries only. Auditing value for objects created in this library Valid for libraries only. Profile that owns objects created by user Valid for user profiles only. Object creation date Current library Valid for user profiles only. Data cyclic redundancy check (CRC) Valid for data queues only. DDM conversation Valid for job descriptions only. Decimal positions Valid for data areas only. Object Domain Data area extended attributes
*CRTOBJAUD2
*CRTOBJOWN
*CRTTSP *CURLIB
*DATACRC2
10 character value
*DDMCNV2
*KEEP, *DROP
0-9 *SYSTEM, *USER Group which checks *DECPOS, *LENGTH, *TYPE, *VALUE
279
Compare Object Attributes (CMPOBJA) attributes Description Pre-determined, extended set Returned Values (SYS1VAL, SYS2VAL) Group which compares the basic set of attributes (*BASIC) plus an extended set of attributes. The following attributes are compared: *AUT, *CRTTSP, *DOMAIN, *INFSTS, *OBJATR, *TEXT, and *USRATR. *NONE, 1 - 32,767 1 - 4294967294
*EXTENDED
*FRCRATIO1 2 *GID
Records to force a write Valid for logical files only. Group profile ID number Valid for user profiles only. Group authority to created objects Valid for user profiles only. Group authority type Valid for user profiles only. Group profile name Valid for user profiles only. Information status
*GRPAUT
*GRPAUTTYP
*PGP, *PRIVATE
*GRPPRF
*NONE, profile-name
*INFSTS
*OK (No errors occurred), *RTVFAILED (No information returned - insufficient authority or object is locked), *DAMAGED (Object is damaged or partially damaged). Menu - *SIGNOFF, menu name Library - *LIBL, library name Program - *NONE, program name Library - *LIBL, library name Group which checks *DDMCNV, *JOBQ, *JOBQLIB, *JOBQPRI, *LIBLIND, *LOGOUTPUT, *OUTQ, *OUTQLIB, *OUTQPRI, *PRTDEV 10 character name
*INLMNU
Initial menu Valid for user profiles only. Initial program Valid for user profiles only. Job description extended attributes Job queue Valid for job descriptions only. Job queue entries Valid for subsystem descriptions only.
*INLPGM
*JOBDEXT
*JOBQ2
*JOBQEIND
No value, indicator only3 When this attribute is returned in output, its Difference Indicator value indicates if the number of job queue entries, job queue names, job queue libraries, and order of entries are the same
280
Compare Object Attributes (CMPOBJA) attributes Description Job queue extended attributes Job queue library Valid for job descriptions only. Job queue priority Valid for job descriptions only. Subsystem that receives jobs from this queue Valid for job queues only. Job queue status Valid for job queues only. Journal attributes Returned Values (SYS1VAL, SYS2VAL) Group which checks *AUTCHK, *JOBQSBS, *JOBQSTS, *OPRCTL 10 character name
*JOBQEXT *JOBQLIB2
*JOBQPRI2
1 (highest) - 9 (lowest)
*JOBQSBS2
Subsystem name
*JOBQSTS2 *JOURNAL
HELD, RELEASED Group which checks *JOURNALED, *JRN, *JRNLIB, *JRNIMG, *JRNOMIT4. Results are described in Comparison results for journal status and other journal attributes on page 290. *YES, *NO 10 character name *AFTER, *BOTH 10 character name *OPNCLO, *NONE *SYSVAL, language-id
Object is currently journaled Current or last journal Record images Current or last journal library Journal entries to be omitted Language ID Valid for user profiles only. Data area length Valid for data areas only Extended library information attributes Initial library list Valid for job descriptions only.
1-2000 (character), 1-24 (decimal), 1 (logical) Group which checks *CRTAUT, *CRTOBJAUD No value, indicator only3 When this attribute is returned in output, its Difference Indicator value indicates if the number of library list entries and entry list values are equal. The comparison is order dependent.
281
Compare Object Attributes (CMPOBJA) attributes Description Limit capabilities Valid for user profiles only. Job log output Valid for job descriptions only. Record format level check Valid for logical files only. Access path maintenance Valid for logical files only. Maximum active jobs Valid for subsystem descriptions only. Maximum members Valid for logical files only. Message queue Valid for user profiles only. Number of logical file members Valid for logical files only. Object attribute Object control level Valid for object types that support this attribute5. Operator controlled Valid for job queues only. Output queue Valid for job descriptions only. Output queue library Valid for job descriptions only. Output queue priority Valid for job descriptions only. Returned Values (SYS1VAL, SYS2VAL) *PARTIAL, *YES, *NO
*LOGOUTPUT2
*LVLCHK1 2
*YES, *NO
*MAINT1 2
*MAXACT 2
*MAXMBRS1 2 *MSGQ2
*NOMAX, 1 - 32,767 Message queue - message queue name Library - *LIBL, library name 0 - 32,767
*NBRMBR1 2
*OBJATR *OBJCTLLVL2
*OPRCTL2 *OUTQ2
*OUTQLIB2
10 character name
*OUTQPRI2
1 (highest) - 9 (lowest)
282
Compare Object Attributes (CMPOBJA) attributes Description Object owner Primary group Pre-start job entries Valid for subsystem descriptions only. Returned Values (SYS1VAL, SYS2VAL) 10 character name *NONE, user profile name No value, indicator only1 When this attribute is returned in output, its Difference Indicator value indicates if the number of prestart jobs, program, user profile, start job, wait for job, initial jobs, maximum jobs, additional jobs, threshold, maximum users, job name, job description, first and second class, and number of first and second class jobs values are equal. *LIBL/*WRKSTN, *DEV
*PRESTIND
*PRFOUTQ2
Output queue Valid for user profiles only. User profile password indicator Printer device Valid for job descriptions only. Private authority indicator
*PRFPWDIND *PRTDEV2
See Comparison results for user profile password (*PRFPWDIND) on page 300 for details. *USRPRF, *SYSVAL, *WRKSTN, printer device name
*PRVAUTIND
No value, indicator only3 When this attribute is returned in output, its Difference Indicator value indicates if the number of private authorities and private authority values are equal No value, indicator only3 When this attribute is returned in output, its Difference Indicator value indicates if the public authority values are equal. *SYSVAL, *NOMAX, 1-366 days
*PUBAUTIND
*PWDEXPITV
Password expiration interval Valid for user profiles only. No password indicator Valid for user profiles only. Job queue allocation indicator Valid for subsystem descriptions only.
*PWDIND
*QUEALCIND
No value, indicator only3 When this attribute is returned in output, its Difference Indicator value indicates if the job queue entries for a subsystem are in the same order and have the same queue names and queue library names. It also compares the allocation indicator values
283
Compare Object Attributes (CMPOBJA) attributes Description Remote location entries Valid for subsystem descriptions only. Returned Values (SYS1VAL, SYS2VAL) No value, indicator only3 When this attribute is returned in output, its Difference Indicator value indicates if the number of remote location entries, remote location, mode, job description and library, maximum active jabs, and default user entry values are equal. No value, indicator only3 When this attribute is returned in output, its Difference Indicator value indicates if the number of routing entries, sequence number, maximum active, steps, compare start, entry program, class, and compare entry values are equal Group which checks *AJEIND, *ASPNBR, *COMMEIND, *JOBQEIND, *MAXACT, *PRESTIND, *RLOCIND, *RTGEIND, *SBSDSTS *ACTIVE, *INACTIVE
*RLOCIND
*RTGEIND
*SBSDEXT
Subsystem description extended attributes Subsystem status Valid for subsystem descriptions only. Object size Special authorities Valid for user profiles only. SQL stored procedures Valid for programs and service programs only.
*SBSDSTS2
*SIZE *SPCAUTIND
Numeric value No value, indicator only3 When this attribute is returned in output, its Difference Indicator value indicates if special authority values are equal *NONE, or indicator only3 *NONE is returned when there are no stored procedures associated with the program or service program. When the indicator only is returned in output, the Difference Indicator value identifies whether SQL stored procedures associated with the object are equal. *NONE, or indicator only3 *NONE is returned when there are no user defined functions associated with the program or service program. When the indicator only is returned in output, the Difference Indicator value identifies whether SQL user defined functions associated with the object are equal. No value, indicator only3 When this attribute is returned in output, its Difference Indicator value indicates if supplemental group values are equal 50 character description
*SQLSP
*SQLUDF
SQL user defined functions Valid for programs and service programs only.
*SUPGRPIND
*TEXT2
284
Compare Object Attributes (CMPOBJA) attributes Description Data area type - data area types of DDM resolved to actual data area types Valid for data areas only. User profile ID number Valid for user profiles only. User-defined attribute User Class Valid for user profiles only. User profile extended attributes Returned Values (SYS1VAL, SYS2VAL) *CHAR, *DEC, *LGL
*UID
1 - 4294967294
*USRATR2 *USRCLS
*USRPRFEXT
Group which checks *ATTNPGM, *CCSID, *CNTRYID, *CRTOBJOWN, *CURLIB, *GID, *GRPAUT, *GRPAUTTYP, *GRPPRF, *INLMNU, *INLPGM, *LANGID, *LMTCPB, *MSGQ, *PRFOUTQ, *PWDEXPITV, *PWDIND, *SPCAUTIND, *SUPGRPIND, *USRCLS *ENABLED, *DISABLED6 For details, see Comparison results for user profile status (*USRPRFSTS) on page 297. Character value of data
*USRPRFSTS
*VALUE2
1. 2. 3. 4. 5. 6.
This attribute only applies to logical files. Use the Compare File Attributes (CMPFILA) command to compare or omit physical file attributes. Differences detected for this attribute are marked as *EC (equal configuration) when the compare request specified a data group and the object is configured for system journal replication with a configured object auditing value of *NONE. If *PRINT is specified for the output format on the compare request, an indicator appears in the System 1 and System 2 columns. If *OUTFILE is specified, these values are blank. These attributes are compared for object types of *FILE, *DTAQ, and *DTAARA. These are the only objects supported by IBM's user journals. The *OBJCTLLVL attribute is only supported on the following object types: *AUTL, *CNNL, *COSD, *CTLD, *DEVD, *DTAARA, *DTAQ, *FILE, *IPXD, *LIB, *LIND, *MODD, *NTBD, *NWID, *NWSD, and *USRPRF. The profile status is only compared if no data group is specified or the USRPRFSTS has a value of *SRC for the specified data group. If a data group is specified on the CMPOBJA command and the USRPRFSTS value on the object entry has a value of *TGT, *ENABLED, or *DISABLED, the user profile status is not compared.
285
Object auditing value Authority attributes Authority list name Pre-determined set of basic attributes Coded character set Create timestamp Data cyclic redundancy check (CRC) Data size Pre-determined, extended set
*JOURNAL
Journal information
286
Compare IFS Attributes (CMPIFSA) attributes Description Current or last journal library Journal optional entries Object type File owner Archived file PC Attributes Hidden file Read only attribute System file Primary group Private authority indicator Returned Values (SYS1VAL, SYS2VAL) 10 character name *YES, *NO *STMF, *DIR, *SYMLNK 10 character name *YES, *NO Group which checks *PCARCHIVE, *PCHIDDEN, *PCREADO, *PCSYSTEM *YES, *NO *YES, *NO *YES, *NO *NONE, user profile name No value, indicator only4 When this attribute is returned in output, its Difference Indicator value indicates if the number of private authorities and private authority values are equal. No value, indicator only4 When this attribute is returned in output, its Difference Indicator value indicates if the public authority values are equal.
*PUBAUTIND
1.
2.
3. 4.
Differences detected for this attribute are marked as *EC (equal configuration) when the compare request specified a data group and the object is configured for system journal replication with a configured object auditing value of *NONE. The *CRTTSP attribute does not compare directories (*DIR) or symbolic links (*SYMLNK). For stream files (*STMF), the #IFSATR audit omits the *CRTTSP attribute from comparison since creation timestamps are not preserved during replication. Running the CMPIFSA command will detect differences in the creation timestamps for stream files. When a stream file has Storage Freed *YES on either the source system or target system, the status of this attribute is reflected as not supported (*NS) and the data has not been compared. If *PRINT is specified in the comparison, an indicator appears in the system 1 and system 2 columns. If *OUTFILE is specified, these values are blank.
287
Object audit value Authority attributes Authority list name Pre-determined set of basic attributes
Coded character set Create timestamp Data size Pre-determined, extended set
Modify timestamp Object type File owner Archived file PC Attributes Hidden file Read only attribute
288
Compare DLO Attributes (CMPDLOA) attributes Description System file Primary group Private authority indicator Returned Values (SYS1VAL, SYS2VAL) *YES, *NO *NONE, user profile name No value, indicator only3 When this attribute is returned in output, its Difference Indicator value if the number of private authorities and private authority values are equal No value, indicator only1 When this attribute is returned in output, its Difference Indicator value if the public authority values are equal 50 character description
*PUBAUTIND
*TEXT
1. 2. 3.
Text description
This attribute is not supported for DLOs with an object type of *FLR. This attribute is always compared. If *PRINT is specified in the comparison, an indicator appears in the system 1 and system 2 columns. If *OUTFILE is specified, these values are blank.
289
When specified on the CMPOBJA command, these values apply only to files, data areas, or data queues. When specified on the CMPFILA command, these values apply only to PF-DTA and PF38-DTA files. *JOURNAL *JOURNALED Object journal information attributes. This value acts as a group selection, causing all other journaling attributes to be selected Journal Status. Indicates whether the object is currently being journaled. This attribute is always compared when any of the other journaling attributes are selected. Journal. Indicates the name of the current or last journal. If blank, the object has never been journaled. Journal Image. Indicates the kinds of images that are written to the journal receiver for changes to objects. Journal Library. Identifies the library that contains the journal. If blank, the object has never been journaled. Journal Omit. Indicates whether file open and close journal entries are omitted.
2.
When these values are specified on a Compare command, the journal status (*JOURNALED) attribute is always evaluated first. The result of the journal status comparison determines whether the command will compare the specified attribute. Although *JRNIMG can be specified on the CMPIFSA command, it is not compared even when the journal status is as expected. The journal image status is reflected as not supported (*NS) because the operating system only supports after (*AFTER) images.
Compares that do not specify a data group - When no data group is specified on the compare request, MIMIX compares the journaled status (*JOURNALED attribute). Table 46 shows the result displayed in the Differences Indicator field. If the file or
290
object is not journaled on both systems, the compare ends. If both source and target systems are journaled, MIMIX then compares any other specified journaling attribute.
Table 46. Difference indicator values for *JOURNALED attribute when no data group is specified Difference Indicator Target Journal Status 1 Yes Source No *NOTFOUND
1.
The returned values for journal status found on the Source and Target systems are shown in the SYS1VAL and SYS2VAL fields. Which system is source and which is target is determined by the value of the DTASRC field.
Compares that specify a data group - When a data group is specified on the compare request, MIMIX compares the journaled status (*JOURNALED attribute) to the configuration values. If both source and target systems are journaled according to the expected configuration settings, then MIMIX compares any other specified journaling attribute against the configuration settings. The Compare commands vary slightly in which configuration settings are checked. For CMPFILA requests, if the journaled status is as configured, any other specified journal attributes are compared. Possible results from comparing the *JOURNALED attribute are shown in Table 47. For CMPOBJA and CMPIFSA requests, if the journaled status is as configured and the configuration specifies *YES for Cooperate with database (COOPDB), then any other specified journal attributes are compared. Possible results from comparing the *JOURNALED attribute are shown in Table 47 and Table 48. If the configuration specifies COOPDB(*NO), only the journaled status is compared; possible results are shown in Table 49.
Table 47, Table 48, and Table 49 show results for the *JOURNALED attribute that can appear in the Difference Indicator field when the compare request specified a data group and considered the configuration settings.
291
Table 47 shows results when the configured settings for Journal on target and Cooperate with database are both *YES.
Table 47. Difference indicator values for *JOURNALED attribute when a data group is specified and the configuration specifies *YES for JRNTGT and COOPDB Difference Indicator Target Journal Status 1 Yes Source No *NOTFOUND
1.
The returned values for journal status found on the Source and Target systems are shown in the SYS1VAL and SYS2VAL fields. Which system is source and which is target is determined by the value of the DTASRC field.
Table 48 shows results when the configured settings are *NO for Journal on target and *YES for Cooperate with database. .
Table 48. Difference indicator values for *JOURNALED attribute when a data group is specified and the configuration specifies *NO for JRNTGT and *YES for COOPDB. Difference Indicator Target Journal Status 1 Yes Source No *NOTFOUND
1.
The returned values for journal status found on the Source and Target systems are shown in the SYS1VAL and SYS2VAL fields. Which system is source and which is target is determined by the value of the DTASRC field.
Table 49 shows results when the configured setting for Cooperate with database is *NO. In this scenario, you may want to investigate further. Even though the Difference Indicator shows values marked as configured (*EC), the object can be not journaled
292
on one or both systems. The actual journal status values are returned in the System 1 Value (SYS1VAL) and System 2 Value (SYS2VAL) fields.
Table 49. Difference indicator values for *JOURNALED attribute when a data group is specified and the configuration specifies *NO for COOPDB. Difference Indicator Target Journal Status 1 Yes Source No *NOTFOUND
1.
The returned values for journal status found on the Source and Target systems are shown in the SYS1VAL and SYS2VAL fields. Which system is source and which is target is determined by the value of the DTASRC field.
Because the data groups values for Journal image and Omit open/close entries can be overridden by a data group file entry or a data group object entry, the CMPFILA and CMPOBJA commands also retrieve these values from the entries. The values determined after the order of precedence is resolved, sometimes called the overall MIMIX configuration values, are used for the compare. For CMPOBJA and CMPIFSA requests, the value of the Cooperate with database (COOPDB) parameter is retrieved from the data group object entry or data group IFS entry. The default value in object entries is *YES, while the default value in IFS entries is *NO.
293
The returned values for *ASP attribute on the Source and Target systems are shown in the SYS1VAL and SYS2VAL fields. Which system is source and which is target is determined by the value of the DTASRC field.
Compares that specify a data group - When a data group is specified on the compare request (CMPFILA, CMPDLOA, CMPIFSA commands), MIMIX does not compare the *ASP attribute. When a data group is specified on a CMPOBJA request which specifies an object type except libraries (*LIB), MIMIX does not compare the *ASP attribute. Table 51 shows the possible results in the Difference Indicator field
Table 51. Difference Indicator values for non-library objects when the request specified a data group Difference Indicator Target ASP Values 1 ASP1 Source ASP2 *NOTFOUND
1.
The returned values for *ASP attribute on the Source and Target systems are shown in the SYS1VAL and SYS2VAL fields. Which system is source and which is target is determined by the value of the DTASRC field.
294
For CMPOBJA requests which specify a a data group and an object type of *LIB, MIMIX considers configuration settings for the library. Values for the System 1 library ASP number (LIB1ASP), System 1 library ASP device (LIB1ASPD), System 2 library ASP number (LIB2ASP), and System 2 library ASP device (LIB2ASPD) are retrieved from the data group object entry and used in the comparison. Table 52, Table 53, and Table 54 show the possible results in the Difference Indicator field. Note: For Table 52, Table 53, and Table 54, the results are the same even if the system roles are switched. Table 52 shows the expected values for the ASP attribute when the request specifies a data group and the configuration specifies *SRCLIB for the System 1 library ASP number and the data source is system 2. .
Table 52. Difference Indicator values for libraries when a data group is specified and configured values are LIB1ASP(*SRCLIB) and DTASRC(*SYS2). Difference Indicator Target ASP Values 1 ASP1 Source ASP2 *NOTFOUND
1.
The returned values for *ASP attribute on the Source and Target systems are shown in the SYS1VAL and SYS2VAL fields. Which system is source and which is target is determined by the value of the DTASRC field.
Table 53 shows the expected values for the ASP attribute the request specifies a data group and the configuration specifies 1 for the System 1 library ASP number and the data source is system 2.
Table 53. Difference Indicator values for libraries when a data group is specified and configured values are LIB1ASP(1) and DTASRC(*SYS2) Difference Indicator Target ASP Values 1 Source 2 *NOTFOUND
1.
1
The returned values for *ASP attribute on the Source and Target systems are shown in the SYS1VAL and SYS2VAL fields. Which system is source and which is target is determined by the value of the DTASRC field.
Table 54 shows the expected values for the ASP attribute when the request specifies a data group and the configuration specifies *ASPDEV for the System 1 library ASP
295
number, DEVNAME is specified for the System 1 library ASP device, and data source is system 2. .
Table 54. Difference Indicator values for libraries when a data group is specified and configured values are LIB1ASP(*ASPDEV), LIB1ASPD(DEVNAME) and DTASRC(*SYS2) Difference Indicator Target ASP Values 1 1 Source 2 *NOTFOUND
1.
The returned values for *ASP attribute on the Source and Target systems are shown in the SYS1VAL and SYS2VAL fields. Which system is source and which is target is determined by the value of the DTASRC field.
296
Compares that do not specify a data group - When the CMPOBJA command does not specify a data group, MIMIX compares the status values between source and target systems. The result is displayed in the Differences Indicator field, according to Table 38 in Interpreting results of audits that compare attributes on page 268. Compares that specify a data group - When the CMPOBJA command specifies a data group, MIMIX checks the configuration settings and the values on one or both systems. (For additional information, see How configured user profile status is determined on page 298.) When the configured value is *SRC, the CMPOBJA command compares the values on both systems. The user profile status on the target system must be the same as the status on the source system, otherwise an error condition is reported. Table 55 shows the possible values.
Table 55. Difference Indicator values when configured user profile status is *SRC Difference Indicator Target User profile status *ENABLED Source *DISABLED *NOTFOUND *ENABLED *EC *NC *NE *DISABLED *NC *EC *NE *NOTFOUND *NE *NE *UN
When the configured value is *ENABLED or *DISABLED, the CMPOBJA command checks the target system value against the configured value. If the user profile status on the target system does not match the configured value, an error condition is reported. The source system user profile status is not relevant. Table 56 and Table 57
297
show the possible values when configured values are *ENABLED or *DISABLED, respectively.
Table 56. Difference Indicator values when configured user profile status is *ENABLED Difference Indicator Target User profile status *ENABLED Source *DISABLED *NOTFOUND *ENABLED *EC *EC *NE *DISABLED *NC *NC *NE *NOTFOUND *NE *NE *UN
Table 57.
Difference Indicator values when configured user profile status is *DISABLED Difference Indicator Target
When the configured value is *TGT, the CMPOBJA command does not compare the values because the result is indeterminate. Any differences in user profile status between systems are not reported. Table 58 shows possible values.
Table 58. Difference Indicator values when configured user profile status *TGT Difference Indicator Target User profile status *ENABLED Source *DISABLED *NOTFOUND *ENABLED *NA *NA *NE *DISABLED *NA *NA *NE *NOTFOUND *NE *NE *UN
298
in an object entry, the default is to use the value *SRC from the data group definition. Table 59 shows the possible values at both the data group and object entry levels.
Table 59. *DGDFT Configuration values for replicating user profile status Only available for data group object entries, this indicates that the specified in the data group definition is used for the user profile statue. This is the default value for object entries. The status of the user profile is set to *DISABLED when the user profile is created or changed on the target system. The status of the user profile is set to *ENABLED when the user profile is created or changed on the target system. This is the default value in the data group definition. The status of the user profile on the source system is always used when the user profile is created or changed on the target system. If a new user profile is created, the status is set to *DISABLED. If an existing user profile is changed, the status of the user profile on the target system is not altered.
*TGT
1.
Data group definitions use these values. In data group object entries, the values *DISABLED and *ENABLED are used but have the same meaning.
299
300
Table 61 shows the possible Difference Indicator values when the user profile passwords are different on the local and remote systems and are not defined as *NONE.
Table 61. Difference Indicator values when user profile passwords are different, but not *NONE Difference Indicator Remote System User Profile Password *ENABLED *DISABLED Local System Expired Not Found *ENABLED *NE *NA *NA *NE *DISABLED *NE *NA *NA *NE Expired *NE *NA *NA *NE Not Found *NE *NE *NE *EQ
Table 62 shows the possible Difference Indicator values when the user profile passwords are defined as *NONE on the local and remote systems.
Table 62. Difference Indicator values when user profile passwords are *NONE. Difference Indicator Remote System User Profile Password *ENABLED *DISABLED Local System Expired Not Found *ENABLED *NA *NA *NA *NE *DISABLED *NA *NA *NA *NE Expired *NA *NA *NA *NE Not Found *NE *NE *NE *EQ
301
302
This procedure describes an IPL performed under normal circumstances. It does not address IPL considerations for system switching environments. Before beginning this procedure, review your startup procedures to determine whether subsystems will start after the IPL. This startup program is defined in the QSTRUPPGM system value.
To perform an IPL in a MIMIX environment, do the following: 1. End MIMIX from either the source or target system. The End MIMIX (ENDMMX) command attempts to end the MIMIX processes for the installation, including the MIMIX managers and the data groups. Data groups can be ended in an immediate (*IMMED) or controlled (*CNTRLD) manner. Note: For more information about the ENDMMX command, see Choices when ending replication on page 141. 2. End the MIMIX subsystems on both the source and target system. On each system, type the following on a command line and press Enter: ENDSBS SBS(MIMIXSBS) OPTION(*IMMED) 3. Perform the IPL. 4. If your subsystems do not start during the startup procedures defined in the QSTRUPPGM system value, start the MIMIX subsystems on both the source and target systems. On each system, type the following on a command line and press Enter: STRSBS SBS(MIMIXQGPL/MIMIXSBS) 5. Verify the communication links start, using the Verify Communications Link (VFYCMNLNK) command. Note: For more information about the VFYCMNLNK command, see Verifying a communications link for system definitions on page 244. 6. Start MIMIX from either the source or target system. The Start MIMIX (STRMMX) command starts the MIMIX processes for the installation, including the MIMIX managers and the data groups. Note: For more information about the STRMMX command, see Starting MIMIX on page 147.
303
Table 63 indicates which procedures are needed for different upgrade scenarios. Use these instructions in conjunction with the instructions provided by IBM for upgrading from one IBM i release to another IBM i release.
Table 63. IBM i operating system upgrade scenarios and recommended processes for handling MIMIX during the upgrade Perform these procedures 1. Perform the preparation steps described in Prerequisites for performing an OS upgrade on either system on page 304. 2. Follow the procedure in MIMIX-specific steps for an OS upgrade on the backup system on page 305. 1. Perform the preparation steps described in Prerequisites for performing an OS upgrade on either system on page 304. 2. Perform one of the following procedures: If you need to maintain user access to production applications during the upgrade, perform a planned switch as described in MIMIX-specific steps for an OS upgrade on the production system with switching on page 307. Your production operations will be temporarily running on the backup system. If you have more flexibility with scheduling downtime, you can perform the upgrade without switching as described in MIMIX-specific steps for an OS upgrade on the production system without switching on page 308. 1. Perform the preparation steps described in Prerequisites for performing an OS upgrade on either system on page 304. 2. Upgrade the backup system first following the MIMIX-specific steps for an OS upgrade on the backup system on page 305. By doing this first, you can ensure that the backup system supports all the capabilities of the production system and you can work through problems or custom operations before affecting your production environment. 3. Once you have the verified that the backup system is upgraded and operating as desired, perform one of the following procedures to upgrade IBM i on the production system: If you need to maintain user access to production applications during the upgrade, perform a planned switch as described in MIMIX-specific steps for an OS upgrade on the production system with switching on page 307. Your production operations will be temporarily running on the backup system. If you have more flexibility with scheduling downtime, you can perform the upgrade without switching as described in MIMIX-specific steps for an OS upgrade on the production system without switching on page 308
304
a. Check the compatibility of the operating systems on the production and backup systems, ensuring the systems will meet the requirements of a MIMIXsupported environment once the IBM i operating system upgrade has occurred. b. Ensure the recommended IBM IBM i PTFs have been applied according to your IBM i version. c. Ensure the recommended MIMIX service packs have been applied according to your MIMIX version. Review the Read Me document that corresponds to the MIMIX service pack, and check the website for relevant Technical Alerts and FAQs. 2. Review your startup procedures to understand how your environment is configured to start after an IPL. This startup program is defined in the QSTRUPPGM system value. An IBM i upgrade may include rebuilding access paths, converting formats, or performing other operations that must be complete before MIMIX or other applications are started. The upgrade may not complete successfully if your QSTRUPPGM procedures start MIMIX or other applications during an IPL. Ensure that these processes are disabled before continuing with the IBM i upgrade.
To perform an operating system upgrade of the backup system in a MIMIX environment, do the following: 1. Ensure that you have completed any prerequisite tasks for your upgrade scenario. See Table 63 for a list of required tasks for different upgrade scenarios. 2. End all user applications, user interfaces, and operations actively running on the backup system. Be sure to address the following: Disarm any monitors, such as MIMIX Monitor, robot jobs, or other job schedulers. Make sure all users are off the system.
Note: For more information, refer to your Runbook, Using MIMIX Monitor, and your applications user manuals.
305
3. End the data groups from either system using the command: ENDDG DGDFN(*ALL) ENDOPT(*CNTRLD) Note: For more information about ending data groups see Choices when ending replication on page 141. 4. Wait until the status of each data group becomes inactive (red) by monitoring the status on the Work with Data Groups (WRKDG) display. Note: For more information about the WRKDG display, see The Work with Data Groups display - 5250 emulator on page 54. 5. If you have applications that use commitment control, ensure there are no open commit cycles. For more information, see Checking for open commit cycles on page 139. a. If an open commit cycle exists, restart the data group and repeat Step 3, Step 4, and Step 5 until there is no open commit cycle for any apply session. 6. Use the following command to end other MIMIX products in the installation library, end the MIMIX managers, and end the RJ link: ENDMMX ENDOPT(*CNTRLD) ENDRJLNK(*YES) 7. Use the following command on the production and backup system to end the MIMIX subsystems: ENDSBS SBS(MIMIXSBS) OPTION(*IMMED) 8. Complete the operating system upgrade. Allow any upgrade conversions and access path rebuilds to complete before continuing with the next step. Note: During the IBM i upgrade, make sure you perform a system save on the system being upgraded. This step will provide you with a backup of existing data. 9. Ensure the names of the journal receivers match the journal definitions: a. From the backup system, specify the command:
installation-name/WRKJRNDFN JRNDFN(QAUDJRN *LOCAL)
b. Next to the JRNDFN(QAUDJRN *LOCAL) journal definition, specify 14 (Build) and press F4. Type *JRNDFN for the Source for values parameter and press Enter. 10. Start the MIMIX subsystems on both the production and backup systems using the following command from each system: STRSBS SBS(MIMIXQGPL/MIMIXSBS) 11. Perform a normal start of the data groups from either system using the STRMMX command. This step also starts the MIMIX managers. 12. Perform your normal process for validating the IBM i release upgrade. Notes: At your convenience, schedule a switch to verify that your applications function on the new operating system on the backup system.
306
After the IBM i upgrade, you may receive object errors for program object types (*PGM) if your source IBM i version is higher than your target IBM i version. MIMIX is unable to save/restore *PGM objects in this case. To avoid these errors, compile the *PGM objects on the source system using the Create Program (CRTPGM) command. On the Target release prompt, specify the IBM i version of your target system.
To perform an operating system upgrade of the production system in a MIMIX environment while maintaining availability, do the following: 1. Ensure that you have completed any prerequisite tasks for your upgrade scenario. See Table 63 for a list of required tasks for different upgrade scenarios. 2. Use the procedures in your Runbook to perform a planned switch to the backup system. Note: Do not perform the synchronize phase of your switch procedures. If you do not have a Runbook, you need to follow your processes for the following: End all user applications, user interfaces, and operations actively running on the production system. Disarm any monitors, robot jobs, or other job schedulers and make sure all users are off the system. Resolve any errors in MIMIX and perform a controlled end of the data groups. Perform a planned switch to the backup system.
3. End MIMIX products in the installation library and end the RJ link using the command: ENDMMX ENDOPT(*CNTRLD) ENDRJLNK(*YES) Note: For more information about the ENDMMX command, see Choices when ending replication on page 141. 4. From the production system, use the following command to end the MIMIX
307
subsystems: ENDSBS SBS(MIMIXSBS) OPTION(*IMMED) 5. Start applications on the backup system and allow users to access their applications from the backup system. 6. On the production system, complete the operating system upgrade. Allow any upgrade conversions and access path rebuilds to complete before continuing with the next step. Note: During the IBM i upgrade, make sure you perform a system save on the system being upgraded. This step will provide you with a backup of existing data. 7. Ensure the names of the journal receivers match the journal definitions: a. From the original production system, specify the command:
installation-name/WRKJRNDFN JRNDFN(QAUDJRN *LOCAL)
b. Next to the JRNDFN(QAUDJRN *LOCAL) journal definition, specify 14 (Build) and press F4. Type *JRNDFN for the Source for values parameter and press Enter. 8. Follow your Runbook procedures to perform a synchronization. If you do not have a Runbook, you need to follow your processes for the following: Starting MIMIX subsystems Starting data groups
9. Follow your Runbook procedures to perform a planned switch back to the production system and start replication. If you do not have a Runbook, you need to follow your processes to switch replication so that you return to your normal replication environment. 10. Perform your normal process for validating the IBM i release upgrade. Note: After the IBM i upgrade, you may receive object errors for program object types (*PGM) if your source IBM i version is higher than your target IBM i version. MIMIX is unable to save/restore *PGM objects in this case. To avoid these errors, compile the *PGM objects on the source system using the Create Program (CRTPGM) command. On the Target release prompt, specify the IBM i version of your target system.
308
direction and state of replication for a classic production to backup environment. MIMIX Model Switch Framework commands, such as RUNSWTFWK, are typically run from the backup system. You can find more information about using the RUNSWTFWK command in the Using MIMIX Monitor book.
To perform an operating system upgrade of the production system in a MIMIX environment without switching, do the following: 1. Ensure that you have completed any prerequisite tasks for your upgrade scenario. See Table 63 for a list of required tasks for different upgrade scenarios. 2. End all user applications, user interfaces, and operations actively running on the production system. Be sure to address the following: Disarm any monitors, such as MIMIX Monitor, robot jobs, or other job schedulers. Make sure all users are off the system.
Note: For more information, refer to your Runbook, Using MIMIX Monitor, and your applications user manuals. 3. End the data groups from either system using the command: ENDDG DGDFN(*ALL) ENDOPT(*CNTRLD) Note: For more information about ending data groups see Choices when ending replication on page 141. 4. Wait until the status of each data group becomes inactive (red) by monitoring the status on the Work with Data Groups (WRKDG) display. Note: For more information about the WRKDG display, see The Work with Data Groups display - 5250 emulator on page 54. 5. If you have applications that use commitment control, ensure there are no open commit cycles. For more information, see Checking for open commit cycles on page 139. a. If an open commit cycle exist, restart the data group and repeat Step 3, Step 4, and Step 5 until there is no open commit cycle for any apply session. 6. Use the following command to end other MIMIX products in the installation library, end the MIMIX managers, and end the RJ link: ENDMMX ENDOPT(*CNTRLD) ENDRJLNK(*YES) 7. End the MIMIX subsystems on the production system and on the backup system. On each system, type the following on a command line and press Enter: ENDSBS SBS(MIMIXSBS) OPTION(*IMMED) 8. Complete the operating system upgrade. Allow any upgrade conversions and access path rebuilds to complete before continuing with the next step. Note: During the IBM i upgrade, make sure you perform a system save on the system being upgraded. This step will provide you with a backup of existing data. 9. Start the MIMIX subsystems on the production system and the backup system as
309
you would during the synchronization phase of a switch. From each system, type the following on a command line and press Enter: STRSBS SBS(MIMIXQGPL/MIMIXSBS) 10. Ensure the names of the journal receivers match the journal definitions: a. From the production system, specify the command:
installation-name/WRKJRNDFN JRNDFN(QAUDJRN *LOCAL)
b. Next to the JRNDFN(QAUDJRN *LOCAL) journal definition, specify 14 (Build) and press F4. Type *JRNDFN for the Source for values parameter and press Enter. c. Record the newly attached journal receiver name by placing the cursor on the posted message and pressing F1 or Help. 11. Using the information you gathered in Step 10, start each data group as follows (This step also starts the MIMIX managers.): a. From the WRKDG display, type an 9 (Start DG) next to the data group and press Enter. The Start Data Group display appears. b. At the Object journal receiver prompt, specify the receiver name recorded in Step 10c. c. At the Object large sequence number prompt, specify *FIRST. d. At the Clear pending prompt, specify *YES. 12. Start any applications that you disabled prior to completing the IBM i upgrade according to your Runbook instructions. These applications are normally started in the program defined in the QSTRUPPGM system value. Allow users back on the production system. Note: After the IBM i upgrade, you may receive object errors for program object types (*PGM) if your source IBM i version is higher than your target IBM i version. MIMIX is unable to save/restore *PGM objects in this case. To avoid these errors, compile the *PGM objects on the source system using the Create Program (CRTPGM) command. On the Target release prompt, specify the IBM i version of your target system.
310
image change
Before you start a hardware upgrade on either system, consider the following: Ensure the new system is compatible with and meets the requirements for a MIMIX-supported environment. For more information, see the Supported Environments Matrix in the Technical Documents section of Support Central. Apply the latest MIMIX fixes on both systems. The fixes are available by product in the Downloads section of Support Central. Obtain new MIMIX product access codes. These codes are required for products when a model, feature, or serial number changes. For more information, see Working with access codes in the License and Availability Manager book. Determine whether a planned switch is required prior to the hardware upgrade. For example, a switch would be necessary if the source system is being upgraded and users need to continue working while the upgrade takes place. To perform a switch, follow the steps in your runbook. For more information, see Switching on page 204. Determine if the transfer definitions need to be changed. For example, transfer definitions would need to be changed if the IP addresses or host names change. For more information, see Configuring transfer definitions in the MIMIX Reference book.
311
b. Press Enter. c. Press F7 for object status and print the display. Keep the information for later use. d. Press F8 for database status and print the display. Keep the information for later use. 5. Optional step: Save the MIMIX software by doing a full system save or by saving all MIMIX installation libraries: LAKEVIEW MIMIXQGPL MIMIX-installation-library MIMIX-installation-library_0 MIMIX-installation-library_1 /LakeviewTech (directory tree)
6. Optional step: If upgrading the source system and performing a switch, follow the steps in your runbook. For more information, see Switching on page 204.
312
MIMIX procedures when performing a hardware upgrade with a disk image change
MIMIX procedures when performing a hardware upgrade with a disk image change
When a hardware upgrade is being performed on a system, MIMIX software may need to be saved from the system being replaced and then restored to the system that is its replacement. The saved MIMIX information must be restored on a system that performs the same role within MIMIX operations. For example, if the network system is being replaced, MIMIX software must be saved from the network system and restored on the new network system. A network system cannot be restored to a new management system. This topic describes steps to consider prior to saving and restoring MIMIX software when upgrading from one system to another. Performing these steps can ensure that MIMIX products start properly once the hardware upgrade is complete. IMPORTANT! To ensure the integrity of your data, contact your Certified MIMIX Consultant for assistance performing a hardware upgrade.
Considerations for performing a hardware system upgrade with a disk image change
Before you start a hardware upgrade on either system, consider the following: Contact your contact your Certified MIMIX Consultant prior to performing the upgrade for instructions that may be specific to your environment. Ensure the new system is compatible with and meets the requirements for a MIMIX-supported environment. For more information, see the Supported Environments Matrix in the Technical Documents section of Support Central. Apply the latest MIMIX fixes on both systems. The fixes are available by product in the Downloads section of Support Central. Obtain new MIMIX product access codes. These codes are required for products when a model, feature, or serial number changes. For more information, see Working with access codes in the License and Availability Manager book. Determine whether a planned switch is required prior to the hardware upgrade. For example, a switch would be necessary if the source system is being upgraded and users need to continue working while the upgrade takes place. To perform a switch, follow the steps in your runbook. For more information, see Switching on page 204. Determine if the transfer definitions need to be changed. For example, transfer definitions would need to be changed if the IP addresses or host names change. For more information, see Configuring transfer definitions in the MIMIX Reference book. Copy all automation for MIMIX to the new machine, including exit programs. Transfer any modifications of programs such as QSTARTUP to the new system. Modifications may be needed to start the MIMIX subsystem after an IPL. Refer to your Runbook for an overview of the required automation changes that need to be performed on the system.
313
IMPORTANT! To ensure the integrity of your data, contact your Certified MIMIX Consultant for assistance performing a system restore. For information about MIMIX-supported environments, see the Supported Environments Matrix in the Technical Documents section of Support Central.
314
Notices
Copyright 1999, 2009, Vision Solutions, Inc. All rights reserved. The information in this document is subject to change without notice and is furnished under a license agreement. This document is proprietary to Vision Solutions, Inc., and may be used only as authorized in our license agreement. No portion of this manual may be copied or otherwise reproduced, translated, or transmitted in whole or part, without the express consent of Vision Solutions, Inc. If you are an entity of the U.S. government, you agree that this documentation and the program(s) referred to in this document are Commercial Computer Software, as defined in the Federal Acquisition Regulations (FAR), and the DoD FAR Supplement, and are delivered with only those rights set forth within the license agreement for such documentation and program(s). Use, duplication or disclosure by the Government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFAR 252.227-7013 (48 CFR) or subparagraphs (c)(1) & (2) of the Commercial Computer Software Restricted Rights clause at FAR 52.227-19. Vision Solutions, Inc. makes no warranty of any kind regarding this material and assumes no responsibility for any errors that may appear in this document. The program(s) referred to in this document are not specifically developed, or licensed, for use in any nuclear, aviation, mass transit, or medical application or in any other inherently dangerous applications, and any such use shall remove Vision Solutions, Inc. from liability. Vision Solutions, Inc. shall not be liable for any claims or damages arising from such use of the Program(s) for any such applications. Examples and Example Programs: This book contains examples of reports and data used in daily operation. To illustrate them as completely as possible the examples may include names of individuals, companies, brands, and products. All of these names are fictitious. Any similarity to the names and addresses used by an actual business enterprise is entirely coincidental. This book contains small programs that are furnished by Vision Solutions, Inc. as simple examples to provide an illustration. These examples have not been thoroughly tested under all conditions. Vision Solutions, therefore, cannot guarantee or imply reliability, serviceability, or function of these example programs. All programs contained herein are provided to you AS IS. THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE EXPRESSLY DISCLAIMED. MIMIX and Vision Solutions are registered trademarks of Vision Solutions, Inc. IntelliStart, MIMIX dr1, MIMIX AutoGuard, MIMIX AutoNotify, MIMIX Availability Manager, MIMIX ha1, MIMIX ha Lite, MIMIX DB2 Replicator, MIMIX Object Replicator, MIMIX Monitor, MIMIX Promoter, MIMIX Switch Assistant, RJ Link, Replicate1, Vision AutoValidate, and Vision Cluster1 are trademarks of Vision Solutions, Inc. AS/400, DB2, eServer, i5/OS, IBM, iSeries, OS/400, Power, System i, and WebSphere are trademarks of International Business Machines Corporation. Internet Explorer, Microsoft, Windows, and Windows Server are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. Netscape is a registered trademark of AOL LLC. Mozilla and Firefox are trademarks of the Mozilla Foundation. UNIX is a registered trademark of The Open Group in the United States and other countries. Java and all Java-based trademarks are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States and other countries. All other trademarks are the property of their respective owners. Corporate Headquarters Vision Solutions, Inc. Irvine, California USA Tel: +1 (949) 253-6500
Index
Symbols
*FAILED activity entry 185, 188 *HLD file entry 170 tracking entry 179 *HLDERR file entry 170 tracking entry 179 *HLDRLTD file entry 170 last performed 100 last successful run 98 policies which affect 109 prevent from running 110 problems reported in installation 54 recommendations 81, 82 recovery phase 19 requirements 81 results 93, 95 rule name 104 running immediately 91 schedule 102 schedule, considerations for changing 105 schedule, shipped default 104 scheduler, alternative 108 scheduler, automatic 104 status 85 status from 5250 emulator 52 status from MIMIX Availability Manager 48 status, compliance 98 status, runtime 87 summary 87 when not to audit 23 audit level best practice 81 changing before switch 210 differences, displaying 92 audit results 93, 95 #DGFE rule 263 #DLOATR rule 288 #DLOATR rule, ASP attributes 294 #FILATR rule 273 #FILATR rule, ASP attributes 294 #FILATR rule, journal attributes 290 #FILATRMBR rule 273 #FILATRMBR rule, ASP attributes 294 #FILATRMBR rule, journal attributes 290 #FILDTA rule 265 #IFSATR rule 286 #IFSATR rule, ASP attributes 294 #IFSATR rule, journal attributes 290 #MBRRCDCNT rule 265 #OBJATR rule 278 #OBJATR rule, ASP attributes 294 #OBJATR rule, journal attributes 290 #OBJATR rule, user profile password attribute 300 #OBJATR rule, user profile status attribute 297 interpreting, attribute comparisons 268
A
accessing MIMIX Availability Status display 50 MIMIX Main Menu 42 status from MIMIX Availability Manager 48 activity entries, object confirm delay/retry cycle 189 failed, resolving 185 remove history 190 retrying 188 additional resources 11 agintro 79 applications, reducing contention with 242 attributes, supported CMPDLOA command 288 CMPFILA command 273 CMPIFSA command 286 CMPOBJA command 278 audit after a configuration change 106 authority level to run 81 automatic recovery 82 before switching 81 best practice 20, 81, 100 bi-directional environment considerations 22 changing schedule 105, 106 compare phase 19 comparison levels 19, 81 compliance 98 compliance threshold 28, 29 concepts 19 definition of 18 differences, resolving 93, 95 displaying compliance status 85, 100 displaying runtime status 85, 90 displaying schedule 102 ending 91 getting started 20 job log 96
316
interpreting, file data comparisons 265 resolving problems 95, 263 troubleshooting 96 auditing level, object set when starting a data group 140 used for replication 192 authority level for auditing, product 81 AutoGuard, MIMIX 15 automatic error recovery policies for 33 system journal replication 34 user journal replication 33 automatic recovery audit recommendations 82 audits 27 concept 18 system journal replication 27 user journal replication 27 AutoNotify feature, MIMIX 124 Availability Manager, MIMIX 15 Availability Status display, MIMIX 50
B
backlog, identifying a 76 backup system 16 best practice audit frequency 100 audit level 29, 81 audit level before switch 82, 210 audit threshold 28, 29 MIMIX AutoGuard 20 switch frequency 204, 215 switch threshold 31 switching 205 bi-directional environment policy considerations 22
C
clear error entries processing 136 when to 136 clear pending entries check for open commits 139 open commit cycle prevents 139 processing 136 resolving open commits before 140 when to 136 cold start, replacement for 136 commands, by mnemonic
CHGDG 233 CHKDGFE 106, 246, 263 CRTDGTSP 254 DLTDGTSP 256 DSPDGSTS 64 DSPDGTSP 256 DSPMMXMSGQ 167 DSPRJLNK 227 ENDDG 131, 141 ENDJRNFE 196 ENDJRNIFSE 199 ENDJRNOBJE 202 ENDJRNPF 196 ENDMMX 131, 141, 147 ENDMMXMGR 165 ENDRJLNK 237 ENDSVR 223 HLDDGLOG 257 MIMIX 42 RLSDGLOG 257 RUNRULE 80, 115 RUNRULEGRP 80, 115 STRDG 131, 133, 135 STRJRNFE 195 STRJRNIFSE 198 STRJRNOBJE 201 STRMMX 131, 133, 147 STRMMXMGR 165 STRRJLNK 237 STRSVR 222 SWTDG 217, 219 VFYCMNLNK 244, 245 VFYJRNFE 197 VFYJRNIFSE 200 VFYJRNOBJE 203 VFYKEYATR 252 WRKCPYSTS 226 WRKDG 54 WRKDGACT 185 WRKDGACTE 186 WRKDGFE 170 WRKDGIFSTE 180 WRKDGOBJTE 180 WRKDGTSP 254 WRKMMXSTS 50, 125 WRKMSGLOG 168 WRKNFY 120 WRKRJLNK 228, 230 commands, by name Change Data Group 233
317
Check Data Group File Entries 246, 263 Check Data group File Entry 106 Create Data Group Timestamps 254 Delete DG Timestamps 256 Display Data Group Status 64 Display Data Group Timestamps 256 Display MIMIX Message Queue 167 Display RJ Link 227 End Data Group 131, 141 End Journal Physical File 196 End Journaling File Entry 196 End Journaling IFS Entries 199 End Journaling Obj Entries 202 End Lakeview TCP Server 223 End MIMIX 131, 141, 147 End MIMIX Managers 165 End RJ Link 237 Hold Data Group Log 257 MIMIX 42 MIMIX Availability Status 50 Release Data Group Log 257 Run Rule 80, 115 Run Rule Group 80, 115 Start Data Group 131, 133, 135 Start Journaling File Entry 195 Start Journaling IFS Entries 198 Start Journaling Obj Entries 201 Start Lakeview TCP Server 222 Start MIMIX 131, 133, 147 Start MIMIX Managers 165 Start RJ Link 237 Switch Data Group 217, 219 Verify Communications Link 244, 245 Verify Journaling File Entry 197 Verify Journaling IFS Entries 200 Verify Journaling Obj Entries 203 Verify Key Attributes 252 Work with Copy Status 226 Work with Data Group Activity 185 Work with Data Groups 54 Work with DG Activity Entries 186 Work with DG File Entries 170 Work with DG IFS Tracking Ent. 180 Work with DG Obj Tracking Ent. 180 Work with DG Timestamps 254 Work with Message Log 168 Work with MIMIX Availability Status 125 Work with Notifications 120 Work with RJ Links 228, 230 commit cycles
effect on audit comparison 265, 267 commit cycles, open checking for 139 checking for after a controlled end 153 effect on clear pend start 137 prevent a clear pending STRDG 139 preventing problems with 144 communications ending TCP sever 223 starting TCP sever 222 compare phase 19 compliance audit 98 concept 19 switch 215 switch, policies for 208, 209 compliance status audit 85 switch 215 concepts auditing 19 MIMIX 15 MIMIX AutoGuard 18 configuration audit after changing 106 determining data areas and data queues 235 determining, IFS objects 234 results of #DGFE audit after changing 263 constraints, CMPFILA file-specific attribute 273 contacting Vision Solutions 12 contention with applications, reducing 242 controlled end confirm end 153 description 143 procedure 152 wait time 144 copying active files 226 correcting file-level errors 176 record-level errors 177 CustomerCare 12
D
data areas and data queues determining configuration of 235 holding user journal entries for 182 resolving problems 180 tracking entries 179 verifying journaling 203
318
data group 15 activity details 61, 64 backlogs 76 controlled vs. immediate end 143 definition 16 determining if RJ link used 230 disabling 233 enabling 233 ending choices 141 ending considerations 146 ending controlled 152 ending immediately 151 ending selected processes 151 indication of disabled state 232 recovery point cleared 146 starting considerations 133, 135 starting selected processes 150 state, disabled or enabled 232 status from 5250 emulator 52 status from MIMIX Availability Manager 48 status, database view 71 status, detailed 61 status, merged view 65 status, object view 69 status, summary 54 switching 205, 217 system journal activity 61 timestamps 254 user journal activity 61 when to exclude from auditing 23 data group entry description 15 database apply (DBAPY) status 71 database error recovery, automatic 34 definition data group 16 journal 16 remote journal (RJ) link 16 system 16 transfer 16 delay intervals journal manager 164 system manager 164 delay/retry cycle, confirm object in a 189 differences, resolving audit 93, 95 disabled data group 232 displaying data group spooled file information 224 data group status details 61 long IFS object names 224
E
ending audit 91 MIMIX managers 164 MIMIXSBS subsystem 148 system and journal managers 165 TCP server 223 ending data group clears recovery point 146 considerations when ending 146 controlled end 152 controlled end wait time 144 controlled vs. immediate 143 how to confirm end 153 immediate end 151 processes 144 processes, effect of 159 processes, specifying selected 151 when to end RJ link 144 ending journaling data areas and data queues 202 files 196 IFS objects 199 IFS tracking entry 199 object tracking entry 202 ending MIMIX 147 considerations 141 controlled vs. immediate 143 end subsystem, when to also 148 follow up after 148 included processes 142 using default values 147 using specified values 148 when to end RJ link 144 ending replication 131 choices and considerations 141 controlled vs. immediate 143 ending RJ link independently from data group 237 when to end 144 Enterprise View 45 errors file level 176 record level 177 system journal replicated objects 185
319
target journal of RJ link 251 user journal replicated objects 170, 179
I
i5/OS upgrade 303 IFS objects determining configuration 234 file IDs (FIDs) 236 hold user journal entries for 182 path names 224 resolving problems 180 tracking entries for 179 verifying journaling 200 immediate end description 143 incomplete tracking entry 143 information and additional resources 11 installation, status of from 5250 emulator 50 from MIMIX Availability Manager 48 IPL 302
F
file file-level errors 176 hold journal entries 174 new 192 not journaled 57 record-level errors 177 replicated 170 file identifiers (FIDs) 236 file in error examine held journal entries 173 resolving 170 file on hold release and apply held entries 176 release and clear entries 176 release at synchronization point 175
J G
guidelines for auditing 81 job log for audit 96 journal 17 journal at create requirements 192 requirements and restrictions 193 journal cache or state resolving problems 57 status 72 journal definition 16 defined to RJ Link 231 journal entry description 17 unconfirmed 249 journal manager 16 delay intervals 164 ending 164, 165 resolving problems 164 starting 164 journal receiver 17 journaling 17 cannot end 196 data group problem with 56 ending for data areas and data queues 202 ending for IFS objects 199 ending for physical files 196 implicitly started 192 requirements for starting 192 starting for data areas and data queues 201
H
hardware upgrade MIMIX-specific steps 311 no disk image change 310 prerequisites 311 with a disk image change 313 held error (*HLDERR) file entry 170 preferred action for entry 171, 181 tracking entry 179 help, accessing 9 history log, removing completed entries 190 hold (*HLD) preferred action for held entry 171, 181 put file entry on hold 174 put tracking entry on hold 182 release a held file entry 176 release a held tracking entry 183 hold ignore (*HLDIGN) preferred action for ignored entry 171, 181 put file entry on hold ignore 174 put tracking entry on hold ignore 182 hold related (*HLDRLTD) 171 hot backup 13
320
starting for IFS objects 198 starting for physical files 195 starting, ending, and verifying 191 verifying for data areas and data queues 203 verifying for IFS objects 200 verifying for physical files 197 journaling status data areas and data queues 201 files 195 IFS objects 198
K
keyed replication verifying file attributes 252
L
last audit performed 98 last switch performed 215 log space 17 logging in, first time 37 long IFS path names 224
policy default 31 MIMIX rules 19, 80 automatic audit recovery 82 command prompting 83 replacement variables 83 MIMIX subsystem (MIMIXSBS) starting 147 when to end 148 MIMIX Switch Assistant 16 best practice 205 getting started 21 setting default switch framework 208 setting switch compliance policies 208 using 212 MMNFYNEWE monitor 124 monitor for newly created objects 124 mxpswtichLiteLastperform 215 mxpswtichLiteSwtCmply 216
N
names, displaying long 224 navigation bar status 46 network system 17 new hardware upgrade 313 prerequisites 313 new objects IFS object journal at create requirements 192 journal at create selection criteria 193 newly created objects, notification of 124 notifications definition 19, 119 displaying 120, 125 new problems in installation 54 severity level 20, 121 status 121
M
management system 17 manager journal 16 system 16 menu MIMIX Main 42 message queue, primary and secondary 167 messages ENDMMX 149 STRMMX 149 MIMIX AutoGuard 15 automatic recovery 18 getting started 20 introduction 18 MIMIX Availability Manager 15 benefits 44 monitoring status with 48 MIMIX CDP feature exclude from audit 23 recovery point cleared 146 MIMIX installation 15 MIMIX managers ending 164 resolving problems 164 starting 164 MIMIX Model Switch Framework 16, 205
O
object auditing concept 17 setting level with STRDG 140 used for replication 192 object error recovery, automatic 35 objects configuration of non-file 234 displaying long IFS names 224 displaying objects in error 67 displaying objects with active entries 67 in error, resolving 185 new 192
321
reducing contention 242 tracking entries for data areas and data queues 179 open commit cycles audit results 265, 267 effect on clear pend start 139 prevent a clear pend start 137 prevent problems with 144 resolving before clearing entries 140 shown in status 153 operations common, where to start 44 less common 221 orphaned recoveries 128 outfiles user profile password 300 user profile status 297 output file fields Difference Indicator 265, 269 System 1 Indicator field 271 System 2 Indicator field 271
P
path names, IFS 224 planned switch 205 policies 19 changing values 24 considerations when choosing values 22 for auditing 109 for automatic recovery during replication 33 for switching 208 introduction 22 policy action for running audits 30 audit action threshold 29 audit level 29 audit notify on success 27 audit rule 27 audit schedule 32 audit warning threshold 28 automatic audit recovery 27 automatic system journal recovery 27 automatic user journal recovery 27 CMPRCDCNT commit threshold 31 data group definition 27 default model switch framework 31 independent ASP library ratio 31 journaling attribute difference action 28 maximum rule runtime 28
notification severity 27 object only on target 28 run rule on system 30 switch action threshold 31 switch warning threshold 31 synchronize threshold size 30 system journal recovery success 27 third delay retry interval 30 third delay retry interval, number of 30 user journal apply threshold 28 user journal recovery success 27 problems reporting a problem 241 troubleshoot 239 where to start 239 problems, journaling data areas and data queues 201 files 195 IFS objects 198 problems, resolving audit results 93, 95, 263 common errors 163 data group cannot end 243 data group cannot start 248 files in error 170 files not journaled 57 journal cache or state 57 objects in error 185 open commits when starting data group 140 RJ link cannot end 249 RJ link cannot start 249 switch compliance 216 tracking entries 179 production system 16 publications, IBM 11
Q
QDFTJRN data area restrictions 193 role in processing new objects 193 QSTRUPPGM system value 303, 305
R
recommendations audit automatic recovery 82 auditing 81 audits and rules 82 before planned switch 206 policies in bi-directional environment 22
322
recoveries active in installation 54 definition 19, 120 detected database errors 34 displaying details 125 occurring in installation 125 orphaned 128 orphaned, identifying 128 orphaned. removing 129 recovery phase 20 recovery point cleared by ENDDG 146 release (*RLS) held file entry 176 held tracking entry 183 release clear (*RLSCLR) file entry 176 tracking entry 184 release wait (*RLSWAIT) file entry 175 tracking entry 183 remote journal (RJ) link 16 remote journal environment processes ended by ENDDG 159 processes started by STRDG 155 unconfirmed journal entry 249 removing activity history entries 190 duplicate tracking entries 184 unconfirmed entries 249 reorganizing, active files 226 replacement variables 83 replication automatic error recovery 33 backlogs, identifying 76 choices when ending 141 choices when starting 133 direction of 17 ending 131 resolve replication errors 163 starting 131 status from 5250 emulator 52 status from MIMIX Availability Manager 48 supported paths 13 switching 204 system journal 13 user journal 13 replication path 15 replication, problems troubleshoot 239
where to start 163 requirements audits 81 journal at create 192 journaling 192 MIMIX AutoGuard 81 resolving problems common replication errors 163 troubleshooting 239 restore MIMIX prerequisites 314 restrictions journal at create 193 QDFTJRN data area 193 results user-defined rules 118 retry objects in error 188 retrying, data group activity entries 188 RJ link 16 displaying 227 ending independently 237 errors for target journal of 251 identifying data groups that use 230 journal definitions by an 231 operating without a data group 237 removing unconfirmed entries 249 status 228 when to end 145 rule #DGFE 104 #DLOATR 105 #FILATR 104 #FILATRMBR 105 #FILDTA 105 #IFSATR 105 #OBJATR 104 user-defined, results of 118 rules 80 advantages of using 18 business 18 considerations for using 82 messages from 84 MIMIX 19, 80 notifications from 84 relationship with rules 80 replacement variables 83 requirements 81 run command considerations 83 run on management system 83 types 80
323
rules, MIMIX descriptions 104 running audits immediately 91 rule groups 115 rules 115
S
schedule audit considerations 105 automatic audit 104 default audit 104 schedule, shipped audit 104 servers ending TCP 223 starting TCP 222 services status from 5250 emulator 53 status from MIMIX Availability Manager 49 severity level, notification 121 source system 17 spooled files, displaying MIMIX-created 224 starting MIMIX managers 164 RJ link independently 237 system and journal managers 164 TCP server 222 starting data group at specified journal location 135 considerations 133, 135 prevented when open commit cycles 137, 139 procedure 150 processes, effect of 155 set object auditing level 140 when to clear entries 136 starting journaling data areas and data queues 201 file entry 195 files 195 IFS objects 198 IFS tracking entry 198 object tracking entry 201 starting MIMIX considerations 133 included processes 133 procedure 147 starting replication 131 choices and considerations 133
status active file operations 226 audit compliance 100 audit runtime and compliance 85 audits 87, 90 audits (runtime) 48, 52 checking from 5250 emulator 50 checking from MIMIX Availability Manager 48 data group detail 61, 64 data group summary 48, 52 database apply (DBAPY) 71 enterprise view 45 installation summary 50 introduction 45 journal cache or state 72 journaling data areas and data queues 201 journaling files 195 journaling IFS objects 198 journaling tracking entries 198, 201 notification 121 notification new in installation 52 recoveries active in installation 125 replication 48, 52 RJ link 228 services 49, 53 switch compliance 215 switching 59, 212 Work with Data Groups display 54 subsystem, MIMIXSBS ended 177 ending 148 starting 147 Switch Assistant, MIMIX 16, 212 getting started 21 switch framework disable policy when not used 210 specify a default 208 switching 204 best practice 20, 204, 205, 215 change audit level before 82, 210 compliance 215 conditions that end 219 description, planned switch 205 description, unplanned switch 206 getting started with MIMIX Switch Assistant 21 journal analysis after unplanned switch 258 last switch field 215 phases of a 205 policies for 208
324
problems checking compliance 216 reasons for 205 setting switch compliance policies 208, 209 setting switch framework policy 208 switch framework vs. SWTDG command 205 SWTDG command details 219 unplanned, actions to complete an 207 using MIMIX Switch Assistant 212 using option on MIMIX Basic Main Menu 212 using STRDG command 217 synchronize file entry 171 objects, system journal replicated 187 tracking entries 182 system definition 16 system journal replication 13 detailed status 61, 69 errors automatically recovered 34 journaling requirements 192 system manager 16 delay intervals 164 ending 164, 165 resolving problems 164 starting 164 system roles management or network 17 production or backup 16 source or target 17
working with active file operations 226 tracking entry 15 file identifiers (FIDs) 236 IFS 179 incomplete 143 not journaled 57 object 179 removing duplicate 184 transfer definition 16
U
unconfirmed journal entries, removing 249 unplanned switch 206 performing journal analysis 258 unprocessed entries 153 upgrade hardware, no disk image change 310 hardware, with a disk image change 313 new hardware 313 OS/400 303 user journal replication 13 detailed status 61, 71 errors automatically recovered 33 journaling requirements 192 non-file objects 234 tracking entries 179 tracking entry 15 user profile password 300 status 297
T
target system 17 threshold audit action 29 audit warning 28 CMPRCDCNT open commit 31 switch action 31 switch warning 31 synchronize size 30 user journal apply 28 timestamps 254 automatically created 254 creating additional 254 deleting 256 displaying 256 printing 256 tips displaying data group spooled files 224 displaying long IFS object names 224 removing journaled changes 257
V
verifying communications link 244, 245 journaling, IFS tracking entries 200 journaling, object tracking entries 203 journaling, physical files 197 key attributes 252 viewing status, active file operations 226
W
wait time, data group controlled end 144 wait time, data group controlled end during switch 219 windows, layout for 37
325