Vous êtes sur la page 1sur 4

Skip to main contentCountry/region [ select ] Redbooks All IBM HomeSolutions By industryAerospace and defenseAutomotiveBankingChemicals and petroleumConsumer productsEducationElectronicsEnergy and

utilitiesFinancial marketsGovernmentHeal thcare and life sciencesIndustrial productsInsuranceMedia and entertainmentRetai lTelecommunicationsTravel and transportationWholesale distributionMedium busines s industriesBy business needBusiness intelligenceCustomer relationship managemen tDigital mediaEnterprise resource planningFinancial managementHuman capital mana gementProduct lifecycle managementSecuritySensors and actuatorsStrategy and chan geSupply chain managementBy IT issueBusiness process managementCollaborationCont ent managementCost managementData managementDisaster recoveryDistribution manage mentEnergy efficiencyEnterprise application integrationRegulatory complianceSecu ritySystems managementVirtualizationWorkforce productivityBy top Business Partne rIBM and CiscoIBM and OracleIBM and SAPMore alliance partnersBusiness consulting FinancingService oriented architecture (SOA)Small business solutionsMedium busin ess solutionsMoreServices IT servicesAll IT servicesBusiness continuity and resiliency servicesEnd-user se rvicesIntegrated communications servicesIT strategy and architecture servicesMai ntenance and technical support servicesMiddleware servicesSecurity and privacy s ervicesServer servicesSite and facilities servicesStorage and data servicesIT se rvices A-ZBusiness consultingAll business consultingCustomer relationship manage mentFinancial managementHuman capital managementStrategy and changeSupply chain managementApplication servicesAll application servicesCustom application develop ment and system integrationApplication managementOutsourcing servicesApplication s outsourcingBusiness process outsourcingIT outsourcing and hostingTrainingSmall business servicesMedium business servicesOther servicesAsset recoveryEngineerin g servicesSoftware servicesMoreProducts Special offersSoftwareSoftware overviewAll software productsBy business needBy c ategoryA to ZBy keyword searchTrials and demosInformation ManagementLotusRationa lTivoliWebSphereSystem z softwareStorageAll storageDisk systemsTape systemsStora ge area networksNetwork attached storageStorage softwareHard drives/microdrivesS torage A to ZSystems & serversAll systems and serversPower SystemsSystem i (iSer ies)System p (pSeries)System z (Mainframe)System x (xSeries)BladeCenterCluster s ystemsUNIX serversLinux serversIntel processor-based serversAMD processor-based serversPoint of salePrinting systems from InfoPrintSemiconductorsThinkPads & Thi nkCentres from LenovoUpgrades, accessories & partsWorkstationsIBM Certified Used EquipmentCommunitiesSmall business productsMedium business productsHardwareSoft wareMoreSupport & downloads DownloadFixes, updates and driversTrials and demosTroubleshootSearchDocumentatio nForums & communitiesPlanInstallUseOpen a service requestGet administrative supp ortSupport by productSoftwareSystems and serversSystem storagePrinting systems f rom InfoPrintLenovo ThinkPads and ThinkCentresMoreMy IBM My accountsMy profileMy interestsMy supportMy customer supportShopping cartContr actsOrders and deliveryInventory and maintenanceInvoices and paymentsSelf-servic e toolsMore customer supportSubscriptionsMore IBM Redbooks Drafts Redbooks Redpapers Technotes Redbooks Domains Residencies Workshops Additional Materials How to order About Redbooks Contact us Mailing list RSS feeds

Related links IBM System i IBM Publications Technical training Developers developerWorks wikis IBM Business Partners IBM Press books IBM Redbooks > IBM System i

Journaling: Why Is My Logical File Journaled? Abstract Starting in IBM i 6.1, logical files, SQL views, and SQL indexes will be journal ed, even if you do not change your environment. Why did the operating system sta rting journaling your logical files? Why are some journaled and some not journal ed? How can you end journaling for some of them or start journaling for others? This technote addresses these questions and more. Written by: Don Zimmerman IBM Systems & Technology Group, Systems Software Development Rochester, MN

Contents The history of logical file journaling--from STRJRNAP to V5R1 to 6.1 Users have been able to journal logical files (including DB/400 logical files, S QL views, and SQL indexes) for many releases. You cannot specify a logical file on the Start Journal Physical File (STRJRNPF) command. But if a logical file's u nderlying physical file is journaled and the logical file contains access paths built over that physical file, then you can use the Start Journal Access Paths ( STRJRNAP) command to start journaling the logical file. Note that a logical file has two parts: the logical file object, which is the external *FILE object that appears in a library, and an underlying part called an access path that maps th e records of a physical file (or multiple physical files). The STRJRNAP command journals both the access paths and the logical file object itself. Normally, you would only use this command if you wanted to journal your access paths. Access paths usually change much more often than the logical file objects, so most of t he journal entries that you would see would be for the access paths. There are r easons to explicitly journal access paths, but it is usually better to allow the system to journal them implicitly using System-Managed Access Path Protection ( SMAPP). Since V5R1M0, the operating system has been behaving as though logical files bui lt over journaled physical files are also journaled, even if their access paths are not journaled. These logical files are not actually journaled. They do not a ppear as journaled on Work with Journal Attributes (WRKJRNA) or the Retrieve Jou rnal Information (QjoRetrieveJournalInformation) API. These logical files also d

o not show as journaled via the Display Object Description (DSPOBJD) command. Bu t journal entries are written for these objects to the same journal to which the underlying physical file is journaled. This includes journal entries such as Cr eate File (journal entry subtype CT), Grant Authority (GT), and other operations that affect the logical file. Since these logical files are not actually journa led in releases prior to V6R1, the journal entries deposited on their behalf do not have any object names or journal identifiers (JIDs) associated with them. Starting in 6.1, the operating system automatically journals logical files. This is not the same journaling that you would get from STRJRNAP. The access paths a re not journaled, only the logical file. At any given time a logical file may or may not be journaled. When a change occurs to a logical file, such as a grant a uthority operation, the operating system automatically starts covert journaling on that file. The Grant Authority journal entry is still written to the journal like before, but now, since the file is actually journaled, the journal entry ha s an object name and a JID. How can I tell whether a logical file is covertly journaled? If you use the Work with Journal Attributes (WRKJRNA) command, logical files wil l now appear in the list of journaled files. Journaled logical files will also b e returned for the Retrieve Journal Information (QjoRetrieveJournalInformation) API. If you look at the file using the Display Object Description (DSPOBJD) comm and or the Display Object Description (QUSROBJD) API, the file will be journaled . Note that if you use the Display File Description (DSPFD) command and the Disp lay Database File Description (QDBRTVFD) API, the Access path journaled field wi ll not indicate journaling unless you explicitly journaled the access paths via the STRJRNAP command. How can I influence covert journaling? In general, you cannot directly affect whether a logical file is covertly journa led. Covert journaling is started when a change occurs for a logical file and on e of the logical file's underlying physical files is journaled. The logical file automatically starts covert journaling to the same journal that the first under lying journaled physical file is journaled to. If all of the physical files that a logical file is built over end journaling, the logical file also ends journal ing. Simply put, the operating system only starts covert journaling when it need s to, and only ends covert journaling when it needs to. What does covert journaling do for me? First, as mentioned above, those journal entries for logical files that did not have object names or JIDs in prior releases now will. This can be useful for aud iting and debugging. After all, it is not very helpful to know what operation oc curred but not know what object was involved. More importantly, the Apply Journaled Changes (APYJRNCHG) command is now able to apply changes to these logical files. The Apply Journaled Changes Extend (APYJR NCHGX) command has always been able to apply logical file journal entries, even when they did not have an object name or JID. But to be able to do that, APYJRNC HGX has much tighter restrictions over which objects you are allowed to specify on the command. APYJRNCHG gives you complete freedom in specifying which objects you want to apply to, but it requires objects to truly be journaled. Specifical ly, it decides which entries to apply and which not to apply by the JIDs in the journal entries. Use the Apply changes to logical files (APYLF) parameter to det ermine whether to apply entries to the logical files built over the physical fil es that you specified. Summary While it may be surprising to have logical files appearing as journaled in IBM i 6.1, it should not be cause for alarm. The operating system automatically journ als logical files when it needs to and ends journaling automatically when approp

riate. This allows for more user-friendly journal entries and enhanced support f or Apply Journaled Changes (APYJRNCHG). Special Notices This material has not been submitted to any formal IBM test and is published AS IS. It has not been the subject of rigorous review. IBM assumes no responsibilit y for its accuracy or completeness. The use of this information or the implement ation of any of these techniques is a client responsibility and depends upon the client's ability to evaluate and integrate them into the client's operational e nvironment.

Document options Printable version Profile Rating: (based on 1 review) Rate this Technote Segment iSeries Integrated Mid-Market Business Servers Product iSeries - Large Business Servers iSeries - Medium Business Servers Publish Date 08 August 2008 Last Update 22 August 2008 IBM Form Number TIPS0677 Feedback Send e-mail

E-mail this pagePrint this pageDigg thisSave to del.icio.usAbout IBM Privacy Con tact Terms of use IBM Feeds

Vous aimerez peut-être aussi