IDMSRSTT Macro Statements › IDMSRSTT RECNAME

IDMSRSTT RECNAME

The IDMSRSTT RECNAME statement identifies a record type that is being restructured and provides new format and length information for the record, if applicable. The IDMSRSTT RECNAME statement also names database procedures to be executed during the restructure process.

Syntax

 ►─── IDMSRSTT RECNAME = record-name ─────────────────────────────────────────►◄

 ►─┬────────────────────────────────────────────────────────────────────────┬─►
   └─ ,MINLEN = ┬ ( min-root-length,min-fragment-length,max-data-length ) ┬─┘
                └ FIXED ──────────────────────────────────────────────────┘

 ►─┬──────────────────┬───────────────────────────────────────────────────────►
   └─ DCT = dctname ──┘

 ►─┬─────────────────────────────────────────┬────────────────────────────────►
   │                ┌──────── , ───────┐     │
   └─ ,NUPROCS = ( ─▼─ procedure-name ─┴─ ) ─┘

Parameters

RECNAME = record-name

Specifies the name of the record being restructured.

MINLEN =

New format and/or length information for the record.

min-root-length

Applies only to variable-length records and fixed-length compressed records.

The minimum root length, in bytes, of the record, rounded up to the nearest multiple of four, with the following qualifications:

• This value does not include the four-byte variable-length indicator for variable-length records nor the record prefix.
• If the record is being changed from fixed-length uncompressed, min-root-length must be at least four.
• If the minimum root length is not being changed, min-root-length must be zero.

min-fragment-length:

The minimum fragment length, in bytes, for the record, not including the fragment prefix. Must be at least four.

max-data-length:

The maximum data length, in bytes, for the record, not including the four-byte variable-length indicator, rounded up to the nearest multiple of four.

FIXED

Specifies that the record is being changed from variable-length or fixed-length compressed to fixed-length uncompressed.

DCT =

Specifies a PressPack DCT to use when:

• Converting the record from uncompressed to PressPack compressed
• Converting a PressPack compressed record from another PressPack DCT to the specified PressPack DCT.

dctname:

The name of the PressPack DCT.

NUPROCS =

Specifies one or more database procedures to be executed during the restructure process. The procedures are executed just before the RESTRUCTURE utility uses a MODIFY statement to rewrite the restructured record to the database.

procedure-name:

Specifies the name of the procedure.

Usage

Account for all changing records

Code one RECNAME statement for each:

• Record being restructured
• Procedure to be executed before RESTRUCTURE utility uses a MODIFY statement to rewrite the restructured record

Length parameters

All lengths are specified in bytes, rounded up to the nearest multiple of four.

Compressing records with DCT =

Records to be converted to PressPack compressed must be variable length records, or have a new format specified by the MINLEN parameter. You cannot specify MINLEN = FIXED for such records.

Records being converted to PressPack compressed should not have any Before Modify procedures defined that expect to see uncompressed data. The record will already be compressed before the Before procedures are called.

RESTRUCTURE will issue a warning if it encounters Before Modify procedures, but it will continue processing.

Uncompressing PressPack compressed records

To convert records from PressPack compressed records to fixed uncompressed, specify MINLEN = FIXED.

When to use NUPROCS =

List all procedures to be executed for a record during the restructure process before a MODIFY statement, as follows:

• A procedure specified in the new schema should be included if it is not included in the old schema, as long as the procedure is to be executed before a MODIFY statement. For example, if CALL IDMSCOMP BEFORE MODIFY is specified for the record in the new schema, include IDMSCOMP.

  Note: If a procedure is specified in the new schema but is not called before a MODIFY statement, do not include the procedure here. For example, if CALL IDMSDCOM AFTER GET is specified for the record in the new schema, IDMSDCOM should not be included here.

• A procedure that is not specified in the new schema should be included if the procedure is to be executed before a MODIFY statement during the restructure process; such procedures must be added manually to the IDMSRSTT macro statements generated by IDMSRSTC. For example, a procedure that initializes a new data item specified in an IDMSRSTT FIELD statement for the record should be included.