Configuring Mobius ViewDirect and Document Direct with TCPaccess.

book

Article ID: 53097

calendar_today

Updated On:

Products

CA TCPaccess

Issue/Introduction

Description:

Options for setting up Mobius to use TLI, HPNS or OE sockets. Also documents how to correct an error that may occur when upgrading from older releases of the stack, or from v6.0 SP1 and lower to SP2 or higher.

Solution:

Please be aware that this document is based on use of Mobius Direct View 6.2.

First a brief overview of the differences.

Mobius Direct View is coded such that it can be implemented over the TCPaccess stack using a variety of configurations.

Implementing TLI sockets is the default way to run the application as defined in the Mobius documentation.

TLI is the TCPaccess proprietary socket interface, and the oldest supported by the stack.

The method for implementing this changed slightly at the SP2 level, so if you are upgrading from SP1 or prior, some minor changes may be needed to run Mobius.


Implementing OE (USS) sockets requires

  • Configuration of the BPXPRM and placing our PFSLOAD either in the Linklist or OMVS STC STEPLIB, and doing an IPL of the system.

  • ROOT and other HFS files must be mounted permanently and be local to that LPAR, not shared.

  • All name resolution will be done through the system, not through TCPaccess.

  • JCL changes to the VDR Started Task are also required.

A few customers may be running Mobius using OE sockets, but most use HPNS.

Implementing HPNS generally requires

  • A few JCL changes and ensuring that your DNRALC is set up correctly.

  • You may need to set up OMVS connectivity but can first test without as this is dependent on your environment.

We have multiple customers running Mobius VDR and Document Direct using HPNS.

Configuring VDR to use TLI sockets at TCPaccess 6.0 SP2 and above

TCPaccess had previously supplied its own version of the SASLINK(LSCNCOM) module that uses the proprietary TLI socket interface.

As of SP2, that process was changed to use the module supplied by SAS, which tries to use USS or HPNS sockets, depending on what is available.

The fastest way to remedy the situation is to run UMODLSC, which is located in the TCPaccess SAMP library.
This usermod recreates the old CA version of LSCNCOM (with aliases) that is by default placed in the TCPaccess.LOAD library.
Since the module will NEVER be called from within the stack, you can run the UMODLSC while the stack is active.

The resulting LOAD library must then be placed BEFORE the SASLINK in your Mobius STEPLIB, and everything will work as before, with the exact same configuration you had in Mobius when running over the lower level of TCPaccess.

We recommend utilizing HPNS or OE if possible, but it is not mandatory.

Configuring VDR to use OE (USS) sockets

  1. Ensure that the VDR application has a valid OMVS security segment defined to it.

  2. The stack must be able to connect to OMVS. You can verify whether or not this is the case by looking in the TCPaccess

    JESMSGLG or T01LOG for T01OE004I.

    If this message occurs, connectivity is there. If not, please refer to Technical document TEC497535 and follow steps 2, 3 and 8 to set up connectivity. Be aware that changes in step 2 and 8 require an IPL.

  3. Follow step 7 in the same Technical document to set up a TCPIP.DATA (see example at the bottom of the file), then include this in your application JCL using a SYSTCPD DD statement.

  4. Remove all TCPaccess datasets from your STEPLIB except for the SASLINK.

  5. Please be aware that while TLI uses the stack to resolve names, OE uses the IBM Resolver for name resolution, so any /etc files defined in OMVS that may be involved in name resolution must be either correct or not defined, and any host names needed should be defined in your network nameservers.

  6. If VDR has a SUBSYS ID parameter, it must point to the hostname of the stack, not the SSID. This may only be for Document Direct.

  7. The Mobius parameter TCPUSER= needs to use the STC name in some instances, and the HOSTNAME in others.

We have not been able to determine when it should be one as opposed to the other so please refer to the Mobius documentation for clarification.

Configuring VDR to use HPNS sockets.

  1. Add the TCPaccess LINK library to your application STEPLIB. This supplies the EZASOH03 module used for HPNS over TCPaccess.

    The same-named module in the IBM SEZALOAD will not work as it will try to connect to the IBM stack.

  2. Add a SYSTCPD DD statement to your application JCL. Please refer to Technical document TEC497535 and refer to step 7 for details.

  3. The application will most likely need an OMVS security segment.

  4. TCPaccess may also need OE connectivity (see item 2 in the above section 'Configuring VDR to use OE (USS) sockets).

  5. If VDR has a SUBSYS ID parameter, it must point to the hostname of the stack, not the SSID. This may only be for Document Direct.

  6. The Mobius parameter TCPUSER= needs to use the STC name in some instances, and the HOSTNAME in others.

    We have not been able to determine when it should be one as opposed to the other so please refer to the Mobius documentation for clarification.

  7. For HPNS, DNRALC configuration is important.

    Check your DNRALCxx member in the TCPaccess PARMLIB.
    The first few entries should either be subsystem ID mapped to IP address hostname mapped to IP address
    or
    fully qualified hostname mapped to IP address

    examples:
    ACSS           147.52.82.12       STACKA.CA.COM. 147.52.82.12
    or
    ACSS           STACKA.CA.COM.        STACKA.CA.COM. 147.52.82.12
    You will also want to map the SMFID of the system to the IP address somewhere in the DNRALC; location for this is less important, as long as it is below the SSID/hostname mapping.

    Example:
    DEV2           147.52.82.12

Environment

Release:
Component: NTCPAC