|
META TOPICPARENT |
name="UnicodeTestPlan" |
Maximum Record Size |
|
Allow large alpha fields to be defined in the APPX DD (up to 4GB) |
|
< < | Note: Even thought the theoretical maximum size of an alpha field is 4GB, we have imposed edit checks to limit the maximum size of an alpha field to 1MB (1048576) in characters. |
| This change effects... |
|
< < | |
> > |
- Permanent disk files (only stored in Oracle initially)
|
|
- Memory Files
- Working Storage files
|
|
< < | |
|
Exceptions... |
|
< < |
- Consecutive disk files (no initial support for large alpha fields)
- Temporary disk files (no initial support for large alpha fields)
- One-Record disk files (no initial support for large alpha fields)
|
> > |
- Consecutive disk files (no initial support for large records)
- Temporary disk files (no initial support for large records)
- One-Record disk files (no initial support for large records)
|
| Test Plan:
DD Edit Checks: (untested) |
|
Note: Test these with key and non-key fields |
|
< < | Does the Data Dictionary Editor enforce a 1M field size limit for... |
> > | Does the Data Dictionary Compiler allow a 4G record size for... |
|
- Permanent disk files?
- Memory Files?
- Working Storage files?
|
|
< < | |
| |
|
< < | Does the Data Dictionary Editor enforce the original 32K limit for... |
> > | Does the Data Dictionary Compiler enforce the original 32K limit for... |
|
- Consecutive disk files?
- Temporary disk files?
- One-Record disk files?
|
|
Test Requirements: |
|
< < | Note: Test there with key and non-key fields |
| Note: Perform the following tests for the following... |
|
< < | |
> > |
- Permanent Oracle disk files
|
|
- Memory Files
- Working Storage files
|
|
< < | |
| |
|
< < | Note: The following FMS interfaces will not initially support large fields... |
> > | Note: The following FMS interfaces will not initially support large records... |
|
- DB2
- ODBC
- SQL Server
- C-ISAM
- Vision
|
|
< < | Does Restructure handle the large field correctly? |
> > | Does Restructure handle the large record correctly? |
| |
|
< < | Does the Oracle interface support large fields correctly? |
> > | Does the Oracle interface support large records correctly? |
|
Do you get a reasonable error message when attempting a non-supported FMS type? |
|
< < | Using a Subroutine process, can you store and retrieve 1M character in an alpha field? |
> > | Using a Subroutine process, can you store and retrieve 4G record data? |
| |
|
< < | Using an Input process can you store and retrieve 1M character in an alpha field? |
> > | Using an Input process can you store and retrieve 4G record data? |
| |
|
< < | Using an Output process can you store and retrieve 1M characters in an alpha field for the following as Text and PDF... (I'm not sure this is a doable test, is there a way to print 1M character in an Appx report from a single field?) |
> > | Using an Output process can you store and retrieve 4G record data for the following as Text and PDF... |
| |
|
< < | Using a Query process can you correctly Sort and Select on 1M alpha fields? |
> > | Using a Query process can you correctly Sort and Select on 4G record data? |
| |
|
< < | Using Child Constraints can you correctly access parent/child data with 1M alpha fields? |
> > | Using Child Constraints can you correctly access parent/child data with 4G record data? |
| |
|
< < | Does TECHDOC print the field sizes correctly up to the max of 1M? |
> > | Does TECHDOC print the record size correctly up to the max of 4G? |
|
Test Results and Notes: |
|
Test Requirements: |
|
> > | Note: Test ILF statements with 4G group header where a field name is required. |
| Do the following ILF Statements handle 1M alpha fields correctly? |
|
< < | |
|
- IF / AND / OR - All relational operators
- IF DIFF
- PASS / RECEIVE
- SET
|
|
< < | |
> > |
- STORE / RESTORE - Record and Field
|
|
Test Results and Notes: |