|
|
|
|
|
The hassign command assigns host service to host sessions.
Synopsis
hassign [hostsvc] host_application to session# [FTSCRT]
Description
The hassign command assigns applications to session numbers. It is necessary to use this command to associate an application with host interactions to a given logical unit (LU). One host session corresponds to one LU.
The FTSCRT argument is required to assign that session for file transfer. If you are using file transfer, valid session numbers are 0-31 (that is, only sessions on the first host communication card can be used for file transfer).
The hassign command automatically executes the host maintenance login sequence on the specified session.
If the application appl is currently assigned to a particular session, and a new application new_app is assigned to that same session, the old application appl is logged out and new_app is logged in. In other words, the application currently assigned to the session is replaced by the new application you wish to assign.
If the application my_appl is assigned to session 0 and you wish to assign the application your_appl to session 0, you must:
If the application my_appl is already assigned to session 0 but the state is logged out and hassign is run on my_appl again, nothing happens. You need to run hlogin to log the application my_appl back in.
Examples
In the following examples, the user is assigning the host application my_appl to session 0, to session 0-19, and to all sessions (up to 64 total with 2 host communications cards installed), respectively.
hassign my_appl to 0
hassign my_appl to 0-19
hassign my_appl to all
In the following example, the user is assigned in the host application file_trans to session 0 for file transfer.
hassign file_trans to 0 FTSCRT
See also
