SPUFI trace messages

The SPUFI trace messages, issued by the TSO attachment facility, have unique message numbers.

Begin program-specific programming interface information.

The following SPUFI trace messages are listed in message number order.
Message text Explanation
DSNESM85 MODULE LIST INCOMPLETE. module address NOT DEFINED

An internal Db2 error occurred. The tracing subsystem is disabled.

This message is issued by the following CSECT: DSNESM85

csectname ENTERED

The CSECT specified in the message was entered.

This message is issued by the following CSECTs: DSNESM21, DSNESM30, DSNESM32, DSNESM81

csectname EXITED

Control left the CSECT that is named in the message. This CSECT is about to return control to the CSECT that called it.

This message is issued by the following CSECTs: DSNESM21, DSNESM30, DSNESM32, DSNESM81

csectname STARTING INITIALIZATION

The CSECT named in the message is starting its initialization processing. Events such as GETMAINs and variable initialization will be taking place.

This message is issued by the following CSECT: DSNESM32

csectname STARTING WRAPUP

The CSECT specified in the message is starting its cleanup processing. Events such as FREEMAINs will be taking place.

This message is issued by the following CSECT: DSNESM32

csectname BEFORE GETMAIN

The CSECT specified in the message is about to perform a GETMAIN of the area that holds the YCOLWID array.

This message is issued by the following CSECTs: DSNESM32, DSNESM21

csectname AFTER GETMAIN

The CSECT specified in the message has completed a GETMAIN of the area that holds the YCOLWID array.

This message is issued by the following CSECTs: DSNESM32, DSNESM21

csectname BEFORE MAIN LOOP

The CSECT specified in the message is about to begin running the CSECT's main loop.

This message is issued by the following CSECTs: DSNESM30, DSNESM32, DSNESM81

csectname LOOPTOP

This message is issued after the main loop in the referred to CSECT specified in the message begins running.

This message is issued by the following CSECTs: DSNESM21, DSNESM30, DSNESM32, DSNESM81

csectname TYPE IS INTEGER

The CSECT specified in the message has detected a data type of integer.

This message is issued by the following CSECT: DSNESM32

csectname TYPE IS SMALL INTEGER

The CSECT specified in the message has detected a data type of small integer.

This message is issued by the following CSECT: DSNESM32

csectname TYPE IS DECIMAL

The CSECT specified in the message has detected a data type of decimal.

This message is issued by the following CSECTs: DSNESM30, DSNESM32

csectname TYPE IS FLOAT

The CSECT specified in the message has detected a data type of float.

This message is issued by the following CSECTs: DSNESM30, DSNESM32

csectname TYPE IS CHARACTER

The CSECT specified in the message has detected a data type of character.

This message is issued by the following CSECTs: DSNESM30, DSNESM32

csectname TYPE IS VARCHAR

The CSECT specified in the message has detected a data type of VARCHAR.

This message is issued by the following CSECT: DSNESM32

csectname TYPE IS LONG VARCHAR

The CSECT specified in the message has detected a data type of LONG VARCHAR.

This message is issued by the following CSECT: DSNESM32

csectname CHECKING FOR COLUMN HEADER TRUNCATION

The CSECT specified in the message has started the section of code that checks for column headers that will not fit in the space allowed for the column (as specified on SPUFI panel 2).

This message is issued by the following CSECT: DSNESM32

csectname COLUMN HEADER TRUNCATION OCCURRED

The CSECT specified in the message has discovered a column header that will not fit into the space allotted for it on panel 2. This will cause a message to be written to the output data set.

This message is issued by the following CSECT: DSNESM32

csectname BEFORE WRITING GUTTER CHARACTER

The CSECT specified in the message is about to write the string of characters that appears between columns of data in SPUFI output.

This message is issued by the following CSECT: DSNESM32

csectname FOUND A QUOTE

The CSECT specified in the message is scanning the SQL statement in the input data set and has just encountered a quotation ("). This quotation indicates the beginning or end of a quoted string.

This message is issued by the following CSECT: DSNESM21

csectname FOUND A DBCS SO

The CSECT specified in the message is scanning the SQL statement in the input data set and has just encountered a shift out (SO) character. This indicates the beginning of a DBCS string or substring.

This message is issued by the following CSECT: DSNESM21

csectname FOUND A DBCS SI

The CSECT specified in the message is scanning the SQL statement in the input data set and has just encountered a shift in (SI) character. This indicates the end of a DBCS string or substring.

This message is issued by the following CSECT: DSNESM21

csectname NOT END OF FILE YET

The CSECT specified in the message has not yet discovered an end-of-file condition. It will continue to look for SQL input.

This message is issued by the following CSECT: DSNESM21

csectname BEGINNING FIRST TIME PROCESSING

The CSECT specified in the message is now starting its initialization section. This section performs a GETMAIN and does variable initialization.

This message is issued by the following CSECT: DSNESM21

csectname COMPLETING FIRST TIME PROCESSING

The CSECT specified in the message has finished its initialization processing.

This message is issued by the following CSECT: DSNESM21

csectname ECHOED A RECORD TO OUTPUT DATA SET

The CSECT specified in the message has written a line of SQL from the input data set to the output data set. The SQL statement is echoed for documentation purposes.

This message is issued by the following CSECT: DSNESM21

csectname FOUND AN APOSTROPHE

The CSECT specified in the message is scanning the SQL statement in the input data set and has just encountered an apostrophe. This indicates the beginning or end of a quoted string.

This message is issued by the following CSECT: DSNESM21

csectname FOUND A SEMICOLON

The CSECT specified in the message was scanning the SQL input from the SPUFI input data set and found a semicolon. This indicates the end of an SQL statement.

This message is issued by the following CSECT: DSNESM21

csectname BEFORE MOVING SQL TO IBUF

The CSECT specified in the message is about to move part of an SQL statement (from the SPUFI input data set) into the statement buffer (IBUF).

This message is issued by the following CSECT: DSNESM21

csectname AFTER MOVING SQL TO IBUF

The CSECT specified in the message has moved part of an SQL statement (from the SPUFI input data set) into the statement buffer (IBUF).

This message is issued by the following CSECT: DSNESM21

csectname NULL DATA FOUND

The CSECT specified in the message has discovered a null data item. Null strings are about to be written to the SPUFI output data set.

This message is issued by the following CSECT: DSNESM30

csectname TYPE IS INTEGER OR SMALL INTEGER

The CSECT specified in the message has discovered a data item of type integer or small integer.

This message is issued by the following CSECT: DSNESM30

csectname BEFORE CONVERSION

The CSECT specified in the message is about to perform a data conversion of either decimal, integer, or small integer to EBCDIC. This is so the data can be written to the output data set.

This message is issued by the following CSECT: DSNESM30

csectname AFTER CONVERSION

The named CSECT just performed a data conversion of either decimal, integer, or small integer to EBCDIC. This is so the data can be written to the output data set.

This message is issued by the following CSECT: DSNESM30

csectname TRUNCATION OCCURRED

The CSECT specified in the message has discovered a data item that will not fit in the space allotted for it on the second SPUFI panel. A message will be written to the output data set to indicate that this has happened. Character-type data will be truncated and the remainder will be written. Numeric data will not be written; rather, it will show as all asterisks.

This message is issued by the following CSECT: DSNESM30

csectname NO TRUNCATION OCCURRED

The CSECT specified in the message has discovered a data item that fits in the space allotted for it on the second SPUFI panel. No truncation has occurred.

This message is issued by the following CSECT: DSNESM30

csectname BEFORE CALLING DSNESM34

The CSECT specified in the message is about to call CSECT DSNESM34 to convert a floating-point number to EBCDIC.

This message is issued by the following CSECT: DSNESM30

csectname AFTER CALLING DSNESM34

The CSECT specified in the message has called CSECT DSNESM34 to convert a floating-point number to EBCDIC.

This message is issued by the following CSECT: DSNESM30

csectname TYPE IS CHAR, VARCHAR, OR LVARCHAR

The CSECT specified in the message has detected a data item of type character, VARCHAR, or LONG VARCHAR.

This message is issued by the following CSECT: DSNESM30

csectname LEAVE YSTUFBUF WITH RBUFU NOW = offset

The CSECT specified in the message has inserted a string of characters into the row buffer so that it can be written to the output data set. The next available free position in the output buffer (RBUF) is now offset.

This message is issued by the following CSECT: DSNESM30

csectname TYPE IS GRAPHIC

The CSECT specified in the message has detected a data type of GRAPHIC.

This message is issued by the following CSECT: DSNESM32

csectname TYPE IS VARGRAPHIC OR LONG VARGRAPHIC

The CSECT specified in the message has detected a data type of VARGRAPHIC or LONG VARGRAPHIC.

This message is issued by the following CSECT: DSNESM32

csectnamecsectname - START COLUMN LOOP WITH SQLD = colcount

The program is about to enter a loop that will cycle once for each column looking for truncated data or column names.

This message is issued by the following CSECT: DSNESM40

csectname - BEGIN YBLDL SUBROUTINE

CSECT DSNESM55 has entered the YBLDL internal subroutine.

This message is issued by the following CSECT: DSNESM55

csectname - END YBLDL SUBROUTINE - OPEN oresult; BLDL bresult

The BLDL has just been completed with an open return code of oresult and a BLDL return code of bresult.

This message is issued by the following CSECT: DSNESM55

modid - END EXECUTION returncode

The CSECT csectname has returned to the caller. The returncode in the message is its return code.

This message is issued by the following CSECTs: DSNESM20, DSNESM22

csectname - EXTRACTED DAIRFAIL TEXT DISPLAYED dftext2

This message will accompany message DSNE582. The dftext2 in the message is the second-level error explanation from DAIRFAIL.

DSNESM55 - BEFORE CLOSE OF DATA SET

DSNESM55 is about to close a data set.

This message is issued by the following CSECT: DSNESM55

DSNESM55 - AFTER CLOSE OF DATA SET

DSNESM55 has closed a data set.

This message is issued by the following CSECT: DSNESM55

DSNESM55 - END OF MODULE EXECUTION - RCODE = returncode

DSNESM55 has terminated.

This message is issued by the following CSECT: DSNESM55 The returncode in the message is its return code.

DSNESM55 - END OPEN SUBROUTINE

DSNESM55 has completed the internal OPEN subroutine.

This message is issued by the following CSECT: DSNESM55

DSNESM55 - BEGIN OPEN SUBROUTINE

The CSECT DSNESM55 is attempting to OPEN a data set.

This message is issued by the following CSECT: DSNESM55

DSNESM55 - END DEALLOCATION SUBROUTINE

The deallocation subroutine of CSECT DSNESM55 has completed.

This message is issued by the following CSECT: DSNESM55

DSNESM55 - AFTER DYNALLOC DEALLOCATION REQUEST

The CSECT DSNESM55 has issued a DYNALLOC request to deallocate a data set.

This message is issued by the following CSECT: DSNESM55

DSNESM55 - BEFORE DYNALLOC DEALLOCATION REQUEST

The CSECT DSNESM55 is about to request deallocation of a data set.

This message is issued by the following CSECT: DSNESM55

DSNESM55 - BEFORE DEALLOCATION SUBROUTINE

The CSECT DSNESM55's deallocation subroutine has been entered.

This message is issued by the following CSECT: DSNESM55

DSNESM55 - END OF ALLOCATION SUBROUTINE

The CSECT DSNESM55's deallocation subroutine has completed.

This message is issued by the following CSECT: DSNESM55

DSNESM55 - AFTER DYNALLOC ALLOCATION REQUEST

The CSECT DSNESM55 has issued a DYNALLOC request.

This message is issued by the following CSECT: DSNESM55

DSNESM55 - BEFORE DYNALLOC ALLOCATION REQUEST

The CSECT DSNESM55 is about to issue a DYNALLOC request.

This message is issued by the following CSECT: DSNESM55

DSNESM55 - BEFORE ALLOCATION SUBROUTINE

The CSECT DSNESM55's allocation subroutine has been entered.

This message is issued by the following CSECT: DSNESM55

DSNESM55 - AFTER INITIALIZATION

Initialization for the current call to CSECT DSNESM55 has completed.

This message is issued by the following CSECT: DSNESM55

modid - BEGIN EXECUTION

The CSECT csectname has been entered.

This message is issued by the following CSECTs: DSNESM20, DSNESM22

CALL PRH. RALE=rale#, FVLE=fvle#, QUAL=qualifier

CSECT DSNESM70 is about to transfer program control to DSNAPRH, the application program request handler, for connection to Db2. The RALE, FVLE, and QUAL are parameters that are passed to the APRH.

This message is issued by the following CSECT: DSNESM70

A TSO trace message is issued.

CONNECTION TO SUBSYSTEM subsystem-id SUCCESSFUL

SPUFI has successfully completed all the necessary protocols to access SQL processing functions. SPUFI is about to open the user-specified input and output data sets.

This message is issued by the following CSECT: DSNESM00

A TSO trace message is issued.

END OF SQL INPUT AND OUTPUT PROCESSING

SPUFI SQL execution function has just completed. The SQL statements in the input data set have been processed, and the results have been written to the output data set. Messages DSNE802 and DSNE805 together bracket the section of SPUFI code that is executed whenever the EXECUTE option is YES and the Db2 subsystem is available.

This message is issued by the following CSECT: DSNESM00

A TSO trace message is issued.

csectname JUST READ IN ONE SQL STATEMENT

A SQL statement from the input data set is now in the SPUFI input buffer. The processing of this statement by Db2 SQL-dependent code is to begin immediately.

This message is issued by the following CSECT: DSNESM20

A TSO trace message is issued.

CSECT name JUST COMPLETED PROCESSING ONE SQL STATEMENT

The processing of the SQL statement (which is still in the SPUFI input buffer) by Db2 SQL dependent code has ended. The execution results have been written to the output data set. Messages DSNE810 and DSNE811 together bracket the parts of SPUFI code that are dependent on the protocols and data structures used by the Db2 SQL processing functions.

This message is issued by the following CSECT: DSNESM20

A TSO trace message is issued.

csectname ABOUT TO WRITE A LINE OF OUTPUT

The current content of the SPUFI output buffer has been formatted and is about to be written to the output data set.

This message is issued by the following CSECT: DSNESM22

A TSO trace message is issued.

csectname - BEGIN EXECUTION - SQL REQUEST = request-type

Program control has been given to the CSECT specified in the message. The request-type in the message is the Db2 request that is to be issued by DSNESM68. The meaning of the request-types (PREPARE, DESCRIBE, EXECUTE, OPEN, CLOSE, FETCH, COMMIT, ROLLBACK) correlate exactly with SQL statements with the same names. PRESCRIB, however, correlates with the composite SQL statement PREPARE INTO.

This message is issued by the following CSECT: DSNESM68

A TSO trace message is issued.

csectname - END OF MODULE EXECUTION - SQLCODE = sqlcode

Program control has been returned to the CSECT specified in the message from Db2. The SQLCODE in the SQLCA is displayed in hexadecimal.

This message is issued by the following CSECT: DSNESM68

A TSO trace message is issued.

End program-specific programming interface information.