SNTDECOD Error Messages

SMA output file cannot be written.

The SMAOUT file is not specified.

This message is informative, not an error message. If you do not want to generate the SMAOUT file, ignore this message, else include the SMAOUT line.

Input file has wrong format. - e not last.

The last record of the input file must contain the string "E......Last Record". Somehow records where included after the "official" last record.

Make sure the FTP does not add records to the end of the transferred file or try deleting those records after "E......Last Record" manually.

Input file has wrong format. - e missing.

The last record of the input file must contain the string "E......Last Record". In this case, this record is missing. Transfer of FTP incomplete?

FTP the Empower encoded file again and ensure that the FTP operates in binary mode. Check that the file is not truncated after the FTP.

Error during open of input file.

The input file contains an EOF in the first record, i.e. the input file contains one record only.

Use a Empower encoded file as input file or check if the FTP passed the file correctly to the mainframe, i.e. created more than one record.

Not used.

Processing stopped. Do not use output file.

This message is printed as a succession of other error messages in this paper.

Find the error preceding this error and follow the recommended action.

Input file has wrong format. - data unit len -.

The length of the encoded data unit is 0 or greater than allowed.

This is an encoding problem. Call Software AG Support.

Input file has wrong format. - record len -

The length of the decoded record is 0 or greater than allowed. Typically the carriage return/line delimiter being marked causes this error. The carriage return/line delimiter should be marked for text, not binary.

Unmark the carriage return/line delimiter and rerun.

Input file has wrong format. - rec i not first.

Multiple "rec i" were found. Only one is allowed.

Wrong version of decoding program.

Input file has wrong format. - rec i not first.

The decoding routine expects the first record of the encoded file to begin with "I", for example, "I111105". This is not the case here.

Make sure the encoded file was not corrupted during the FTP. After the file is uploaded to the mainframe, the first three lines of a good file uploaded would look as follows:

000001 I111105
000002 C(C) Software AG, date/time stamp
000003 dataset set name, format, DCB and blksize information

Input file has wrong format. - nbf -.

The number of data bytes in the file does not match the NumByteFile count contained in the last record of the coded file.

Make sure the encoded file was not corrupted during the FTP.

Input file has wrong format. - chks -.

The number of data bytes in the file does not match the checksum contained in the last record of the coded file.

Make sure the encoded file was not corrupted during the FTP.

Fatal error during decompression - call SAG support.

Typically this error is caused by a corrupt data set. Try downloading and decoding the data set again.

Output file not available.

The SNTOUT file cannot be found

Check that the physical file referenced by SNTOUT is available.

SMA output file must have record length 80.

Specify the record length of 80 for SMAOUT. For z/OS: LRECL=80.

SMA output file must have fixed record length.

Specify a fixed record length for SMAOUT. For z/OS: RECFM=F.

Invalid record format in SNTOUT file.

When uploading the PC file to mainframe, make sure the transfer tool supports the binary mode. The record format of the SNTOUT data set on the mainframe must be FB, record length of 80 and a block size of a multiple of 80, e.g., 6000. Once the upload has been done, one can check if this was successful by examining the contents of this uploaded file. The third record should read something like:

TFRZ.NAT232.ALLI001,VB,4628,4624

IRMALINK adds sequence numbers to the end of the record which may change the format from 80 bytes to 72. Looks like IRMALINK prepares the data for utilities such as IEBCOPY and is not usable for file transfer for SNT.

Invalid record length of SNTOUT file.

For a fixed blocked SNTOUT file, the record length must match the record length of the input file.

Adjust the record length of the SNTOUT file.

Record length of SNTOUT file too small.

For a variable blocked SNTOUT file, the record length must be greater than or equal to the record length of the input file.

Adjust the record length of the SNTOUT file.

Block size of SNTOUT file too small.

For a undef blocked SNTOUT file, the block size must be greater than or equal to the block size of the input file.

Adjust the block size of the SNTOUT file.

Link not successful. CCMO999Exit 12.

Error affects ISP format. Statement STATE=UPDATE is missing.

Include statement STATE=UPDATE when using FORMAT=ISP.

Error writing file Length n / 0.

Drive space limit.

Increase the size of the SNTOUT file. There also may be the possibility that the file is corrupted. You may want to download the fix again from Empower.

Output record too big: n / n

Unable to close output file

Please check the JCL for the input (SNTCOD) and two output files (SNTOUT and SMAOUT). Try specifying SMAOUT (even if you do not use SMA).