External File

[David Abramowitz]

A physical file may only have a single record format, but a logical may have many. While attempting to convert older S/36 systems, I found it necessary in some cases to define multi-formatted flat files as physical files with only a few fields, and then one big field of everything else. I then created logicals for each format, substringing the large field to appropriate smaller fields. I then created an additional logical which contained all of the formats of the previous LFs. This was not the best comprehensive solution, but the only one that time and budget would allow in this case. Dave

[EDIguru]

This may sound like a dumb question, but is it possible to create a physical file with multiple record formats? I am familiar with multiple format logical files and have a situation where a physical file with mulitple record formats would work well if I could do it.

[Guest.Visitor]

I had a similar situation that the EDIguru has. A large Customer wanted PO's in a flat file for there PC system. I started to see a large investment in time ($$$). Then it hit me. When programmers encounter a Multiple Record format Physical file, we usually create a logical (or two) over it. I created a Logical over several Physical files to represent the required format. Copied (CPYF) the logical to another file created by the command. Then FTP'd it to the Customer. I was happy, he was not. The Customer wanted 12 blank characters on the end of the file. Fear not! I just created a PF of the required width. Then did the same CPYF with FMTOPT(*NOCHK)