home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Monster Media 1994 #1
/
monster.zip
/
monster
/
MODEM
/
BONEZ.ZIP
/
BONE$.DOC
< prev
next >
Wrap
Text File
|
1994-01-13
|
33KB
|
886 lines
*-----------------------------------------------------------------------------*
B e a r B o n e $
"The IND$FILE-Compatible External File Transfer Protocol"
Copyright (c) 1993 Computer Vectors, Inc. All rights reserved.
TECHNICAL REFERENCE MANUAL - VERSION 2.5
*-----------------------------------------------------------------------------*
Computer Vectors, Inc.
74-5599 Luhia St., Suite E-7
Kailua-Kona, Hawaii 96740
Marketing.............1-808-329-6645
Tech Support..........1-808-329-5426
Bulletin Board........1-808-329-5142
FAX...................1-808-329-6523
*-----------------------------------------------------------------------------*
INTRODUCTION
*-----------------------------------------------------------------------------*
BEAR BONE$ is an IND$FILE external protocol designed to work with most any PC-
based asynchronous communications package. It allows the user to transfer text
and binary files to and from IBM hosts that support IND$FILE.
*-----------------------------------------------------------------------------*
REQUIREMENTS
*-----------------------------------------------------------------------------*
You will need an asynchronous communications package such as PROCOMM Plus,
PROCOMM for Windows, DYNACOMM, Q-MODEM, HYPERACCESS/5, etc.. It must support
the use of external protocols OR have the ability to shell-out to DOS while
on-line. It must also emulate one of the following terminals:
VT100
ANSI
3101
FTTERM
HYDRA/PCCR
TV950 (Procomm 3270/950)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
NOTE FOR WINDOWS USERS:
Two options: BDR=<number> and BTS=ABC (explained near the end of the
"BEAR BONE$ OPTIONS" section) must be set to use BEAR BONE$ with a
"true" Windows communications product. These options deal with the way
Windows resets the communications port when opening a "DOS BOX".
Also, you should set the device contention to "never warn" under the
386 Enhanced options of the control panel.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Among others, BEAR BONE$ is compatible with the following protocol converters:
DATALYNX 3174
HYDRA II
HYDRA SNA
HYDRA 3000
IBM 3708
IBM 3174 w/AEA
IBM 7171
IBM 9370
INTERLYNX
TYMNET
...and has been tested to work with the following communications packages:
CEDER ISLAND LINK
COM-AND
CROSSTALK MK. IV
CROSSTALK FOR WINDOWS
DYNACOMM ASYNCHRONOUS FOR WINDOWS
FTTERM
HYPERACCESS/5
HYPERACCESS FOR WINDOWS
MICROPHONE PRO FOR WINDOWS
MIRROR III
MIRROR FOR WINDOWS
PERELINE
PROCOMM PLUS
PROCOMM PLUS FOR WINDOWS
PROCOMM PLUS NETWORK VERSION
QMODEM
RCOM-2/PC
RELAY
REXXTERM
SimPC
UNICOM
TELIX
Please call 1-808-329-5426 if you have a protocol converter that is not on
the list, or if you have any other compatibility questions.
*-----------------------------------------------------------------------------*
EXTERNAL PROTOCOL SETUP FOR PROCOMM-PLUS v2.01
*-----------------------------------------------------------------------------*
From PROCOMM's terminal mode, hit ALT-S to bring up the setup menu, then select
PROTOCOL OPTIONS. Next, select EXTERNAL PROTOCOL OPTIONS. Here is a sample
setup for BEAR BONE$ using a parameter file named VM.PRM:
EXTERNAL PROTOCOL 1
A- Name ................ BONE$
B- Type ................ PROGRAM
C- Upload command ...... BONE$ VM PUT
H- Download command .... BONE$ VM GET
Once set up, BEAR BONE$ will appear on PROCOMM's upload and download protocol
selection boxes. After you choose BEAR BONE$ as the protocol type, you will
be prompted to "Enter parameters:". You only need to enter the PC filename
followed by the mainframe filename and mainframe options, like this:
C:\AUTOEXEC.BAT JUNK TEST A (ASCII CRLF
*-----------------------------------------------------------------------------*
EXTERNAL PROTOCOL SETUP FOR PROCOMM-PLUS FOR WINDOWS
*-----------------------------------------------------------------------------*
We have included a script file for use with PROCOMM-PLUS for WINDOWS. We
recommend that you bind a meta-key to the script file ("BONE$.WAS") to make
it easier to use.
The script simply pops up a dialog box and asks you to "Enter parameters:".
Unlike PROCOMM-PLUS for DOS, you must type in "PUT" or "GET" before entering
the PC filename and mainframe filename:
PUT C:\AUTOEXEC.BAT JUNK TEST A (ASCII CRLF
*-----------------------------------------------------------------------------*
EXTERNAL PROTOCOL SETUP FOR QMODEM v4.31
*-----------------------------------------------------------------------------*
Type ALT-N from QMODEM's terminal mode. Next, select the PROTOCOLS pull-down
menu. Here is a sample setup:
Select Character $
Protocol BONE$
Upload BAT BONE$ VM PUT
Download BAT BONE$ VM GET
Filename Prompt Y
Once set up, BEAR BONE$ will appear on QMODEM's upload and download protocol
selection boxes. After you choose BEAR BONE$ as the protocol type, you will
be prompted with "Upload file allocation:". You only need to enter the PC
filename followed by the mainframe filename and mainframe options, like this:
C:\AUTOEXEC.BAT JUNK TEST A (ASCII CRLF
*-----------------------------------------------------------------------------*
WHAT'S ON THE DISK
*-----------------------------------------------------------------------------*
ORDER .FRM BEAR BONE$ order form
BONE$ .EXE The BEAR BONE$ executable program
BONE$ .PRM Default parameter file
BONE$ .DOC This document
BONE$ .WAS Script file for PROCOMM Plus for Windows
RECEIVE .BAT Sample batch file for downloading
SEND .BAT Sample batch file for uploading
GENERIC .111 Sample parameter file for a generic protocol converter using
VT100 emulation - Modify this parameter file to suit your
protocol converter
3174-31 .111 3174 using 3101 emulation
3174-FT .111 3174 using FTTERM emulation
3174-TV .111 3174 using TV950 emulation
3174-VT .111 3174 using VT100 emulation
3270-950.111 Generic protocol converter using PROCOMM 3270/950 emulation -
Modify this file to suit your protocol converter
3708-31 .111 3708 using 3101 emulation
3708-31 .1 3708 using 3101 emulation and IND$FILE version 1
3708-FT .111 3708 using FTTERM emulation
3708-FT .1 3708 using FTTERM emulation and IND$FILE version 1
3708-TV .111 3708 using TV950 emulation
3708-VT .111 3708 using VT100 emulation
7171-31 .111 7171 using 3101 emulation
7171-TV .111 7171 using TV950 emulation
7171-VT .111 7171 using VT100 emulation
HYII-HY .111 HYDRA-II using HYDRA/PCCR emulation
*-----------------------------------------------------------------------------*
DETERMINING THE IND$FILE VERSION
*-----------------------------------------------------------------------------*
Before you attempt a transfer, it is important to find out what version of
IND$FILE is running on the host. Please follow the steps below:
1) Dial or connect to the host using your terminal emulation software.
2) Log on to your account.
3) Get to the "Ready" state by issuing a "Clear-Screen" command or
<Control-C>.
4) Type "IND$FILE PTP <MF File Name>", followed by <Enter>.
(Please see the MAINFRAME OPTIONS sections for examples of valid
mainframe file names.)
5) IF VERSION 1.1.1 IS RUNNING,
the screen will clear and "Caaa" will appear in the upper left hand
corner. Press the <PF2> or <Clear> key several times to cancel the
transfer. In this case, you should specify the following options in
your parameter file (more on parameter files in the next section):
SEN=IND$FILE PTP
REC=IND$FILE GTP
6) IF VERSION 1 IS RUNNING, EITHER
... the screen will clear and the cursor will move to the bottom right
hand corner of the screen. You are running version 1 but DO NOT have
"non-display" fields available. You will either need to modify your
protocol converter's TDF (terminal definition file) or get an upgrade
to version 1.1.1 of IND$FILE.
... OR the screen will clear and you will get a "TRANS16 Incorrect
request code: file transfer canceled$" or similar message. You are
running version 1 of IND$FILE. Use the following options in your
parameter file:
SEN=IND$FILE PUT
REC=IND$FILE GET
*-----------------------------------------------------------------------------*
INVOKING BEAR BONE$
*-----------------------------------------------------------------------------*
Before invoking BEAR BONE$, be sure that you are in the "READY" state on the
host. This is normally done by hitting the <Clear> key or Control-C. If
you'd like, you can include the code for the <Clear> key in the PRE=
parameter.
Now, call up BEAR BONE$ by invoking it as an external protocol (see one of
the EXTERNAL PROTOCOL SETUP sections below), or if your communications
package doesn't have this feature, shell out to DOS and type in your command
line manually.
The format of a BEAR BONE$ command line looks like the following:
BONE$ <Param-file> PUT|GET <PC-file> <MF-file> [<MF-options>]
<Param-file> is the name of a file containing multiple lines of BEAR BONE$
options (see BEAR BONE$ OPTIONS below). Any line that does not have an
EQUAL SIGN in it is considered to be a comment line and is discarded.
Another way to comment a line out is to put a semicolon at the BEGINING of
the line. Here is a sample parameter file:
******************************************************************
*** VM IND$FILE 1.1.1 using FTTERM emulation on a 3174 w/AEA ***
******************************************************************
SEND AND RECEIVE COMMANDS
-------------------------
sen=ind$file ptp
rec=ind$file gtp
ERR-CHECK METHOD, TYPE-AHEAD BUFFER LENGTH, ETC..
-------------------------------------------------
err=auto
buf=2000
blk=700
dly=0
TERMINAL TYPE AND KEY SEQUENCES
-------------------------------
trm=ftterm
ent=^m
rht=^[c
rst=^r
try=^[r
can=^[2^m
pre=^[>^[o
pst=^[<<^[p^c
COMMUNICATION PORT OPTIONS
--------------------------
prt=1
adr=0
irq=0
Unless a path is specified for the parameter file, BEAR BONE$ will first try
and open a parameter file from the same path where the BEAR BONE$ executable
is located. If it can't find it, BEAR BONE$ will try and open it from your
current path. This means that you are able to conveniently place all your
parameter files in one directory. We suggest that you put BEAR BONE$ and
its associated parameter files in the same directory as your communications
software.
You may omit the <Param-file> if you have a file named BONE$.PRM in either
your current directory, or in the same directory as your BONE$.EXE.
Next on the command line, you need to specify either a PUT to send a file to
the host, or a GET to download a file from the host. You may abbreviate these
to P and G. Also, SEND and RECEIVE are valid and will perform the same
functions as PUT and GET.
<PC-file> is the name of the file on the PC. If you are doing a PUT, data is
read from this file and transmitted to the host. If you are doing a GET,
this file is created and host data is written to it.
<MF-file> is a proper file name, or data set name on your mainframe.
<MF-options> are file format and translation options that are available
on your mainframe IND$FILE program (see MAINFRAME OPTIONS below).
*-----------------------------------------------------------------------------*
BATCH TRANSFERS
*-----------------------------------------------------------------------------*
If you would like to do batch transfers, you may use a command line like
this:
BONE$ <Param-file> @<List-file>
Each line of the <List-file> should contain one transaction. Here's an
example:
PUT C:\AUTOEXEC JUNK TEST A
GET JUNK. JUNK TEST A
PUT D:DATA.FIL JUNK DATA A
*-----------------------------------------------------------------------------*
BEAR BONE$ OPTIONS
*-----------------------------------------------------------------------------*
MAINFRAME STRINGS
-----------------
SEN=<string> (Default: SEN=IND$FILE PTP)
SEND=<string>
This is the string that BEAR BONE$ will send to the mainframe to invoke
an upload. You would normally use IND$FILE PTP if your mainframe is
running version 1.1.1 of IND$FILE, or IND$FILE PUT if your mainframe
is running version 1 of IND$FILE.
REC=<string> (Default: REC=IND$FILE GTP)
RECEIVE=<string>
BEAR BONE$ will send this string to the mainframe to initiate a download.
You should use either IND$FILE GTP (v1.1.1) or IND$FILE GET (v1).
OPT=<string> (Default: NOT USED)
OPTIONS=<string>
PARAMETERS=<string>
DEFAULTS=<string>
Default mainframe options used if none specified on the command line.
Example:
OPT=(ASCII CRLF
or
DEFAULTS=(BINARY NOCRLF
RELIABILITY OPTIONS
-------------------
ERR=AUTO|CHECKSUM|CRC (Default: ERR=AUTO)
ERRORCHECK=AUTO|CHECKSUM|CRC
This option is only available for uploads.
ERR=AUTO will cause BEAR BONE$ to determine the type of error checking
that is performed on the mainframe. This is a typically used option,
but is not recommended for use with the CICS IND$FILE.
ERR=CHECKSUM forces BEAR BONE$ to use a one byte checksum error detection.
Use this option only if your mainframe is running version 1 of IND$FILE,
or running a CICS version.
ERR=CRC tells BEAR BONE$ to use an advanced 6 byte CRC (Cyclical
Redundancy Check). Version 1.1.1 supports this feature.
BUF=<number from 1 to 2000> (Default: BUF=50)
BUFFERSIZE=<number from 1 to 2000>
TYPEAHEAD=<number from 1 to 2000>
KEYBOARDBUFFER=<number from 1 to 2000>
PACING=<number from 1 to 2000>
Specifies the size of your protocol converter's type-ahead buffer. When
sending a file, BEAR BONE$ will never be more than <number> characters
ahead of echoed back characters. Generally, the lower the number, the
slower the transfer will be. On the other hand, if BUF is set too high,
your protocol converter may disconnect, or lock up on you during your
transfer. Experiment to get the best results.
BLK=<number from 200 to 1914> (Default: BLK=1914)
BLOCKSIZE=<number from 200 to 1914>
FRAMESIZE=<number from 200 to 1914>
Sets the block size of the data for uploads only. As with the BUF
parameter, a small block size will slow the transfer. Use this
option only if you are having problems with file uploads.
DLY=<number from 0 to 50> (Default: DLY=0)
FRAMEDELAY=<number from 0 to 50>
BEAR BONE$ will pause this many ticks (1/18th second intervals) between
blocks, to make the transfer more reliable.
CLK=A,B,C (Default: NOT USED)
XCLOCK=A,B,C
Tells BEAR BONE$ to use the mainframes XCLOCK to determine when the
screen has been updated. "A" is the ROW NUMBER, "B" is the COLUMN
NUMBER, and "C" is the character located at that position.
Example:
CLK=25,9,X
TMO=A,B (Default: TMO=20,3)
TIMEOUT=A,B
Sets the time-out limit and number of retries. If the communications
port remains inactive for "A" seconds, BEAR BONE$ will request a
screen refresh from the host. The valid range for "A" is 5 seconds
to 150 seconds. The "B" parameter specifies the maximum number of
times BEAR BONE$ will ask for a screen refresh for any given frame.
The valid range for "B" is 1 to 10.
TERMINAL TYPES AND KEY DEFINITIONS
----------------------------------
TRM=VT100|ANSI|FTTERM|3101|TV950|HYDRA (Default: TRM=VT100)
TERMTYPE=VT100|ANSI|FTTERM|3101|TV950|HYDRA
Tells BEAR BONE$ what type of terminal to emulate during the transfer.
The transfer will not work if this option is set incorrectly. It should
match the terminal type that your communications software is emulating.
TV950 should be used if you are using PROCOMM's 3270/950 emulation.
The key mappings are likely to be different, however, so please double
check them using PROCOMM's PCKEYMAP utility.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
NOTE:
The following key definitions should coincide with the terminal type and
key mapping that your communications package uses.
An <extended string> may be any combination of the following definitions:
Normal displayable ASCII characters:
IND$FILE PTP
ASCII DIGITS surrounded by parenthesis and separated with spaces:
(123 12 32 42)
HEXADECIMAL DIGITS surrounded by less-than/greater-than symbols and
separated with spaces:
<0F 1B C4 12>
ASCII CONTROL CHARACTERS may be defined by using the carat (^)
followed by an ASCII character in the range of 64-95 (DECIMAL) or
40-5F (HEXADECIMAL):
^C^M
Special cases are ^, (, and <. They may be specified by using
^^, ((, and << respectively.
The following examples are all equivalent:
^[J1
<1B>J1
(27)J1
^[<4A 32>
(27 74 49)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
ENT=<extended string> (Default: ENT=^M)
ENTER=<extended string>
The key sequence your mainframe expects for the <Enter> key.
RHT=<extended string> (Default: RHT=^[[C)
RIGHT=<extended string>
The key sequence your mainframe expects for the <Right Arrow> key. This
key must be defined correctly for uploads to work.
RST=<extended string> (Default: RST=^R)
RESET=<extended string>
The key sequence your mainframe expects for the <Reset> key. BEAR BONE$
sends this key when the protocol converter has locked up and sent us the
bell character (hexadecimal 07).
TRY=<extended string> (Default: TRY=^[r)
RETRY=<extended string>
REDISPLAY=<extended string>
The key sequence for your protocol converter's "REDISPLAY SCREEN" function.
If your protocol converter does not have such a function, try using the
<PF1> key definition.
CAN=<extended string> (Default: CAN=^[2^C^C)
CANCEL=<extended string>
BEAR BONE$ will send this sequence to cancel a file transfer. Usually
this is defined as your <PF2> key followed by a couple of <Clear> keys.
PRE=<extended string> (Default: NOT USED)
PREAMBLE=<extended string>
The preamble string. BEAR BONE$ will send it to the protocol converter
before initiating a transfer. Use this to set up XON/XOFF flow control,
or other protocol converter dependent options that the manufacturer
recommends. Ask your systems operator for more information.
If your protocol converter displays the status line on the 24th line
instead of the 25th line, you MUST disable it before starting a transfer.
PR2AMBLE=<extended string> (Default: NOT USED)
This is our "2nd" preamble. Only use this if the mainframe pauses and
needs the enter key or something before actually starting the transfer.
MID=<extended string> (Default: NOT USED)
MIDAMBLE=<extended string>
The "midamble" string. BEAR BONE$ will send this between batch transfers
to get the host back to a "Ready" state.
PST=<extended string> (Default: NOT USED)
POSTAMBLE=<extended string>
The postamble string. BEAR BONE$ will send it when the transfer is
complete to "undo" the preamble.
PORT OPTIONS
------------
PRT=<number from 1 to 8> (Default: PRT=1)
PORT=<number from 1 to 8>
COM=<number from 1 to 8>
Specifies the communications port number on the PC.
ADR=<number> (Default: ADR=0)
ADDRESS=<number>
The address of the communications port in hexadecimal (i.e., 03F8).
If you specify 0 for the port address, BEAR BONE$ will use the port
defaults.
IRQ=<number from 0 to 15> (Default: IRQ=0)
Specifies the port's IRQ. Use 0 to have BEAR BONE$ use port's default
IRQ.
PS2=YES|NO (Default: NO)
'Yes' indicates you are using a genuine IBM PS/2. This will cause
Bear Bones to use default port addresses specific to the ps/2, unless
you specify the address using the ADDRESS parameter.
BDR=<number> (Default: NOT USED)
BAUD=<number>
SPEED=<number>
Causes the port's baud rate to be set when opened. By default,
BEAR BONE$ leaves the baud rate alone. Valid options are 1200, 2400,
4800, 9600, 19200, 38400, 57600, 115000. This option (and the BTS
option) must be specified if you are using BEAR BONE$ in conjunction
with a Windows product (such as PROCOMM for Windows).
BTS=ABC (Default: NOT USED)
BITS=ABC
Where "A" is the number of DATA BITS (7 or 8), "B" is the PARITY
(N=None, O=Odd, E=Even, M=Mark, and S=Space), and "C" is the number of
STOP BITS (1 or 2).
Example:
BTS=8N1
or
BTS=7E1
NET=INT14|NASI (Default: USE LOCAL COM PORT)
NETWORK=INT14|NASI
Tells BEAR BONE$ to use either INT14 or NASI/NCSI calls to route data
through your LAN's "modem pool". You must also be using a "network"
communications package that supports one of these methods.
If you specify NASI, BEAR BONE$ will use the first active virtual
circuit. Because of this, you must have only one circuit open.
MISCELLANEOUS OPTIONS
---------------------
DEL=<number from 20 to 200> (Default: NOT USED)
DELETE=<number from 20 to 200>
Tells BEAR BONE$ to delete two characters every X number of bytes.
This is useful to strip carriage return/line feed pairs if your mainframe
IND$FILE puts them in when it shouldn't.
LOG=<filename> (Default: NOT USED)
LOGFILE=<filename>
Will cause BEAR BONE$ to append the results of the transfer to the
specified log file:
SEN FAIL 04/12/93 08:19:49 0:03 1632 c:autoexec.bat
REC -OK- 04/12/93 08:23:42 0:09 6285 pcodes.doc
.
.
.
PAU=<number from 0 to 1000> (Default: 3)
PAUSE=<number from 0 to 1000>
Forces BEAR BONE$ will pause this many seconds before exiting.
RET=A,B (Default: RET=0,1)
RETURNCODES=A,B
Sets the values that BEAR BONE$ will return on exit. "A" is the
return code for a successful transfer, and "B" is the return code for
a failed transfer.
SOUND=YES|NO (Default: YES)
'No' Turns off the beeping at the end of the transfer.
TRC=<filename> (Default: NOT USED)
TRACEFILE=<filename>
Causes BEAR BONE$ to record all data that is sent or received on the
communications port. Use this option only for debugging, as it creates
a VERY LARGE file.
VID=COLOR|B&W (Default: COLOR)
VIDEO=COLOR|B&W
Tells BEAR BONE$ to write to the screen either in full color, or black
and white. This option could be useful on laptop machines or machines
with paper-white VGA monitors.
WAT=YES|NO (Default: NO)
WATCH=YES|NO
Lets you watch the emulation screen as the transfer takes place.
*-----------------------------------------------------------------------------*
MAINFRAME OPTIONS
*-----------------------------------------------------------------------------*
This section gives a brief listing of the mainframe IND$FILE options. Please
refer to your mainframe IND$FILE manual for detailed descriptions of the
following options.
CICS:
SEND Options RECEIVE Options
-------------------------------------------
ASCII|BINARY APPEND
CRLF|NOCRLF ASCII|BINARY
P(xxx) CRLF|NOCRLF
P(xxx)
ASCII CRLF is the default data type.
Example: BONE$ CICS.PRM PUT C:\AUTOEXEC.BAT JUNK (ASCII CRLF
IWS:
SEND Options RECEIVE Options
-------------------------------------------
ASCII|BINARY ASCII|BINARY
BLANK BLANK
CRLF|NOCRLF CRLF|NOCRLF
NOREPLACE|REPLACE REPLACE|APPEND
P(xxx) P(xxx)
FILE=HTF|FILE=TS FILE=HTF|FILE=TS
if FILE=HTF: if FILE=HTF:
FOR=usid1...usid8 FROM=usid
PRIVATE|PUBLIC DELETE|KEEP
TYPE=EDIT|TYPE=PRINT
if FILE=TS: if FILE=TS:
QNAME=CFTRxxxx QNAME=CFTRxxxx
PROGRAM=CFTRxxxx PROGRAM=CFTRxxxx
ASCII is the default data type.
BINARY is used for binary files.
Options available depends on the level of VSE/SP.
Example: BONE$ IWS.PRM PUT C:\COMMAND.COM JUNK (BINARY
MVS/TSO:
SEND Options RECEIVE Options
-------------------------------------------
APPEND APPEND
ASCII ASCII
CRLF CRLF
BLKSIZE(n) P(xxx)
LRECL(n)
P(xxx)
RECFM(F|V|U)
SPACE(n1,n2)AVBLOCK(n)
SPACE(n1,n2)CYLINDERS
SPACE(n1,n2)TRACKS
BINARY is the default data type.
ASCII and CRLF are commonly used for text files.
ASCII and CRLF are the only valid options for members of a partitioned
data set.
80 characters is default length for a fixed length records.
Example: BONE$ TSO.PRM PUT C:\CONFIG.SYS 'JUNK.TEST.A' ASCII CRLF
(Note that a left-paren does not precede the option list.)
VM/SP:
SEND Options RECEIVE Options
-------------------------------------------
APPEND APPEND
ASCII ASCII
CRLF CRLF
LRECL P(xxx)
P(xxx)
RECFM V|F
BINARY is the default data type.
ASCII and CRLF are commonly used for text files.
Example: BONE$ VM.PRM PUT D:\README.DOC JUNK TEST A (ASCII CRLF
*-----------------------------------------------------------------------------*
ERROR MESSAGES
*-----------------------------------------------------------------------------*
Can't allocate memory for communications buffer.
Can't allocate memory for screen buffer.
Can't allocate memory for frame buffer.
These errors usually mean that you don't have enough low memory available.
Try unloading some TSR's.
Timeout limit reached while waiting for frame.
The mainframe failed to give us a valid format screen. This error message
only pops up after BEAR BONE$ has tried to redisplay the screen several
times. Double-check the codes for your TRY= key in the parameter file.
Transfer ABORTED by user.
The user has hit the ESCAPE key.
Invalid port number specified.
No port found at specified address.
No default port address available.
No default IRQ defined for this port.
Error opening communications port.
These errors usually mean that you are trying to access a port that isn't
there. Double-check the PRT= parameter. If the PRT= parameter looks
correct, try adding the ADR= and IRQ= parameters. You can usually find
these values in your communication program's setup screens.
Can't set DTR on exit.
Can't set remote XON/XOFF flow control.
Can't set local XON/XOFF flow control.
Can't set baud rate.
Can't set parity.
Can't set data bits.
Can't set stop bits.
This sounds like your port or UART has some register-level problems. Try
hooking up your modem to a different port.
NASI/NCSI not loaded.
The NASI/NCSI device driver was not found. Make sure that NASI/NCSI
software is loaded.
NASI/NCSI virtual circuit not found.
The NASI/NCSI device driver was found, but no circuits are active. It
sounds like you're not connected to the host.
Transfer ABORTED by user.
Error reading from send-file.
Error writing to receive-file.
There was a problem with the disk. Run CHKDSK on your drive or
another disk checker program like NORTON DISK DOCTOR.
Option SEN= cannot be empty.
Option REC= cannot be empty.
Option ENT= cannot be empty.
Option RHT= cannot be empty.
These options cannot be defined as blank. Check your parameter file for
the appropriate option.
Illegal baud rate specified.
The parameter file or command line contained an illegal baud rate
specifier. Valid baud rates are: 1200, 2400, 4800, 9600, 19200, 38400,
57600, AND 115000. If you'd like, you only need to use the first two
digits.
The XCLOCK scan character may not be a SPACE.
Make sure there aren't any spaces in you CLK= parameter. "CLK=24,9,X"
is valid, while "CLK=24, 9, X" is not.
Illegal XCLOCK position.
You had specified a screen position that is out of range. The maximum
column number is 79, and the maximim row is 24 (origin at [0,0]).
Illegal CRLF strip position.
The DEL= parameter can take values in the range of 20 to 200 only.
Default parameter file (BONE$.PRM) not found.
BEAR BONE$ could not find any parameter file to open.
Usage: BONE$ <Param-file> PUT|GET <PC-file> <MF-file>
Protocol converter appears to have hung.
The protocol converter has sent us many bell characters (0x07). And
appears to be frozen. BEAR BONE$ will try to reset the converter several
times before bombing out.
Unable to open BATCH file.
The specified batch file does not exist.
Received an unexpected screen type. Transfer canceled.
The mainframe has become lost and sent us the wrong type of screen.
Can't open PC file for input.
The PC file does not exist.
Can't open PC file for output.
The PC filename is invalid or cannot be created.
Bad key definition "?????" on line ? of parm file.
There is a syntax problem with a key definition in the paramter file.
Bad key definition "?????" on command line.
There is a syntax problem with a key definition on the command line. We
recommend that you put all your key definitions in your parameter file.
Can't find parameter file "?????"
The first option is the parameter file name. The one specified could not
be opened. Maybe its in another directory, or the name was typed wrong.
A 'PRM' extension is added if none is specified. BONE$.PRM is the default
parameter file.
Invalid option "?????", expected GET or PUT.
The second option must be GET, PUT, SEND or RECEIVE (may be abbreviated).
Something else was found here.
Batch file error: ?????
There was an error inside the batch file when we expected to find the
direction (GET, PUT, SEND, RECEIVE).