Q. I have a multi-company General Ledger system. Each company has its own set of files. The record formats are the same for the different companies. I define the files externally. Some programs such as the payroll G/L entries now reference more than one G/L master file. I don't know if there is a way to eliminate multiple RPG file specifications for the different G/L master files. I thought of two approaches. One is to make each company a member in the new externally defined G/L master. I know you can specify member(*all) on the OVRDBF statement but the CL manual says that you can then only read the records sequentially. The other idea is a logical over the physical files but I'm unsure about having a logical over files with the same record format name. Does anybody have any suggestion or comments?
A. Whether you decide to use a single multiple-member file, or multiple files, you could still create a single logical over the whole shebang.
If you elect to use the multiple file approach though, you do need to have a separate record name for each physical file. A logical file record does not necessarily need to have the same name as the based-on physical file record. If it doesn't, you need to list all the fields that you want included in the record. This can be as simple as copying the field definitions from the physical file source and deleting everything except the field names. You can also rearrange or modify the definitions of the fields if you wish. You end up with something like 5.
If you elect to use the multiple file approach though, you do need to have a separate record name for each physical file. A logical file record does not necessarily need to have the same name as the based-on physical file record. If it doesn't, you need to list all the fields that you want included in the record. This can be as simple as copying the field definitions from the physical file source and deleting everything except the field names. You can also rearrange or modify the definitions of the fields if you wish. You end up with something like Figure 5.
If you go with the single multiple-member file, you can specify DTAMBRS(*ALL) (the default) on the CRTLF or ADDLFM command. I've never used this myself, but I have accidentally created this type of logical a few times when writing applications that use multiple member files. Just be sure not to specify the UNIQUE keyword for the access path.
You may have better control with the pseudo-multiple record type logical, because it allows you to use the record names to discriminate between the different physical files, but either way should work just fine.
TechTalk: File Design
Figure 5 Logical file definition for multiple PFs
Figure 5: Logical File Definition for Multiple Physical Files ... 1 ...+... 2 ...+... 3 ...+... 4 ...+... 5 ...+... 6 ...+... 7 ...+ A R COMPANY1 PFILE(GLMAST1) A FIELD1 A FIELD2 A FIELD3 A K FIELD1 A K FIELD2 A R COMPANY2 PFILE(GLMAST2) A FIELD1 A FIELD2 A FIELD3 A K FIELD1 A K FIELD2 ... 1 ...+... 2 ...+... 3 ...+... 4 ...+... 5 ...+... 6 ...+... 7 ...+
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