Function
Causes a Terminal Executive (sometimes known as a TCP) to be teleloaded into a remote terminal system connected via a message buffering multiplexer, using the program #XTLG.
Format
The identifier number specifies the device to be teleloaded.
The JB parameter is optional, and specifies the name of the job to be run. If JB is absent the job will be named TELEOP-identifier number, unless the LOADTCP was issued automatically by GEORGE, in which case the jobname will be TELELO-identifier number. To avoid jobnname clashes with the automatic system, users are advised not to use the name TELELO-identifier number in a JB parameter.
The parameters Tt and *CRfile description are alternative ways of specifying which terminal executive is to be used. Automatic teleload always uses Tt, where t is a two-character reference used to select a terminal executive from the ICLTLLOADLIB.
The format *CRfile description may be used when LOADTCP is issued by an operator, and the terminal executive required has been input from cards to a file.
The parameters may be given in any order.
Forbidden contexts
NOT OPERATOR, REMOTE
Execution
A message buffering conceptual named TELELO-identifier number will be created, if it does not alreadt exist, with one identifier with number identifier number. The device to be teleloaded will be attached to the conceptual and a job started to perform the teleload operation for the specified identifier. The job will normally run under :SYSTEM, and :SYSTEM will also own the conceptuals. It is recommended that no traps to the conceptuals be given to other users.
Since the macro can fail with a command error because of activity within :SYSTEM, for example of the conceptual is already online to a program, of if the jobname used by the macro is not unique, the installation manager may wish to reserve a special user name for teleload purposes so as to avoid any possible interaction with other jobs. This can be done by editing the LOADTCP macro to replace :SYSTEM by ab alternative user name. The file ICLTLLOADLIB must also be under this user, and if any conceptuals have already been created under :SYSTEM, they should be cancelled before the macro is run under the alternative user name.
The LOADTCP macro is necessary when the GEORGE restore-time macro RETAINAH is used. It ensures that teleload identifiers are detached from their conceptual when a teleload is complete. LOADTCP may be used without using RETAINAH.
When the job starts it will display:-
TELELOADING Iidentifier number WITH TCP Tt
If the *CRfile description parameter was used, FROM FILE file description will appear instead of Tt.
The teleload job will not normally list its monitoring file, except in the case where an operator-initiated teleload is unsuccessful. If the program #XTLG used by LOADTCP encounters an error, a core print of it will be taken to a workfile and listed.
If the identifier is found to be inoperable or ON TEST when #XTLG attempts to teleload it, the job will output a display to this effect and then finish. The job will run #XTLG with REALTIME ON if the user has a sufficient REALTIME core budget.
Error Messages
The macro issues CONCEPTUAL, ATTACH and RUNJOB commands in no-user context, and any of these can generate error messages. If either of the parameters specifying the identifier number or the terminal executive required is omitted, a parameter format error message will be produced. Note that if there is an error in the RUNJOB the identifier will be left attached to the conceptual.
Once the RUNJOB has been successfully executed, the teleload job begins, and any of the following error messages can occur:-
IDENTIFIER identifier number HAS BECOME INOPERABLE
IDENTIFIER identifier number ON TEST
TCP NOT FOUND
ERROR ON PROGRAM #XTLG
After an error message, the job will display:-
IDENTIFIER identifier number: TELELOAD ABANDONED
The job will then finish, and list its monitoring file if it was issued by the
operator.