|
Hi Dan, Unless I've missed something too, <grin> a physical file can have only one record format. The RCDFMT parameters (in the CPYF command) of *ALL and *ONLY refers to logical files, since they really mean the same thing to any file with only one record format. I believe the CPYF command was developed as a "do-as-such-as-possible" command, instead of having separate CPYPF and CPYLF commands. I hope this helps. Terry D.BALE@handleman.co m To: MIDRANGE-L@midrange.com Sent by: cc: owner-midrange-l@mi Subject: Can a PF have >1 record format? drange.com 01/09/01 08:51 AM Please respond to MIDRANGE-L I asked this last week and got one response (thanks, Peter!) but would appreciate a little more discourse on the topic. The help for CPYF seems to imply that a PHYSICAL file can have multiple record formats. Am I missing something? I am already familiar with logical files having mulitple record formats. Can someone educate me how the RCDFMT parameter on the CPYF command is used on a physical file? Is this something that would be used for a non-described, multi-format file (i.e., S/36-style Header & Detail formats combined into one file)? The help on my v3r2 says (and v4r4 softcopy is similar): Record format of logical file (RCDFMT) - Help Specifies, for copying from a database file only, the name of the record format that is copied. If the from-file is not a logical or physical file, *ONLY is the only value allowed. A record format name is optional if the logical file has only a single record format, but either a format name or *ALL must be specified if the from-file has more than one record format. The possible values are: *ONLY The only record format in the from-file is copied. When the from-file is a logical file, this value is allowed only if the file has a single record format. *ALL All record formats in the logical from-file are used. record-format-name Specify the name of the record format that is copied when the from-file is a logical or physical file. Dan Bale IT - AS/400 Handleman Company 248-362-4400 Ext. 4952 +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +--- +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.