1200-1299 - DBSpan

Error code	Message and description
`1201`	*Found task taskname* in audit** This informational message indicates that Span met the requirements set by the `STOP` option. It has found the task indicated in the STOP option and will terminate at the next quiet point.
`1202`	Exceeded audit file limit: n This is an informational message that informs you that Span met the requirements set by the STOP option. Span has processed the number of audit files (n) indicated in the `STOP` option and will terminate at the next QPT.
`1203`	Exceeded audit timestamp limit: time This is an informational message that informs you that Span met the requirements set by the `STOP` option. Span passed the timestamp indicated in the `STOP` option and will terminate at the next QPT.
`1204`	Encountered record limit: n This is an informational message that informs you that Span met the requirement set by the `STOP` option. Span received the number of record updates indicated (n) in the `STOP` option and will terminate at the next QPT.
`1205`	Error repositioning filename This message indicates a problem with a `SEEK` command on one of the Span output files. This problem might be a hardware problem. If the hardware is functioning properly and the error message persists, contact Technical Support.
`1206`	No dataset entries in parameter file This message indicates that you did not select any data sets to be processed. Remove the percentage sign (%) in front of the status information for the data sets you want to replicate.
`1207`	Creating new parameter file filename This message indicates that Span is creating the specified parameter file.
`1208`	No header in existing file The Span parameter file indicates that the output data files will contain a header record showing the starting and ending audit locations contained in the file. Span tried to read an existing output file’s header record but did not find it. It is likely that the `HEADER` option was changed to TRUE in the parameter file after the output file was created. If this is the case, transfer the output file to the target system and remove it from the source system so that Span does not find it. Then rerun Span.
`1209`	Ending location too short in existing file The Span parameter file indicates that the output data files will contain a header record showing the starting and ending audit locations contained in the file. Span tried to read an existing output file’s header record, but the area for the ending audit location information was too short. Although a corrupted output file could cause this problem, it is more likely that the HEADER option was changed to TRUE in the parameter file after the output file was created. If this is the case, transfer the output file to the target system and remove it from the source system so that Span does not find it. Then rerun Span.
`1210`	Output file audit location mismatch This message can occur when the following conditions are true: HEADER = TRUE in the Span parameter file You are running Span version 2.0 or later A Span UPDATES file is present In this case, Span tried to append data to an existing output data file with HEADER=TRUE but found that the existing file’s header doesn’t match the current audit location. Span renames the file `.../BAD` and opens a new data file. To avoid this message, move any UPDATES files created by a previous version of Span before you run the current version. If the current version of Span created the existing UPDATES file, then either the Span parameter file was replaced with an older version, or the UPDATES file was replaced with an older version.
`1211`	Previous end location = auditlocation This is an informational message that tells you the audit file location (AFN, ABSN, SEG, and INX) according to the header record in an existing output file from which Span will start to gather updates. This message is displayed when there is a conflict between the audit location in the parameter file and the audit location in the header record of an output file.
`1212`	Current start location = auditlocation This is an informational message that tells you the audit file location (AFN, ABSN, SEG, and INX) according to the header record in an existing output file. The header record corresponds to the first data record in the output file. This message is displayed when there is a conflict between the audit location in the parameter file and the audit location in the header record of an output file.
`1218`	No starting location in existing file The Span parameter file indicates that the output data files will contain a header record showing the starting and ending audit locations contained in the file. Span tried to read an existing output file’s header record but did not find the delimiter indicating the starting location. The output file is probably corrupted. Either remove it or replace it from a backup copy. Then rerun Span.
`1219`	No ending location in existing file The Span parameter file indicates that the output data files will contain a header record showing the starting and ending audit locations contained in the file. Span tried to read an existing output file’s header record but did not find the delimiter indicating the ending location. Most likely, the output file is corrupted. Either remove it or replace it from a backup copy.
`1220`	** parameter must be greater than 0. Adjusting to nnn The Span parameter file contained a negative value for parameter. Span automatically adjusts it to nnn.
`1221`	*MAXRECSIZE not file-equated. Using default nnn* bytes** This is a warning message. The Span parameter file says to write a consolidated output file to tape, but the WFL did not specify a MAXRECSIZE for OUTFILE. Tape files must have a fixed record size. Span will use a MAXRECSIZE of nnn bytes for OUTFILE. Records longer than that will be truncated.
`1222`	** datasetname formatted record size nnn truncated to mmm bytes This is a warning message. The output file record size specified for datasetname in the Span parameter file, mmm, is smaller than the size of a formatted record, nnn, for datasetname. The records will be truncated.
`1223`	** datasetname attribute cannot exceed nnn. Adjusting to mmm The output file record size, block size, or area size for datasetname (or DEFAULT) in the Span parameter file is larger than the mainframe size limit of nnn and will be changed to mmm.