Newsgroups: bit.listserv.sas-l
Date:         Mon, 28 Sep 1992 12:33:00 EDT
Reply-To:     "A. Barrios" <UABC@UNC.BITNET>
From:         "A. Barrios" <UABC@UNC.BITNET>
Subject:      SAS CONNECT under OS/2
Comments: To: sug-l@UNCVM1.BITNET
Comments: cc: Sally Muller <UNCSM1@UNC.BITNET>

 ---------------------------------------------------------------------  -
 SUMMARY:  Using SAS/CONNECT with OS/2 with modem or OS/2 CM and
           a 3270 card.
 REL/PLTF: 6.06 OS/2 2.0
 E-ADDR:   uabc@unc.bitnet
 NAME:     Arturo Barios
 PH/ADDR:  919-962-6501  OIT CB#3455, UNC, Chapel Hill NC 27514
 ---------------------------------------------------------------------  -

 Saludos a todos,

 Do you remember a posting that we couldn't get SAS/CONNECT to
 work under OS/2 2.0 ?  Dick Rober and Allan Rosen sent
 suggestions (thanks) but I did end up calling SAS tech support.
 Got real good help there, who wish to remain anonymous, and it
 all works now.  Here are two methods that work:

 Using a Modem ++++++++++

 Dirk Rober suggested: verify the following statement in your
 config.sys file:
                 DEVICE=C:\OS2\COM.SYS
 and apply the patches for COM.SYS available at several FTP/listserv
 sites. We have a copy under FTP.OIT.UNC.EDU in the directory
 pub/os2 and the file name is COMMGA.ZIP.

 To be sure the settings in your modem are correct include the
 following line in your TTY.CMD file located in your sasroot
 directory, or type in the OS2 command prompt:
       mode com#:baud, parity,databits,stopbits, IDRS=off
                 ODSR=off,OCTS=off,DTR=on,RTS=off

 where: com# is the port where your modem is conected, it could be
             com1, com2, or com3.
         baud is: 96 for 9600 bps
                  48 for 4800 bps
                  24 for 2400 bps
                  12 for 1200 bps.
         parity is: e for even
                    n for none
                    o for odd
                    m for mark
                    s for space.
          databits: 7 or 8 .
          stopbits: 0 or 1.

 In the AUTOEXEC.SAS file include the following:
      Options comamid=RASYNC remote=com#;
      Filename rlink 'd:\sasroot\connect\saslink\your_script_file';

 From the command prompt in a OS/2 window invoke TTY typing TTY,
 press Alt-Q and you are going to receive the following message:
     TTY suspended -enter 'c' to continue, 'q' to quit
 do not select C or Q, just switch to your SAS session and signon,
 the link will be established.

 Using an IBM-3270 card +++++++++

 In order to use the 3270 card, install the Communications
 Manager (CM) that comes with the Extended Services for OS/2. To
 connect with the mainframe here at UNC I used the following
 configuration:
               -Terminal 3270
               -DFT (Distributed Function Terminal)
               -SNA (System Network Architecture)

 Start your CM session, and switch to the SAS session (e.g. click
 on the SAS icon). Include the following lines in autoexec.sas

      Options comamid=EHLLAPI remote=your_session_name;
      Filename rlink 'd:sasroot\connect\saslink\your_script_file';

 On the command line of SAS type signon, and the connection is
 done.  The script files that I used are available in the Bulletin
 Board at ftp.oit.unc.edu in the directory pub/os2.

 You can find more information in the SAS/CONNECT Software Usage
 and Reference Manual.

 Remember to use the RSUBMIT to execute the commands in your
 remote session, and don't forget to signoff.

 Arturo Barrios / OIT - User Services
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU