Remote System Information › OpenVMS › Restrictions—OpenVMS

Restrictions—OpenVMS

The following restrictions apply to CA XCOM Data Transport for OpenVMS Alpha:

• Specifying transfer type

  All transfers must be TYPE=SCHEDULE (for batch) or QUEUED (from ISPF).

• Non-queued host transfers

  Due to restrictions in the DEC SNA software, the z/OS or z/VSE TYPE=EXECUTE (non-queued) transfer feature fails with an 8003 sense code. It is not supported by CA XCOM Data Transport to an OpenVMS system.

• Operating system

  CA XCOM Data Transport currently supports the OpenVMS Alpha operating system.

• Connectivity

  Specifies the DECNET/SNA software is based on the Physical Unit 2.0 standard and not on the more flexible 2.1. This means that the system must be connected to a VTAM (PU 5) system in an SNA network. CA XCOM Data Transport uses the store-and-forward function (described previously as an additional z/OS, z/VM, and z/VSE feature) to transfer files with other CA XCOM Data Transport partners.

• Multiple session configuration

  Digital does not support parallel sessions with a z/OS or z/VSE system. However, if three file transfers are needed concurrently with an OpenVMS system, it does allow you to define three APPC logical units as a group. A group name can be from one to eight characters. The first character must be alphabetic, while the rest can be any combination of alphanumeric or national characters. Try to use mnemonic names. This feature is useful for assigning nicknames as well.

Example:

The following example calls three logical units, LUD1, LUD2, and LUD3, and assigns them a group name of LAVAX. Code the GROUP and LU parameters for this #PSOTAB entry as follows:

GROUP=LAVAX, 
LU=(LUD1,LUD2,LUD3)

Type LAVAX as the remote system name to schedule transmissions to this VAX through the menu interface. When using the batch interface, use the GROUP parameter instead of the LU parameter. Use the following code:

GROUP=LAVAX

Groups can be used with all the CA XCOM Data Transport interfaces, including the Process SYSOUT Interface.

• Initiating the session bind request

  Although separate VTAM LU names can be used for CA XCOM Data Transport sessions, you should not LOGAPPL these LUs to CA XCOM Data Transport when configuring on z/OS, z/VSE, or z/VM. This fails with an 0801 or 8003 sense code, because the DEC software must initiate the session bind request.

• Compression options

  Large packing is supported as well as a number of different compression algorithms.

• ASCII-based

  The OpenVMS platform is an ASCII‑based system.