Difference: UnicodeRecordSize (1 vs. 2)

Revision 22011-03-04 - PeteBrower

Line: 1 to 1
 
META TOPICPARENT name="UnicodeTestPlan"

Maximum Record Size

Line: 9 to 9
  Allow large alpha fields to be defined in the APPX DD (up to 4GB)
Deleted:
<
<
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...
Changed:
<
<
  • Permanent disk files
>
>
  • Permanent disk files (only stored in Oracle initially)
 
  • Memory Files
  • Working Storage files
Deleted:
<
<
  • Work fields
  Exceptions...
Changed:
<
<
  • 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)

Line: 28 to 25
  Note: Test these with key and non-key fields
Changed:
<
<
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?
Deleted:
<
<
  • Work fields?
 
Changed:
<
<
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?
Line: 46 to 42
  Test Requirements:
Deleted:
<
<
Note: Test there with key and non-key fields
 Note: Perform the following tests for the following...
Changed:
<
<
  • Permanent disk files
>
>
  • Permanent Oracle disk files
 
  • Memory Files
  • Working Storage files
Deleted:
<
<
  • Work fields
 
Changed:
<
<
Note: The following FMS interfaces will not initially support large fields...
>
>
Note: The following FMS interfaces will not initially support large records...
  • Appx-IO
 
  • DB2
  • ODBC
  • SQL Server
  • C-ISAM
  • Vision
Changed:
<
<
Does Restructure handle the large field correctly?
>
>
Does Restructure handle the large record correctly?
 
Changed:
<
<
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?
Changed:
<
<
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?
 
Changed:
<
<
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?
 
Changed:
<
<
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...
 
Changed:
<
<
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?
 
Changed:
<
<
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?
 
Changed:
<
<
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:
Line: 87 to 80
  Test Requirements:
Added:
>
>
Note: Test ILF statements with 4G group header where a field name is required.
 Do the following ILF Statements handle 1M alpha fields correctly?
Deleted:
<
<
  • APPEND
  • BEG AT / END AT
 
  • IF / AND / OR - All relational operators
  • IF DIFF
  • PASS / RECEIVE
  • SET
Changed:
<
<
  • STORE / RESTORE
>
>
  • STORE / RESTORE - Record and Field
  Test Results and Notes:

Revision 12011-03-04 - PeteBrower

Line: 1 to 1
Added:
>
>
META TOPICPARENT name="UnicodeTestPlan"

Maximum Record Size

Increase maximum record size to 4GB


Overview

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
  • Memory Files
  • Working Storage files
  • Work fields

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)

Test Plan:

DD Edit Checks: (untested)

Test Requirements:

Note: Test these with key and non-key fields

Does the Data Dictionary Editor enforce a 1M field size limit for...

  • Permanent disk files?
  • Memory Files?
  • Working Storage files?
  • Work fields?

Does the Data Dictionary Editor enforce the original 32K limit for...

  • Consecutive disk files?
  • Temporary disk files?
  • One-Record disk files?

Test Results and Notes:

Untested

Storage and Processing Capabilities: (untested)

Test Requirements:

Note: Test there with key and non-key fields

Note: Perform the following tests for the following...

  • Permanent disk files
  • Memory Files
  • Working Storage files
  • Work fields

Note: The following FMS interfaces will not initially support large fields...

  • AppxIO
  • DB2
  • ODBC
  • SQL Server
  • C-ISAM
  • Vision

Does Restructure handle the large field correctly?

Does the Oracle interface support large fields 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 an Input process can you store and retrieve 1M character in an alpha field?

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 a Query process can you correctly Sort and Select on 1M alpha fields?

Using Child Constraints can you correctly access parent/child data with 1M alpha fields?

Does TECHDOC print the field sizes correctly up to the max of 1M?

Test Results and Notes:

untested

ILF Statements: (untested)

Test Requirements:

Do the following ILF Statements handle 1M alpha fields correctly?

  • APPEND
  • BEG AT / END AT
  • IF / AND / OR - All relational operators
  • IF DIFF
  • PASS / RECEIVE
  • SET
  • STORE / RESTORE

Test Results and Notes:

untested

-- PeteBrower - 2011-03-04

 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2024 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback