In a PeopleSoft Integration Broker environment, encountering Peoplesoft Messaging Transactions transactions stuck in the “Working” status can be a common challenge. This situation can disrupt the smooth flow of data and transactions across the system. In this blog post, we’ll explore a comprehensive step-by-step guide to canceling transactions that are stuck in the Working status and preventing potential bottlenecks in your PeopleSoft environment.

Step 1: Deactivate the Domain Navigate to the domain status page using the path PeopleTools > Integration Broker > Service Operation Monitor > Administration > Domain Status. Set the domain to inactive to halt any ongoing transactions.

Step 2: Check Transaction Status in Service Operation Monitor Proceed to the Service Operation Monitor (PeopleTools > Integration Broker > Service Operation Monitor > Monitoring) to assess the status of the problematic transaction. Determine whether it is in “Working” or “New” status.

Step 3: Handling Transactions in “New” Status If the transaction is in “New” status, follow these sub-steps:

3.1. Select the transaction and click “Cancel.” 3.2. Reactivate the domain to resume regular operations.

Step 4: Handling Transactions in “Working” Status If the transaction persists in the “Working” status, back-end intervention is required. Execute the following SQL queries based on the contract type (Operation Instance, Publication Contract, or Subscription Contract):

4.1 SQL SELECT Queries:

  • For Operation Instance:
  • SELECT IBTRANSACTIONID, PUBSTATUS FROM PSAPMSGPUBHDR WHERE PUBSTATUS = 3 AND IBTRANSACTIONID = '<transaction id>' AND STATUSSTRING = 'WRKNG';
  • For Publication Contract:
  • SELECT IBTRANSACTIONID, PUBCONSTATUS FROM PSAPMSGPUBCON WHERE PUBCONSTATUS = 3 AND IBTRANSACTIONID = '<transaction id>' AND STATUSSTRING = 'WRKNG';
  • For Subscription Contract:
  • SELECT IBTRANSACTIONID, SUBCONSTATUS FROM PSAPMSGSUBCON WHERE SUBCONSTATUS = 3 AND IBTRANSACTIONID = '<transaction id>' AND STATUSSTRING = 'WRKNG';

4.2 SQL UPDATE Queries:

  • For Operation Instance:
  • UPDATE PSAPMSGPUBHDR SET PUBSTATUS = 8, STATUSSTRING = 'CNCLD', RETRYCOUNT = 0 WHERE PUBSTATUS = 3 AND IBTRANSACTIONID = '<transaction id>' AND STATUSSTRING = 'WRKNG';
  • For Publication Contract:
  • UPDATE PSAPMSGPUBCON SET PUBCONSTATUS = 8, STATUSSTRING = 'CNCLD', RETRYCOUNT = 0 WHERE PUBCONSTATUS = 3 AND IBTRANSACTIONID = '<transaction id>' AND STATUSSTRING = 'WRKNG';
  • For Subscription Contract:
  • UPDATE PSAPMSGSUBCON SET SUBCONSTATUS = 8, STATUSSTRING = 'CNCLD', RETRYCOUNT = 0 WHERE SUBCONSTATUS = 3 AND IBTRANSACTIONID = '<transaction id>' AND STATUSSTRING = 'WRKNG';

4.3 Commit the Update: Issue a SQL COMMIT to finalize the changes.

4.4 Verification Queries: Check that the changes were successfully made by executing the appropriate SELECT queries for the updated tables.

4.5 Activate the Domain: Finally, reactivate the domain to resume normal processing.

Conclusion: Resolving PeopleSoft messaging transactions stuck in the “Working” status requires a systematic approach, combining both front-end and back-end actions. By following the outlined steps and exercising caution, you can efficiently address and prevent transactional roadblocks in your PeopleSoft Integration Broker environment. Remember to perform these actions in a test environment first before applying changes to your production system.

If you are looking to learn about COBOL trace click here

By admin

Related Post

Leave a Reply

Your email address will not be published. Required fields are marked *