|
An Open field (type O) is one which can concurrently contain both SBCS and bracketed DBCS data (bracketed meaing DBCS data bracketed by Shift Out and Shift In controls). Other types of fields you may not run into every day are J - can only contain bracketed DBCS, E - can contain either SBCS or bracketed DBCS but not both concurrently, G - graphic data without brackets (can be DBCS or Unicode - UCS2/UTF16). The help text for IGCDTA indicates that *YES will cause the use of Open fields. Can you determine why IGCDTA(*YES) is being used? Assuming that it's a program generating CRTPF ... ICGDTA(*YES) one difference between V5R2 and V5R3 is that the system value QIGC is now always "on" as all systems can now support DBCS (previously a DBCS version of i5/OS needed to be installed). This difference is mentioned in the Memo to Users under 'Changes to system QIGC value'. Bruce Vining "Brad Stone" <brad@xxxxxxxxxxx m> To Sent by: Midrange Systems Technical midrange-l-bounce Discussion s@xxxxxxxxxxxx <midrange-l@xxxxxxxxxxxx> cc 07/13/2005 02:30 Subject PM Data type of "Open"? Please respond to Midrange Systems Technical Discussion I'm on V5R2 and working with a customer on V5R3. The application in question creates a PF and does a CPYSPLF to that file. On V5R2 and previous the field used was of data type "Char". On V5R3 it's now showing as a data type of "Open" which is messing up their SQL statements that they're doing on the file. The command being used is: CRTPF FILE(QTEMP/TEMPFILE) RCDLEN(134) + MBR(*FILE) IGCDTA(*YES) + SHARE(*NO) + LVLCHK(*NO) IGCDATA used to be set to *YES or *NO depending on if the spooled file was DBCS or not, and on V5R3 it seems that they all are, so this is the only difference I can see. Any ideas? What is a data type of "Open"? -- This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
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.