ITEM: AA4029L

ap/? about setting up dialers file & attach queue to modem

ENV: 3.2.5, 550
.DESC:  Mike has a connection with MCI.  He uses "cu" to connect with
       MCI only to send a fax request from the MCI server.  Everything is
       working fine.  He connects fine, and then issues "~ and !" then from
       the command line he issues the following command "cat \
       >/dev/tty1"  and then that request goes to the MCI fine. However,
       He wants to AUTOMATE the process by script.

       He wants to crate a queue that uses tty1 the device, and on this 
       queue he would have the fax_requests that needs to be sent to MCI.
       These queued jobs would be sent by the script if he connects to the 
       MCI sever by using "cu MCI" and then connects, and afterward he can
       run the script, that needs to check if there is any queued jobs and
       then send it to the MCI server.   Instead of doing it manually by
       finding out the jobs that needs to sent, and then do it manually
       off cu by using the cat command.

Response:

There are basically 2 ways to solve this problem
Way one is to have the queue down in it's normall state.  A shell script
runs as a cron job or at a sleep interval that checks the queue for a
certain number of jobs.  When it is ready, it calls up the remote site
establishes the connection and leaves the port/modem available, and then
enables the queue with does a simple /bin/cat to the /dev/tty1.
Do this with:
1.  smit mkque
2.         Add a Local Queue
3. Fill in the following fields:
* NAME of queue to add                               [dialq]
  ACTIVATE the queue?                                 yes
  Will this become the DEFAULT queue?                 no                      +
  Queuing DISCIPLINE                                  first come first serve  +
  ACCOUNTING FILE pathname                           []
* NAME of device to add                              [diald]
* BACKEND OUTPUT FILE pathname                       [/dev/tty1]
  ACCESS MODE of backend output file                  write only              +
* BACKEND PROGRAM pathname                           [/bin/cat]
  Number of FORM FEEDS prior to printing             [0]                       \#
  Print HEADER pages?                                 never                   +
  Print TRAILER pages?                                never                   +
  ALIGN pages between files within jobs?              yes                     +

Option 2:
In this case everything is done through a shell script called dial.sh.
By setting BACKEND OUTPUT FILE pathname to FALSE, the filename of the
file to output is input parameter $1 for the shell script dial.sh
dial.sh can do the cu, establish connection and queue file immediately,
or wait untill x number files are queued and then open the connection
and send.

1.  smit mkque
2.         Add a Local Queue
3. Fill in the following fields:
* NAME of queue to add                               [dialq]
  ACTIVATE the queue?                                 yes
  Will this become the DEFAULT queue?                 no                      +
  Queuing DISCIPLINE                                  first come first serve  +
  ACCOUNTING FILE pathname                           []
* NAME of device to add                              [diald]
* BACKEND OUTPUT FILE pathname                       [FALSE]
  ACCESS MODE of backend output file                  write only              +
* BACKEND PROGRAM pathname                           [/bin/sh /bin/dial.sh]
  Number of FORM FEEDS prior to printing             [0]                       \#
  Print HEADER pages?                                 never                   +
  Print TRAILER pages?                                never                   +
  ALIGN pages between files within jobs?              yes                     +

Customer says he can work with this.

dial.sh can simply do a 'cat $1 > /dev/tty0' after the \#! stuff.



Support Line: ap/? about setting up dialers file & attach queue to modem ITEM: AA4029L

Dated: July 1994 Category: N/A

This HTML file was generated 99/06/24~13:30:32

Comments or suggestions?
Contact us