You are not too late to join CCA for the user conference devoted solely to System 1032, held this year in Framingham. March 28–30 is fast approaching. You won’t want to miss the following talks:
Details and registration form for US’99 are on the CCA Web site, www.cca-int.com. You can also call: 508-270-6666 to register.
This release introduces MQ/204, a new product that helps CCA customers use IBM’s MQSeries to integrate their Model 204 database applications with other applications in the enterprise.
And there’s support for:
You can order V4R2.0 on the CCA Web site.
Announcing MQ/204 – Uniting Model 204 and MQSeries
CCA is happy to announce MQ/204, a new product that provides an interface to IBM’s MQSeries product from within Model 204 applications. MQ/204 will help you easily program Model 204 applications to exchange information with other applications on the network, regardless of the operating systems or development environments in use.
How MQSeries works
IBM’s MQSeries is a message queuing middleware product that provides an easy-to-use programming interface, and allows applications to exchange information freely and easily. In the simplest case, Application A puts a message on a queue, and Application B retrieves it. But depending on your application needs, the scenario could be far more complex, and involve multiple computers, multiple queues, and deferred messages.
How MQ/204 works
CCA’s MQ/204 is an intuitive extension to User Language that lets you take advantage of MQSeries from within Model 204. By simply learning a few new command parameters, programmers can modify User Language applications to send and receive messages using MQSeries’ queues.You can even use Model 204 variables and images in your MQSeries operations, and there’s no need to link to complex, external routines.
How Model 204 sites benefit
There are numerous benefits realized from incorporating MQSeries and MQ/204 into applications:
Furthermore, MQ/204 helps you maximize the efficiency of Model 204 applications through a variety of tuning parameters that give you a high degree of control over application performance. It also makes efficient use of subtasks in multiprocessor environments.
For more information on MQSeries and MQ/204, please visit the following Web sites.
Web site
Address
Education Schedule March – May 1999
Model 204 Training
System 1032 Training
For more information or to register for a class, please visit CCA’s Web site at www.cca-int.com or call the Framingham, MA office at 508-270-6666.
System 1032
Logical Redefinition for S1032/ODBC — Part II
ODBC-Specific Environment Checking
by Tym Stegner
In Part I of this article (CCAprint, February 1999), we discussed performing logical name definition for ODBC-specific processing. We saw that we could redefine logical names in the S1032 initialization files to supplement the 'persona shift' used for ODBC session authorization.
While a local initialization file for the ODBC administrator's account can handle many of the required logical redefinitions, it is helpful to have a method of determining, from within S1032, if a procedure is being run from within an ODBC process.
What, then, distinguishes the ODBC environment? Yes, the process scope is NETWORK, but that isn't enough. A unique, identifiable feature of an ODBC process is the presence of a particular system rights identifier, S1032ODBC_ACCESS.
This rights identifier is used by the ODBC server to limit access to S1032/ODBC dictionary databases. Therefore, the ODBC client process must have this identifier to be able to access ODBC dictionaries. If you want to determine if you have the identifier, then you need to use an external procedure like the following.
Am I ODBC?
A tool to perform this check is currently available in the System 1032 FTP customer support area, FOX.CCA-INT.COM, in the subdirectory [.UTILITIES.IDENT].
The tool consists of:
The command procedure defines an external procedure named AM_I_ODBC. This external procedure calls the C function and starts by retrieving the decimal value of the S1032ODBC_ACCESS identifier. The function then uses $GETJPI to check if the current image has the identifier. We check at the image level because the identifier is assigned to the System 1032 ODBC program, not the process. If the identifier does not exist for the current image, a NOSUCHID warning is returned to $STATUS.
Using the procedure is simple:
Call Am_I_ODBC;
if $STATUS eq 1 then
!do logical redefinition, or whatever
end_if
Any status values are returned as warnings, so that procedure execution is not aborted. Status values are described in the program source.
Note that the function and procedure are supplied as an unsupported tool. The function and procedure have been tested to cleanly compile, link and run on both VAX and Alpha VMS V7.1 systems. It is expected that the function will compile and run on prior versions of OpenVMS.
Contact CCA Webmaster Copyright 2008
