How to detect data stream errors and search for specific information

Although the Optimizer can detect data stream errors, it cannot correct any of them for the following reasons:

The Optimizer does not know the application’s true intent. For example, when a bad Set Buffer Address (SBA) has been found, the Optimizer could attempt to correct the error by guessing what the correct address should be. However, if the Optimizer guesses incorrectly, the way that your panels are displayed could vary, which could make things difficult for the terminal user and impossible for your applications to process.

SUPEROPT has been designed to operate transparently in your environment. For example, a CICS application programmer might not be aware of an error if BMC corrected an X PROG error.

System checks for specific information

Examine your system for the following information:

Devices that intercept outbound or inbound data streams to search for specific information
PC software that checks the 3270 data streams for specific information

When SUPEROPT is installed, the data that is being searched for might no longer be transmitted.

Note

PC software should look at the buffer instead of the data stream whenever possible.

If optimization should cause incorrect results

If you discover devices or applications that intercept data streams to search for specific information, ensure that they work correctly when optimization is active. If optimization causes incorrect results, consider one of the following solutions:

Use the Monitor to exclude terminals or transactions from optimization.
Use one of the user exits (controlled from option 1.5.1) to insert data into the following data streams:
- Outbound data stream (after optimization)
- Inbound data stream (after the Optimizer has finished its processing)

Displaying the data stream analysis menu

Summary: In this task, you will display the Data Stream Analysis Menu.

The Data Stream Analysis Menu (Fig. below) displays the data stream analysis panels when you select an appropriate option. To display the Data Streams Analysis Menu, perform the following steps:

Select option 3 on the Monitor Primary Menu.
Press Enter.
The Data Stream Analysis Menu is displayed.
(3.0.0) 3270 SUPEROPTIMIZER/CICS March 30, 2001
Option. . ______ Data Stream Analysis Menu 19:13:04
CICSID:CICSJXE
Select a choice from below.
_ 1 . Application Outbound Data Stream Errors
2 . Hardware Inbound Data Stream Errors
4 . Wraparound Data Stream Trace
9 . Print or Reset Statistics
Optimizer status . . . : Active
Imaging. . . . . . . . : On
Input Suppression. . . : On
Erase Input Key Allowed: No
SCS Printer. . . . . . : On
F1=Help F2=Keys F3=End F4=Return F9=Print

Options 1 and 2 let you determine the frequency and types (application outbound and hardware inbound) of errors that were found in your data streams. Option 4 lets you capture and examine your CICS data streams.

Displaying application outbound data stream errors

Summary: In this task, you will display the Application Outbound Data Stream Errors panel.

To display the Application Outbound Data Stream Errors panel , perform the following steps:

Select option 3 on the Monitor Primary Menu.
Press Enter.
The Data Stream Analysis Menu is displayed.
Select option 1.
Press Enter.

The Application Outbound Data Stream Errors panel is displayed.

Following block shows a typical example of the information that the Optimizer provides for any errors in your outbound data streams. Twenty-three types of errors can occur. Application Outbound Data Stream Error Codes lists all possible error codes and provides a description of each code. The Monitor displays only errors that were found by the Optimizer. If the Optimizer determines that a data stream contains an error, the data stream is excluded from optimization.

(3.1.0) 3270 SUPEROPTIMIZER/CICS December 02, 2001
Option. . ______ Application Outbound Data Stream Errors 15:01:41
CICSID:CICS321

------Error------ -------------Data Stream Error Information-------------
Code Description Frequency Termid Transid SF PI PS Dspl OR/COM TV/A
A18 Invalid SO/SI pairing
4 NS0C SIM1 40 00 0780 0001 00 000A
A05 Invalid data stream order
4 NS0C SIMP 40 00 0780 000D 04 000A

Total Outbound Errors . . . . . . . : 8
Total Errors. . . . . . . . . . . . : 8
F1=Help F2=Keys F3=End F4=Return F9=Print

The statistics that are displayed by the Application Outbound Data Stream Errors panel and the Hardware Inbound Data Stream Errors panel are reset at the following times:

Cold-start of CICS
When the Optimizer is shut down
User-specified times

If a COPSHUT statement is in your DFHPLTSD table, and the COPOPT file is available, these statistics are retained when you perform a warm-start of CICS.

The Reset Statistics options can be set by using option 9. For more information about this option, see Printing and Resetting Optimization Statistics.

For more information about outbound data stream errors, see the IBM 3270 Information Display System Data Stream Programmer’s Reference.

Following table describes the data stream error information that is displayed on the Application Outbound Data Stream Errors panel:

Field	Definition
Error Code	Three-character identifier in the format Axx or Hxx, where A indicates an application outbound data stream error H indicates a hardware inbound data stream error xx is a two-digit number that identifies the error For specific error codes and their descriptions, see table application outbound data stream error code and table hardware inbound data stream error codes.
Error Description	Short message that accompanies the error code For specific error codes and their descriptions, see table application outbound data stream error code and table hardware inbound data stream error codes.
Frequency	Number of data streams in which the Optimizer detected the error
Termid	CICS Termid or VTAM Netname
Transid	CICS Transid or TASKREQ
SF	Structured field code For a list of valid structured field codes, see the glossary
PI	Partition ID or the Local Character Set Identifier (LCID) for programmed symbols
PS	Buffer size or partition size, depending on the state of the device. For programmed symbols, this field contains the structured field length.
Dspl	Displacement of the error in the data stream or the buffer address (for codes A17 through A20)
OR/COM	3270 order or command code, depending on the error type For programmed symbols, this field contains the flag byte with the data format type. For a list of valid command codes and 3270 orders, see the glossary.
TV/A	Type-Value pair or 3270 address, depending on the error type For programmed symbols, this field contains other information that is relevant to the error code.
Total Outbound Errors	Total number of application outbound data stream errors that were found by the Optimizer
Total Inbound Errors	Total number of hardware inbound data stream errors that were found by the Optimizer
Total Errors	Total number of errors that were found by the Optimizer

Following table lists each possible application outbound data stream error code that you can receive, its associated error message, and a description of the error:

Error Code	Description
A01	Truncated parameter list An outbound data stream ended with an incomplete 3270 order.
A02	Unknown character set attribute An SA, SFE, or MF order contains an unknown local character set identifier (LCID). The LCID should have been loaded by a previous load programmed symbol (LPS) structured field. This is usually an application program error. The Optimizer might have detected this error incorrectly if the data stream containing the LPS was excluded from optimization or the Optimizer was not active at the time the LPS was sent to the controller.
A03	Partition ID unknown or invalid The partition ID specified in the structured field was either unknown or invalid for the device. This is usually an application program error. The Optimizer might have detected this error incorrectly if the data stream containing the Create Partition (CP) was excluded from optimization or the Optimizer was not active at the time the CP was sent to the controller.
A04	Invalid structured field An unknown or invalid structured field was detected.
A05	Invalid data stream order An invalid 3270 data stream order was detected. If this was an SCS Printer data stream, then an invalid set function, MPP, left and right margins, or horizontal tab were specified. See the glossary for a list of valid 3270 orders. If an invalid SCS data stream is detected, all subsequent SCS data streams that are sent to the associated SCS printer will not be optimized.
A06	Invalid address An invalid buffer address was detected in an EUA, RA, or SBA order. One of the following conditions was found: Address is unknown. Address is larger than the current device buffer size. Addressing mode is not in sync with the data stream (12, 14, or 16-bit addressing mode). The addressing mode is set in the Create Partition (CP) structured field.
A07	Invalid attribute type An invalid attribute type was detected in an MF, SA, or SFE order. Valid attribute types are 3270 Field Attributes Extended Highlighting Extended Color Character Set Field Outlining Background Transparency Field Validation
A08	Invalid attribute value An invalid attribute value was found for an attribute type other than Character Set in an MF, SA, or SFE order.
A09	Invalid character set An invalid LCID was found in the attribute value field of an attribute type Character Set (programmed symbols) in an MF, SA, or SFE order. This value must be: X'00' or X'40' to X'FE'
A10	Invalid graphic escape character An invalid GE (Graphic Escape) order was detected. Valid values are: X’40’ to X’FE’.
A11	Invalid AID An invalid AID was detected in a 3270 outbound data stream.
A12	Invalid repeat character An invalid repeat character was specified for an RA (Repeat-to-Address) order. The valid repeat characters are: X’00’ and, X’40’ to X’FE’.
A13	Invalid LCID in a Load Programmed Symbols structured field An invalid LCID was detected in a LPS (load programmed symbol) structured field. Valid values for the LCID are: X’40’ to X’EF’.
A14	Invalid RWS in a Load Programmed Symbols structured field An invalid RWS (Read/Write Store) was detected in a LPS (Load Programmed Symbol) structured field. Valid values for the RWS are: X’02’ to X’0B’.
A15	Invalid reply mode in a Set Reply Mode structured field An invalid Reply Mode was detected in the SRM (Set Reply Mode) structured field. Valid Reply Modes are as follows: Field Extended Field Character
A16	Target of a modify field is not an attribute The target of a MF order must be an attribute byte. In this case, the target was not an attribute byte.
A17	Invalid character set in DBCS field Character set character attributes were detected in a DBCS field. The character set character attributes were set by an SA order.
A18	Invalid Shift Out/Shift In pairing A Shift Out/Shift In (SO/SI) pair was detected that is invalid or incomplete. The SO and SI orders must appear as pairs in the terminal buffer.
A19	Invalid DBCS character An invalid DBCS character was detected. Valid DBCS characters are: X'4040' to X'FEFE'.
A20	Invalid DBCS field A DBCS field was detected that has an odd number of bytes and the next byte is not an attribute. This is usually found in conjunction with a SA (Set Attribute) order.
A21	Invalid structured field length A structured field was present in the outbound data stream which was longer than the remaining length of the data stream.
A22	Load Programmed Symbols beginning code point invalid The beginning code point of a LPS (Load Programmed Symbol) must be in the range from X'41' to X'FE'.
A23	Load Programmed Symbols data exceeds RWS limit The programmed symbol (PS) data, which started at the specified beginning code point in the PS set RWS (Read/Write Store), has overflowed. It has exceeded the maximum code point that is allowed for that RWS