HP 3000 Manuals HP 3000 Manuals
#RJLINE
Use the #RJLINE command to define a communications link between RJE and a
remote processor.
Syntax
#RJLINE emulator type
[;CHNL3=channel number]
[;CONNECT={DIAL} [{,"telephone number"}
{,"selection signals"}*
{,DIRECT }*]
{ANSWER}]
[{DEV={linkname id}+
{device id}*}
{;NODE=logical node name }*]
[;ID=terminal id string ]
[;LANGID=language ID ]
[;LINECODE={ASCII}
{EBCDIC}]
[;LOCK={YES}
{NO }]
[;MAXRPB=blocking factor ]
[;MSGFILE=message file name ]
[;PRI={HIGH}
]
[;QUEUETIME=[m ],[s ]]*
[;RIN=rin number, password ]
[;TRACE=ON[,[ALL]*[,[mask]*[,[numentries]*[,[WRAP]*
[,[trace file name]]]]]]]
[;XEND]
+ A parameter or value applicable to RJE/XL only.
* A parameter or value applicable to RJE/V only.
Parameters
You can specify the following parameters with the #RJLINE command.
emulator type Required. Emulator type specifies the type of data transmission
or communication terminal to be emulated.
Value: Either 2780 or 3780.
NOTE Whenever you have the choice of emulating either an IBM 2780 or IBM
3780, you should be aware that RJE operates more efficiently in the
IBM 3780 mode.
Default: There is no default; you must specify either 2780 or
3780.
CHNL3 = Use the CHNL3 parameter to specify a channel number on a line
printer carriage control tape. Under MPE, channel 3 is always
used for single spacing with a skip from bottom-of-form to
top-of-form. The CHNL3=channel number parameter causes RJE to
convert channel 3 codes received from the remote processor to
whatever channel number is indicated. It is assumed that the
specified channel on the line printer carriage control tape
contains the sequence of punches expected by the remote
processor. It is a responsibility of the user to ensure that
this setting is correct.
channel number Value: An integer between 0 and 12.
Default: If the CHNL3 parameter is omitted, the default is 8
(the single space VFU position).
CONNECT = This parameter specifies the method of initiation of connection.
ANSWER CONNECT=ANSWER puts the HP 3000 in the state of
a secondary contention station. If the line is
not yet established and if RJE is ready to
receive or to transmit data, the wait time is
indefinite. If a connection has not been
established and a subsystem command to transmit
or to receive data is waiting to execute, you
must abort it to begin another operation.
DIAL Use CONNECT=DIAL to eliminate the problem of
determining the appropriate time to dial the
host system. With the DIAL parameter and
assuming manual dial set-up, the HP 3000
terminal operator dials and makes the
connection immediately after receiving the dial
prompt (immediately after the first #RJIN,
#RJOUT, #RJLIST, or #RJPUNCH command executes).
Without this parameter, no prompting message
appears at the terminal.
For this reason, always provide the CONNECT=DIAL parameter if a
terminal operator other than yourself must actually dial the
telephone number. CONNECT=DIAL implies that your HP 3000 is the
primary contention station.
If RJE is ready to transmit or to receive data and the line has
not yet been established, RJE waits until the communications
link is present. In this case, RJE will wait up to the time
specified by the connect timeout configuration parameter (30-900
seconds) for the Data Set Ready (CC) signal from the modem. If
Data Set Ready is not detected within the allowed time, RJE
issues a CS ERROR 1, (read),151 or CS ERROR 2 (write), 151
message.
If CONNECT=DIAL is used and the communications line is
configured with the autodial capability, normal operations are
transparent both to the RJE user and HP 3000 terminal operator.
Default: If the CONNECT parameter is not specified, then the
default is ANSWER.
telephone number The telephone number entered is included as
part of the dial message which is displayed at
the operator's terminal immediately after
execution of the first #RJIN, #RJOUT, #RJLIST,
or #RJPUNCH command to notify the HP 3000
terminal operator to dial the remote processor
or is used to notify the automatic calling unit
(ACU) to dial the remote processor
automatically (autodial). In response to the
dial message, the terminal operator dials the
remote processor. The answer will be an
audible carrier tone signal. With RJE/V, if a
successful connection is made, the operator
replies to the dial request with a YES. With
RJE/XL, a successful connection does not
require a reply (the request is removed).
After the connection is made (and a YES reply is entered for
RJE/V), RJE completes the current command and then reads the
next command (batch job) or displays a # (interactive use) at
the terminal to prompt the user to enter the next command.
If the terminal operator enters NO before a connection is made,
RJE responds by issuing a CS ERROR 1,57 or CS ERROR 2,57
error/warning message. Refer to appendix A, "Interpreting
Messages," for explanation.
The telephone connection can be established by dialing the
remote processor via a modem or by receiving a call from the
remote processor. With a leased line or a switched line
configured as a nonswitched line, the connection is not broken
after each call and redialing is not required.
If the communications line specified by the user is configured
with an autodial capability, then no operator action is required
in an ordinary situation.
When the autodial feature is used, a telephone number must be
specified in the #RJLINE command or configured for the device
identified. The characters comprising the value of the
telephone number are transmitted to the ACU to be dialed.
Value: An ASCII character string of not more than 30 (34 for
RJE/XL) numeric characters (0 through 9) and hyphens. If the
communications line is configured with the autodial capability,
the following characters may also be used:
E End of number (Some autodialers require this)
/ Wait for a second dial tone (as in going
through a PBX to get an outside line)
D Pause for 1 second
Blank Valid but will be ignored
() Valid but will be ignored
# and * Valid
No delimiters, for example, quotes, are necessary. The number
may include an area code; the area code may be followed by a
hyphen, then the telephone number.
Default: If telephone number is omitted from the CONNECT=DIAL
parameter, the default phone number entered during RJE
configuration is used. (See the RJE/XL Node Manager's Guide or
RJE/V Node Manager's Guide). Entering a telephone number
automatically overrides the default telephone number.
selection signals(X.21 only). The selection sequences are
defined by the X.21 network manager. These
character sequences specify facility requests
such as a request for charge information,
called line identification or a node address.
This information is in a network configuration
database as explained in appendix F, "X.21."
Value: An ASCII character string consisting of
up to 30 characters. These characters may be
anything except:
double quotation mark "
commercial 'at sign' @
left parenthesis (
right parenthesis )
equal sign =
semicolon ;
(X.21 only)
DIRECT Specifies a request for a X.21 direct call.
DEV = Specifies the communications line to be opened by RJE.
linkname id (RJE/XL only). A 1 to 8 character name of a
link configured in NMMGR.
A number up to 3 digits (nnn). If a number is
specified, RJE will look for and use the
linkname RJEnnn in NMMGR.
Default (RJE/XL only): If DEV is omitted, the
default is to use one of the available
configured RJE links in NMMGR.
device id (RJE/V only). The device identification is a
device class name or logical device number.
The device class name is a 1 to 8 character
name of a configured link which is a device
class name assigned to the communications line
at system generation time. If several
communication interfaces share the same device
class name, RJE will use the first available
one, starting with the lowest logical device
number. If a device class name is specified,
then RJE assumes that this refers to a line
with a V-series interface. If a logical device
number is specified, RJE will attempt to open
the line with that number.
(X.21 only). If a logical device number is
specified then an attempt is made to locate a
corresponding entry in an X.21 network
configuration database. The network
configuration database is described in appendix
F, "X.21." If the logical device number is
located in the database and is configured as an
X.21 line then RJE proceeds on this basis. If
the database does not exist or the logical
device number cannot be found within the
database then RJE assumes that the logical
device number refers to a line with a V-series
interface.
Default (RJE/V only): If both the DEV and NODE
parameters are omitted, the default is to open
a device in class #RJLINE as a V-series
interface.
NODE= (X.21 only). RJE does not allow the user to specify both the
DEV and NODE options in the same #RJLINE command. Use NODE to
specify the destination node. When this parameter is used, RJE
will select the CS device.
logical node name Value: An entry in the Network
Configuration database.
Default: If both the DEV and NODE parameters are omitted, a
device is opened in class #RJLINE as a V-series interface.
ID= Use this parameter when the remote processor requires a terminal
identification string. If the ID parameter is present, RJE
transmits a terminal ID using the supplied terminal
identification character string. RJE will transmit the terminal
ID only if RJE initiates transmission; that is, if the first
input/output operation is #RJIN. No terminal ID is transmitted
if the first input/output operation is #RJOUT, #RJLIST, or
#RJPUNCH. (RJE/V ignores a terminal ID sent by a remote
processor.)
terminal id string Value: An ASCII character string of up to
15 characters to be used to identify your
terminal when the communications link is
being established. If LINECODE= EBCDIC, RJE
automatically converts the terminal
identification from ASCII to EBCDIC.
Default: If the ID parameter is omitted, no terminal ID is
transmitted.
LANGID= This parameter states which code from the Native Language
translation tables is to be used in natural language processing.
For further information, see the LANGNUM parameter in the NLINFO
intrinsic in the MPE Intrinsics Reference Manual
language ID Value: Integer from 0 - 255
Default. 0 (NATIVE3000)
LINECODE= This parameter specifies the transmission code. If the
transmission code to be used is EBCDIC, the LINECODE must be
passed explicitly.
code Value: ASCII or EBCDIC
Default: If you omit the LINECODE= parameter, the default is
ASCII.
LOCK= The LOCK parameter has no effect on the allocation of buffer
space by the CS driver. When RJE is invoked, the driver
allocates space as usual.
YES If LOCK=YES is specified, RJE locks its stack
during activity.
NO LOCK=NO allows the RJE stack to be managed like
any other portion of memory. The MPE memory
manager may move (swap) the data stack out to
virtual memory; the benefit of this is most
apparent in small memory configurations where
there is contention between subsystems and
programs with large stack requirements. Use
LOCK=NO parameter with care, because this is
the exceptional condition. It is usually more
desirable to retain the data stack of the RJE
subsystem in memory.
Default: If the LOCK parameter or option is
omitted, the default is YES.
MAXRPB= Use MAXPRB to specify the blocking factor: the maximum number
of records per transmission block on a communications line.
blocking factor Value: blocking factor is a decimal
integer between 0 and 255.
Default: If the MAXRPB parameter is
omitted, the default blocking factor is:
2780 - nontransparent: 7
2780 - transparent: 4
3780 - nontransparent: 255
3780 - transparent: 6
See the #RJIN command for a description of
transparency and nontransparency.
MSGFILE= This parameter is used for the programmatic control of RJE
subsystem commands. Only RJE users with System Supervisor (OP)
capability may use this parameter.
The message file must be a permanent file in the group and
account MSG.RJE. A message file needs to be able to contain file
names with lockwords and to be of sufficient size to accomodate
the demands of the users of the system. For more information on
message files, consult appendix B, "Using RJE Files," chapter 5,
"Using RJE in Programmatic Mode," and appendix E, "User-Written
Procedures."
message file name Value: Actual file designator, 1 to 8
characters long, which specifies where RJE
will find the references to the command
files submitted by users for processing.
PRI= This parameter specifies RJE execution priority.
HIGH Value: PRI=HIGH establishes RJE execution
priority by a call to the GETPRIORITY
intrinsic, resulting in RJE having higher
priority than the CS subqueue. The priority is
150 absolute in a linear subqueue, the bottom
of the BS and top of the CS queue.
NORMAL Value: PRI=NORMAL omits the call to the
GETPRIORITY intrinsic and allows RJE to compete
for priority in either interactive or batch
mode like a normal process.
Default: If the PRI parameter is omitted, the default is HIGH.
QUEUETIME= (X.21 only). QUEUETIME is used to specify the time that RJE
will queue in an X.21 connection attempt. The value of m and s
together must not exceed 32767 seconds (or 546 minutes and 7
seconds). If the total of the QUEUETIME parameter is zero, then
RJE will queue indefinitely.
m Value: Minutes of queueing time.
s Value: Seconds of queueing time.
Default: If omitted, RJE will wait until the current connect
timeout is exceeded; then abandon the connection attempt.
RIN= Use this parameter to enqueue batch jobs which use RJE and a
communications line. Since a communications line is a non-
shareable device, the use of RINs will allow you to execute RJE
processes serially.
The RIN capability should be used whenever the possibility
exists that more than one job or interactive session will try to
use the same communication interface at the same time. This
could occur if a batch RJE job enters the system while an
interactive RJE session is in progress or when several batch
jobs enter a system that has spooling capability. If the RIN
capability is not used in such situations, some of the jobs
could be terminated by a CS ERROR 0, 13 error condition. Note
also that the proper operation of the RIN capability requires
the cooperation of all jobs and interactive sessions which wish
to use the particular communications interface. All must know
the proper RIN to use and all must use it.
If the RIN parameter is present, RJE attempts, using the
LOCKGLORIN intrinsic, to perform a global lock on the specified
RIN. If the RIN can be locked, processing continues. If the RIN
is already locked (in use), the RJE session/job waits for it to
become available. If you specify an erroneous RIN or password,
RJE issues a RIN ERROR:0 error message. For interpretation,
refer to appendix A, "Interpreting Messages." The use of
resource identification numbers is described under "Managing
Resources through Resource Identification Numbers (RINs)" in the
MPE Commands Reference Manual.
rin number Value: A valid global resource identification
number (RIN). This RIN number is defined by the
system when you type in :GETRIN followed by
your user-selected password.
password Value: A valid rin password as defined by you
when you enter the :GETRIN command.
Default: There is no default RIN number or password. You must
specify both options for this parameter to work.
TRACE=ON TRACE=ON is used to provide a record of the line actions, CS
states and events that occur during RJE operation. Refer to the
RJE/V Node Manager's Guide (chapter on CS trace). RJE/XL will
not provide the same types of entries as RJE/V. Therefore, the
ALL, mask, numentries, and WRAP options will have no effect for
RJE/XL. Refer to the RJE/XL Node Manager's Guide, chapter 5,
"Troubleshooting Procedures" and chapter 6, "Trace Formatter."
ALL (RJE/V only). Will generate trace records for
all calls to CS intrinsics, whether or not they
complete successfully.
Default: If ALL is omitted from the TRACE=ON option list, the
default is the tracing of I/O errors only; the trace facility
enters in the trace file only those records in which an error
occurred during the execution of a CS intrinsic. The word
'error' appears on the trace listing.
mask (RJE/V only). Value: An octal integer
preceded by a % sign (%nn) or an equivalent
decimal number. It consists of a six-bit field
representing the two-digit (nn) mask field.
Select the types of entries required from the
table below, set the bits required (bit 0 is
the high-order bit) and use this or an
equivalent decimal number for your mask.
Bit Positions: | 0 | 1 | 2 | 3 | 4 | 5 |
Set Bit 0 = generate PSTN entries
Set Bit 1 = generate POPR and PEDT entries
Set Bit 2 = generate PRCT entries
Set Bit 3 = generate PRTX entries
Set Bit 4 = generate PSCT, PPOL and PSEL entries
Set Bit 5 = generate PSTX entries
For example, to generate PSTN and PRTX entries, the mask would
be %44 (bits 0 and 3 set).
Default: If the mask option is omitted, the default is the
generation of all entry types except PSTN.
NOTE PCMP entries are automatically generated. If bits 0 through 5 are
zeroes, all entry types except PSTN are generated.
numentries (RJE/V only). Value: A decimal integer for
the maximum number of trace entries in a trace
record; the maximum permissible value is 248.
The value actually used by the trace facility
will be the largest integer multiple of eight
that is not greater than the number you enter.
It is not possible to change the value of numentries once a
trace file has been built. If the numentries value you choose
turns out to be inadequate, you will have to purge the file and
rebuild it or let RJE rebuild it.
Default: If the numentries is omitted from the TRACE=ON option
list, the default is a maximum of 25 trace entries per trace
record.
WRAP (RJE/V only). Causes trace entries exceeding
maximum numentries to overflow the trace record
and overlay the prior trace entries.
The trace entries are deposited in a trace record in a circular
pattern. If the number of trace entries exceeds numentries,
they will overlay the entries at the start of the record. The
overlaid trace entries will be missing from the listing and a
warning message will appear at the start of the record in the
listing stating that the records are missing.
Default: If WRAP is omitted from the TRACE=ON option list, the
default is to discard overflow trace entries. NOWRAP appears in
the trace listing.
trace file name Value: File in which the user wants the trace
information to be written.
Default: If tracefile name is omitted for RJE/XL, the default
is NMTC####.PUB.SYS. For RJE/V, a file named RJTRCEn, RJETRCnn
or RJETRnnn will be opened, depending on whether the logical
device number of the line (the value of the DEV parameter) has
one, two or three digits. RJE will replace 'n', 'nn' or 'nnn'
with the logical device number.
XEND XEND suppresses the CS ERROR 158 printout. It is used only when
communicating with GE High-Speed Service to avoid an error
printout when no error exists. The use of this parameter causes
DLE EOT to be treated like an EOT. Do not use this parameter for
any other RJE communications.
Default: If the XEND parameter is omitted, the default is an
error condition when DLE EOT is received.
Examples
The following examples show different uses of the #RJLINE command and its
parameters.
Example 1
#RJLINE 2780;LINECODE=ASCII;TRACE=ON,ALL,,128;DEV=30
(For RJE/XL, the ALl and 128 trace values will be ignored.) An IBM 2780
is to be emulated. For a V-series interface, the communications link is
established by the computer operator, who dials the remote processor via
a modem. No terminal ID is to be transmitted. The transmission code is
ASCII. The maximum number of records per transmission block is either 7
for nontransparent mode or 4 for transparent mode. All events, including
errors, will be traced with a 37% mask and 128 entries per request can be
made in the trace record. Additional trace entries will be lost. For
RJE/XL, linkname "RJE30" will be searched for in NMCONFIG.PUB.SYS. RJE/V
will open the communications line configured as logical device 30.
Example 2
#RJLINE 2780;ID="MM";LINECODE=ASCII;TRACE=ON,ALL,,128;DEV=30
(For RJE/XL, the ALL and 128 trace values will be ignored.) This is the
same as above except that RJE is to transmit the terminal ID 'MM' when
the communications link is being established. The ID will be transmitted
only if the next subsystem command in the job or interactive session is
an #RJIN command.
Example 3
#RJLINE 3780;LINECODE=EBCDIC;CONNECT=DIAL;DEV=RJE30
An IBM 3780 is to be emulated. For a V-series interface, the
communications link is established by the computer operator, who dials
the remote processor via a modem. No terminal ID is to be transmitted.
The transmission code is EBCDIC. The maximum number of records per
transmission block is 255 for nontransparent mode or 6 for transparent
mode. RJE/XL will search for linkname "RJE30" in NMCONFIG.PUB.SYS. RJE/V
will open the first available communications device configured under
device class "RJE30".
Example 4
#RJLINE 2780;CONNECT=ANSWER;LINECODE=ASCII
An IBM 2780 is to be emulated. RJE is to monitor the modem for an
incoming call from the remote processor. A V-series communications
interface is the default if no network configuration database exists and
is in effect. No terminal ID is to be transmitted. The transmission
code is ASCII. The maximum number of records per transmission block is 7
for nontransparent mode or 4 for transparent mode. Since the DEV and
NODE parameters are omitted, RJE/V will open the first available device
in class "RJLINE". RJE/XL will open one of the configured RJE links in
NMCONFIG.PUB.SYS (not recommended).
Example 5
#RJLINE 3780;MAXRPB=100;LINECODE=ASCII;DEV=RJLINE
An IBM 3780 is to be emulated. For a V-series interface,the
communications link is established by the computer operator, who dials
the remote processor via a modem. No terminal ID is to be transmitted.
The transmission code is ASCII. The maximum number of records per
transmission block is 100. For RJE/XL, a linkname "RJLINE" will be
searched for in NMCONFIG.PUB.SYS. RJE/V will use the first available
communications device configured under device class "RJLINE".
Example 6
#RJLINE 3780; CONNECT=DIAL, "SPECIAL"; NODE=POINT5
(X.21 only.) An IBM 3780 is to be emulated. The communications link is
to be established with a "SPECIAL" selection sequence. The node is
POINT5 in the network configuration database.
Example 7
#RJLINE 3780; CONNECT=DIAL; MSGFILE=WORKTODO;DEV=130
An IBM 3780 is to be emulated. For a V-series interface, the
communications link is to be established by dialing with the configured
telephone number for the communications line in device class #RJLINE. If
the device is configured with an autodialing capability no operator
interaction will be required. There is a message file WORKTODO.MSG.RJE
which will contain the names of command files to be processed in
programmatic control mode. RJE/V will open the communications line
configured as logical device 130. RJE/XL will use the linkname "RJE130"
in NMCONFIG.PUB.SYS.