It is extremely important to terminate called programs properly. Failure to
terminate a called program properly can cause damage to production data if you
think you're using test data to test program modifications.
Suppose your production library list consists of production data files (PRODF)
and production programs (PRODP). Now, suppose your test library list consists
of test data files (TESTF), programs in testing (TESTP), and production
programs (PRODP).
PRODP contains only executable programs, print files, and display files. This
way, duplicates of these objects do not need to be kept in the test libraries.
TESTP contains only programs that are actually in testing. Many shops use
similar library list structures.
Here's how damage can occur.
1. You execute PRODP/PGMA. This program calls PRODP/PGMB, which opens
PRODF/FILE1. Then, PGMB terminates with a RETRN statement. Control is returned
to PGMA, but PGMB remains resident and PRODF/FILE1 remains open.
2. You terminate PRODP/PGMA and set up your test library list to test
modifications to PGMA. PGMB has not been modified.
3. You call TESTP/PGMA, which calls PGMB. Since PGMB is not in testing,
PRODP/PGMB is called. But PRODP/PGMB is already resident, and its files are
open. Therefore, your test affects PRODF/FILE1. You've compromised your
production data, thinking you were in your test environment.
To prevent this problem, make PGMA pass a parameter telling PGMB to set on its
LR indicator. This method may not be practical if this error is widespread
throughout your software (as is the case with some commercially available
software packages.)
Another solution is to execute the Reclaim Resource (RCLRSC) command in the CL
program that calls PGMA. This technique disposes of stray resident programs and
closes the files associated with them.
If you use CL programs to set up your library list, a simple solution is to put
the RCLRSC command at the beginning of those programs. Any stray programs left
over from production processing will be cleaned up before you start testing and
vice versa.
--Sam Stafford
More 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.
TRY 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.
Forms 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.
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:
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.
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:
LATEST COMMENTS
MC Press Online