S (Sort) Errors


 

 

The following are untrappable SORT errors that do not abort the program. Some of these errors do not occur unless there is a hardware malfunction. Though these errors are not trappable, they may be interrogated through the S$ERROR$ system error variable after a SORT operation:

 

Code

Description

S02

Read Error.

S03

Open Error

S04

Prep Error

S08

Write Error

S09

Memory Error

S11

Large File Support Error

S13

Syntax Error

S14

Specified sort key length equals zero.

S15

Format error in the SORT command string (See `S13' error).

S16

Hardware failure. Drive not ready. Destination drive, subdirectory or file is read only.

 

Subcodes:

 

Code

Description

3

Invalid read size accessing temporary work file.

4

Invalid read size accessing input data file.

5

Invalid EOR found for record in input data file.

6

Invalid fixed record size found for input file.

7

Variable record length larger than maximum allowed.

8

Error writing to output file.

9

Insufficient memory to allocate buffers.

10

Data file is not in correct format.

11

Invalid parameter for '-i' option.

12

Help screen not available.

13

The INDEX instruction has encountered an ISI tree depth stack overflow error. This error indicates that the ISI tree structure required for the number of records being indexed has exceeded the capabilities of the runtime. This error can only be corrected by increasing the number of ISI tree levels supported by the runtime.

14

The AAMDEX instruction has encountered an error executing an OS 'lseek' function. This means that the OS has given an error attempting to seek to a position in the input data file. If Windows is being used, the Windows Error Code' is appended to the error message to give more information about the failure.

15

The AAMDEX instruction has encountered an error executing an OS 'read' function. This means that the OS has given an error attempting to read the input data file. If Windows is being used, the 'Windows Error Code' is appended to the error message to give more information about the failure.

21

The operation was canceled by the user.

100

Bad Ouput File Name.

101

Unable to open an ISI file.

102

The ISI version is invalid.

103

ISI header key info invalid.

104

Invalid command line syntax.

105

Read error accessing text data.

106

Error creating output file.

107

File name too long.

108

Invalid record length specification.

109

Error generating temporary file name.

110

Error opening/creating temporary work file.

111

The key specification is too big.

112

Invalid command line syntax.

113

Invalid to overlap keys.

114

ISI maximum key size is too large. The total key size can not be larger than 99.

115

ISI maximum number of key specs exceeded. The total number of key specs is more than 31.

116

Invalid input file name.

117

Unable to open alternate sort sequence file.

118

Invalid primary option syntax.

119

Invalid alternate sort sequence file name.

120

Unable to open the input file.

121

Unable to determine file size for input file.

122

Filename+Extension size limited to 255 characters with 'z' option.

123

Full Path+Filename+Extension size limited to 255 characters without 'z' option

124

Conflicting utility options specified. (f, s, & v).

125

Cannot use L option with V or S option.

126

The Output file name can not be same as Input name.

127

Record size not valid for file length found.

128

Conflicting key options.

129

'm' option fill percentage is invalid.

130

Invalid reformat specification syntax.

131

Insufficient memory to support Reformat option.

132

Output file not specified for tag file specification.

133

Options '-f or -g' require record length specification.

134

Output file not given for reformat file specification.

135

Cannot use more than 10 'P' option parameters.

136

Uppercase option must be given prior to key specification.

137

Conflicting record length specifications.

138

File too large to use space compression or variable length records.

139

Invalid AAM output file name.

140

Unable to open AAM file.

141

Not a valid .aam file.

142

Unable to use AAM file because of invalid version.

143

No keys defined. Invalid .AAM file

144

Re-index command buffer overflow.

145

Unable to open AAM Uppercase Translation File.

146

AAM Uppercase Translation File error.

147

The input line is too long.

148

Too many keys have been selected.

149

A record longer than 32767 bytes was found.

150

Unable to write segment of aamdex file

151

Null file must have record length on command line.

152

Data file is not in the correct format.

153

Insufficient memory.

154

Relinquishing super-powers failed (Linux).

155

Invalid parameter for -i option.

156

Too many records to index.

157

Unable to write segment of index file.

158

Error during output IO.

159

Invalid 'O' option value.

160

Record length not found. A record length must be specified to index an empty TXT file.

161

A record length longer than 65533 has been found. A record length cannot be longer than 65533.

162

A bad ISI header version has been detected during the compact operation of the ISAM file.

163

Not Used!

164

A bad command line has been found in an ISI header during a compact operation of an ISAM file.

165

The INDEX instruction command line is invalid when performing a compact operation of an ISAM file.

166

The command line to be embedded into an ISI during a compact operation cannot be longer than 527 characters.

167

A compact operation could not create a backup of the ISI file.

168

There was an error during a restoration action an ISI file during a compact operation of an ISAM file.

169

Unable to open the TXT data file for an ISI file during a compact operation of an ISAM file.

170

Unable to get exclusive access of a TXT data file during a compact operation of an ISAM file. In addition, the TXT data file size was changed unexpectedly during a TXT data compact operation of an ISAM file.

171

An invalid numeric clarifier for the INDEX 'Cn' compact option has been detected. The numeric 'n' clarifier must be '0', '1', '2', or '3'.

172

Too many AAM blocks have been written to the '.AAM' file for the number of records in the TXT data file. (9.6A)

173

Unable to determine the maximum number of AAM blocks to be written to a '.AAM' file. This error can only occur if the runtime is unable to determine the length of a TXT data file. (9.6A)

174

AAMDEX operation has encountered a case where the same TXT data block has been read more than once to create a .AAM hash reference. This can only happen if an unexpected OS IO error has occurred.

 

 

See Also: PL/B Errors

 



Compiler and Runtime Options O (Object) Errors S (Spool) Errors