Dialog Reports

CA ADS Dialog and Application Reporter › Dialog Reports

Dialog Reports

The dialog reporting capabilities of ADSORPTS enable the application developer to request any or all of the following reports for one or several dialogs:

Summary Reports

These list the following information about the object dialog:

The name and version number of the dialog, and the date and time at which the dialog was compiled
The name and version number of the map associated with the dialog, and the date and time at which the map was compiled
The name and version number of the schema associated with the dialog
The name of the subschema associated with the dialog
The dialog's autostatus specification
The dialog's FDB size

Processes Reports

These list the module source statements for the premap and response processes associated with the object dialog. Source statements from included process modules are listed separately.

For each module listed, the following information is provided:

The name and version number of the module
The date on which the module was created, the date on which the module was last modified, and the ids of the users who created and modified the module

Note: The cross-reference report options are available with processes.

Records Reports

These list the following information:

The dictionary definitions for all records associated with the dialog
The decimal position and hexadecimal offset of the fields in the listed records
The lengths of the fields in the listed records

FDBLIST Reports

These list the contents of the Fixed Dialog Block (FDB) for the dialog. The FDBLIST report includes the following information:

General information, such as the dialog's name and compilation date, its map name and compile date, and its subschema description.
Record descriptions contained in the Record Description Elements (RDEs).
Premap process information contained in the Premap Process Element (PME).
Response process information contained in the Response Process Elements (RSEs).
Object code contained in the Process Object Code Table. One Process Object Code Table is associated with each PME and RSE of an FDB that contains object code.
Command information contained in the Command Element (CME). One or more CMEs can be associated with a PME or RSE.
Executable code and vector call information contained in the Executable Code/Vector Call Offset Table. One Executable Code/Vector Call Offset Table is associated with each PME and RSE of an FDB that contains object code.
Included process module information in the Included Module Table (MDTA). One MDTA is displayed for each process in a dialog that has included modules.

Note that the representation of premap and response process information in a dialog's FDB and, consequently, the representation of this information in the report, depend on how the dialog was compiled, as follows:

If the dialog was compiled with the symbol table option enabled, premap and response process commands are converted in the FDB to a series of command elements (CMEs).
If the dialog was compiled without the symbol table option, premap and response process commands are converted in the FDB to object code. The object code for a command can be either an item of executable code or a vector call that references a CME.

Note: Dialogs being reported on by ADSORPTS should be compiled with the diagnostic tables option enabled. ADSORPTS uses diagnostic tables to format premap and response process information. If a dialog's FDB does not contain diagnostic tables, ADSORPTS produces an unformatted report wherever formatting is not possible.

Fixed Dialog Block Field Descriptions

The following table lists the fields displayed in the FDBLIST report.

Group	Field	Description
FDB	ID	Fixed dialog block identifier
	NAME	Dialog name
	DATE	Date dialog compiled
	TIME	Time dialog compiled
	MPNM	Map name
	MPDT	Date map compiled
	MPTM	Time map compiled
	SCHNM	Schema name
	SSNM	Subschema name
	RDEA	Offset— start of record table
	PMEA	Offset— start of premap element
	RSEA	Offset— start of response table
	LITA	Offset— start of literal pool
	SSANA	Offset— subschema area name table
	NSSAN	Number of subschema area names
	SVER	Schema version
	MPVER	Map version
	DVER	Dialog version
	NRECS	Number of map records
	NFLDS	Number of map fields
	NDREC	Number of dialog records
	RSPMI	MRE index of map response field
	MSGMI	MRE index of map message field
	SEGVW	MRB— subschema segmented view
	FLAG	Fixed dialog block flag byte
	LREA	Offset— first logical record RDE
	ASRA	Offset— status definition record ASR
	RLSE	CA ADS release
	FLAG2	FDB flag byte 2
	MAPPG	Map paging type
	HEXTA	Offset— FDB header extension area
	MDBO	Offset— map descriptor block (MDB)
	FLAG3	FDB flag byte 3
	PREFX	Message prefix
	DRSPO	Offset— default response process
	FDEO	Offset— format description headers (FDH) and elements (FDE)
FHE (FDB header extension)	NODE	Alternate DB name
	DICT	Alternate dictionary name
	SDDN	Suspense file DD name
	DCLA Offset— SQL declaration process
	SQLAM	SQL Access module name
	SQLTM	SQL time format
	SQLDT	SQL date format
	SQLFL	SQL compliance flag
MDB (map descriptor block)	MPNAM	Map name (batch)
	NEXT	Offset— next MDB
	DATE	Date map compiled
	TIME	Time map compiled
	VER	Version
	NRECS	Number of records
	NFLDS	Number of fields
	RSPMI	MRE index of map response field
	FLG1	Flag byte 1
	DDNAM	File/ddname
	CRECL	Compressed length for output map external record
	RECL	Real external record length
	CRECO	Offset— compressed external record
SSAN		Subschema area names
ASR	NAME	Status definition record name
	VER	Status definition record version
RDE	NAME	Record name
	NRDEA	Offset— next RDE
	RECL	Record length (except logical records)
	NLRE	Number of logical record elements
	VER	Record version
	INDX	Relative variable record element index entry
	MINDX	Map record index
	FLG1	Flag byte 1
	FLG2	Flag byte 2
	CRECL	Compressed INIT record size
	INTOF	Offset— RDEINITV within RDE to the compressed initialized record
	NLRA	Offset— next logical record RDE (logical records only)
	FLG3	Flag byte 3
	IMNDX	Input map record index
	OMNDX	Output map record index
	SCHML	Length of schema name when created from an SQL table
	SCHMO	Offset into RDE of schema name when created from an SQL table
	INITV	Initial value (in compressed format)
FDH (format description header)	LEN	Length of format description
	ID	Format identifier
	FDES	Start of format descriptor element
FDE (format description element)	TYPE	Element type
	FLAGS	Flag byte
	PEND	Type dependent section
DCL (declaration module)	NAME	Declaration module name
	VER	Declaration module version
	DATLU	Date module last updated
	DATCR	Date module last created
PME	NAME	Premap process name
	LASTB	Offset of last byte in PME
	RATA	Offset to ready area table
	FCMEA	Offset to first CME`1`
	PVER	Process version
	NCMES	Number of CMEs in response`2`
	NEWF	Initialized to X'FF' if new format
	FLAG1	Flag byte
	NMDTE	Number of module table entries
	LNTA	Offset of line number table
	DATLU	Date module last updated
	DATCR	Date module created
	MDTA	Offset of included module table
	OFTBL	Offset to executable code/vector call offset table
RSE	NAME	Response process name
	NXTA	Offset of next RSE in FDB
	LASTB	Offset of last byte in response process
	RATA	Offset to ready area table
	FCMEA	Offset to first CME`1`
	PVER	Process version
	NCMES	Number of CMEs in response`2`
	PFKEY	PF key for response
	FUNLN	Length of response field
	OFUNC	Start old-format function code
	FLAG1	Flag byte
	FUNOF	Offset within RSE to function code
	NMDTE	Number of module table entries
	LNTA	Offset of line number table
	DATLU	Date module last updated
	DATCR	Date module created
	MDTA	Offset of included module table
	OFTBL	Offset to executable code/vector call offset table
	FUNC	Response field value
PROCESS OBJECT CODE TABLE	ICMD# GENERATED CODE	Internal command number Executable code and vector calls
CME	CLASS	Command element major class
	FUNC	Command element function
	NXTA	Offset to next CME from first CME within PME or RSE
	NEXT	Offset of next CME with FDB
	INCLUDED MODULE	Name of included module from which CME was generated
	VERS	Included module version
	SEQ#	IDD sequence number
	FLAG1	First flag byte
	FLAG2	Second flag byte
	FLAG3	Third flag byte
	FLAG4	Fourth flag byte
	ICMD#	Internal command number
	BODY	Parameter for use by run-time system
EXEC CODE/ VECTOR CALL OFFSET TABLE	ICMD#	Internal command number
	VECTOR #	Vector code
	CODE/CME LEN	Length of object code, if executable code; length of CME, if a vector call
	CODE OFF	Offset from first item of object code in process
	VECTOR CALL	Identifies an ICMD as a vector call
RAT TABLE		Ready Area Table
INCLUDED MODULE TABLE	PROCESS	Included module name
VER	Included module version
	DATLU	Date included module last updated
	DATCR	Date included module created
LIT	POOL	Literal pool

1 If the FDB contains object code, the FCMEA indicates the offset to the first item of object code in the Process Object Code Table.

2 If the FDB contains object code, the NCMES contains the original number of CMEs before their conversion to executable code and vector calls.

Vector Call Codes

The following table lists vector call codes and their associated process commands.

Vector code	Process command
0000 0001 0002 0003 0004 0005 0006 0007 0008 0009 000A 000B 000C 000D 000E 000F	Database command Database command— logical record ABORT INVOKE TRANSFER RETURN DISPLAY -- LEAVE LINKT Assignment command Conditional command WHILE REPEAT Internal branch Subroutine call --
0010 0011 0012 0013 0014 0015 0016 0017 0018 0019 001A 001B 001C 001D 001E 001F	ON ADD SUBTRACT MULTIPLY DIVIDE MOVE COMPUTE MODIFY MAP (DC) ACCEPT PUT/GET/DELETE SCRATCH PUT/GET/DELETE QUEUE WRITE PRINTER INITIALIZE RECORDS KEEP LONGTERM SNAP COMMIT
0020 0021 0022 0023 0024 0025 0026 0027 0028 0029 002A 002B 003D 003E 003F	ROLLBACK TASK EXECUTE NEXT FUNCTION -- -- Last vector call; end of process PUT DETAIL GET DETAIL WRITE TRANSACTION READ TRANSACTION CONTINUE WRITE TO LOG CLOSE FILE MAPS ALLOCATE CONTROL SESSION SEND-DATA CONFIRM
0040 0041 0042 0043 0044 0045 0046 0047 0048 0049 004A 004B 004C	CONFIRM CONFIRMED REQUEST-TO-SEND SEND-ERROR RECEIVE-AND-WAIT PREPARE-TO-RECEIVE DEALLOCATE SQL call TRACE OPEN CLOSE SEND RECEIVE

Debugging Information

The information provided in the dialog reports generated by ADSORPTS can be used for debugging. For example, when the CA ADS runtime system causes a dialog to abnormally terminate, it sends messages to the system log. The messages provide the following information:

The reason for the abnormal termination.
The name of the aborted dialog.
The name of the process that was executing at the time of the termination.
The hexadecimal offset within the Fixed Dialog Block (FDB) of the command that was executing at the time of the termination. If the FDB does not contain object code, the offset is to the CME representing the command. If the FDB contains object code, the offset is to the object code that references the CME representing the command.
The IDD sequence number (SEQ#) of the source line containing the command that caused the abend.
The internal command number (ICMD#) of the source line containing the command that caused the abend.

Note: The information above is also displayed on the Dialog Abort Information screen, if enabled.

The information in the system messages can be used in conjunction with the FDBLIST report to determine the command that caused the abend. The internal command number and the hexadecimal offset of the problem command can both be used to locate the command as it is represented in the Process Object Code Table, the list of CMEs, and the Executable Code/Vector Call Offset Table. A CME displays the process command that it represents; an item in the Process Object Code Table and the Executable Code/Vector Call Offset Table displays the vector code of the command, as described in the vector call codes table earlier in this appendix.

More information:

CA ADS Runtime System

CA ADS Dialog Compiler (ADSC)