From: James Moore To: All
I need to add a field to our Master physical file. Can anyone give me some tips on what to watch out for? Will I have to recompile the logicals (10 of them) or will an IPL take care of that? Also, will I run into level check problems? Any help would be appreciated.
From: Pete Hall To: James Moore
Yes-on all counts. You could specify LVLCHK(*NO) on the CRTxF or CHGxF commands; but if you do that, your new field may not be properly initialized when records are added, and if the new field is not at the end of the record, you stand a very good chance of corrupting your data. Even input operations may return garbage. You will need to delete all dependent logicals before you will be able to delete the old physical file. If you leave the old physical file on disk, the logicals will remain attached to it. In general, the procedure for modifying a physical file record definition is as follows:
1. Delete all dependent logicals.
2. Rename the old physical file.
3. Create the new physical file (CRTPF).
4. Map the old data into the new file:
CPYF FROMFILE(LIB/OLDFILE) +
TOFILE(LIB/NEWFILE) +
MBROPT(*ADD) FMTOPT(*MAP *DROP)
5. Recreate all dependent logicals (CRTLF).
6. Recompile all programs which use the file or any dependent logicals. If you can't easily identify the programs, either use PDM to scan for the file name, specifying option 14 (compile), or use DSPPGMREF to build an output file for all programs in the application libraries, and write a query to list the programs that use the file(s) or the record name(s), and then manually submit the compiles working from the query report. If you want to get fancy, you can write a CL program to process the DSPPGMREF file and submit the compile commands automatically. You could even front-end the CL program with an OPNQRYF, which would allow a general purpose program to recompile all impacted programs based on a variable file name. I'll bet that would make a neat utility for MC.
7. Delete the old physical file after you are sure that the data is OK.
From: Ernie Malaga To: James Moore
Pete's advice is sound, but I want to add one more tip you may have missed. QUSRTOOL contains a command to recreate a physical file, named Rebuild Database File (RBLDBF). There's also another command to delete all dependent logicals at once (DLTDEPLGL), which is worth looking into.
In general, I don't trust QUSRTOOL much. So, though I can't really recommend that you use these utilities, they could be what the doctor ordered.
LVLCHK(*NO) should be used only temporarily, to get something urgent out the door, but never as a permanent solution. It's a sure-fire way to get into trouble, as Pete mentioned.
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