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