High Availability for IBM Power i TM

Transcription

1 GENERAL INFORMATION High Availability for IBM Power i TM 21, Rue Rollin Paris France T él. : +33 (0) Fax : +33 (0)

2 Table of contents 1. GENERAL ORGANIZATION OF THE REPLICATIONS General Diagram Software Components Prerequisites OS/400 restrictions DIFFERENT MODES TO USE QUICK-EDD/HA «HIGH AVAILABILITY» mode «DATA» mode «LOCAL» mode «VERIFY MODE» only SRS mode: Smart Remote Staging Display depending on the mode Counters PREREQUISITE RULES Object audit Journaling Journal performances Receiver management STARTING WITH QUICK-EDD/HA Concepts Glossary Access to the menus PF Key General Rules Global menu «EDH» PMEDH* - LIST OF COMMANDS BY ALPHABETICAL ORDER DATABASE FILES Capacity Limits (Record Length) Full file management Documentation Quick-EDD/HA 2

3 7. AUTOMATIC MANAGEMENT WITH JOURNAL ENTRIES Commands processing Sample: daily backups made on target instead of source Continuous protection of the data during batch processes /07/2013

4 Note: To be user friendly, because Quick-EDD/HA is meant to be used only by technicians, it s possible to access all the product functionalities thanks to any entry point. The product is built around a unique screen displaying the overview of the replication properties and allowing the necessary accesses to the setup and supervision. Warning: RIGHT AFTER THE INSTALLATION, you ll have to send to your partner or to Trader s the required information to get the software KEYS. To ask for a temporary key, please ask support@traders.fr To ask for a permanent key, please ask keys@traders.fr Quick-EDD/HA is a software made to provide security and continuity for the IBM Power i environment. The product allows you to replicate easily and safely all events from a source production system to a (remote) target system, using a communication link. Based on the continuous monitoring of the journals, Quick-EDD/HA replicates, on a remote site, all the modifications made on the objects and data of the users libraries and on the configuration and security components; IFS or Spools are also managed by Quick-EDD/HA. Documentation Quick-EDD/HA 4

5 1. GENERAL ORGANIZATION OF THE REPLICATIONS We can describe Quick-EDD/HA in four steps: Event detection That first step is a function to monitor all journals corresponding to the environment parameters for any kind of transaction (i.e. creation, modification, deletion) related to any defined object (i.e. data, PGM, profiles, configuration, spools, IFS ) Communication The second step is replication in real time of any detected modification on the source system. Depending on the transaction, the exchange will be more or less fast: I/O transactions and object transfer are very fast; synchronization can take more time because every object in the environment is compared between the source system and the target system. Processing On the target system, the detected event from source system is processed immediately in the same way. Depending on the type of event, Quick-EDD/HA has to manage one or many data updates, perform an object restoration, or run a command in order to replicate the modification (i.e. change of a password, system value ). Acknowledgement To ensure a complete process and a perfect completion of transactions, every transaction will be acknowledged in real time. The acknowledgement validates the whole process and allows to retrieve information for history and statistics. Note: ALL THESE FUNCTIONS ARE EXECUTED IN A SYNCHRONOUS MANNER BY Quick-EDD/HA. 5 12/07/2013

6 1.1. General Diagram AUDIT Journal Data System OBJ IFS SPOOL PARAMETRAGE DB Journal DB DB Journal Journal Events detection step Journals Management SUPERVISION TCP/IP Communications Communication towards target system OBJ IFS SYS DATA SPOOL Event integration step I/O, RSTxxx, command TARGET SYSTEM Destination Libraries, IFS, Spools Acknowledgement from target to source Documentation Quick-EDD/HA 6

7 1.2. Software Components Quick-EDD/HA consists of three libraries: Library PMEDH contains all functionalities and processes. PMEDH, approximately 6 MB in size, must be installed on both Production and Recovery servers. You can choose the name of the library, but it must be the same on source and target systems. Library PMEDHUSR contains all details of the site settings, the Quick-EDD/HA objects that can be customized (subsystem, job description ), objects containing the settings for replication environments and switch scenarios. You can t choose the name of this library. Library PMEDHUSR must be in the replication perimeter, because it contains all information for the switch A user profile must be created on any system using Quick-EDD/HA (see EDD_HA_Installation.pdf). A third library, PMEDHTOOLS - mandatory name - contains tools to integrate replication functions into your general processes and specific tools for controls and switch functions. This library includes source files of those tools, allowing you to modify the tools to meet your unique context Prerequisites Quick-EDD/HA does not require neither specific feature of the IBM Power i nor specific model, but needs TCP/IP communication features for connection between the systems. Quick-EDD/HA uses the communication line described on your system; it does not automatically create, and does not manage, this configuration OS/400 restrictions Quick-EDD/HA runs with all OS/400 releases from level V5R2M0 to V7R1M0. Note: Please check with your reseller on the compatibility of the Quick-EDD/HA with the OS/400 of the two systems. Quick-EDD/HA allows you to have a maximum difference of TWO levels of release between the operating systems of your source and target servers, following the limitations of IBM SAV/RST functions. Note: in case the source system runs a V5R3 or V5R4 and the target system runs a V6R1 or V7R1, the systems in V5R3 or V5R4 must have the appropriate PTFs to accept V6R1 or V7R1 objects. Each OS releases has specific PTFs for that purpose. If those PTFs are installed, switch is not an issue at all. 7 12/07/2013

8 2. DIFFERENT MODES TO USE QUICK- EDD/HA Quick-EDD/HA can be used in 5 different ways: «HIGH AVAILABILITY» mode allows 100% of the functionalities «DATA» mode limits the replication to a limited type of objects «LOCAL» mode replicate inside the same system (same partition) «VERIFY MODE» only «SRS» mode allowing that replication be active and keep sending the journal entries towards the target system, but the apply process of those journal entries is paused ; for example in order to perform daily backup on target system instead of source system 2.1. «HIGH AVAILABILITY» mode HIGH AVAILABILITY is the focus of the product and allows all the functionalities of replication between a Production server and a Recovery server «DATA» mode The DATA mode is a restricted use of Quick-EDD/HA used to replicate DATA only. Only the following objects will be selected: Database files (PF LF) Data queues (*DTAQ) Data areas (*DTAARA) User profiles (*USRPRF) to keep ownership and authorities on the replicated objects The DATA mode must be activated at General parameters level, in order to correspond with the license key: DATA replication mode 1 Note: The license key will automate the check for selection of objects 2.3. «LOCAL» mode The LOCAL mode is a special usage of the product, when you want to replicate inside the same server (same partition). In this case, restrictions are given by the system: It is not possible to replicate configuration objects located in QSYS such as profiles, or configuration objects Objects must be replicated into a DIFFERENT library IFS files must be replicated into a different root Spool files must be replicated in a different output queue System values cannot be replicated Note: Replication in LOCAL mode can be done in both HA and DATA modes Documentation Quick-EDD/HA 8

9 2.4. «VERIFY MODE» only The verify mode allows using a Quick-EDD/HA environment in order to compare two systems. No change will be done neither on source objects nor on target objects. In this specific case: the settings are the same as for a standard replication the audit is not activated on the objects the journaling is not activated the process stops automatically right after the last object is checked The verify mode has to be activated at the general parameters level: Synchro servers - Mini 1 Synchro servers - Maxi 1 Verify mode only 1 Start the environment in Normal mode: Quick-EDD will create the list of elements to be controlled and then run the control into the unique synchronization job. When the control is finished, the environment stops, the result is available in the EDH_xx_S01 spool; xx being the name of the environment; produced by the synchronization source job. The details of the performed control correspond to the IOA function, see documentation EDD_HA_Supervision_EN.pdf SRS mode: Smart Remote Staging Presentation The S.R.S. function inside Quick-EDD/HA allows to keep sending the journal entries on the target system and deactivate their apply process. This is called *NOIO mode. The objective is to give more availability for the target database, allowing customers to access data on objects for backups, extraction of data, tests, etc. without stopping the high availability process. Usually Quick-EDD/HA is using an internal synchronous loop to read journal entries from the source system, send and apply them on the target system then return an acknowledgement back to the source system. It s the *IO mode. When you activate the S.R.S, you deactivate the apply process, and in this case journal entries are stored on the target system in temporary user spaces. They will be applied later when you will reactivate the usual Quick-EDD/HA process. Settings - Stop the environment - In the second screen of the general parameters, choose the Maxi storage SRS Mb and/or the Maximum entries which Quick-EDD/HA will use/store on the target system. This allows to adapt to the available target disk space. 9 12/07/2013

10 Maxi storage SRS Mb or Maximum entries Outside the environment, use the tool command EDHSRSOPT with option *ON Note: If you don t use EDHSRSOPT, by default, the S.R.S. process is limited to 261k entries. For examples of how to pause the journal entries application process on the target, see Document: «S.R.S: Backup on the target system and continuous data protection» 2.6. Display depending on the mode Here is the main screen of the environment. Each parameter line is displayed with dashes on the left of the line: EDH EN_SND Work Environment QSLFRA1 20/03/09 19:18:08 1=Insert 2=Modify 4=Delete 5=Display 8=Explore 9=Activity M=Messages J=Journal S=Start E=End?=Others h ---- Synchro Wait - nbr Type Descript. * Wait Ac ok nok hld rep obj _ EN_snd Environment _ General parameters _ Target site -> QSLFRA2 PMSOFTICF _ Journals +..5 _ Jobs _ Library parameters +..1 _ Libraries _ SYS object parms _ IFS parameters _ Spool parameters F5=Refresh F10=View> F11=View< F12=Cancel F17=Top F18=Bottom F8=Select F20=Job Depending on the mode, the display of the screen and color of the dashes can be different: For DATA mode, settings lines for IFS, SPOOLS and SYSVAL will disappear For DATA or LOCAL mode, dashes can be displayed in RED if some settings don t match the mode For SRS mode, when *NOIO mode is on, you ll see Generally speaking, three colors are used for dashes: GREEN Settings level is available, and there is no group definition yet WHITE Settings level is available and some groups are defined RED Some group definitions don t match the current mode. The corresponding selections will be ignored. Documentation Quick-EDD/HA 10

11 «SRS» mode, when *NOIO is activated ; that is to say when the apply of journal entries on the target system is paused EDH US_SND ---s Work Environment QSLTST1 8/07/13 noio 14:26:35 1=Insert 2=Modify 4=Delete 5=Display 8=Explore 9=Activity M=Messages J=Journal S=Start E=End?=Others h ---- Synchro Wait - nbr Type Descript. * Wait Ac ok nok hld rep obj _ US snd ENGLISH DOC ---s _ General parameters _ Target site -> QSLTST2 PMSOFTICF _ Journals -> QAUDJRN +..1 _ Jobs +..2 _ Library parameters _ SYS object parms _ IFS parameters _ Spool parameters _ SYSVAL parameters End F5=Refresh F10=View> F11=View< F12=Cancel F17=Top F18=Bottom F8=Select F20=Job Edh US_RCV ---s Gestion Environnement QSLTST2 8/07/13 noio 14:26:32 1=Insérer 2=Modifier 4=Supprimer 5=Afficher 8=Explorer 9=Activité M=Messages J=Journal S=Démarrer E=Arrêter?=Autres h ---- Synchro Attente- nbr Type Intitulé * Wait Ac ok nok ret rep obj _ US rcv ENGLISH DOC ---s _ General parameters _ Target site -> QSLTST2 PMSOFTICF _ Journals -> QAUDJRN +..1 _ Jobs +..2 _ Library parameters _ SYS object parms _ IFS parameters _ Spool parameters _ SYSVAL parameters Fin F5=Réafficher F10=Vue> F11=Vue< F12=Annuler F17=Début F18=Fin F8=Sélection F20=Job 11 12/07/2013

12 2.7. Counters ---- Synchro ---- Wait => Number of objects waiting for synchronization Ac => Number of objects currently being synchronized ok => Number of synchronized objects nok => Number of objects in synchronization error Note: «nok» objects indicate a «fatal» error which occurred during synchronization. Every 5 minutes, Quick-EDD/HA will retry to synchronize these objects. In certain case, a manual control is mandatory, to solve the error and re launch synchronization (see EDD_HA_Daily_Checklist.pdf) Besides, when the error is solved and the synchronization is done, the «nok» counter is decremented. Wait hld => Journal entries that are held by Quick-EDD/HA. When, for example, a synchronization is running, all the new journal entries of the object are held, in order to be applied at the end of the synchronization (last step of the synchronization). rep => Journal entries sent to the target and not acknowledged yet Nbr obj nbr obj => Number of elements inside the sub menu Documentation Quick-EDD/HA 12

13 3. PREREQUISITE RULES 3.1. Object audit Quick-EDD/HA activates Audit on all the objects concerned by the replication (*CHANGE). Notice that after Audit activation, some functions will be automatically audited. If audit is not currently in use on the system, Quick-EDD/HA will automatically create the necessary elements (receiver PMEDHJRN/AUDRCV0001 and journal QSYS/QAUDJRN) and activate the minimum needed system values, as a result of the command CALL PMEDHOPEN used during the installation. No existing value will be modified automatically: neither QAUDLVL or QAUDCTL, nor the audit value within already audited objects. The values on your systems will have to be checked. The audit journal can receive a large amount of entries. Therefore, its management has to be defined with care. When the replication is started for the first time, audit is activated on every object; this action may impact your backup if you are using a SAVCHGOBJ command (all objects may be modified, so they will be saved) Journaling Quick-EDD/HA will dynamically start journaling on files and other special objects (DTAQs, IFS ) depending on the defined settings (see EDD_HA_Settings.pdf). Because of the large number of objects, it may be judicious to split the different applications and environments into different journals. This will avoid reaching system limits, and makes the system easier to maintain and manage. It is also possible to process files without journaling, only in specific cases: Files which are never updated and kept sometimes for historical purposes, as EDI files Archives Source files, in which only some members could change For those special cases, use specific management functions, which allow you to manage files like non-database objects (See Non journaled files in EDD_HA_Settings.pdf) Journal performances Journal activation undoubtedly has an effect on server performance, and moreover, the transmission of entries will have repercussions on the network. It is therefore imperative to understand the process in its whole so that this activation doesn t provoke dysfunction of the production system. The implementation of Quick-EDD/HA should take care of available functions: Automatic management of the receivers Performances Journal options 13 12/07/2013

14 3.4. Receiver management The HA process is fully based on journaling. Quick-EDD/HA allows you to manage journal and journal receivers, their detachment, and their deletion, depending upon the settings you choose. We have to confirm that journals and journal receivers are not used by some other function in the system or by another software application. If existing journals are used for an application, you do not want Quick-EDD/HA to delete the receivers before the other application has completed their processing. Depending on the needs and the configurations (OS/400 release level), you will have to setup carefully the receiver management, see EDD_HA_Journaling.pdf Documentation Quick-EDD/HA 14

15 4. STARTING WITH QUICK-EDD/HA 4.1. Concepts Quick-EDD/HA has been written around simplicity for the system administrator and highperformance to ensure the replication. We defined these rules to achieve those goals: No link and independence between settings and processing o Settings are defined in groups, depending on application or software used. o The process reads the journals, runs updates and database I/Os in sequence to replicate operations on the target system, without taking into account the group from which the event is issued. Minimize active jobs in the system. Quick-EDD/HA dynamically controls the number of jobs depending on activity. o Only one master job ensures the follow-up of all journals and the replication for fast transactions (mainly I/O transactions of database) o Server jobs, dynamically managed, are charged with slow transactions (save/restore, synchronization ). The minimum and maximum numbers of server jobs are defined in the settings /07/2013

16 APPLICATIONS APPLICATIONS APPLICATIONS APPLICATIONS IFS DTAQs??? DB JOURNAL DB JOURNAL DB JOURNAL D DB JOURNAL IFS Journal DTAQs Journal Vx.Rx Journal SETTINGS QAUDJRN AUDIT Journal Quick-EDD/HA SUPERVISOR PROCESSING Données (EDD) Données (EDD) DATA (I/Os) SAV/RST SAV/RST SAV/RST COMMANDS SPOOLS SYSVAL JOBS

17 The previous schema shows the general organization of Quick-EDD/HA: The settings part depends on your applications and your journals (currently used or to be created during the implementation of Quick-EDD/HA). Groups are defined by the customer, depending on replication rules defined previously for the system. They are used to make parameters easy to follow, understand and maintain The journal list is automatically built by Quick-EDD/HA directly from file descriptions, and depending on the group settings linked with automatic journal activation. The supervisor reads all the journals AT THE SAME TIME, including audit journal QAUDJRN. This functionality allows processing all system events, in the correct sequence, on the target system. The supervisor dispatches the different transactions, depending on the type of function to process. DATABASE replication processing of input/output transactions on records (CRT/UPD/DLT) and some commands on members (INZPFM, CLRPFM ) Commands SAV/RST for new objects or important modifications that need to recreate the object(s) on the target system Commands that will reproduce a modification (change password, object modification ) on the target system Manage system values Send/delete spool files Send information from jobs running on the source system 17 12/07/2013

18 4.2. Glossary The documentation of Quick-EDD/HA respects the terms usually used in IBM Power i environments. The list below details the vocabulary specific to Quick-EDD/HA. Environment The environment, in Quick-EDD/HA context, corresponds to a setup table, gathering all the settings to replicate to an IBM Power i server or partition. Environment objects have been created to make it possible to differentiate between different applications, and/or different distribution areas (application environments, multiple remote sites ). This distinction makes the management easier and more logical, and expands the maintenance capability. Environment is an IBM Power i object, of type *USRIDX, which will be created in the library PMEDHUSR. The object name is xx_snd on the source system (xx represents the environment code), and xx_rcv on the target system. Note: depending on the amount of set information, the *USRIDX may be followed by *USRSPC, named xx_sndnnn on the source and xx_rcvnnn on the target; nnn ranges from 001 to 255. In that case, all objetcs xx_s* (or xx_r*) are the environment. *USRIDX xx_snd and xx_rcv are exactly identical on the source and target system. So are *USRSPC XX_SNDnnn and XX_RCVnnn. All other XX* objects of PMEDHUSR are linked to the activity with: - Pointers on current positions - Storage of journal entries to manage different functions: Running entries if a commit cycle is opened Memorizing new journal entries during a synchronization SRS: Smart Remote Staging Each time the environment is started, all RCV objects are recreated during the "Send parameters" step. So, if you delete the objects on the target, it s not an issue. Any missing object will be recreated when the replication is started, including the object XX_MSG containing the replication messages. Warning: if there are stored journal entries on the target - objects xx_rco* - and if you delete those objects, it won t be possible to restart the environment by processing the residual journal entries; see EDD_HA_Supervision for more details Target or Recovery System Basically, HA needs a target system for switching while the production system is down for any reason. That term will be used often. The source system is often named «production system». Site For Quick-EDD/HA a site is a target system. Usually, a site corresponds to a network node name or a TCP/IP address. Quick-EDD/HA uses the site to establish communication between source and target systems. Documentation Quick-EDD/HA 18

19 Group A group allows you to manage a unique entity, a coherent set of objects following the same replication rules. There are five different types of domains involved in managing the different parts of IBM Power i. Each domain will have one or several groups: Objects All types of objects which can be created in a user library (database or not). Configuration The objects created in QSYS library (security and configuration). IFS The objects corresponding to an organization by directory (PC files). Spools The spool files on the source system are replicated to the target. System values Most system values can be replicated. The group is also very important to organize your replication. Logically organized groups make your installation easier to maintain and modify in the future /07/2013

20 4.3. Access to the menus The standard command to enter Quick-EDD/HA is "PMEDH". This command, without parameters, displays the main menu. QSLFRA2 Q U I C K - E D H 13/03/10 GODEC PMsoft Inside 15:44:43 High Availability V Select one of the following options: Sender site Remote site 1. Parameter 2. Start 3. Control 3. Control 4. Stop Option, or command 7. Commands 8. Messages 9. Object ===> F3=Exit F4=Prompt F9=Recall F12=Cancel F13=PMsoft system The menu has 3 kinds of options: Functions for the Sender site Access to settings Start of the replication Control of the replication Stop of the replication Function for the Target site Control of the replication Other functions List of Quick-EDD/HA commands Messages of the replication Management of the objects linked to the replication Documentation Quick-EDD/HA 20

21 Function keys : F3=Exit Exit from job F4=Prompt Prompt of command PMEDH* commands list if the command line is blank F9=Recall Retrieve previous command F12=Cancel Return to previous screen 4.4. PF Key General Rules Quick-EDD/HA sticks to IBM standard PF Keys rules for OS/400: F3=Exit F4=Prompt F5=Refresh F6=Create F9=Retrieve F10/F11=View F12=Cancel F14=Children deletion F16=Deletion of everything F17=Top F18=Bottom F19=Left F20=Right End of process Exit menu List for commands Also, list of PMEDH* commands if command line is blank Refresh data on screen Create a new element Retrieve previous processed commands Display more line information on a sub file Cancel Back to previous screen Used when deleting a setup element Used when deleting a setup element Display from the top of the list (sub file) Display the end of the list (sub file) Move on to the left (display longer than 80 characters) Move on to the right (display longer than 80 characters) 21 12/07/2013

22 4.5. Global menu «EDH» A global menu «EDH» allows you to manage all options from the two menus «PMEDH» and «EDHTools» (tools of Quick-EDD/HA). It s now the main menu of the product. Check that you have PMEDH and PMEDHTOOLS in your library list; then run command EDH. The following menu is displayed: QSLFRA EA Quick-EDD/HA - Tools V13_ /04/13 GODEC PRODUCTION 16:09:54 EDH - HIGH AVAILABILITY Quick-EDD/HA : V Select one of the following options: Parameters Activity 1. Work with environments 6. Manage replications 2. Manage specific objects 3. Supervision parameters 7. Start supervision process 4. Monitoring options 8. Start msg monitoring 5. Monitoring filtering Switch Others 11. Work with switch scenarios 21. Display EDH messages 12. Run switch scenario 22. Work with objects (PMEDHUSR) 23. Tools menu - EDHTools Option, or command ===> F3=Exit F4=Prompt F9=Repeat F12=Cancel This menu introduces the different available options with one focus: perform in sequence all operations from the definition of settings (options 1-5), and then execution of replications (options 6 8) and implementation of the additional tools (options 21-23). Four categories are available on this menu: SETTINGS ACTIVITY 1 Setup the replication environments 2 - Setup the management of specific objects 3 Setup the supervision 4 Setup the monitoring options (MSGQ, , SNMP) 5 Setup monitoring filtering options (MSGQ, , SNMP) 6 Manage replications 7 Start supervision process 8 Start monitoring Documentation Quick-EDD/HA 22

23 SWITCH 11 Setup the switch scenarios 12 Run switch scenarios ADDITIONAL TOOLS 21 Display Quick-EDD/HA messages 22 Manage objects (PMEDHUSR) 23 Access to the tools menu Note: Libraries PMEDH and PMEDHTOOLS must be available in the library list of your job before running EDH command. Release numbers Two release numbers are displayed on the main menu: In the title, version is corresponding to the tools library (PMEDHTOOLS library). On the right, «Quick-EDD/HA: Vnnnnnn» is the release corresponding with the product itself (PMEDH library). Function keys: F3=Exit Exit from job F4=Prompt Prompt of command F9=Recall Retrieve previous command F12=Cancel Return to previous screen The main menu includes a control of the license key. If the key is expired or if the key will expire in the next 2 days a red message will be displayed on the top of the screen: QSL/PMsoft software 13 not available since the 27/04/10 07:47: /07/2013

24 5. PMEDH* - LIST OF COMMANDS BY ALPHABETICAL ORDER Some Quick-EDD/HA functions might be used externally in user-program through commands existing in the software library. Those commands will be detailed in appropriate chapters of the documentation. PMEDHCOPXR Reorganize the environment: to be used with support team PMEDHCOPXX Copy the environment: to be used with support team PMEDHCTL Environment management function: rather use PMEDHSTR PMEDHEND Stop an environment PMEDHGEN Generation + start of audit and journaling, based on the settings PMEDHINSG Insert a setting line PMEDHJRNPO Specific journal position PMEDHMOD SRS, Execution mode for the environment PMEDHOPXCF Options on configuration objects PMEDHOPXIF Options on IFS PMEDHOPXJO Options on Jobs PMEDHOPXOB Options on libraries and objects PMEDHOPXSP Options on spools PMEDHOPXSV Options on system values PMEDHPARUN Access to performances advanced settings: to be used with support team PMEDHPURGE Purge of the deleted elements PMEDHRCI SRS and fail-over : Apply stored journal entries on target before switching PMEDHRCO Fail-over : Commit management PMEDHSBMJ Fail-over : Jobs Follow Up PMEDHSBMP Fail-over : Jobs Follow Up PMEDHSTR Start options for the environments PMEDHSWI Switch of the environments PMEDHWAT Internal supervision management PMEDHWRK Access to the environments Documentation Quick-EDD/HA 24

25 6. DATABASE FILES 6.1. Capacity Limits (Record Length) The OS/400 system allows you to create physical files with a maximum length of record of 32,766. This value can be reduced in case the function allow null is used at the field level; in this case, the maximal length is reduced by as many bytes as the number of fields using this functionality (one field allow null = one byte less). Besides, the OS/400 requires 11 complementary bytes for reading by blocks function. The limits of Quick-EDD/HA are therefore identical to those of the system; that means 32,755 bytes ( ), less the possible number of bytes bound to the function allow null Full file management When a PF gets to its critical size, message CPA5305 is sent by the system to the console. The answer I allows to add an increment and to continue processing. For the same reasons, message CPA3138 is sent after a command INZPFM. That second message must be managed the same way. Unfortunately, that transaction does not change the object and logically is not present in the System Audit Journal, so Quick-EDD/HA is not able to detect that modification and replicate it to the target system. Solution: ON THE TARGET SYSTEM Add message CPA5305 to the system reply list ADDRPYLE SEQNBR(1000) MSGID(CPA5305) RPY('9999') ADDRPYLE SEQNBR(1001) MSGID(CPA3138) RPY('I') (Change sequence number if needed) Change PMEDH job description to use the system reply list CHGJOBD JOBD(PMEDHUSR/PMEDH) INQMSGRPY(*SYSRPYL) Note: System reply list is unique; however, only jobs with description (JOBD) using the value INQMSGRPY(*SYSRPYL) will be affected by the modification /07/2013

26 7. AUTOMATIC MANAGEMENT WITH JOURNAL ENTRIES Some Quick-EDD/HA functions can be managed with journal entries. Hold an object *HLD Release an object *RLS Synchronize an object *SYN Job follow-up *JOB Stop the replication *END Local command *CMD Remote command *CMR General control (I.O.A.) *CTG SRS *IOE SRS *IOS SRS *JRE Those functions could be automated by sending a journal entry in the audit journal this way: SNDJRNE JRN(QAUDJRN) TYPE('EH') ENTDTA('*ACT**&OBJNAM&LOBJNAM&OBJTYPFORCE(*YES)') Message syntax is the following: Type Entry «EH» ACTION Position 1 Len 4 value (*HLD/*RLS/*SYN ) Env. Code Position 5 Len 2 (**=All) OBJECT Position 7 Len 10 LIB. Position 17 Len 10 TYPE Position 27 Len 8 FORCE Position 35 Len 11 value FORCE(*YES) If using *SYN function, as in EDHOBJREP, all elements in hold will be released 7.1. Commands processing The options *CMD and *CMR allow you to submit, thanks to Quick-EDD/HA, commands which will be processed either on the source system (*CMD) or on the target system (*CMR). The IBM Power i already provides standard functions, such as RUNRMTCMD, to process this kind of job. This said, if you use Quick-EDD/HA to process a command, the latter will be processed respecting the sequence: the command will be processed at a specific moment of the operation. Documentation Quick-EDD/HA 26

27 7.2. Sample: daily backups made on target instead of source Performing your backup on target system is now really simple thanks to SRS. You just have to write the CLP which will launch the backup; Quick-EDD/HA will handle the rest of the process. Sample 1 Your standard CLP which does backups is written as follows: PGM. SAVLIB SAVLIB(XXXXX) DEV... SAVDLO... SAVCFG.... ENDPGM You already have tested this program. It must be present on target system. All you have to do now is submit it using the remote command function from Quick- EDD/HA. For that you will only have to send a journal entry in the audit journal using a SNDJRNE. This journal entry, using the special code *CMR (remote command) and containing the CALL command will be sent on the target system and the program will be executed by a Xnn server job of the environment. Example: SNDJRNE JRN(QAUDJRN) TYPE('EH') ENTDTA('*CMRXXCALL YYYYYY') *CMR Replace XX by the name of the environment CALL YYYYYY: the name of your CLP, which must be in a library present in the library list of the Xnn jobs When a *CMR command is processed, Quick-EDD/HA will automatically do the following: - Apply and acknowledge all previous entries - Close all opened files - TURN the target environment to *NOIO: apply process is stopped - Run the command defined in the journal entry YOUR BACKUP - When the program is finished the environment is turned back to *IO: apply process restarts Using such a scenario you can make a backup on your target system very easily with only a standard CLP. Sample 2 One command can be used to manage the S.R.S: PMEDH/PMEDHMOD Two options are available for S.R.S., to be used on the target system: *NOIO - Deactivate the Apply process *IO - Activate the Apply process (apply stored entries and restart synchronous replication) 27 12/07/2013

28 In case there are several environments, for example E1, E2 and E3, the target CLP will be called by the command SNDJRNE JRN(QAUDJRN) TYPE('EH') ENTDTA('*CMRE1CALL YYYYYY') and must contain : PGM PMEDHMOD ENV(E2) ENT(*RCV) MOD(*NOIO) PMEDHMOD ENV(E3) ENT(*RCV) MOD(*NOIO). SAVLIB SAVLIB(XXXXX) DEV... SAVDLO... PMEDHMOD ENV(E2) ENT(*RCV) MOD(*IO) PMEDHMOD ENV(E3) ENT(*RCV) MOD(*IO) ENDPGM Sample 2 Depending on companies it is sometimes required to validate the backups, and if the backup failed IT IS MANDATORY to run the backup again AT THE SAME POSITION. Using sample one it is not possible to do that. When the CLP is finished even if it failed - the environment is turned back to *IO automatically. If a customer wants to validate backups as described, the CLP will have to be more sophisticated to manage separately the S.R.S. and the backup itself: The backup can be submitted either by the source or the target system The main CLP program will use the PMEDHMOD command to turn the environment to *NOIO The backup will be executed May be a CALL or independent SBMJOB Option 1 The backup CLP is well monitored and if it finishes normally the PMEDHMOD command is used to turn back the environment to *IO Option 2 If the CLP fails for any reason, the environment stays in *NOIO and the operator can take the decision to run a new backup or to turn back manually the environment to *IO In this case the most important is that the PMEDHMOD is not managed automatically by the *CMR function but as an independent function. A program or a manual operation done by the operator will take the decision to reactivate the *IO process Continuous protection of the data during batch processes If you wish to suspend the apply process of the journal entries on the target system while your batch jobs are running on the source system; and restart the apply only if those batch jobs ended properly, 2 types of journal entries can be sent to the audit journal: SNDJRNE JRN(QAUDJRN) TYPE('EH') ENTDTA('*IOEXX'), XX has to be replaced by the name of the environment; *NOIO mode starts immediately. Then, you can launch the batch jobs. If they ended as expected: SNDJRNE JRN(QAUDJRN) TYPE('EH') ENTDTA('*IOSXX'), XX has to be replaced by the name of the environment; *IO mode starts immediately to apply the corresponding journal entries on the target. Documentation Quick-EDD/HA 28

29 If the batch jobs failed and you don t want to apply their result on the target system, you only have to stop the environment and delete the objects PMEDHUSR/XX_RCO*. Then, you can skip the journal entries related to the batch jobs, and restart the replication. Note: A third type of journal entry,*jre, allows to stop the reading of the journals on the source system. In such a case, the PMEDHMOD command, used with option *JRN, allows to restart reading the journals. Attention: journal entries *JRE, *IOE and *IOS are processed by the SND job. Therefore, if you send a *IOE entry when there is latency; *IOS entry might be sent too soon: the environment will remain in *NOIO until someone notices it /07/2013