![[BACK]](/cvsweb/icons/back.gif){kind=icon}
Return to batch.8 CVS log ![[TXT]](/cvsweb/icons/text.gif){kind=icon}
![[DIR]](/cvsweb/icons/dir.gif){kind=icon}
Up to [Power 6/32 Unix Tahoe 4.2BSD] / cci / usr / src / usr.bin / bsc / doc|
Return to batch.8 CVS log | Up to [Power 6/32 Unix Tahoe 4.2BSD] / cci / usr / src / usr.bin / bsc / doc |
1.1 ! root 1: '\" t ! 2: .TH BATCH 8 1.9 DLBA ! 3: \" @(#)batch.8 1.9 ! 4: .SH NAME ! 5: batch \- Binary Synchronous Batch Terminal Emulation ! 6: .SH SYNOPSIS ! 7: .br ! 8: .I /etc/bscd ! 9: .br ! 10: .I /usr/bin/bscbatch ! 11: .br ! 12: .I /usr/bin/bscpr ! 13: .br ! 14: .I /usr/lib/bsc/bsclog ! 15: .br ! 16: .I /usr/lib/bsc/bsclean ! 17: .br ! 18: .I /usr/lib/bsc/bscmon ! 19: .br ! 20: .I /usr/lib/bsc/bsctrace ! 21: .br ! 22: .SH DESCRIPTION ! 23: .P ! 24: BATCH is the communal name for the collection of programs and a file ! 25: organization that allows a computer system to communicate emulating an IBM ! 26: binary synchronous batch terminal, such as the 2780 and 3780 batch ! 27: transmission terminals. ! 28: .P ! 29: The Binary Synchronous protocol, commonly called BISYNC, is a byte-oriented, ! 30: half-duplex protocol, although full-duplex communications facilities ! 31: are sometimes used in order to reduce the time required to turn the ! 32: transmission direction around. A set of control characters are used ! 33: to provide framing and data transparency; data containing imbedded ! 34: control characters may be transmitted in a "transparent" mode to ! 35: avoid conflicts with the protocol control characters. ! 36: Communications may be point-to-point, in which case a contention ! 37: method is used to control the line; communications may also be multi-point, ! 38: in which case one node is designated the controlling node and polls ! 39: and/or selects the other nodes in order to control communications. ! 40: .P ! 41: In the BATCH system, the administrator designates a collection of ! 42: one or more hosts to which the computer connects emulating an ! 43: IBM batch terminal. For each of these hosts, the administrator provides ! 44: a set of parameters pertaining to that host connection and the specific ! 45: terminal parameters for emulation. ! 46: .P ! 47: A user may submit files to be sent to a particular host by means ! 48: of the ! 49: .I bscbatch ! 50: command. ! 51: Parameters to this command allow for the specification of ! 52: host, mail to be sent regarding transmission, and file to be sent. ! 53: The user may force the file to be sent in transparent mode, but normally ! 54: the file will be scanned at time of transmission to see if it contains ! 55: any control characters which force the file to be sent in transparent ! 56: mode. Normally the file will be sent as it appears at time of transmission; ! 57: the user may force a copy to be made of the file at time of submission ! 58: instead, so that the original file may be removed or be changed without ! 59: affecting the data to be transmitted. ! 60: .P ! 61: There is no easy way for the BATCH programs to know what to name ! 62: or where to put file received from the host computer. However, a ! 63: particular installation may be able to examine the received data ! 64: files and determine the appropriate owner and file name. For this ! 65: purpose, an installation-written subroutine may be linked with one ! 66: of the BATCH programs; this subroutine will be called to identify ! 67: and provide an appropriate name for received files. A standard subroutine ! 68: is provided which will result in all files being placed in a common ! 69: spool directory. ! 70: .P ! 71: An audit trail can optionally be kept which records all BATCH ! 72: activity. The audit trail logs host, user, and time for various messages ! 73: about connection and disconnection, sending and receiving files, ! 74: various statistics and all errors, temporary or permanent. ! 75: Once started, the audit trail file grows indefinitely; the administrator ! 76: is responsible for trimming it back when necessary. ! 77: .P ! 78: The BATCH facility can run completely unattended if the communications ! 79: interface is via a leased (dedicated) line, or if all communications ! 80: are to operate in automatic answer mode, i.e., the computer system answers ! 81: calls from the remote host. If communications are via dial-up (switched) ! 82: connections, either an operator is required to do the dialing, or ! 83: there must be an automatic calling unit connected with the synchronous ! 84: modem. ! 85: .P ! 86: The BATCH utilities do not provide for automatic calling units. However, ! 87: an installation-written routine can be invoked immediately before ! 88: host connection and just following host termination ! 89: to provide for such things as operator instructions ! 90: or automatic dialing. ! 91: .P ! 92: The following diagram shows the programs and file organization used ! 93: at various levels. ! 94: .P ! 95: .TS ! 96: box,center; ! 97: c|c|c|c|c. ! 98: DESIRED USER FILE FRAME LINK ! 99: FUNCTION LEVEL LEVEL LEVEL LEVEL ! 100: _ ! 101: Send file bscbatch <dir>/C* ! 102: [<dir>/D*] ! 103: _ _ _ ! 104: Receive file bscpr, <dir>/PR* bscd /dev/bsc* ! 105: bscbatch -q <dir>/PU* (daemon) ! 106: _ _ _ ! 107: Check status bsclog <dir>/AUDIT ! 108: _ ! 109: Monitor bscmon, /dev/bsctr* ! 110: Activity bsctrace ! 111: .TE ! 112: .P ! 113: The designator ! 114: .I <lib> ! 115: refers to directory name "/usr/lib/bscbatch"; ! 116: in this directory are parameter files for each ! 117: possible host connection (<hostname>). ! 118: .P ! 119: The ! 120: .I <dir> ! 121: designator refers to the host's spool directory. ! 122: This name is a combination of ! 123: the directory prefix "/usr/spool/bscbatch/" ! 124: followed by the <hostname> directory into which all active files ! 125: pertaining to this host are placed. ! 126: .P ! 127: The ! 128: .I bscbatch ! 129: program is used to add files to the ! 130: transmit queue; one C* file is created for each new file to be sent. ! 131: The D* file is created if it is necessary to make a copy of the file. ! 132: Received files will be assigned a base file name of PR* or PU*, depending ! 133: on whether they were directed to the PRinter or PUnch. An installation ! 134: may choose to place the received files elsewhere; see the description ! 135: of the user exit facility in the installation procedures to follow. ! 136: .P ! 137: The ! 138: .I bscd ! 139: daemon is normally started via an entry in ! 140: .I /usr/lib/crontab, ! 141: which allows the daemon to ! 142: search for work as often as the system administrator desires. ! 143: (Telephone line costs may dictate running the daemon during hours ! 144: of lower charges, or there may be a regular overnight transmission.) ! 145: .P ! 146: The daemon searches for work ! 147: by examining each host's spool directory for a C* file. If there ! 148: is such a file, it will attempt to connect to that host. ! 149: An installation-provided exit routine can be invoked by ! 150: .I bscd ! 151: at this moment to allow ! 152: use of an auto-dialer or any necessary operator communication to ! 153: make the connection. ! 154: Once the connection is made, files received are handled as above, ! 155: and the C* files provide the names of files to be sent. ! 156: An empty C* file ("Connect", for example) may be used to force ! 157: .I bscd ! 158: to make a connection even if there are no ! 159: files to be sent. (One may want to place an entry in /usr/lib/crontab ! 160: which will create such a file for certain hosts.) ! 161: An audit file, as discussed above, if it exists, will have appended ! 162: to it the audit information. ! 163: .P ! 164: After an installation-specified period of inactivity with respect ! 165: to a host, the daemon will terminate the connection to that host. ! 166: The installation may provide an exit routine to be invoked at this ! 167: time (immediately after termination of connection) to take care of ! 168: any necessary cleanup. ! 169: .P ! 170: The daemon may also be terminated by sending the terminate signal, ! 171: .I ! 172: kill -15, ! 173: .R ! 174: to the daemon's process. The daemon will make an appropriate entry in ! 175: the audit file (if one exists), remove the lock files, and call the ! 176: cleanup installation exit. ! 177: .P ! 178: A trace facility can be invoked which records communications events ! 179: and the time they occur, ! 180: and optionally records actual data, transmitted and received. The ! 181: trace information can be placed into a file for immediate or later ! 182: analysis by another program. ! 183: The general intent is to provide enough information for communications ! 184: debugging that a data link analyzer is not necessary. ! 185: .P ! 186: The ! 187: .I bsctrace ! 188: program interprets trace information provided to ! 189: .I bscmon ! 190: by /dev/bsc*tr. A state diagram provided with the ! 191: .I bscmon(8) ! 192: document shows the communication ! 193: states and flow which makes up the BISYNC protocol; state transition ! 194: information is provided to ! 195: .I bscmon, ! 196: which records ! 197: it and optionally the transmitted and received data, in a file. ! 198: .I Bsctrace ! 199: is used to display this data in a readable format. ! 200: .P ! 201: .SH ADMINISTRATION ! 202: .SS Installation. ! 203: .P ! 204: The BSC BATCH tape is used in the installation process for the Batch ! 205: facility. To install the BATCH facility, do the following: ! 206: .RS ! 207: .IP 1. ! 208: Make a directory to contain the installation files, e.g., ! 209: /usr/sys/src/bsc, then change to that directory. Use ! 210: .I "tar xov0" ! 211: to copy the files from tape to the directory. ! 212: The following files should be extracted: ! 213: .TS ! 214: center; ! 215: l l l l. ! 216: 2780 3780 ! 217: bscbatch bscbinst bscd bscd.x ! 218: bscinst bscio.h bsclean bsclog ! 219: bscmon bscpr bsctr.h bsctrace ! 220: install.c libbsc.a trace.text maninst ! 221: .TE ! 222: .IP 2. ! 223: Prepare installation exit subroutines, if necessary. ! 224: File install.c contains four default ! 225: subroutines for the installation exits, as described below. They ! 226: may be modified or completely replaced, but must exist. ! 227: .IP ! 228: .I "connect (host, dev)" ! 229: .br ! 230: .I "char *host, *dev;" ! 231: .br ! 232: is called when ! 233: .I bscd ! 234: is ready to make a connection to ! 235: .I host ! 236: via device ! 237: .I devname. ! 238: The connection will be made only if ! 239: .I connect ! 240: returns a zero value; if a non-zero value is returned, a note will be placed ! 241: in the AUDIT file (if one exists), and the daemon will skip processing ! 242: for this host. ! 243: .IP ! 244: This routine may perform auto-dialing or operator communication ! 245: necessary for connection. The default (supplied) routine merely ! 246: returns a zero value immediately. ! 247: .IP ! 248: .I "disconnect (host, devname)" ! 249: .br ! 250: .I "char *host, *devname;" ! 251: .br ! 252: is called when ! 253: .I bscd ! 254: has just disconnected from ! 255: the given host and device. This routine may perform any cleanup necessary ! 256: at this time. The default (supplied) routine merely returns. ! 257: .IP ! 258: .I "notefile (uname, sfile, mailflag)" ! 259: .br ! 260: .I "char *uname, *sfile;" ! 261: .br ! 262: .I "int mailflag;" ! 263: .br ! 264: is called when file ! 265: .I filename ! 266: has been sent successfully to ! 267: .I host ! 268: on behalf of ! 269: .I username. ! 270: This routine is responsible for sending mail if requested, and for ! 271: making any notes necessary for association of files received to files ! 272: sent, such as noting a file submit number. ! 273: The default (supplied) version of ! 274: this routine merely sends mail to the user, if it was requested. ! 275: .IP ! 276: .I "char *asgnfile (host, file)" ! 277: .br ! 278: .I "char *host, *file;" ! 279: .br ! 280: is called to change the name assigned to a received file ! 281: .I (fname) ! 282: to a more meaningful name, if possible. It may be possible, for example, to ! 283: associate the received file with a particular user by examining the ! 284: file and any data noted by the ! 285: .I notefile ! 286: routine. ! 287: The value returned is the new name assigned (if not reassigned, return ! 288: the current name). ! 289: .I Fname ! 290: is a file in the current directory. ! 291: .IP ! 292: Suggested procedure: link ! 293: .I fname ! 294: to ./<username>/ ! 295: .I fname; ! 296: unlink ! 297: .I fname; ! 298: optionally send mail to <username>. ! 299: .IP ! 300: The default (supplied) routine merely returns the file name given ! 301: to it. ! 302: .IP ! 303: .I "audit (message)" ! 304: .br ! 305: .I "char *message" ! 306: .br ! 307: is a routine which may be called by any of the installation-supplied ! 308: routines which need to place information into the AUDIT file. The ! 309: single parameter will be written into the AUDIT file along with a ! 310: time stamp and the current host's name. ! 311: .IP 3. ! 312: Install all files. "Bscbinst" is a shell command file which will ! 313: link the bscd command object file with install.c and ! 314: install all batch commands and files into the appropriate directories. ! 315: Shell command file "bscinst" will install the remaining commands, ! 316: files, and system library. ! 317: Shell command file "maninst" will install the programmer manual files ! 318: in /usr/man. ! 319: .IP 4. ! 320: Modify system generation files, generate system. ! 321: .RS ! 322: .IP - ! 323: Make entry in /usr/sys/cf/dfile for bsc and bsct ! 324: .IP - ! 325: Add dependencies on libbsc to makefile ! 326: .IP - ! 327: Use "config" to build "low.s" and "conf.c" ! 328: .IP - ! 329: Generate system ! 330: .RE ! 331: .RE ! 332: .SS "Set up host configurations." ! 333: .P ! 334: For each separate host, a file must be created in /usr/lib/bscbatch ! 335: which supplies the control and administrative information used by ! 336: the BATCH utilities. The file may be created via the text editor. ! 337: Sample configurations for emulating a 2780 and a 3780 terminal ! 338: (respectively) appear in files 2780 and 3780, extracted in step 1 above. ! 339: Any of the following parameters may be specified in the configuration ! 340: file, one parameter per line. The default will be taken for any unspecified ! 341: parameters. ! 342: .TP ! 343: BLKSIZE=nnn. ! 344: .I Nnn ! 345: must be at least 32 and no more than 512. ! 346: This parameter indicates the maximum number of characters which may ! 347: be placed into each transmission block, and the space to be reserved ! 348: for each receive block. ! 349: Default: 512. ! 350: .TP ! 351: CODE=ASCII\||\|EBCDIC. ! 352: This specifies the transmission code ! 353: to be used in the protocol, and what translation is to be performed ! 354: on transmitted or received data. ! 355: Default: EBCDIC. ! 356: .TP ! 357: COMPRESS=YES\||\|NO. ! 358: YES should be specified if 3780-style space compression and expansion ! 359: should be performed on non-transparent data. Compression is never ! 360: performed on transparent data. ! 361: Default: YES. ! 362: .TP ! 363: DEVICE=/dev/bsc*. ! 364: The device to be used for BISYNC operations must be specified here. ! 365: Note this device must be the one corresponding to the ! 366: .I bsc.o ! 367: driver installed in step 5 above. ! 368: Default: /dev/bsc. ! 369: .TP ! 370: DUPLEX=HALF\||\|FULL. ! 371: Specify FULL for a full-duplex modem, HALF for a half-duplex modem. ! 372: Default: HALF. ! 373: .TP ! 374: IDCHECK=hostid. ! 375: In the BISYNC protocol, allowances are made for erroneous connections ! 376: in a switched network. The two nodes are allowed to exchange identification ! 377: in the form of a short sequence of characters added to the initial ! 378: handshake. If it is desired that the host's identification be checked, ! 379: and that communications not be allowed to occur unless the identification ! 380: matches that given here, specify this parameter. The host identification ! 381: may consist of up to twenty alphanumeric characters. ! 382: Default: ! 383: Do not check host identification. ! 384: .TP ! 385: MAIL=userid. ! 386: .I Bscd ! 387: will send mail to the system administrator (name given by ! 388: .I userid) ! 389: for any significant problems requiring attention. These include incorrect ! 390: parameters in this file, truncated receive files, minimum space limit ! 391: problems, inability to connect to host, and host id check failures. ! 392: Default: ! 393: Messages sent to /dev/console. ! 394: .TP ! 395: MAXFSIZE=nnnnnn. ! 396: .I Nnnnnn ! 397: is the maximum number ! 398: of bytes a received file can have without forced truncation; a value ! 399: of zero indicates no maximum. This is an administrative parameter ! 400: to prohibit extremely long files from taking up so much disk space ! 401: that the operating system is no longer able to function properly. ! 402: Maximum value for ! 403: .I nnnnnn: ! 404: 1000000000. Default: 0 (No maximum). ! 405: .TP ! 406: MINSPACE=devname,nnnnnn. ! 407: .I Nnnnnn ! 408: is the minimum number of blocks which device ! 409: .I devname ! 410: must have for ! 411: .I bscd ! 412: to accept data from a host, or for ! 413: .I "bscbatch -c" ! 414: to allow copying of a file for transmission. ! 415: .I bscbatch ! 416: will give a warning to a user trying ! 417: to send a file if at least 150% of the minimum space required is ! 418: not available at that time. ! 419: .I bscd ! 420: will make an audit trail entry and send mail ! 421: to the administrator (optionally, see MAIL above) when the minimum ! 422: space is not available. Maximum value for ! 423: .I nnnnnn: ! 424: 1000000000. Default: No minimum space requirement. ! 425: .TP ! 426: MPTADDR=aa. ! 427: .I Aa ! 428: is the address of the emulated terminal if this is a multipoint network. ! 429: If this is point-to-point, this parameter must not be specified. ! 430: .I Aa ! 431: consists of two printable characters, the first being the poll address, ! 432: the second the select address. ! 433: Default: ! 434: Point-to-point mode. ! 435: .TP ! 436: NBID=nn. ! 437: .I Nn ! 438: is the number of initial handshakes, ! 439: or "line bids" which will be made when there is no host response. ! 440: In a multipoint or other leased line arrangement, this value should ! 441: be zero, which means retry forever. ! 442: Maximum value for ! 443: .I nn: ! 444: 127. Minimum value\/Default: 0 (no limit). ! 445: .TP ! 446: NNAK=nn. ! 447: .I Nn ! 448: specifies the number of NAK's (negative ! 449: acknowledgement to text block due to CRC error) that the driver should ! 450: give before terminating communications via sending EOT instead of ! 451: NAK. This parameter prevents endless transmissions for cases where ! 452: the text block was actually built incorrectly. ! 453: Maximum value for ! 454: .I nn: ! 455: 127. Minimum value: 0. Default: 16. ! 456: .TP ! 457: NRETRY=nn. ! 458: .I Nn ! 459: is the number of retries which will ! 460: be made during transmission where a text block has been NAK'd (received ! 461: with incorrect CRC, or check characters) or where a text block has ! 462: had no response from the host (timeout). ! 463: Maximum value for ! 464: .I nn: ! 465: 127. Minimum value: 0. Default: 15. ! 466: .TP ! 467: NTTD=nn. ! 468: .I Nn ! 469: is the number of TTD's (temporary ! 470: text delays from host) that the driver should receive and NAK before ! 471: terminating the receive operation via sending EOT. This parameter ! 472: may be used to prevent prolonged delays from tying up a communications ! 473: line. A value of zero will force the driver to always NAK a TTD. ! 474: Maximum value for ! 475: .I nn: ! 476: 127. Minimum value: 0. Default: 150. ! 477: .TP ! 478: NWACK=nn. ! 479: .I Nn ! 480: is the maximum number of WACK's (wait ! 481: acknowledgements) the driver will accept while attempting to transmit ! 482: before terminating transmission via sending EOT. This parameter may ! 483: be used to prevent prolonged delays while the host computer is unable ! 484: to accept the next data block due to delays. ! 485: A value of zero will force the driver to always accept a WACK. ! 486: Maximum value for ! 487: .I nn: ! 488: 127. Minimum value: 0. Default: 150. ! 489: .TP ! 490: RECBLK=nn. ! 491: .I Nn ! 492: is the maximum number of records ! 493: which can be placed into one block for non-transparent transmission. ! 494: For transparent transmission, only one record will be placed in a ! 495: block. ! 496: Maximum value for ! 497: .I nn: ! 498: 32767. Default: 507 or BLKSIZE-5, whichever is less. ! 499: .TP ! 500: RECSEP=EM\||\|IRS. ! 501: Records will be separated within a block by either an IRS (typical ! 502: for 3780 terminal) or EM (typical for 2780 terminal). ! 503: Default: IRS. ! 504: .TP ! 505: RECSIZE=nnn. ! 506: .I Nnn ! 507: gives the maximum number of characters ! 508: per record. ! 509: .I Bscd ! 510: will complain if it has to truncate any records due to length restrictions. ! 511: Default: 507 or BLKSIZE-5, whichever is less. ! 512: .TP ! 513: RVIMODE=IGNORE\||\|ABORT. ! 514: When an RVI (reverse interrupt) is received during transmission, ! 515: .I bscd ! 516: can ignore the interrupt and continue transmitting, ! 517: or it can abort the transmission. ! 518: Default: ABORT. ! 519: .TP ! 520: SIGNON=filename. ! 521: Upon establishing communications with a host, ! 522: .I bscd ! 523: can send a standard file (containing, for example, a "signon" record). ! 524: .I Bscd's ! 525: current directory at time of establishing ! 526: initial communications will be the host's SPOOL directory. ! 527: If for any reason there is an error in sending this file (for example, ! 528: contention), the error will be logged and the remaining (if any) files ! 529: sent normally. ! 530: Communications for this host will not be aborted due to any error ! 531: having to do with the signon file. ! 532: Default: No signon file. ! 533: .TP ! 534: SIGNOFF=filename. ! 535: When ready to terminate communications with the host, ! 536: .I bscd ! 537: can send a standard file (containing, for example, a "signoff" ! 538: record). ! 539: If for any reason there is an error in sending this file (for example, ! 540: loss of DSR due to other host having disconnected the line), the error ! 541: will be logged and communications for this host terminated. ! 542: Default: No signoff file. ! 543: .TP ! 544: STATION=PRIMARY\||\|SECONDARY. ! 545: In point-to-point mode, it is possible that there will be ! 546: contention for control of the communications line (if both host and ! 547: this computer wish to transmit at the same time). To eliminate bid ! 548: collisions, one end of the line is designated a primary station, ! 549: the other a secondary. The primary station bids once per second; ! 550: the secondary bids once every three seconds. ! 551: This parameter is not used in a multipoint mode. ! 552: Default: PRIMARY. ! 553: .TP ! 554: TERMID=ident. ! 555: If this parameter is specified, ! 556: .I ident ! 557: will be ! 558: provided to the host as this (emulated batch) terminal's identification ! 559: (see ! 560: .I IDCHECK, ! 561: above). ! 562: .I Ident ! 563: may be a string of up to twenty alphanumeric characters. ! 564: Default: No identification. ! 565: .TP ! 566: TIMEOUT=nnnn. ! 567: If there are no files to be sent to the current host, and there is ! 568: no activity from the host (no files being received from the host) ! 569: for ! 570: .I nnnn ! 571: seconds, ! 572: .I bscd ! 573: will disconnect. ! 574: .I nnnn ! 575: must be greater than 0 and not more than 3000. ! 576: Default: 60. ! 577: .TP ! 578: TRANSPARENT=YES\||\|NO. ! 579: If it is not ! 580: permissable to send transparent files, this parameter should be set to ! 581: .I NO. ! 582: Default: YES. ! 583: .TP ! 584: UNITSEP = YES\||\|NO. ! 585: In 2780 mode, a "unit separator" (US) marks the end of a block, following EM. ! 586: If transmission is to be in 2780 mode, this parameter ! 587: should be set to ! 588: .I YES. ! 589: Default: NO. ! 590: .SS "Set up Host Spool Area." ! 591: .P ! 592: For each host, make a directory /usr/spool/bscbatch/<hostname>. ! 593: If an audit trail is to be kept on this host, create an empty file ! 594: in that directory called AUDIT. ! 595: .SS "Make /usr/lib/crontab entries." ! 596: .P ! 597: Make an entry in crontab which starts the daemon at the desired time(s). ! 598: For example, ! 599: .br ! 600: 0 * * * * /etc/bscd ! 601: .br ! 602: will cause the daemon to be started every hour, on the hour. ! 603: (See ! 604: .I cron(8)). ! 605: .SS "Regular Maintenance." ! 606: .P ! 607: Some minimal maintenance of the host spool areas is required. ! 608: The administrator's mailbox should be inspected and cleaned out regularly. ! 609: The audit trail file (/usr/spool/bscbatch/<hostname>/AUDIT) should be truncated ! 610: via the ! 611: .I bsclog ! 612: utility regularly. Most convenient ! 613: is an entry in crontab, again -- once per day, ! 614: .I "bsclog -purge=3 " ! 615: could be run to discard all but ! 616: AUDIT information for the last three days (see ! 617: .I bsclog(8)). ! 618: PR* and PU* ! 619: files should probably be removed when they are over a certain number ! 620: of days old; the ! 621: .I bsclean ! 622: utility may be used to do this in a fashion akin to that of ! 623: .I bsclog. ! 624: .SH "SEE ALSO" ! 625: .P ! 626: bscbatch(1C), bscpr(1C), bsclog(8), bsclean(8), bscmon(8). ! 627: .br ! 628: .I "Setting Up UNIX" ! 629: .br ! 630: .I "General Information - Binary Synchronous Communications," ! 631: IBM document GA27-3004. ! 632: .br ! 633: .I "Component Description: IBM 2780 Data Transmission Terminal," ! 634: IBM document GA27-3005. ! 635: .br ! 636: .I "Component Information for the IBM 3780 Data Communication Terminal," ! 637: IBM document GA27-3063. ! 638: .SH "SYSTEM REQUIREMENTS" ! 639: .SS Modems. ! 640: .P ! 641: If two identical modems (same manufacturer, same options) ! 642: are used at each end of the communications line, most any synchronous ! 643: RS-232-C interface modem will function correctly. The following modems ! 644: are definitely supported: ! 645: .br ! 646: Bell 201A3 (2000 bits per second) ! 647: Bell 201C (2400 bits per second) ! 648: Bell 208B (4800 bits per second) ! 649: Bell 209A (9600 bits per second) ! 650: .br ! 651: .SS Hardware. ! 652: .P ! 653: This software is supported when used with the following: ! 654: .br ! 655: UNIX Release 3 operating system ! 656: MODEM port jumpered for external clocking ! 657: MODEM port jumpered as Data Terminal Equipment ! 658: .br ! 659: .SH "DIAGNOSTICS" ! 660: .P ! 661: bscd <host>: can't open <confdir> configuration directory. ! 662: .IP ! 663: The configuration directory for this host couldn't be opened. ! 664: Check the modes. Processing for this host was aborted. ! 665: .P ! 666: bscd <host>: <devname> cannot be opened for communications. ! 667: .IP ! 668: The communications device <devname> for the specified ! 669: host could not be opened. Either the mode is set wrong, or some other ! 670: process has the device open. Processing for this host was aborted. ! 671: .P ! 672: bscd <host>: unrecognized keyword, line <l> in <filename>. ! 673: .IP ! 674: While reading the host configuration file <filename>, ! 675: an unrecognized keyword was found on line <l>. Probably a typographical ! 676: error. Processing for this host was aborted. ! 677: .P ! 678: bscd <host>: invalid parameter for keyword <k> in <filename>. ! 679: .IP ! 680: While reading the host configuration file <filename>, ! 681: keyword <k> was found to have an invalid parameter. Probably a typographical ! 682: error, but it is also possible that the given parameter was out of ! 683: range. Processing for this host was aborted. ! 684: .P ! 685: bscd <host>: file system <devname> has less than minimum ! 686: blocks available. Processing aborted. ! 687: .IP ! 688: The amount of free space on <devname> is below the specified ! 689: minimum amount. ! 690: .I Bscd ! 691: refuses to receive any files ! 692: from this host while this condition lasts. Processing for this host ! 693: was aborted. ! 694: Check the MINSPACE parameter ! 695: in the host configuration file and the amount of free space on the ! 696: file system. ! 697: .P ! 698: bscd <host>: Transmission of <file> aborted: Attempt to send transparent ! 699: to non-transparent host. ! 700: .IP ! 701: While sending file <file> to this host, configured for normal data ! 702: only, transparent characters were encountered. Check <file> for ! 703: control characters or typographical errors. Transmission of <file> ! 704: was aborted. ! 705: .P ! 706: bscd <host>: directory <dirname> not readable. ! 707: .IP ! 708: The spool directory for <host> can not be read. ! 709: Check the directory's mode. Processing for this host was aborted. ! 710: .P ! 711: bscd <host>: file <filename> can't be created. ! 712: .IP ! 713: While attempting to create <filename> to hold a file being ! 714: received, an error was encountered. Check the modes on the directory ! 715: and/or file. The receive operation will be aborted. ! 716: .P ! 717: bscd <host>: file <filename> can't be removed. ! 718: .IP ! 719: The C* and D* files are normally removed from the host's spool ! 720: directory once the file has been sent. ! 721: In this case, an error was encountered while trying to unlink the ! 722: named file. The file will be left there, which will mean the file ! 723: will be sent every time ! 724: .I bscd ! 725: connects to this host, usually highly undesirable. ! 726: .I Bscd ! 727: will abort processing with this host immediately. ! 728: .I Bscd ! 729: will attempt to prevent itself from being started again by leaving a lockfile ! 730: in /usr/spool/bscbatch locked after termination; unless this file ! 731: is removed by the system administrator, no further batch communication ! 732: will occur. ! 733: .P ! 734: bscd <host>: device <devname> reports modem failure. ! 735: .IP ! 736: The named device reported a transmit timeout error. The usual reason ! 737: for this is that the device did not get a transmit clock signal from ! 738: the modem. This could be due to improper modem option specification, ! 739: improper cable to the modem from the computer system, or to not having ! 740: jumpered the MODEM port for external timing. Transmission is ! 741: aborted for this host.
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.