Conference orarep::nomahs::sql_services

    Ok, after a little (all I'm capable of) thought, another more specific
    question is where, in the VMS api, do I specify an alternate port?  
    
    I've installed sqs v7.0 mv on a vax here, I've specified an alternate
    port for the dispatcher.  When I run the example vms client, I get 
    invalid class name.  Generic, which uses 5.1 and the "standard" port,
    works fine.   I've looked at the API routines and can't see anywhere to
    specify another port. 
    
    But, I'd still like a little detail about .0.   
    
    TIA guys, 
    
    

    Thanks to my gifted colleague JHAYTER, I now know how to specify the
    alternate ports on vms.  Install guide section 4.2.2.2. Use logicals
    to point to the DISPATCHER.  
    
    For example, 
    
    $ DEFINE SQLSRV$TCPIP_PORT "PORTNUM" 
    
    You should be able to find this using the SQLSRV manager.  
    
    Thanks, Jerry.

Hi Pat,

You must direct the clients to the new server.  Depending on what the client
is, depends on how you do this "directing".  It is all documented in the 
Installation Guide, chapter 4.  Section 4.2.2.2 specifically details what
you need to do at the client side to make sure the clients are communicating
on the new port.

I think this is what you are looking for.

Renee

    
    

RE: .2  note collision!!
    
Guess that section is what you needed!!  :)

Renee

>    So, what reads sys$manager:sqlsrv$alternate_ports70.com and when does it
>    do it?

                   -  sqlsrv$alternate_ports70.com - a command procedure
                       that defines symbols for the alternate ports
                       used by the Oracle SQL/Services dispatcher and
                       management service. This procedure is used by
                       sqlsrv$startup70.com and sqlsrv$ivp.com
    

    Well, I appreciate the help you've given me on this Jerry, but I looked
    at that com file and see no reference to sqlsrv$alternate_ports70.com.
    In fact, a
    
    $ sea sys$startup:sq*.com alternate
    only finds the following 2 files.  Maybe I messed up the install and
    the startup that it put out there is not correct for alternate ports.  
    
    
    ******************************
    SYS$COMMON:[SYSMGR]SQLSRV$DEINSTALL_DELETE.COM;2
    
    $           REMOVE
    'RDB$$ROOT':[SYSMGR]SQLSRV$ALTERNATE_PORTS'VARIANT'.COM;*
    
    ******************************
    SYS$COMMON:[SYSMGR]SQLSRV$SHUTDOWN70.COM;2
    
    $       ! Use alternate ports if specified
    $       if f$search("sys$manager:sqlsrv$alternate_ports''version'.com")
    .nes. ""
    $           @sys$manager:sqlsrv$alternate_ports'version'
    $       endif       ! if f$search("sys$manager:sqlsrv$alternate_ports...
    

>    Well, I appreciate the help you've given me on this Jerry, but I looked
>    at that com file and see no reference to sqlsrv$alternate_ports70.com.

I don't write 'em, just cut and paste 

~~             <<< Note 2138.6 by M5::PSOEHL "Go see THE RELIC!!!" >>>
~~                            -< still can't find it >-

~~    Well, I appreciate the help you've given me on this Jerry, but I looked
~~    at that com file and see no reference to sqlsrv$alternate_ports70.com.
~~    In fact, a

Not that I'd consider myself an expert in this area but...

How did you install SQL/Services?  Standard or MV?  If MV, how did you 
answer the question about using the default SQL/Services network ports?  If 
you say you want to use the defaults, then the defaults are used and the 
SQLSRV$ALTERNATE_PORTS70.COM file isn't created.  I believe the COM file is 
created during the install if you don't want to use the default ports.  The 
installation then asks additional questions on the various port numbers to 
use.
    

    Well, here's what happened.  I installed mv.  First time, I took
    standard ports.  Didn't work.  2nd time, alternate ports.  The 
    alternate ports com file is there, but I don't see where it gets
    invoked, except in shutdown and deinstall_delete. I've looked on other
    nodes and don't see it there either. 
    
     

Lots of nice guesses and one answer that was right but we changed it (sorry 
Jerry)...

If you install a multiversion kit and choose to use alternate ports, the 
installation creates the sqlsrv$alternate_portsxx.com procedure.  As you've 
noticed, this procedure defines symbols for the alternate ports chosen during 
install.

This command procedure is used only by the IVP.  SQLSRV$IVP.COM invokes this 
command procedure in order to define the port logicals so it can communicate 
with the local server via the correct ports.

It used to be used by SQLSRV$SHUTDOWN[xx].COM, but now SHUTDOWN just invokes 
SQLSRV_MANAGE which reads the config file to determine what ports to use to 
connect to the server.

Sue