T.L. Ashford is “The Labeling Answer”® for the System i.
Ashford's Barcode400 has been the dependable choice for the industry since 1983. With Barcode400's newly enhanced Graphic Designer no “green screen” interaction is needed for label design. New features include: AFP/HP-compatible printing, easy-to-use graphics import tool, test print to desktop printer, simple font download tool, updated drivers and format listing reports. Even compliance labeling is made easy with design templates. Call 800-541-4893 to order your Fully-Functional, FREE Trial Software or visit us at T.L. Ashford & Associates.
Implement the mutex primitive via MI instructions CHKLKVAL and CLRLKVAL.
Written by Junlei Li
Efforts of numerous computer scientists have been devoted to solving performance problems in different performance-critical circumstances. One of these performance problems is the expense in thread synchronization. Thread synchronization is the application of particular mechanisms to ensure that two concurrently executing threads do not execute specific portions of a program at the same time. By using MUTual EXclusion (mutex), access to shared resources from multiple threads can be serialized, and mutually exclusive program logic can be guaranteed to run in a single thread at any time. Thread synchronization is not limited to threads in the same process; it also applies to synchronization between different processes, or in other words, threads in different processes.
Request a Presto or WebSmart PHP White Paper or a 30-day trial for a chance to win an iPad! The Presto White Paper explains why you should modernize your Green Screen apps and how Presto works. Presto gives all your IBM i green screens a Web GUI in one minute with no RPG, COBOL or DDS code changes. The WebSmart PHP White Paper explains PHP as a technology and how WebSmart PHP leverages that on the IBM i and other platforms using Templates & Wizards to rapidly create new web apps or transform older apps. Click here to enter.
In last month's column, "Automating Recovery, Part II," we looked at the Process Commands (QCAPCMD) API and the flexibility the API provides for determining just what went wrong when attempting to run a CL command and the command fails for one reason or another. In this article, we will look at what's available with the API system when it comes to determining what went wrong when a CL command fails in the middle of our RPG application and attempting to recover from the error situation.