Status Messages

The following status messages may appear on the ODT and on the station that is running the accessory or component. Note that status messages are not processed by error handler routines.

Accessory

Message

Description

Any

Fatal error

The accessory encountered an error condition that won’t allow it to continue processing. The program will terminate. Possible errors include:

  • Syntax error in the parameter file
  • Software version mismatch
  • An error during initialization

Any

Syntax error on line linenumber column columnnumber: 'token' unexpected

The accessory detected a syntax error in the parameter file at the indicated line number and column number. It found token rather than the expected keyword or value. Correct the parameter file and rerun the accessory.

Any

Syntax error on line linenumber column columnnumber: Missing end quote mark

The accessory detected a syntax error in the parameter file at the indicated line number and column number. It expected to find the closing quotation mark (") for a string. Strings must start and close on the same line of the parameter file. Correct the parameter file and rerun the accessory.

Any

Unexpected end of parameter file

The accessory encountered the end of the parameter file before finding required keywords or values. Add the necessary syntax to the parameter file and rerun the accessory.

Any

Version version compiled compiletime

version indicates the release of the accessory and compiletime indicates when it was compiled. This is an informational message.

Engine

Workers can not exceed maxnumber

This message indicates that the number of Workers specified in the DBEngine parameter file or in an AX WORKERS command exceeds the maximum allowable number. See Workers.

Engine

Workers limit: nn

This message indicates the Workers limit. See Workers.

Engine

Workers unrecognized limit: text

This message indicates that the Workers limit is incorrect. Additional text appears with this message, which explains the problem. See Workers.

Snapshot

Snapshot: After modifying the parameter file, please rerun

When you run Snapshot for a database for the first time, it creates a parameter file. Use CANDE to edit this file so that the options have the proper values. After saving the file, rerun Snapshot.

Snapshot

Snapshot: Creating filename

You ran Snapshot without a parameter file so it is generating one called filename for future use. This run of Snapshot does not generate any data files.

Snapshot

Snapshot: nnn records extracted (nnn filtered out)

This is the response to an AX STATUS command for Snapshot. It shows how many records Snapshot has read so far and how many it has skipped because the DBFILTER procedure discarded them.

Snapshot

Unrecognized command: text

This message indicates that you entered an unrecognized AX command. For valid AX commands, see Snapshot Commands.

Span

DBSpan: After reviewing the parameter file, please rerun

When you run the Span Accessory for a database for the first time, it creates a parameter file. Use CANDE to edit this file so that the options have the proper values. After saving the file, rerun the Span Accessory.

Span

DBSpan: Audit location: AFN = nnn ABSN = nnn

This is the second line of the response to AX STATUS command. It indicates the audit file number and the audit block serial number currently being processed.

Span

DBSpan: Audit time: timestamp

This is the third line of the response to an AX STATUS command. It indicates the original time of the transaction that Span Accessory last processed.

Span

DBSpan: DATABridge SPAN Initializing time on hostname

This is an informational message that tells you the time Span Accessory is starting and the name of the host it is running on.

Span

DBSpan: DATABridge SPAN Terminating time

This is an informational message that tells you the time Span Accessory is stopping. The Span Accessory could be stopping because of an AX QUIT command or because the requirements have been met for the STOP option. See STOP or in Span Accessory Commands, see AX QUIT.

Span

DBSpan: Existing output file has different attributes

The Span Accessory has found an existing output file to append to but it has different file attributes (for example, BLOCKSIZE, AREASIZE, etc.) than what it computed. The existing file will be renamed with the …/OLDATTS node. Process this file on the target system. Then change the target system to expect the output file with the new file attributes.

Span

DBSpan: Final audit location: time, AFN=nnn, ABSN=nnn

This is an informational message that tells you the point in the audit file at which the Span Accessory stopped processing. This information is also located in the NOTE attribute of each Span Accessory output file.

Span

DBSpan: nnn records replicated (nnn skipped)

This is the first line of the response to an AX STATUS command. It indicates the number of records written to the output files and the number of records that were skipped because the DBFILTER procedure discarded them.

Span

DBSpan: Reading parameter file filename

This is an informational message that gives you the name of the Span Accessory parameter file.

Span

DBSpan: Renaming to .../name

Span Accessory has encountered a problem file and is renaming it as follows:

  • Appending /OLDATTS
  • Appending /BAD
  • /OLDATTS

    Span Accessory appends /OLDATTS to indicate that the existing file has different record sizes than the data that the accessory is attempting to write. This can occur after a reorganization. In this case, do the following:

    1. Process the old files on the target system.
    2. Remove them on the source system.
    3. Prepare the target system to receive data files that have the new layout.

    /BAD

    Span Accessory appends /BAD to indicate that the existing file ending audit location does not match the current starting location. If the files were created before changing the HEADER option to TRUE in the Span Accessory parameter file, follow the same procedure as above, but in place of step 3, prepare the target system to receive data files containing the header.

Span

DBSpan: Terminating at next quiet point

An operator has given the Span Accessory an AX QUIT. Span Accessory will terminate at the next quiet point.

Span

DBSpan: Thruput: nnn records/sec. CPU

This is an informational message that tells you the number of data records that the Span Accessory processed per second of CPU time.

Span

DBSpan: Warning: datasetname block size nnn exceeds limit of mmm

The output file block you specified in the Span Accessory parameter file for datasetname is larger than the system block size limit of mmm.

Span

DBSpan: Warning: datasetname block size adjusted to nnn

Span Accessory revised the output file block size to nnn to make the block size within the mainframe limit.

Span

DBSpan: Warning: previous limittype limit ignored

The parameter file contains duplicate settings for the STOP option. limittype can be any of the following:

  • Time
  • Task name

    Specify only one task name and one time limit. If you specify a second task name or a second time limit, the Span Accessory discards the first one and uses only the second one. See STOP.

Span

DBSpan: Unrecognized command: text

This message indicates that you entered an unrecognized AX command. See Span Accessory Commands for valid AX commands.