Non-FOCUS data sources, JOIN structures used for reporting, and COMBINE structures used for MODIFY can have a maximum of 256 segments. XFOCUS data sources can have 256 segments, but when they are included in COMBINE structures used for MODIFY requests, the limit is 192 (segments plus indices).

The total number of segments in the structure includes segments defined as static cross references (SEGTYPE = KU or KM) in the Master File. Dynamic cross references (SEGTYPE = DKM, DKU, KL, or KLU) are not included in the count.

All other limits such as the number of fields in a Master File, the total length of all fields, and the number of JOINs or COMBINEs allowed are still in effect.

The number of segments in a single FOCUS data source is 64. However, FOCUS data sources can participate in JOIN or COMBINE structures with up to 256 segments. The maximum number of segments plus indices for a single FOCUS data source is 191.

Using an indexed view reduces the maximum number of segments plus indices to 191 for the structure being used. If AUTOINDEX is ON, you may be using an indexed view without specifically asking for one.

A FOCUS segment cannot be longer than a FOCUS page, 3968 (4096 minus overhead) bytes. An XFOCUS segment can be up to 16K bytes. In either case, a data source path cannot be longer than 32K bytes.

In prior releases, any HOLD FORMAT FOCUS or XFOCUS request that specified more than a page of data generated the following message, and the data source was not created:

(FOC397)	LENGTH OF FIELDS ON FOCUS DATA PATH EXCEEDS 32K BYTES:

(FOC400)	KEY FIELDS LENGTH IN SEGMENT EXCEEDED MAXIMUM:

SET ASNAMES=ON
DEFINE FILE MOVIES
NEWTITLE/A1024=TITLE;
END
TABLE FILE MOVIES
PRINT NEWTITLE AS TITLE1
      NEWTITLE AS TITLE2
      NEWTITLE AS TITLE3
      NEWTITLE AS TITLE4
      NEWTITLE AS TITLE5
ON TABLE HOLD AS GIANTMOV FORMAT FOCUS
END

FILENAME=GIANTMOV, SUFFIX=FOC     , $
  SEGMENT=SEG01, SEGTYPE=S1, $
    FIELDNAME=FOCLIST, ALIAS=E01, USAGE=I5, $
         FIELDNAME=TITLE1, ALIAS=E02, USAGE=A1024,  TITLE='TITLE1', $
         FIELDNAME=TITLE2, ALIAS=E03, USAGE=A1024,  TITLE='TITLE2', $
         FIELDNAME=TITLE3, ALIAS=E04, USAGE=A1024,  TITLE='TITLE3', $
  SEGMENT=SEG02, SEGTYPE=U, PARENT=SEG01, $
       FIELDNAME=TITLE4, ALIAS=E05, USAGE=A1024,  TITLE='TITLE4', $
       FIELDNAME=TITLE5, ALIAS=E06, USAGE=A1024,  TITLE='TITLE5', $

Dialogue Manager variable names on z/OS and z/VM can be up to 100 characters.

An unlimited number of Dialogue Manager variables can be used in a procedure.

The limit on FML tag values is now based on available memory rather than on a hardcoded value to service larger FML requests. There is no new syntax and users interact with FML by entering FML requests using an editor or as before.

Reqfor: out of memory

Rectok: out of memory

The number of joins that can be in effect at one time for one data source has been raised to 63. The joined structure can have a total of up to 64 segments. The total length of all fields can be up to 32K and the number of fields in a data source can be up to 3072.

For example, you can have 63 joins between 64 one-segment data sources or three joins between four 16-segment data sources, or any combination that does not exceed 64 segments.

If you are using a relational data adapter, the Relational Database Management System (RDBMS) may have its own limit for the number of joins allowed in an SQL statement. If you create a joined structure that exceeds the number of JOINs allowed by the RDBMS but is within the number of JOINs allowed by FOCUS, the join is processed by FOCUS, but not optimized (passed to the RDBMS for processing).

You could previously merge up to six different data sources or merge data from the same data source up to six times per request. That limit has been raised to 16, allowing you to merge up to 16 data sources in a single MATCH request.

The manner in which MATCH merges the data depends on the request context, or more specifically, the order in which the data sources, BY fields, and display commands are mentioned, as well as on the number of verb objects and BY phrases employed. As before, the following general MATCH conditions apply:

• You can use a total of 32 BY phrases and the maximum normal number of display fields in each MATCH request. You must specify at least one BY field for each file named in the MATCH request.
• DEFINE commands can be used.
• Up to 32 sort sets are supported, including the normal number of common sort fields.
• If used with MATCH, SET HOLDLIST behaves as if HOLDLIST were set to ALL.
• The ACROSS and WHERE TOTAL phrases are not permitted and you cannot use COMPUTE or BY HIGHEST in a MATCH request.

There is no new syntax for this feature.

The length of the DESCRIPTION attribute for a field definition in a Master File has been raised to 2K.

The length of the LINREC and DATREC buffers has increased to 64K. Therefore, the total length of all fields read in a request can be up to 64K bytes. This includes fields in the Master File that are used in the request, fields created with the DEFINE and COMPUTE commands, and fields created internally as a result of internal computations or field reformatting. The total length of fields in the report output has not increased.

The number of fields allowed has not changed. All existing compiled MODIFY procedures should work without recompiling them.

DBA passwords can be up to 64 characters in length.

MAXLRECL indicates the largest actual file record length that FOCUS can read. The limit for MAXLRECL is 65536 bytes, allowing the user to read a record twice as large as the length of the internal matrix, which is limited to 32K. Therefore any request has this processing and output limitation.

SET MAXLRECL = 65536