When WebSphere Application Server is running a transaction, the transaction information is written to the tranlog directory to log1 & log2. The resources required for that transaction (database name, user, password, etc) are recorded in the partnerlog directory to it's log1 & log2. When a transaction completes, the transaction information is garbage collected from the logs. If the application server should abend or be forced off mid-transaction, such that a transaction does not complete, then on subsequent server restarts, the... [More]

As a CICS level 2 support person, lately I have been working on calls that are dealing with Replication Logging which is new in CICS 5.1. So perhaps it would be worthwhile to dig into this and explain exactly what this is and how it can be useful in your shop. This blog will serve as an overview of this topic. From the CICS Transaction Server for z/OS (CICS TS) 5.1 documentation, here is a description of what Replication Logging is: "Replication logging is a form of logging in CICS® where updates to VSAM files, including RLS files, in... [More]

In this post I would like to share with you some important backup considerations that I highly recommended that you take into account when creating a backup policy and your backup mechanism. So the most important difference between a plain WebSphere Application Server environment and a WebSphere Process Server environment is that with WebSphere Process Server you have permanently active data sources for the business process engine (BPC), general WebSphere Process Server data source (WPRCSDB), Common Event Infrastructure (CEIDB), and Messaging... [More]