Computer Corporation of America
|
Feedback
Search CCA:
   
USA CCA
CCA Products
CCA Customer Support
CCA Resources
CCA - Company
CCAPRINT: A Newsletter for Model 204® and System 1032® Users
June 10, 1999

Model 204 — Year 2000

Specifying and Resetting Parameters: DEFCENT Crossing the 1999-2000 Boundary

by William Laub

This article briefly explains three types of Model 204 parameters and their behavior when you reset them. The article then describes how DEFCENT, which is a USER parameter, will behave when a Model 204 run crosses the 1999-2000 boundary.

Resetting parameters

The following types of Model 204 parameters have initial default values, but can be changed:

Parameter type Where the value can be changed...
FILE In the CREATE block of parameters
SYSTEM In User 0 CCAIN stream or as an EXEC parameter
USER As inherited from User 0 CCAIN, but can be overridden on each IODEV line

You can reset these parameters, where allowed, using the RESET command to assign a new value to the parameter. The result of the RESET depends on the parameter type:

See the Model 204 Command Reference Manual for a full description of all parameters, including the parameter type.

DEFCENT parameter example

Figure 1 is an example of how the parameter DEFCENT is set, and remains properly set across the 1999-2000 year boundary. In this figure are the CCAIN stream settings and excerpts from CCAPRINT and CCAAUDIT, which relate to the DEFCENT parameter.

Notice that the date is 1999 when the run comes up, and then, about a half-minute later, the date is in the year 2000. The parameter DEFCENT remains set at 19.

You can feel secure that, if you have procedures that run across the 1999-2000 boundary, the procedures will complete using the same parameter settings that were designated when the run came up.

When neither the CENTSPLT nor the DEFCENT mutually exclusive parameters are set in the CCAIN stream, Model 204 defaults the setting to use the DEFCENT parameter. The value of DEFCENT defaults to the century at the time that the run comes up. If the century changes during the run, this in no way changes the setting of DEFCENT.

Users who log in to the Online after the change in century might ask the question, "I thought that DEFCENT defaults to the current century — what is wrong?" The answer is that, although DEFCENT does default to the current century, this default action happens only during system initialization.

Remember to reset

If you plan to have a Model 204 job running across the 1999-2000 date boundary and you are running applications that use DEFCENT, and you want the value of DEFCENT to change, then your application must reset DEFCENT.

If you want the system to reset DEFCENT in the year 2000, bring your Online down before the end of 1999 and then bring it up after midnight in 2000.


Figure 1. DEFCENT settings and excerpts from CCAPRINT and CCAAUDIT

CCAIN stream settings:

DEFCENT=19, X
SYSDATE=1999/12/31, X
SYSTIME=23:59:30, X

From CCAPRINT:

DEFCENT 19 DEFAULT CENTURY
SYSDATE 1999/12/31 SYSTEM INITIAL DATE
SYSTIME 23:59:30 SYSTEM INITIAL TIME

From CCAAUDIT:

99365235936 0 1 0 AD /// M204.0075: INITIALIZATION COMPLETED. BUFFERS = 256
. . .
00001000104 0 1 0 LI B;AUDIT $VIEW(’DEFCENT’);END
00001000104 3 1 0 US 19


System 1032

Running Multiple Versions of ODBC Driver

by David Stone

For a number of reasons, you might want to run multiple concurrent versions of the ODBC Driver on a single system. These reasons include testing different versions or partitioning of resources.

To run multiple versions, you must manually edit some of the command procedures used by ODBC Driver, as described in this article.

Beginning steps

  1. Stop any current ODBC sessions, and stop the S1032ODBCSVC process, ODBC automatic server discovery, if it is currently running.
  2. Decide which version of ODBC Driver to make the default. For the purpose of this procedure, the default version runs on port 1583. (If you are doing testing, then the current installed version should remain the default.)
  3. Remove the definition for the ODBC services from the DEC TCP/IP for OpenVMS (UCX) or MULTINET configuration files.
  • For UCX the commands are:
  • UCX> DISABLE SERVICE S1032SRVMGR

    UCX> SET NOSERVICE S1032SRVMGR

  • For MULTINET, the commands are:
  • $ MULTINET CONFIG/SERVICE

    SERVER-CONFIG> DELETE S1032SRVMGR

    Editing the network configuration file

    You must edit the network configuration file, which is located in:

    S1032ODBC_LIB:DEFINE_ODBC_SERVER.COM

    or, for version T3.0 or later:

    CONFIG_NET_xxx.COM

    where xxx is UCX or MULTINET, depending on the TCP/IP stack being used. Four symbols are defined at the top, which are similar to:

    $ user = ODBCMGR

    $ service_name = S1032SRVMGR

    $ port = 1583

    $ command_file = S1032ODBC_LIB:S1032ODBC.COM

    The only symbol that must be changed in an existing installation is SERVICE_NAME, because during the installation process you can choose a different user name and port number, but you cannot choose a different service name. You might want to use the version number as part of the name.

    For example, for Version 2.1-1:

    $ service_name = S1032SRV211

    Managing port numbers

    Change the port number, if the new installation uses the default port of 1583. Contact your network or system administrator for a free port number to use:

    1. If you have changed the port numbers, then edit the file S1032ODBC_INIPATH:ODBC.INI and change the entries for MgrPort and SvcPort to reflect the new values. In the SERVERLIST section, change the line that identifies this system to have the new port number. For example, if your system name is VMS001 and your new port number is 1584, then find the line that reads:

    VMS001=1583

    Change the port number to 1584.

    1. Execute the network configuration procedure that you just edited. This recreates the existing services using the new service name and/or port number.

    Responding to a client request

    Edit the file:

    S1032ODBC_LIB:S1032ODBC.COM

    This command procedure is executed to actually start the ODBC Driver in response to a client request. Add the following lines before the line that executes the driver image:

    $ DEFINE/JOB S1032ODBC_INIPATH: default_dir

    $ DEFINE/JOB S1032ODBC_LIB: current_lib_dir

    $ DEFINE/JOB S1032ODBC_IMAGE: current_image_dir

    $ DEFINE/JOB S1032ODBC_DEMO: current_demo_dir

    where default_dir is the default directory for the ODBC manager account that runs this service, and current_lib_dir, current_image_dir and current_demo_dir are the logical name definitions currently used.

    You can find these logicals by entering the DCL command SHOW LOGICAL S1032ODBC_*). These job-level logicals are used instead of the system logicals created when the new installation is performed.

    Note: You do not need to change the logical definition for S1032ODBCSHR (or S1032ODBCSHR3).

    Automatic server discovery

    If you are using automatic server discovery, then you must also edit the file:

    S1032ODBC_LIB:S1032SERVICE.COM

    This file creates the detached process that runs the automatic server discovery daemon. Change process_name in the line:

    /process_name="S1032ODBCSVC" -

    to a unique process name.

    As for the service name, you might want to use the version number as part of the name, for example, S1032SVC211. From a privileged account, execute this command procedure to restart the daemon.

    Installing the new ODBC Driver

    1. Create a new ODBC manager account with a different user name and default directory from the existing account. Executing multiple versions of the ODBC Driver from the same manager account is not recommended.
    2. Specify the new ODBC manager account for this installation. If you did not change the port numbers from the current installation, then you must choose new port numbers for this installation.
    3. You might want to edit the new CONFIG_NET_xxx.COM, (or DEFINE_ODBC_SERVER.COM, for version 2.1-1 and earlier), S1032ODBC.COM, and S1032SERVICE.COM procedures and change the service names and logical names to use unique values similar to what is described above.

    Finishing touches

    Both versions of System 1032 ODBC Driver are now operational. Remember to create new dictionaries and data sources (or copy the existing dictionaries and data sources) for the new installation.

    In order for a client to switch between servers, you must execute the Simba Configuration Utility (installed in C:\SIMBA\Client32\Simutl32.exe by default):

    1. Click the Advanced... button.
    2. On the Advanced Data Source Management screen, change the Use This Server field to point to the new server, and change the port numbers as appropriate.
    3. Click OK.
    4. From the Data Source Management screen, click Update to locate and install the new data sources.

    You can now access the new data sources from the client.

     

    System 1032

    WEBGEN Is Now Available

    by Tym Stegner

    The WEBGEN HTML Form Definition Utility, which was demonstrated at the System 1032 US’99 Symposium, is now available.

    The WEBGEN utility enables rapid prototyping of System 1032 forms into HTML forms, including optional System 1032 form-field validation.

    WEBGEN can also define HTML forms from a System 1032 dataset or a System 1032 ODBC table.

    If you have licensed or are currently evaluating the System 1032 ODBC Driver and you are interested in obtaining a copy of the WEBGEN library and supporting files, send an e-mail message to: 1032_support@cca-int.com

    Education Schedule
    June – July 1999

    Course Dates Location
    Model 204
    Introduction to System Management (SM100) 6/16-18 McLean, VA
    Programmer’s User Language (UL200) 6/21-25 McLean, VA
    File Design & Management (FM100) 6/28-30 McLean, VA
    Introduction to User Language (UL150) 7/21-23 Framingham, MA
    System 1032
    DBMS Fundamentals (F1032) 6/21-22 Framingham, MA
    Essential PL1032 (P1032) 6/23-25 Framingham, MA

     

     
    Copyright © 2003 Computer Corporation of America.
    All right reserved. Published in the United States of America.

    500 Old Connecticut Path, Framingham, MA 01701
    webmaster@cca-int.com
    Copyright 2005