From: Ricky Thompson To: All
Has anyone out there converted S/36 multiformat files to native AS/400 externally described files? We have our order entry file in two different formats. The first line, line item zero, has the basic customer information. The next lines, detail lines, have what the customer ordered. Because almost 75 percent of our programs use this order file, there is no way we can convert this overnight.
Can I create a line item zero file and a detail file and join them with a logical file? For example, our order file is WF.ORD. Can I make two files called ZERO & DETAIL and make a join logical file called WF.ORD without changing any of my programs? They all use the file WF.ORD with both records in it.
From: Pete Hall To: Ricky Thompson
I've done this many times; it's fairly straightforward. You're on the right track. The first thing to do is to create two externally described physical files; one for each record. Copy each record type from the S/36 flat file to the appropriate externally described file.
Now, create a multiformat logical file, not a join logical file. 7 shows a sample of the DDS required for a multiformat logical file. The record format and field names must be the same as the names in the based-on physical files unless you want to create specifications for each field. When you create the logical file, you specify a format selector program, or you can add the format selector later with the Change Logical File (CHGLF) command.
Now, create a multiformat logical file, not a join logical file. Figure 7 shows a sample of the DDS required for a multiformat logical file. The record format and field names must be the same as the names in the based-on physical files unless you want to create specifications for each field. When you create the logical file, you specify a format selector program, or you can add the format selector later with the Change Logical File (CHGLF) command.
Each time you add a record to the database, the format selector program is automatically called and passed two parameters. The first is the entire output buffer and the second is a return parameter in which your format selector returns the name of the record format that the data is to be written to. A simple CL program can do this, as illustrated in 8.
Each time you add a record to the database, the format selector program is automatically called and passed two parameters. The first is the entire output buffer and the second is a return parameter in which your format selector returns the name of the record format that the data is to be written to. A simple CL program can do this, as illustrated in Figure 8.
In this example, &BUFFER is declared with a length of three because that's the last byte that's referenced. The program is really passed a pointer to the data buffer. The record format name is always 10 bytes long.
The only real gotcha is if your multiformat physical doesn't have a key. It's required. If that's the case, you have to manufacture one somehow or live with a flat file. You need to look at the OCL that manipulates the new file, too. Many things that are done with a single physical file on the S/36, such as the copy-delete-rename reorganization technique, are not appropriate with a multiformat logical. You also must replace DELETE with the Clear Physical File Member (CLRPFM) command (in this case twice) and get rid of any BLDFILEs.
Multiformat Files
Figure 7 Multiformat Logical File DDS
*. 1 ...+... 2 ...+... 3 ...+... 4 ...+... 5 ...+... 6 ...+... 7 A R HEADR PFILE(HEADP) A K INVNO * A R DETR PFILE(DETP) A K INVNO A K LINENO
Multiformat Files
Figure 8 Sample Format Selector Program
PGM PARM(&BUFFER &FORMAT) DCL VAR(&BUFFER) TYPE(*CHAR) LEN(256) DCL VAR(&FORMAT) TYPE(*CHAR) LEN(10) IF COND(%SST(&BUFFER 3 1) *EQ 'H') THEN(CHGVAR + VAR(&FORMAT) VALUE(HEADR)) ELSE CMD(CHGVAR VAR(&FORMAT) VALUE(DETR)) ENDPGM
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