In asynchronous communication, a client computer logs into a host/server and makes requests for services or data from the host computer. A client PC/workstation normally must provide a valid user ID and a password to log onto a host computer/server.
To set up a pfs/Async communications client computer, you must perform the following steps:
Define the communications channel, choosing Asynchronous as the communications type. You do not need to enter a user ID and password on the Host tab of the Comm Channel – New window. You do, however, have to know the user ID and password for the host PC which you will be logging on to when reading an asynchronous communications script.
Enter setup information for the pfs/Async communications type. If the asynchronous communications client will only send data and not receive, the direction must be Send. If the asynchronous communications client will only receive data and not send, the direction must be Receive. If the asynchronous communications client will both send and receive data, the direction is Both. However, the direction chosen on the host PC will override the direction chosen on the client PC. For example, if a client PC attempts to send data to a host PC that is not set to receive, the transmission will not take place.
Record the script (save the script file) that tells the asynchronous communications client to dial into and communicate with the asynchronous communications host.
Often, pfs/Async is set to start on a time- or event-driven basis on an asynchronous communications client. Upon either occurrence, the client dials into the asynchronous communications host and executes the commands in the appropriate script file.
