Commit | Line | Data |
---|---|---|
72133c74 CL |
1 | -4 |
2 | "arg count" | |
3 | You typed either too few or too many arguments. | |
4 | -6 | |
5 | "bad date/time" | |
6 | The date/time must be a legitimate date/time in the form | |
7 | "YY[MM[DD[HH[MM[SS]]]]]". The program knows about things | |
8 | like leap years, so be precise. | |
9 | -7 | |
10 | "bad heuristic level" | |
11 | The heuristic level must be a number from 0 to 3. | |
12 | -8 | |
13 | "bad lookahead" | |
14 | The lookahead must be an integer greater than 0. | |
15 | -26 | |
16 | "can't open ..." | |
17 | The file couldn't be opened for reading. Either it doesn't exist | |
18 | or it isn't readable. | |
19 | -42 | |
20 | "format error at record ..." | |
21 | The format of the SCCS file is logically invalid. The error | |
22 | was discovered at the stated record. See if you can | |
23 | find the problem with the prt command. If not, do a "help stuck". | |
24 | -46 | |
25 | "level not allowed with e" | |
26 | You can't specify a level when you're getting with the "e" argument. | |
27 | -47 | |
28 | "level not numeric" | |
29 | You erred in typing a level number. | |
30 | -48 | |
31 | "level too big" | |
32 | You specified a level greater than the highest level for the | |
33 | release, or else one bigger than 9999. | |
34 | -49 | |
35 | "missing file arg" | |
36 | You left the file argument off. | |
37 | -53 | |
38 | "not an SCCS file" | |
39 | The file isn't an SCCS file, Use prt if you don't believe it. | |
40 | -55 | |
41 | "out of space" | |
42 | There's no more dynamic memory left. If you got this from | |
43 | delta, try a smaller lookahead ("l" argument). If you got | |
44 | it somewhere else, better go to "help stuck". | |
45 | -58 | |
46 | "premature eof" | |
47 | The SCCS file ended in a strange place. Its probably a goner. | |
48 | You can try "help stuck", but chances are you're going to | |
49 | have to go to a backup copy. | |
50 | -63 | |
51 | "release not numeric" | |
52 | You erred in typing a release number. | |
53 | -69 | |
54 | "unknown key letter" | |
55 | You typed an illegal argument key letter. | |
56 | -71 | |
57 | "zero release" | |
58 | You can't specify release 0. | |
59 | -75 | |
60 | "Who are you?" | |
61 | Your entry in "/etc/passwd" is messed up. Tell the UNIX system | |
62 | administrator. | |
63 | -83 | |
64 | "not found" | |
65 | No helpful information associated with your argument was found. | |
66 | If you're sure you've got it right, do a "help stuck". | |
67 | -115 | |
68 | "hardware -- <message>" | |
69 | This error is most likely due to an intermittent hardware error. | |
70 | You should report this to your local UNIX support group. | |
71 | immediately, since others may be getting the same error and it is useful | |
72 | to discover a pattern if one exists. After reporting it, if you rerun | |
73 | the command it will probably not recur. If it won't go away contact | |
74 | your PWB counsellor. | |
75 | ||
76 | (If required, a core dump will be produced if the file "dump.core" exists | |
77 | in the current directory.) | |
78 | -201 | |
79 | "corrupted file" | |
80 | The computed hash count of the input SCCS file did not check with the | |
81 | stored hash count. The file may have been damaged since it was last | |
82 | accessed. See your local SCCS maintenance person. | |
83 | -202 | |
84 | "record too big" | |
85 | Internal error. Execute "help stuck". | |
86 | (putr called with len > 255.) | |
87 | -204 | |
88 | "can't read `...'" | |
89 | The named directory exists but isn't readable. Checks its modes with | |
90 | "ls -ld ...". | |
91 | -205 | |
92 | "`...' too long" | |
93 | The pathname is too long. | |
94 | -206 | |
95 | "directory `...' unwritable" | |
96 | The effective user (probably you) doesn't have write permission in | |
97 | the directory. Do a "ls -ld ..." to check the modes. | |
98 | -207 | |
99 | "error ... creating `...'" | |
100 | An unusual error in attempting to create the file. Try "help stuck". | |
101 | (Function xcreat; number is external errno.) | |
102 | -208 | |
103 | "`...' nonexistent" | |
104 | The file does not exist. Check for typos. | |
105 | -209 | |
106 | "`...' unreadable" | |
107 | The file probably exists, but the effective user doesn't have read permission. | |
108 | It is also possible that one or more directories in the path aren't executable. | |
109 | -210 | |
110 | "`...' unwritable" | |
111 | The file exists, but the effective user doesn't have write permission. | |
112 | It is also possible that one or more directories in the path aren't executable. | |
113 | -211 | |
114 | "`...' unreadable or unwritable" | |
115 | The file exists, but the effective user either doesn't | |
116 | have read permission, or write permission, or both. | |
117 | It is also possible that one or more directories in the path aren't executable. | |
118 | -212 | |
119 | "error ... opening `...'" | |
120 | An unusual error occurred while opening the file. Try "help stuck". | |
121 | (Function xopen; number is external errno.) | |
122 | -213 | |
123 | "directory `...' nonexistent" | |
124 | The directory doesn't exist. Check for typos. | |
125 | -215 | |
126 | "writable `...' exists" | |
127 | For safety's sake, SCCS won't overwrite an existing g-file if it's writable. | |
128 | If you don't need the g-file, remove it and rerun the get command. | |
129 | -216 | |
130 | "bad p-file" | |
131 | The p-file has the wrong format. If you have write permission on it you can | |
132 | try to fix it with the editor, or else remove it and do another get with an | |
133 | e argument. | |
134 | -217 | |
135 | "release too big" | |
136 | Release numbers can't be bigger than 9999. | |
137 | -218 | |
138 | "release ... < ... (floor)" | |
139 | Either the release you specified or else the default release is lower | |
140 | than the lowest allowable release (the floor). If you're not sure what's | |
141 | wrong see your SCCS administrator. | |
142 | -219 | |
143 | "release ... > ... (ceiling)" | |
144 | Either the release you specified or else the default release is higher | |
145 | than the highest allowable release (the ceiling). If you're not sure what's | |
146 | wrong see your SCCS administrator. | |
147 | -220 | |
148 | "release ... locked" | |
149 | The release you specified or the default release is locked. | |
150 | Refer questions to your SCCS administrator. | |
151 | -222 | |
152 | "bad range" | |
153 | In a delta list, the two limits of a range of deltas were not in ascending | |
154 | order. | |
155 | -223 | |
156 | "delta list syntax" | |
157 | A list of deltas was syntatically erroneous. The correct syntax is: | |
158 | <list> ::= <range> | <list> , <range> | |
159 | <range> ::= <delta> | <delta> - <delta> | |
160 | <delta> ::= <rel> | <rel> . <lev> | |
161 | -224 | |
162 | "invalid release" | |
163 | In a delta list, one of the following errors was made: | |
164 | 1. A release number was less than 1. | |
165 | 2. A release number was greater than the highest release which | |
166 | has a delta. | |
167 | -225 | |
168 | "invalid level" | |
169 | A level specified in a delta list does not exist. | |
170 | -226 | |
171 | "vacant release" | |
172 | A level was omitted in a delta list, but the specified release has | |
173 | no deltas in it. | |
174 | -227 | |
175 | "e not allowed with m" | |
176 | You can't use both the -e and -m arguments on the same get command. | |
177 | -228 | |
178 | "being edited at release ... by `...'" | |
179 | You can't do a get with an -e argument because someone else already | |
180 | did and hasn't made a delta yet. If that someone else is really you, | |
181 | you can regenerate a new file to be edited, if necessary, by using the -k | |
182 | argument. If you want to cancel the reservation entirely, see your | |
183 | SCCS administrator, and tell him/her you want the p-file removed. | |
184 | -229 | |
185 | "... already included" | |
186 | You mentioned the same delta twice with an -i and/or an -x argument. | |
187 | -230 | |
188 | "... already excluded" | |
189 | You mentioned the same delta twice with an -x and/or an -i argument. | |
190 | -231 | |
191 | "internal error in get/enter()" | |
192 | Do a "help stuck". | |
193 | -232 | |
194 | "value after ... arg" | |
195 | You had something after the indicated keyletter argument and you weren't | |
196 | supposed to. | |
197 | -301 | |
198 | "not an SCCS file" | |
199 | A file that you think is an SCCS file | |
200 | does not begin with the characters "s.". | |
201 | -302 | |
202 | "Release p is empty; accessing r.l" | |
203 | No level was specified; the release specified has no deltas. | |
204 | The release and level actually being accessed is r.l. | |
205 | (If the k keyletter was not explicitly or implicitly supplied, the | |
206 | replacement for the 1 and 1 keywords will be r and l, respectively -- | |
207 | not p and 0.) | |
208 | This is not an error, only a warning. | |
209 | -303 | |
210 | "clock set wrong!!!" | |
211 | The time of day is wrong. Contact your local UNIX support group immediately! | |
212 | (Try a "date" command.) | |
213 | (This error is produced whenever the creation date of the newest delta | |
214 | in the SCCS file is newer than the current date. This will happen | |
215 | whenever the date is accidently set wrong. This error | |
216 | will also occur if a delta was created while the clock was | |
217 | set ahead - but less than a year - and has since been corrected. | |
218 | In this case the current time is correct, but the date of the | |
219 | delta is wrong.) | |
220 | -304 | |
221 | "level zero not allowed" | |
222 | You are not allowed to specify level zero because level zero doesn't | |
223 | mean anything. If you want the highest level | |
224 | of a given release, specify the release number without a level. | |
225 | -305 | |
226 | "No id keywords" | |
227 | No SCCS identification keywords were substituted for. | |
228 | You may not have any keywords in the file, | |
229 | in which case you can ignore this warning. | |
230 | If this message came from delta then you just made a | |
231 | delta without any keywords. | |
232 | If this message came from get then | |
233 | the last time you made a delta you changed the lines | |
234 | on which they appeared. | |
235 | It's a little late to be | |
236 | telling you that you messed up the last time you made a delta, but this is | |
237 | the best we can do for now, and it's better than nothing. | |
238 | ||
239 | This isn't an error, only a warning. | |
240 | -306 | |
241 | "Clock may be set wrong!" | |
242 | The time of day may be set wrong. | |
243 | Check the current time with the "date" command. | |
244 | If it is wrong, contact your local UNIX support group immediately! | |
245 | (This message is produced whenever the difference between | |
246 | the current date and the creation date of the newest delta in | |
247 | the SCCS file is greater than one year.) | |
248 | -307 | |
249 | "you are not `...'" | |
250 | Your login name is not the same as the one found in the p-file. | |
251 | You can't remove a delta when a p-file exists, and the name therein | |
252 | is not yours. | |
253 | -308 | |
254 | "you are not `...'" | |
255 | Your login name is not the same as the login name | |
256 | of the person who made the most recent delta. Only the person who made | |
257 | a delta can remove it (when a p-file exists). | |
258 | -309 | |
259 | "sorry" | |
260 | You are not the owner of both the directory containing the sccs file, | |
261 | and the sccs file itself. If a p-file doesn't exist, only the owner | |
262 | of the file and directory can remove a delta. | |
263 | -310 | |
264 | "no delta" | |
265 | The release and level specified is not the release and level of | |
266 | any delta in the sccs file. | |
267 | -311 | |
268 | "sorry" | |
269 | You are not the owner of both the directory containing the sccs file, | |
270 | and the sccs file itself, or you are not the user who made the named delta. | |
271 | -312 | |
272 | "illegal data on line ..." | |
273 | The named line (of the ASCII file) is 5 characters long | |
274 | (not counting the newline), | |
275 | and the fifth character is one of octal 363, 364, or 365. | |
276 | It is illegal to input such data to SCCS. | |
277 | -313 | |
278 | "history too long" | |
279 | A history response can be at most 200 characters long. | |
280 | -322 | |
281 | "you are not `...'" | |
282 | You are not the same person who last did a `get' with an `e' argument. | |
283 | Only the person who did the last `get' with an `e' can make a delta. | |
284 | -323 | |
285 | "read error on standard input" | |
286 | A response from the standard input was solicited and | |
287 | an error occurred. | |
288 | -324 | |
289 | "delta will not propagate" | |
290 | The delta being made is in a release which is lower than the highest | |
291 | numbered release that has deltas. When the SCCS file is gotten | |
292 | at any release higher than the one in which this delta is being inserted, | |
293 | this delta will NOT be applied. | |
294 | This is not an error, only a warning. | |
295 | -325 | |
296 | "more than one link" | |
297 | SCCS files may only have one name (link). | |
298 | This is because the delta program unlinks the old file | |
299 | and then links to the new file. | |
300 | -326 | |
301 | "missing history" | |
302 | If you specify the `-' argument (standard input), | |
303 | you must supply the history on the command line (-y argument). | |
304 | -330 | |
305 | "error ... linking `...' to `...'" | |
306 | An error occurred while linking the first file to the second file. | |
307 | The number is the system error number (see INTRO(II)). | |
308 | If you can't figure out what happened, | |
309 | execute "help stuck". Remember the error number. | |
310 | (Function xlink; number is external errno.) | |
311 | -331 | |
312 | "error ... unlinking `...'" | |
313 | An error occurred while unlinking the file. | |
314 | The number is the system error number (see INTRO(II)). | |
315 | If you can't figure out what happened, | |
316 | execute "help stuck". Remember the error number. | |
317 | (Function xunlink; number is external errno.) | |
318 | -350 | |
319 | "write error" | |
320 | The file which caused the write error is as large | |
321 | as a file can be (currently 1M bytes). | |
322 | -351 | |
323 | "no space!" | |
324 | The file system (on which the file which caused the error is being written) | |
325 | is out of space. Very serious!! Contact someone in | |
326 | your local UNIX Support Group immediately! | |
327 | Also, if you can remove any files please do so. | |
328 | -352 | |
329 | "write error ..." | |
330 | This is probably a transient error. | |
331 | Try again; if it happens again do a "help stuck". | |
332 | Remember the error number. | |
333 | (Function xwrite; number is external errno.) | |
334 | -399 | |
335 | "not authorized to make deltas" | |
336 | Your User ID is not on the list of users who are allowed to add deltas to this | |
337 | file. You can execute "prt -h file" to see who is allowed. See your | |
338 | project administrator to get your login on the list. | |
339 | -410 | |
340 | "missing r" | |
341 | You didn't give an "r" argument. | |
342 | -411 | |
343 | "no level specified" | |
344 | You didn't specify a level. | |
345 | -416 | |
346 | "not the most recent delta" | |
347 | Only the most recent delta (the first one printed by prt) | |
348 | can be removed. The release and level you specified are | |
349 | not the same as those of the most recent delta. | |
350 | -420 | |
351 | "bad starting record" | |
352 | The starting record number (s argument) is not a positive integer. | |
353 | -421 | |
354 | "not an SCCS file" | |
355 | The magic number of the named file is not what it should be. | |
356 | The file is probably not an SCCS file. If you're sure it is, | |
357 | then it has probably been corrupted. | |
358 | -450 | |
359 | "bad ceiling" | |
360 | The ceiling (c argument) is not a positive integer. | |
361 | -451 | |
362 | "bad ceiling" | |
363 | The ceiling (c argument) is either too large or too small. | |
364 | -452 | |
365 | "bad floor" | |
366 | The floor (f argument) is not a positive integer. | |
367 | -453 | |
368 | "bad floor" | |
369 | The floor (f argument) is either too large or too small. | |
370 | -454 | |
371 | "bad r argument" | |
372 | The release is not a positive integer. | |
373 | -455 | |
374 | "bad r argument" | |
375 | The release is either too large or too small. | |
376 | -456 | |
377 | "too many locks" | |
378 | More than 5 l arguments were specified. | |
379 | -457 | |
380 | "bad lock" | |
381 | A lock (l argument) is not a positive integer. | |
382 | -458 | |
383 | "bad lock" | |
384 | A lock (l argument) is either too large or too small. | |
385 | -459 | |
386 | "too many unlocks" | |
387 | More than 5 u arguments were specified. | |
388 | -460 | |
389 | "bad unlock" | |
390 | An unlock (u argument) is not a positive integer. | |
391 | -461 | |
392 | "bad unlock" | |
393 | An unlock (u argument) is either too large or too small. | |
394 | -462 | |
395 | "bad y argument" | |
396 | The release is not a positive integer. | |
397 | -463 | |
398 | "bad y argument" | |
399 | The release is either too large or too small. | |
400 | -464 | |
401 | "key letter twice" | |
402 | A key letter was specified twice. | |
403 | This is probably a typo on your part. | |
404 | -465 | |
405 | "more than one file" | |
406 | Only one file argument is allowed when an i argument is specified. | |
407 | -466 | |
408 | "file exists" | |
409 | The file you are trying to create already exists. | |
410 | -467 | |
411 | "file does not exist" | |
412 | The file to be modified does not exist. | |
413 | -468 | |
414 | "read error" | |
415 | The named file is either not an SCCS file, | |
416 | or a corrupted SCCS file. | |
417 | -469 | |
418 | "Release X wasn't locked" | |
419 | You tried to unlock release X which wasn't locked. | |
420 | This is only a warning. | |
421 | -470 | |
422 | "too many locks" | |
423 | The file has already been locked some number of times. | |
424 | You are trying to add some number of locks which will make | |
425 | the total number of locks more than 5. | |
426 | -471 | |
427 | "description too large" | |
428 | More than 99 characters of description (d argument) were specified. | |
429 | -472 | |
430 | "person too large" | |
431 | More than 13 characters of `person' (p argument) were specified. | |
432 | -473 | |
433 | "type too large" | |
434 | More than 9 charcters of `type' (t argument) were specified. | |
435 | -474 | |
436 | "write error" | |
437 | An error occured while trying to update the file. | |
438 | The system is probably in very bad shape. | |
439 | The file did not get updated correctly. | |
440 | -475 | |
441 | -476 | |
442 | "release X twice" | |
443 | You specified X in two lock or unlock arguments. | |
444 | This is probably a typo on your part. | |
445 | -477 | |
446 | "person not in passwd file" | |
447 | The person to be added (or erased) is not in the system password file. | |
448 | * | |
449 | * icat/ucat messages | |
450 | * | |
451 | -600 | |
452 | "missing account number" | |
453 | You forgot to specify an account number (-a argument). | |
454 | -601 | |
455 | "account number" | |
456 | The account number specified is either non-numeric, | |
457 | or is not four characters long. | |
458 | -602 | |
459 | "bad account number" | |
460 | The account number specified is not numeric. | |
461 | -603 | |
462 | "bad forms value" | |
463 | The forms value specified is not four characters long. | |
464 | -604 | |
465 | "bad forms value" | |
466 | The forms value specified is not numeric. | |
467 | -605 | |
468 | "Bad job class" | |
469 | The job class specified is not an alphabetic. | |
470 | -606 | |
471 | "Bad job name" | |
472 | The job name specified is longer than eight characters. | |
473 | -607 | |
474 | "program `...' not found" | |
475 | The specified program is not in /usr/bin or /bin. | |
476 | -608 | |
477 | "bad location" | |
478 | The specified location is not 47, 49, or 51. | |
479 | -609 | |
480 | "bad runid" | |
481 | The specified run id is longer than 6 characters. | |
482 | -610 | |
483 | "bad page limit" | |
484 | The page limit specified is not numeric. | |
485 | -611 | |
486 | "bad time limit" | |
487 | The time limit specified is not numeric. | |
488 | * | |
489 | * end icat/ucat messages | |
490 | * | |
491 | * | |
492 | * ifetch, ufetch, and extr messages | |
493 | * | |
494 | -803 | |
495 | "missing file arg" | |
496 | You forgot to specify a file argument. | |
497 | -804 | |
498 | "premature eof" | |
499 | In extr, a prnt file ended at a strange place. | |
500 | -805 | |
501 | -806 | |
502 | -807 | |
503 | "format err" | |
504 | In epnch, a pnch file has an invalid format. | |
505 | -808 | |
506 | "Possible errors" | |
507 | The file being processed by extr | |
508 | is not in the proper format - | |
509 | this is usually a result of an ifetch or ufetch failure of some kind. | |
510 | Examine the printout file!! | |
511 | This message is only a warning. | |
512 | -809 | |
513 | "cannot fork - try again" | |
514 | The system process table is temporarily full, | |
515 | wait a while and try again. | |
516 | * | |
517 | * vc messages | |
518 | * | |
519 | -901 | |
520 | "unknown command on line ..." | |
521 | The line given begins with a control character, | |
522 | but the command is not a legal one. | |
523 | -902 | |
524 | "`...' never used" | |
525 | The given keyword name was never used in any replacements. | |
526 | This is only a warning. | |
527 | -903 | |
528 | "`...' never declared" | |
529 | The given keyword name never occured in a `dcl' | |
530 | statement. If you did declare it, check for typos. | |
531 | This is only a warning. | |
532 | -904 | |
533 | "`If' with no matching `end'" | |
534 | There is a missing `end' statement, | |
535 | or an extra `if' statement. | |
536 | -905 | |
537 | "`...' declared twice on line ..." | |
538 | The named keyword has been redeclared | |
539 | on the indicated line. | |
540 | -906 | |
541 | "out of space" | |
542 | A maximum of 40 keywords per invocation of vc are allowed. | |
543 | This limit has been exceeded. | |
544 | -907 | |
545 | "unmatched `:' on line ..." | |
546 | On the given line there is no control character | |
547 | to indicate the end of the keyword name. | |
548 | -908 | |
549 | "keyword name too long on line ..." | |
550 | On the indicated line a keyword name exceeds nine characters. | |
551 | -909 | |
552 | "invalid keyword name on line ..." | |
553 | On the indicated line the keyword name does not | |
554 | start with an alphabetic character, or does not contain | |
555 | only alphanumeric characters. | |
556 | -910 | |
557 | "`end' without matching `if' on line ..." | |
558 | There is an extra `end' statement or a missing | |
559 | `if' statement. | |
560 | -911 | |
561 | "parenthesis error on line ..." | |
562 | A left parenthesis occured with no matching right | |
563 | parenthesis or a parenthesis was found where it was not expected. | |
564 | -912 | |
565 | "invalid operator on line ..." | |
566 | An unrecognized operator was found. | |
567 | The legal operators are `!=', `=', `<', and `>'. | |
568 | -914 | |
569 | "non-numerical value on line ..." | |
570 | On the indicated line an attempt was made to compare | |
571 | a string which contains non-numeric characters with another | |
572 | string using the `<' or `>' operator. | |
573 | -915 | |
574 | "err statement on line ..." | |
575 | The user has put an `err' statement on the given line. | |
576 | -917 | |
577 | "syntax on line ..." | |
578 | The equal sign has been left out of an `asg' statement, | |
579 | or the right side of an `asg' statement is missing. | |
580 | -918 | |
581 | "syntax on line ..." | |
582 | The syntax for the `if' statement on | |
583 | the indicated line is incorrect. | |
584 | An `&' or an `|' occurred in the wrong | |
585 | place, or were not found when they were expected. | |
586 | -919 | |
587 | "syntax on line ..." | |
588 | There is something strange about the indicated line. | |
589 | -920 | |
590 | "`...' never assigned a value" | |
591 | The given keyword name was never used in an assignment statement. | |
592 | This is only a warning. | |
593 | -916 | |
594 | "out of space [line ...]" | |
595 | The indicated line requires too many replacements. | |
596 | Currently, only 32 replacements per line are allowed. | |
597 | -e1 | |
598 | "no space!" | |
599 | The file system you are writing to is out of space. | |
600 | Very serious!! Contact someone in the UNIX Support Group immediately! | |
601 | If you desire to save your latest changes you must, before leaving | |
602 | the editor, do a w command to /tmp/some-unique-file-name | |
603 | If you can remove any files please do so. | |
604 | If you were writing to a non-existent file, a truncated | |
605 | new file has been created. The approximate number of | |
606 | characters written is printed. If useless, remove it. | |
607 | -e2 | |
608 | "no space?" | |
609 | <> blocks left | |
610 | The file system you are writing to may not have | |
611 | enough space to write out this multiple linked file. | |
612 | Very serious!! Contact someone in the UNIX Support Group immediately! | |
613 | If you still desire to write, do another 'w' command. | |
614 | If there is not enough space, your file will be truncated. | |
615 | Therefore, use caution. It may be smart to save your | |
616 | file first by doing a 'w' command to /tmp/some-unique-file-name. | |
617 | If you can remove any files please do so. | |
618 | -e3 | |
619 | ustat: | |
620 | can't chown: | |
621 | System problem. CHOWN or USTAT failed in ED(I). Contact someone | |
622 | in UNIX Support Group immediately. | |
623 | -e4 | |
624 | can't link: | |
625 | Can not remake file name. Your file exists in the directory you | |
626 | were writing to as a funny name. | |
627 | Funny name has the first letter of your file name followed by five numbers. | |
628 | ls -lt on that directory will show it. | |
629 | -570 | |
630 | "UNIX System <> is not configured for <> RJE [to <>]." | |
631 | Send has decided, from the first card of your jobstream, | |
632 | whether you want IBM or UNIVAC RJE. In addition, you may | |
633 | or may not have specified a particular host (158,168,1110). | |
634 | According to the configuration table, /usr/rje/lines, no | |
635 | such connection is provided from this system (/usr/rje/sys). | |
636 | -571 | |
637 | "Aborted." | |
638 | The execution of send/gath has been terminated prematurely. | |
639 | A signal may have been received, a write error may have | |
640 | occurred, the process may have exceeded its core limit, | |
641 | or standard input may have been read too far. | |
642 | -572 | |
643 | "Errors detected. Send anyway?" | |
644 | This question demands an answer (a string of characters | |
645 | terminated by a newline). Anything beginning "y" or "Y" is | |
646 | affirmative and causes the suspect jobstream to be submitted. | |
647 | Otherwise the jobstream is discarded. | |
648 | -573 | |
649 | "Cannot execute queuer." | |
650 | Send has located what it thinks is the proper RJE subsystem | |
651 | for your job but cannot execute the associated queueing program. | |
652 | Please bring this fact to the attention of PWB operations. | |
653 | -574 | |
654 | "Core exceeded." | |
655 | The program has been unable to allocate more storage for | |
656 | keyword definitions. Reduce the number of keywords or | |
657 | the depth of nesting of input sources (both on a global | |
658 | basis). | |
659 | -575 | |
660 | "Cannot create temporary <>." | |
661 | Send writes the collected jobstream into a temporary | |
662 | file created in the "pool" subdirectory of the appropriate | |
663 | RJE subsystem. The pool directory may have been made | |
664 | unwritable to prevent people from adding to a backlog | |
665 | of queued jobs. | |
666 | -576 | |
667 | "Write error - {file too large|no space left|number <>}." | |
668 | Send/gath will abort if it encounters a write error. | |
669 | The first two errors are distinguished, because you | |
670 | may be able to do something about them. Either segment | |
671 | your file into smaller pieces or clean up on disk blocks. | |
672 | Remaining errors are reported by number, as per intro(II). | |
673 | -577 | |
674 | "Hang-up." | |
675 | A hang-up signal has been received (loss of carrier from tty). | |
676 | -578 | |
677 | "Interrupt." | |
678 | An interrupt signal has been received (BREAK or DEL from tty). | |
679 | -579 | |
680 | "Quit signal." | |
681 | A quit signal has been received (FS from tty). | |
682 | -580 | |
683 | "Signal #<>." | |
684 | The process has received an unusual signal, which may indicate | |
685 | hardware problems. The number of the signal is reported. | |
686 | -581 | |
687 | "Line <> of <>, cannot open source <>." | |
688 | The specified input source cannot be opened. If the | |
689 | source is an ordinary file argument, examine the name | |
690 | (which is repeated) for possible typographical errors. | |
691 | Extraneous spaces or tabs are not allowed. If the source | |
692 | is cited on a control line, the -c flag may help. | |
693 | -582 | |
694 | "Line <> of <>, format spec rejected." | |
695 | The line containing the format spec is reproduced | |
696 | following the diagnostic. Either it does not conform | |
697 | to the syntax of fspec(PWB V), or it specifies | |
698 | unreasonable parameters, such as too many tabs or | |
699 | excessive s and m values. | |
700 | -583 | |
701 | "Line <> of <>, bad control line ignored." | |
702 | The bad control line is reproduced following the | |
703 | diagnostic. It may be too long. In -s mode, it may | |
704 | contain non-graphics or undefined tabs. | |
705 | -584 | |
706 | "Line <> of <>, non-graphic deleted." | |
707 | The transformed line is reproduced following the | |
708 | diagnostic. The non-printing ASCII characters whose | |
709 | octal codes are 000-010,013-037,177 are excised, | |
710 | except when they occur within keywords or keyword | |
711 | replacements. | |
712 | -585 | |
713 | "Line <> of <>, undefined tab deleted." | |
714 | The transformed line is reproduced following the | |
715 | diagnostic. Tabs beyond the last position at which | |
716 | they are set by the format spec are excised. See | |
717 | fspec(PWB V) to learn how to specify tab stops. | |
718 | -586 | |
719 | "Line <> of <>, cannot reverse chdir." | |
720 | This diagnostic occurs at the end of included | |
721 | sources which have caused a change of current | |
722 | directory by citing an argument of the form | |
723 | "!chdir <>". It indicates that the current | |
724 | directory cannot be reset to its previous value. | |
725 | -587 | |
726 | "Line <> of <>, cannot run shell (<>)." | |
727 | The shell cannot be run on a series of $ arguments | |
728 | because a syscall (create, pipe or fork) has failed. | |
729 | The file which was to be shelled is reproduced | |
730 | following the diagnostic. This probably indicates | |
731 | a scarcity of system resources. | |
732 | -588 | |
733 | "Line <> of <>, default spec rejected." | |
734 | The rejected format spec is reproduced following | |
735 | the diagnostic. It occurred in an argument of the | |
736 | form ":<>:". Either the spec does not conform to the | |
737 | syntax of fspec(PWB V), or it specifies unreasonable | |
738 | parameters, such as too many tabs or excessive s and m | |
739 | values. | |
740 | -589 | |
741 | "Line <> of <>, cannot chdir <>." | |
742 | It is not possible to execute the change of current | |
743 | directory specified by a "!chdir <>" argument. | |
744 | -590 | |
745 | "Line <> of <>, cannot run command (<>)." | |
746 | The shell cannot be run for a ! argument because | |
747 | a syscall (pipe or fork) has failed. The command | |
748 | which was to be executed is reproduced following | |
749 | the diagnostic. This probably indicates a scarcity | |
750 | of system resources. | |
751 | -591 | |
752 | "Line <> of <>, cannot redefine keyword." | |
753 | An attempt has been made to assign a new value to | |
754 | a keyword which is still active at some source level. | |
755 | The current definition of the keyword is reproduced | |
756 | following the diagnostic. | |
757 | -592 | |
758 | "Line <> of <>, shell exit {type|code} <>." | |
759 | The shell which was invoked to process $ or ! arguments | |
760 | has terminated abnormally (type!=0) or has indicated | |
761 | error status upon exit (code!=0). See wait(II). | |
762 | The shell file or command which was processed is | |
763 | reproduced following the diagnostic. Since many | |
764 | standard UNIX commands (but few PWB commands) return | |
765 | an arbitrary status upon exit, you may want to follow | |
766 | them with an "exit 0", which will suppress the | |
767 | diagnostic. | |
768 | -593 | |
769 | "Line <> of <>, long line detected." | |
770 | Gath has encountered a line which violates the s | |
771 | parameter of the current format specification. | |
772 | The line is reproduced following the diagnostic. | |
773 | -594 | |
774 | "Line <> of <>, long line truncated." | |
775 | The transformed line is reproduced following the | |
776 | diagnostic. Send/gath cannot process lines longer | |
777 | than about 300 bytes. The length is further | |
778 | constrained by the s parameter of the current format | |
779 | specification. If the line is to be included in | |
780 | a jobstream, its length cannot exceed 80 bytes (IBM) | |
781 | or 132 bytes (UNIVAC). | |
782 | -595 | |
783 | "Line <> of <>, illegal card excised." | |
784 | The line which send will not allow to be included | |
785 | in a jobstream is reproduced following the diagnostic. | |
786 | Lines beginning "/*$" are excised from IBM jobs | |
787 | because they are interpreted as commands by HASP/JES2. | |
788 | The beginning of an IBM job is indicated by a line | |
789 | which begins with a "/". UNIVAC runs begin with a | |
790 | line of the form "@RUN ..." or "`run ...", etc. | |
791 | Until the beginning of a jobstream is detected, all | |
792 | lines will be flushed. | |
793 | -596 | |
794 | "Overrun on standard input." | |
795 | For the sake of efficiency, data is read from the input | |
796 | stream in blocks or 512 bytes. Data which is not used | |
797 | up by the program is returned by seeking backwards on | |
798 | file descriptor zero. Unfortunately, one cannot seek | |
799 | on pipes. The input which is being piped to send/gath | |
800 | should not include any arguments of the form "-" or | |
801 | "-:prompt". Neither should it attempt a logical | |
802 | end-of-file "~.". | |
803 | -597 | |
804 | "Cannot <> - only <> {blocks|inodes} free on file system <>." | |
805 | Before it proceeds very far, send checks that there are | |
806 | 1500 blocks and 50 inodes free on the file system of the | |
807 | destination RJE subsystem. If there are not, send aborts. | |
808 | The queuer which send invokes also checks for free space, | |
809 | but it is somewhat more lenient. If you have unneeded | |
810 | files on the full file system, please delete them. | |
811 | -598 | |
812 | "..." | |
813 | These diagnostics are issued by the queueing program | |
814 | which is invoked by send. They should only occur if | |
815 | a programming error violates the interface between | |
816 | the two programs. | |
817 | -599 | |
818 | "<>qer: <>. Try again?" | |
819 | The queuer invoked by send has run into trouble, | |
820 | perhaps temporary. Type "y" and newline to try | |
821 | again, or hit interrupt to cancel this attempt | |
822 | to send. You might contact PWB operations. | |
823 | -send | |
824 | send [-lqy] [158,168,1110] file ... | |
825 | ||
826 | Control lines ("~ file2 ...") include additional files. | |
827 | -gath | |
828 | gath [-hi] file ... | |
829 | ||
830 | Control lines include additional files ("~ file2 ...") | |
831 | or collect the output of a command ("~!command arg ..."). | |
832 | * | |
833 | * Biscus project interface error messages | |
834 | * | |
835 | -120 | |
836 | "line ... of ... - bad format" | |
837 | Report this problem to your local SCCS administrator. | |
838 | In the meantime, specify the full pathname of the SCCS file. | |
839 | If you don't know it you'll just have to wait. | |
840 | -121 | |
841 | "no sccs file for ..." | |
842 | Report this problem to your local SCCS administrator immediately! | |
843 | -err1 | |
844 | error 1 "Not owner and not super-user": | |
845 | Typically this error indicates | |
846 | an attempt to modify a file in some way forbidden | |
847 | except to its owner. | |
848 | It is also returned for attempts | |
849 | by ordinary users to do things | |
850 | allowed only to the super-user. | |
851 | -err2 | |
852 | error 2 "No such file or directory": | |
853 | This error occurs when a file name is specified | |
854 | and the file should exist but doesn't, or when one | |
855 | of the directories in a path name does not exist. | |
856 | -err3 | |
857 | error 3 "No such process": | |
858 | The process whose number was given to | |
859 | signal does not exist, or is already dead. | |
860 | -err4 | |
861 | error 4 "Interrupted system call": | |
862 | An asynchronous signal (such as interrupt or quit), | |
863 | which the user has elected to catch, | |
864 | occurred during a system call. | |
865 | If execution is resumed | |
866 | after processing the signal, | |
867 | it will appear as if the interrupted system call | |
868 | returned this error condition. | |
869 | -err5 | |
870 | error 5 "I/O error": | |
871 | Some physical I/O error occurred during a | |
872 | read or write. | |
873 | This error may in some cases occur | |
874 | on a call following the one to which it actually applies. | |
875 | -err6 | |
876 | error 6 "No such device or address": | |
877 | I/O on a special file refers to a subdevice which does not | |
878 | exist, | |
879 | or beyond the limits of the device. | |
880 | It may also occur when, for example, a tape drive | |
881 | is not dialled in or no disk pack is loaded on a drive. | |
882 | -err7 | |
883 | error 7 "Arg list too long": | |
884 | An argument list longer than 512 bytes | |
885 | (counting the null at the end of each argument) | |
886 | is presented to exec. | |
887 | -err8 | |
888 | error 8 "Exec format error": | |
889 | A request is made to execute a file | |
890 | which, although it has the appropriate permissions, | |
891 | does not start with one of the magic numbers | |
892 | 407 or 410. | |
893 | -err9 | |
894 | error 9 "Bad file number": | |
895 | Either a file descriptor refers to no | |
896 | open file, | |
897 | or a read (resp. write) request is made to | |
898 | a file which is open only for writing (resp. reading). | |
899 | -err10 | |
900 | error 10 "No children": | |
901 | Wait and the process has no | |
902 | living or unwaited-for children. | |
903 | -err11 | |
904 | error 11 "No more processes": | |
905 | In a fork, | |
906 | the system's process table is full and no | |
907 | more processes can for the moment be created. | |
908 | -err12 | |
909 | error 12 "Not enough core": | |
910 | During an exec or break, | |
911 | a program asks for more core than the system is able to supply. | |
912 | This is not a temporary condition; the maximum core size | |
913 | is a system parameter. | |
914 | The error may also occur if the arrangement | |
915 | of text, data, and stack segments is such as to | |
916 | require more than the existing 8 segmentation registers. | |
917 | -err13 | |
918 | error 13 "Permission denied": | |
919 | An attempt was made to access a file in a way forbidden | |
920 | by the protection system. | |
921 | -err15 | |
922 | error 15 "Block device required": | |
923 | A plain file was mentioned where a block device was required, | |
924 | e.g. in mount. | |
925 | -err16 | |
926 | error 16 "Mount device busy": | |
927 | An attempt to mount a device that was already mounted or | |
928 | an attempt was made to dismount a device | |
929 | on which there is an open file or some process's current | |
930 | directory. | |
931 | -err17 | |
932 | error 17 "File exists": | |
933 | An existing file was mentioned in an inappropriate context, | |
934 | e.g. link. | |
935 | -err18 | |
936 | error 18 "Cross-device link": | |
937 | A link to a file on another device | |
938 | was attempted. | |
939 | -err19 | |
940 | error 19 "No such device": | |
941 | An attempt was made to apply an inappropriate | |
942 | system call to a device; | |
943 | e.g. read a write-only device. | |
944 | -err20 | |
945 | error 20 "Not a directory": | |
946 | A non-directory was specified where a directory | |
947 | is required, | |
948 | for example in a path name or | |
949 | as an argument to chdir. | |
950 | -err21 | |
951 | error 21 "Is a directory": | |
952 | An attempt to write on a directory. | |
953 | -err22 | |
954 | error 22 "Invalid argument": | |
955 | Some invalid argument: | |
956 | currently, dismounting a non-mounted | |
957 | device, | |
958 | mentioning an unknown signal in signal, | |
959 | and giving an unknown request in | |
960 | stty to the TIU special file. | |
961 | -err23 | |
962 | error 23 "File table overflow": | |
963 | The system's table of open files is full, | |
964 | and temporarily no more opens | |
965 | can be accepted. | |
966 | -err24 | |
967 | error 24 "Too many open files": | |
968 | Only 15 files can be open per process. | |
969 | -err25 | |
970 | error 25 "Not a typewriter": | |
971 | The file mentioned in stty or gtty | |
972 | is not a typewriter or one of the other | |
973 | devices to which these calls apply. | |
974 | -err26 | |
975 | error 26 "Text file busy": | |
976 | An attempt to execute a pure-procedure | |
977 | program which is currently open for writing | |
978 | (or reading!). | |
979 | Also an attempt to open for writing a pure-procedure | |
980 | program that is being executed. | |
981 | -err27 | |
982 | error 27 "File too large": | |
983 | An attempt to make a file larger than the maximum of 32768 blocks. | |
984 | -err28 | |
985 | error 28 "No space left on device": | |
986 | During a write | |
987 | to an ordinary file, | |
988 | there is no free space left on the device. | |
989 | -err29 | |
990 | error 29 "Seek on pipe": | |
991 | A seek | |
992 | was issued to a pipe. | |
993 | This error should also be issued for | |
994 | other non-seekable devices. | |
995 | -err30 | |
996 | error 30 "Read-only file system": | |
997 | An attempt to modify a file or directory | |
998 | was made | |
999 | on a device mounted read-only. | |
1000 | -err31 | |
1001 | error 31 "Too many links": | |
1002 | An attempt to make more than 127 links to a file. | |
1003 | -err32 | |
1004 | error 32 "Write on broken pipe": | |
1005 | A write on a pipe for which there is no process | |
1006 | to read the data. | |
1007 | This condition normally generates a signal; | |
1008 | the error is returned if the signal is ignored. |