Chapter Contents
Previous
Next
|
Chapter Contents |
Previous |
Next |
| Communications Access Methods for SAS/CONNECT and SAS/SHARE Software |
| Installing the SASVXMS Load Module |
To use the XMS access method for communication between a SAS/SHARE server and a client, you must copy the module SASVXMS0 from the SAS load library data set into an authorized link list library. You must then rename this module SASVXMS by removing the 0.
When SAS/SHARE loads the module SASVXMS, it must find that module to be marked authorized, re-entrant, and reusable and to have been loaded from an authorized library.
The version of SASVXMS that is distributed with each maintenance release of SAS/SHARE software can be used only with that maintenance release.
Detailed procedures on how to install the SASVXMS load module follow:
You can copy the module SASVXMS0 into any authorized library that is part of the link list. Alternatively, you can install this module into the link pack area. You can use any standard utility program to copy the module SASVXMS0 from your HLQ.LIBRARY data set to your link list library.
After copying SASVXMS0 into the appropriate library, you must rename it. You can use any standard utility to rename the module.
If you do not have a previous release of SAS/SHARE installed, rename SASVXMS0 to SASVXMS. Specify the communications access method as XMS in the SAS configuration file for batch processing and in the TSO CLIST.
See Specifying the APPC Communications Access Method for details about specifying the access method.
If you have a previous release of SAS/SHARE installed, rename SASVXMS0 to SASVXMSn, where n is the last digit of the release of SAS. Specify the communications access method as XMSn.
For example, for Release 6.08, rename SASVXMS0 to SASVXMS8 and specify the access method as XMS8. See Specifying the APPC Communications Access Method for details about specifying the access method.
| Defining an Anchor Point |
To use the default XMS access method for communication between a SAS/SHARE server and a client, you must define an anchor point. The anchor point is a place in common memory that can be located by servers and clients and that is used to store and retrieve cross-memory communication information. If you have defined an anchor point for a previous release of SAS/SHARE software, it is not necessary to repeat this step now.
Detailed procedures on defining an anchor point follow:
The anchor point is specified by defining an inactive OS/390 subsystem. Doing this causes OS/390 to create a subsystem communications vector table (SSCVT) at IPL time. The SSCVT chain is in common memory and easily accessible to the cross-memory access method routines. The SSCTSUSE field of the SSCVT is available to these routines and is used as the anchor point for their control blocks.
Although you define a subsystem to OS/390, the subsystem will never be considered active and will provide no system services because the SSCTSSVT field of the SSCVT will never be non-zero.
You can define the inactive subsystem by adding an entry to any of the following:
Consult OS/390 system initialization and tuning documentation for details about each option.
Regardless of which method you choose, you must include the subsystem name, but you must not specify an initialization routine name. Use the name SAS0 unless it conflicts with standards or conventions at your site.
The name that you specify for the inactive subsystem that is defined as the anchor point for the XMS access method must also be specified as the value of the SAS option SUBSYSID. See SUBSYSID Option for information about setting this SAS option.
You have completed the configuration of the XMS subsystem for SAS/SHARE.
|
Chapter Contents |
Previous |
Next |
 Top of Page |
Copyright 1999 by SAS Institute Inc., Cary, NC, USA. All rights reserved.