02
Sat, Nov
2 New Articles

What Do You Need to Know to Turn an Idea for an Article or Book into a Published Work?

General
Typography
  • Smaller Small Medium Big Bigger
  • Default Helvetica Segoe Georgia Times

The answer to that question is right here!

 

According to a 2003 survey conducted by Jenkins Group, Inc., a Michigan publishing services firm, 81 percent of Americans would like to write a book. And, although it appears that a similar study about writing articles has never been done, it's probably safe to say that a fairly large number of people have entertained the thought of writing for a magazine as well. There are certainly enough books on the subject to back up this theory, as well as support the 2003 survey's findings; a recent search for books on writing at Amazon.com returned an astonishing 149,911 hardback and paperback titles.

 

With so many books on writing available, choosing the right one to help you get started can be a daunting task. To begin with, only a fraction of these books are designed to guide you through the process of turning an idea for a technical article or book into a published work. And unfortunately, many of the books that focus on this aspect of writing contain material that's outdated and no longer relevant. For example, most describe how to query an editor by way of regular mail, even though today, the majority of editors prefer to be contacted by e-mail. (And there is a significant difference in how e-mail queries are submitted.) Or they fail to provide information that every first-time author needs to know, such as how to use tables and artwork and how to revise early drafts until the wording is clear, concise, and strong. More importantly, almost all of these books neglect to mention just how difficult the task of writing can be. They also fail to offer suggestions on how to develop good writing habits; habits that will help you overcome any obstacle you are likely to encounter.

 

From Idea to Print: How to Write a Technical Article or Book and Get It Published is different. First and foremost, it contains up-to-date information on everything you need to know to turn an idea for a technical article or book into a published work. I can make this claim without hesitation because I contacted several editors and an agent to find out how they do business before I documented the process a writer should follow when creating and submitting a query and/or a book proposal. Furthermore, it combines and summarizes important information found in a wide variety of resources, some of which are available only to authors who have already signed a publishing agreement with a publisher. For example, when you sign an agreement with a large publishing house like McGraw-Hill or Prentice Hall, you normally receive a copy of their "author guidelines," which you are expected to adhere to as you prepare your manuscript for publication. Portions of Chapters 6, 7, and 10 were developed by combining the information found in the author guidelines used by six well-known publishers that specialize in producing technical and educational books. Similarly, a careful analysis of the publishing agreements I received from publishers I have worked with in the past, as well as a comprehensive examination of agreements I received from friends and colleagues who have worked with other publishers, went into the creation of Chapter 4—a chapter that took me just over five months to complete and that many early reviewers have said is the most important chapter in this book.

 

More importantly, much of the information found in this book is derived from my own personal experience writing technical articles and books for publication. When I set out to create this book, one of my goals was to capture, in writing, tips and suggestions I have offered friends and colleagues who have sought my advice in the past. Another was to reinforce many of the concepts presented with real-world examples taken from my own writing projects that were ultimately published by companies like McGraw-Hill, Prentice Hall, CMP Media, TDA Group, and IBM. But I didn't stop there. As I developed the manuscript for this book, I relied heavily on the feedback of subject matter experts to ensure that the information being presented was both accurate and complete. For example, two attorneys who specialize in intellectual property and publishing agreements reviewed and provided valuable feedback on the sections in this book that address understanding and negotiating the terms of a publishing agreement (Chapter 4) and describe how to avoid making libelous statements, how to avoid plagiarizing others, and how to avoid copyright infringement (Chapter 7). As a result, if you have little or no experience writing, this book will give you a clear and accurate picture of the steps involved in authoring a technical article or book for publication. It should also answer any questions you may have about turning an idea for an article or book into a printed work. If, on the other hand, you're an established author with a list of published works to your credit, this book may teach you a few things you don't already know.

 

As I alluded to earlier, Chapter 4 of From Idea to Print is designed to introduce you to a very important document that most writers receive after getting an offer to publish their work—the publishing agreement. The following material was taken from that chapter:

The Publishing Agreement

Many first-time authors are so excited that someone wants to publish their work that they don't pay a lot of attention to the terms and conditions outlined in their publishing agreement. Instead, they skim it, sign it, and send it back, without giving it a second thought. However, once an agreement is signed, it becomes a legally binding document, and some of the terms and conditions they have agreed to can, and usually do, have long-lasting consequences.

 

At the very least, a publishing agreement is designed to supply answers to the following questions:

 

  • When does the agreement (and by extension, the author-publisher relationship) take effect?
  • Who is legally bound by the terms and conditions of the agreement?
  • How will the author's work be prepared for publication and when will it be delivered?
  • How and when will the author's work be published?
  • Who will have final approval over the published work's format and appearance?
  • Who will own the copyright to the published work?
  • What rights to the author's work are to be granted to the publisher?
  • How much and when will the author be paid in exchange for these rights?
  • How long will these rights be tied up?
  • What promises and guarantees is the author required to make?
  • What happens if someone claims the author did something wrong (for example, infringed someone else's copyright)?
  • What are the consequences if either the author or the publisher fails to comply with the terms of the agreement?
  • When does the agreement (and consequently, the author–publisher relationship) end?

 

And, although authors and publishers rarely have serious disagreements, if a difference of opinion does arise, the publishing agreement forms the basis for resolving any and all disputes.

 

Given that they've been designed to provide the answers to these and other questions, publishing agreements tend to be lengthy and complex (most are typically ten to fifteen pages long, single-spaced). And reading one can be an exercise in boredom and frustration—particularly if you're unfamiliar with most of the terminology used. Nonetheless, it's imperative that you take the time to carefully examine any agreement you receive, and more importantly, that you understand the immediate and long-term ramifications of each provision it contains before you sign and return it. Because once an agreement is signed, you're legally obligated to deliver on the promises you've made in it—and for the price that you've agreed to.

 

Although the wording in publishing agreements can vary (primarily because the writing styles of the lawyers that draft them differ), most adhere to a similar format. Typically, they begin with the title "Publishing Agreement," "Publishing Contract," or "Agreement" and continue with a preamble, in which the names and geographical locations of the parties involved are provided and the book to be published is briefly described. The term party is a lawyer's term that's used to identify the persons or businesses that are legally bound by a contract; the geographical location of each party is required because where the parties live and work often determines which state's laws will apply should a dispute between the parties arise. The preamble is followed by a series of numbered paragraphs, referred to as "clauses," that spell out the specific terms of the agreement. Most publishing agreements contain anywhere from fourteen to twenty clauses, and some of these clauses have multiple subclauses.

 

An example of one such clause is the "out-of-print" clause. There are few things an author would like more than to see his or her book become a best seller that continues to earn royalties throughout the duration of its copyright (which is the life of the author, plus seventy years). Unfortunately, most books have a much shorter shelf life—the longest that any of my books have remained in print is just over five years. Because of this, many publishing agreements contain an out-of-print clause that gives the publisher permission to stop producing a book if demand for it is no longer sufficient to warrant its continued manufacture and sale. In some cases, this clause also defines how rights are to revert to the author once the decision to stop publication has been made.

 

You would think that a book would automatically be declared "out of print" according to its earnings—for example, if its sales fall below 500 copies a year or if the author fails to earn at least $800 in royalties in two consecutive accounting periods. However, many publishers resist the use of such guidelines, preferring instead to wait until their supply of books has been exhausted, even though they may only be selling two or three copies a year. And, with more and more publishers utilizing print-on-demand and e-book technology to make backlist titles available, a book can technically remain "in print" long after all physical copies have been either sold or destroyed.

 

Even if a publisher allows a book to go out of print, it typically does not notify the author that the book is no longer available. Instead, it's up to the author to make this determination. And, in most cases, if an author discovers that his or her book is no longer for sale, the out-of-print clause requires them to request, in writing, that the publisher put the book back into print. (Again, with today's technology, there can be a question as to what exactly "into print" means—does it refer to a printed book, an e-book, or something else entirely?) Usually, the publisher then has some period of time, often anywhere from eight to eighteen months, to respond by either putting the book back into print or by licensing the reprint rights to another publisher. If the publisher chooses to do nothing in the period in which it is required to act, the publishing agreement is normally terminated. Even then, the reversion of rights is not likely to be automatic. Instead, the author may be forced to ask for and receive written Reversion of Rights or Termination of Agreement documentation from the publisher before all rights previously granted will be reverted.

 

To ensure that a publisher doesn't keep a poorly performing book in print forever, it's imperative that the out-of-print clause be worded in such a way that leaves no question of when a book goes out of print. This is especially true now that digital and on-demand publishing can make the literal meaning of traditional out-of-print clauses obsolete. (Publishers are likely to favor a clause that defines "out of print" as meaning that the book is not available for sale in any format.) Ideally, the out-of-print clause in your publishing agreement should state that your book is to be automatically considered out of print if annual sales fail to reach a specified level (say, 500, 1,000, or even 2,000 copies a year). Having an out-of-print clause worded this way puts you in a much stronger position to insist on a reversion of rights when your royalty statement indicates that sales have sharply declined.

 

(In Chapter 4, you'll be introduced to fifteen clauses that are found in most publishing agreements and, in many cases, you will receive recommendations on how to make the terms and conditions of these clauses more favorable to you.)

Staying out of Trouble

In Chapter 7, you will learn how to keep from alienating or offending others by using bias-free text, and you'll discover why and how to avoid making libelous statements in your writing. You will also learn what plagiarism is, as well as what you can do to avoid it, and you'll become knowledgeable about things like copyright, copyright laws, the public domain, the "fair use" doctrine, and the proper way to "reuse" someone else's copyrighted material in your work.

 

One of the most interesting topics covered in Chapter 7 has to do with self-plagiarism and copyright infringement. The following except from Chapter 7 explains what self-plagiarism is and illustrates how it can lead to copyright infringement:

 

As the term implies, self?plagiarism is the reuse of significant portions of one's own work without acknowledging that the material is being reused and without citing the original work. Typically, self-plagiarism is considered to be an ethical issue in situations in which it is implied that a publication consists primarily of new material, such as in academic publishing or educational assignments. However, the practice of self-plagiarism can also be illegal if the copyright of the original work has been transferred to another entity, which is normally what takes place when you sign a publishing agreement that allows a publisher to produce, market, distribute, and sell your work.

 

In 1994, Pamela Samuelson, the Richard M. Sherman 1974 Distinguished Professor of Law and Information Management at the University of California, Berkeley, with a joint appointment in the UC Berkeley School of Information and Boalt Hall, the School of Law, identified several factors in which reuse of one's previously published work should not be considered self-plagiarism. These factors are:

 

  • The previous work needs to be restated to lay the groundwork for a new contribution in the second work.
  • Portions of the previous work must be repeated to deal with new evidence or arguments.
  • The audience for each work is so different that publishing the same work in different places is necessary to get the message out.
  • The author thinks he or she said it so well the first time that it makes no sense to say it differently a second time.

 

Samuelson also stated that "Although it seems not to have been raised in any of the self-plagiarism cases, copyright law's fair use defense would likely provide a shield against many potential publisher claims of copyright infringement against authors who reused portions of their previous works." While this statement may be valid if the same publisher holds the copyright for both works, that's not always the case when one publisher holds the rights to the previous work and another publisher holds the rights to the second work. I know, because when I started writing DB2 Certification Exam Study Guides, I learned this firsthand.

 

My sixth and last book with McGraw-Hill, DB2 Administration All-In-One Exam Guide, happened to be my first book on DB2 certification. The purpose of this book was simple—to prepare the reader for two DB2 7.1 for Linux, UNIX, and Windows certification exams (Exams 512 and 513). But, when IBM came out with a new set of exams for DB2 8.1 (Exams 700 and 701), the material in that book quickly became dated. Yet, McGraw-Hill made the decision to not update this book to cover the new certification exams. So, when Pearson Education/Prentice Hall learned that both IBM and I wanted to make an updated version of this book available and that McGraw-Hill had no interest in producing a revised edition, they extended me offers to publish three new DB2 8.1 Certification Exam Study Guides.

 

Shortly after signing the publishing agreements for these new books, I discovered that the topics covered on Exams 700 and 701 were almost identical to the topics that had been covered on Exams 512 and 513 (which I had just written about). Unfortunately, I also learned that I could not reuse any of my material from the DB2 Administration All-In-One Exam Guide because McGraw-Hill now owned the copyright for that material; if I attempted to reuse any portion of that material, I would be guilty of both self-plagiarism and copyright infringement. And, because McGraw-Hill felt that the DB2 8.1 books would harm the sales of my previous book, they indicated that they would bring a lawsuit against me if they thought I infringed on their copyright in any way. Suddenly, I found myself under contract to write two new books on essentially the same subject, and I was forbidden to reuse a single sentence from my previous work (which was approximately 800 pages in length). I did it, but it was a painful exercise in rewriting and revision that I promised myself I would never go through again.

 

Later, when I left Pearson Education/Prentice Hall and went to MC Press for similar reasons (Pearson Education/Prentice Hall did not want to revise my DB2 8.1 books for the DB2 9 exams and MC Press did), I had Pearson Education/Prentice Hall revert back to me all the rights I had given them in exchange for publishing the DB2 8.1 books. And I did not sign publishing agreements for the DB2 9 books until I received a statement, in writing, that the rights to the DB2 8.1 material had been returned to my possession. This guaranteed that Pearson Education/Prentice Hall could never sue me for copyright infringement because I now owned the rights to my material and could freely reuse portions of it in any way that I pleased.

 

Since then, I've learned to look for ways to hold on to the right to reuse portions of my material in other works so that I won't get into a similar situation. For instance, because parts of the articles that I write for my regular column in IBM Data Management magazine have the potential to be incorporated into the manuscript of a future book on DB2, I have a special contract in place with the magazine publisher (TDA Group) that allows me to freely reuse any material I create for the magazine in a future book if I so desire.

 

As a writer builds a vast collection of material to draw from, there are cases in which he or she may try to reuse portions of his or her material that has already been published. (Reusing material in a book to create a magazine article is one example; reusing material in a book or magazine article as a blog posting is another.) After consulting with an attorney who specializes in intellectual property law, I believe that the factors for reuse that Samuelson identified in 1994 are a good set of guidelines to follow. However, they may not necessarily represent the factors a publisher will use to determine whether an author's work should be viewed as self-plagiarism.

 

At a minimum, you should avoid acts of self-plagiarism unless you meet the criteria outlined in Samuelson's guidelines. Otherwise, you run the risk of disappointing readers—especially if they're expecting something new. But more importantly, unless you have safeguards in place to protect you, keep in mind that whenever you self-plagiarize, you run the risk of copyright infringement. This is particularly true if different publishers end up owning the rights to different works that contain identical material. Consequently, if you truly want to avoid claims of copyright infringement, treat your own previously published works (where copyright was assigned to the publisher) as you would any other copyrighted work that has been authored by someone else.

Final Thoughts

I begin the book From Idea to Print: How to Write a Technical Article or Book and Get It Published by saying that writing is hard work—a worthwhile task that is rarely easy. I also point out that writing an article or a book and getting it published can be extremely rewarding. It took me just over a year to write my first book, The Developer's Handbook to DB2 for Common Servers, and, although I didn't know it at the time, the publication of that book started a chain of events that literally changed my life. Fifteen years, twenty-two books, and numerous magazine articles later, my name has become synonymous with DB2 for Linux, UNIX, and Windows, and I have received several accolades and awards as a result.

 

The goal of this book is to provide you with everything I know about the craft of writing technical articles and books. I trust you will find the information contained in this book helpful and well worth the time you will spend reading it.

 

Roger Sanders

Roger E. Sanders is a Principal Sales Enablement & Skills Content Specialist at IBM. He has worked with Db2 (formerly DB2 for Linux, UNIX, and Windows) since it was first introduced on the IBM PC (1991) and is the author of 26 books on relational database technology (25 on Db2; one on ODBC). For 10 years he authored the “Distributed DBA” column in IBM Data Magazine, and he has written articles for publications like Certification Magazine, Database Trends and Applications, and IDUG Solutions Journal (the official magazine of the International Db2 User's Group), as well as tutorials and articles for IBM's developerWorks website. In 2019, he edited the manuscript and prepared illustrations for the book “Artificial Intelligence, Evolution and Revolution” by Steven Astorino, Mark Simmonds, and Dr. Jean-Francois Puget.

From 2008 to 2015, Roger was recognized as an IBM Champion for his contributions to the IBM Data Management community; in 2012 he was recognized as an IBM developerWorks Master Author, Level 2 (for his contributions to the IBM developerWorks community); and, in 2021 he was recognized as an IBM Redbooks Platinum Author. He lives in Fuquay Varina, North Carolina.


MC Press books written by Roger E. Sanders available now on the MC Press Bookstore.

QuickStart Guide to Db2 Development with Python QuickStart Guide to Db2 Development with Python
Discover how Python, SQL, and Db2 can successfully be used with each other.
List Price $9.95

Now On Sale

DB2 10.5 Fundamentals for LUW (Exam 615) DB2 10.5 Fundamentals for LUW (Exam 615)
Don't even think about attempting to take the DB2 Fundamentals exam without this indispensable study guide.
List Price $79.95

Now On Sale

DB2 10.1 Fundamentals (Exam 610) DB2 10.1 Fundamentals (Exam 610)
Let one of the world's leading DB2 authors and a participant in the exam development help you succeed.
List Price $79.95

Now On Sale

Artificial Intelligence: Evolution and Revolution Artificial Intelligence: Evolution and Revolution
Operational AI has become available to the masses, setting the wheels in motion for a worldwide AI revolution that has never been seen before.
List Price $16.95

Now On Sale

DB2 10.5 DBA for LUW Upgrade from DB2 10.1: Certification Study Notes DB2 10.5 DBA for LUW Upgrade from DB2 10.1: Certification Study Notes
Here's everything you need to know to take and pass Exam 311, complete with a practice exam and study key.
List Price $21.95

Now On Sale

From Idea to Print From Idea to Print
Here's everything you need to know to turn your technical knowledge and expertise into a published article or book.
List Price $49.95

Now On Sale

DB2 9 Fundamentals (Exam 730) DB2 9 Fundamentals (Exam 730)
Use this review before taking the test to prove you've mastered the basics of DB2 9.
List Price $59.95

Now On Sale

DB2 9 for Linux, UNIX, and Windows Database Administration (Exam 731) DB2 9 for Linux, UNIX, and Windows Database Administration (Exam 731)
Use this indispensable study guide to prepare to take, and pass, Exam 731.
List Price $64.95

Now On Sale

DB2 9.7 for Linux, UNIX, and Windows Database Administration (Exam 541) DB2 9.7 for Linux, UNIX, and Windows Database Administration (Exam 541)
Get ready to take the DB2 9.7 certification exam with this handy study guide.
List Price $21.95

Now On Sale

DB2 9 for Linux, UNIX, and Windows Advanced Database Administration (Exam 734) DB2 9 for Linux, UNIX, and Windows Advanced Database Administration (Exam 734)
Review all exam topics and take the included practice test to be sure you're ready on testing day.
List Price $64.95

Now On Sale

DB2 9 for Linux, UNIX, and Windows Database Administration Upgrade (Exam 736) DB2 9 for Linux, UNIX, and Windows Database Administration Upgrade (Exam 736)
Prep for success with the master of DB2 certification study guides!
List Price $34.95

Now On Sale

Data Fabric: An Intelligent Data Architecture for AI Data Fabric: An Intelligent Data Architecture for AI
This book explains the concepts and values that a data fabric approach can deliver to both technical and business communities.
List Price $19.95

Now On Sale

BLOG COMMENTS POWERED BY DISQUS

LATEST COMMENTS

Support MC Press Online

$

Book Reviews

Resource Center

  • SB Profound WC 5536 Have you been wondering about Node.js? Our free Node.js Webinar Series takes you from total beginner to creating a fully-functional IBM i Node.js business application. You can find Part 1 here. In Part 2 of our free Node.js Webinar Series, Brian May teaches you the different tooling options available for writing code, debugging, and using Git for version control. Brian will briefly discuss the different tools available, and demonstrate his preferred setup for Node development on IBM i or any platform. Attend this webinar to learn:

  • SB Profound WP 5539More than ever, there is a demand for IT to deliver innovation. Your IBM i has been an essential part of your business operations for years. However, your organization may struggle to maintain the current system and implement new projects. The thousands of customers we've worked with and surveyed state that expectations regarding the digital footprint and vision of the company are not aligned with the current IT environment.

  • SB HelpSystems ROBOT Generic IBM announced the E1080 servers using the latest Power10 processor in September 2021. The most powerful processor from IBM to date, Power10 is designed to handle the demands of doing business in today’s high-tech atmosphere, including running cloud applications, supporting big data, and managing AI workloads. But what does Power10 mean for your data center? In this recorded webinar, IBMers Dan Sundt and Dylan Boday join IBM Power Champion Tom Huntington for a discussion on why Power10 technology is the right strategic investment if you run IBM i, AIX, or Linux. In this action-packed hour, Tom will share trends from the IBM i and AIX user communities while Dan and Dylan dive into the tech specs for key hardware, including:

  • Magic MarkTRY the one package that solves all your document design and printing challenges on all your platforms. Produce bar code labels, electronic forms, ad hoc reports, and RFID tags – without programming! MarkMagic is the only document design and print solution that combines report writing, WYSIWYG label and forms design, and conditional printing in one integrated product. Make sure your data survives when catastrophe hits. Request your trial now!  Request Now.

  • SB HelpSystems ROBOT GenericForms of ransomware has been around for over 30 years, and with more and more organizations suffering attacks each year, it continues to endure. What has made ransomware such a durable threat and what is the best way to combat it? In order to prevent ransomware, organizations must first understand how it works.

  • SB HelpSystems ROBOT GenericIT security is a top priority for businesses around the world, but most IBM i pros don’t know where to begin—and most cybersecurity experts don’t know IBM i. In this session, Robin Tatam explores the business impact of lax IBM i security, the top vulnerabilities putting IBM i at risk, and the steps you can take to protect your organization. If you’re looking to avoid unexpected downtime or corrupted data, you don’t want to miss this session.

  • SB HelpSystems ROBOT GenericCan you trust all of your users all of the time? A typical end user receives 16 malicious emails each month, but only 17 percent of these phishing campaigns are reported to IT. Once an attack is underway, most organizations won’t discover the breach until six months later. A staggering amount of damage can occur in that time. Despite these risks, 93 percent of organizations are leaving their IBM i systems vulnerable to cybercrime. In this on-demand webinar, IBM i security experts Robin Tatam and Sandi Moore will reveal:

  • FORTRA Disaster protection is vital to every business. Yet, it often consists of patched together procedures that are prone to error. From automatic backups to data encryption to media management, Robot automates the routine (yet often complex) tasks of iSeries backup and recovery, saving you time and money and making the process safer and more reliable. Automate your backups with the Robot Backup and Recovery Solution. Key features include:

  • FORTRAManaging messages on your IBM i can be more than a full-time job if you have to do it manually. Messages need a response and resources must be monitored—often over multiple systems and across platforms. How can you be sure you won’t miss important system events? Automate your message center with the Robot Message Management Solution. Key features include:

  • FORTRAThe thought of printing, distributing, and storing iSeries reports manually may reduce you to tears. Paper and labor costs associated with report generation can spiral out of control. Mountains of paper threaten to swamp your files. Robot automates report bursting, distribution, bundling, and archiving, and offers secure, selective online report viewing. Manage your reports with the Robot Report Management Solution. Key features include:

  • FORTRAFor over 30 years, Robot has been a leader in systems management for IBM i. With batch job creation and scheduling at its core, the Robot Job Scheduling Solution reduces the opportunity for human error and helps you maintain service levels, automating even the biggest, most complex runbooks. Manage your job schedule with the Robot Job Scheduling Solution. Key features include:

  • LANSA Business users want new applications now. Market and regulatory pressures require faster application updates and delivery into production. Your IBM i developers may be approaching retirement, and you see no sure way to fill their positions with experienced developers. In addition, you may be caught between maintaining your existing applications and the uncertainty of moving to something new.

  • LANSAWhen it comes to creating your business applications, there are hundreds of coding platforms and programming languages to choose from. These options range from very complex traditional programming languages to Low-Code platforms where sometimes no traditional coding experience is needed. Download our whitepaper, The Power of Writing Code in a Low-Code Solution, and:

  • LANSASupply Chain is becoming increasingly complex and unpredictable. From raw materials for manufacturing to food supply chains, the journey from source to production to delivery to consumers is marred with inefficiencies, manual processes, shortages, recalls, counterfeits, and scandals. In this webinar, we discuss how:

  • The MC Resource Centers bring you the widest selection of white papers, trial software, and on-demand webcasts for you to choose from. >> Review the list of White Papers, Trial Software or On-Demand Webcast at the MC Press Resource Center. >> Add the items to yru Cart and complet he checkout process and submit

  • Profound Logic Have you been wondering about Node.js? Our free Node.js Webinar Series takes you from total beginner to creating a fully-functional IBM i Node.js business application.

  • SB Profound WC 5536Join us for this hour-long webcast that will explore:

  • Fortra IT managers hoping to find new IBM i talent are discovering that the pool of experienced RPG programmers and operators or administrators with intimate knowledge of the operating system and the applications that run on it is small. This begs the question: How will you manage the platform that supports such a big part of your business? This guide offers strategies and software suggestions to help you plan IT staffing and resources and smooth the transition after your AS/400 talent retires. Read on to learn: