As a Computer Associates Diamond Level Enterprise Solution Provider, G & Z Systems is automatically apprised of XCOM problem solutions. As a service to our customers we list below the notices we have received after May 1, 2001. For notices prior to this date, please contact us at (914) 345-5600 or support@g-and-z.com. Customers under current maintenance with G&Z Systems are entitled to no charge updates.¹ If you are not under current maintenance, upgrade versions are available for purchase. These notices are grouped below by platform.
NT/2000/XP Server/Workstation |
QI35305
Solution #: 7
|
New Pre-allocation Exit 6 MAR 2003
APAR QO35302 includes an additional pre-allocation exit, xcompre, for
customizing the processing of locally and remotely initiated transfers.
Using the pre-allocation exit,
xcompre, for customizing the processing of locally and remotely
initiated transfers.
When to Use
------------------------------------------------------------------------
Use the xcompre exit to validate all locally and remotely initiated
transfers before they begin, and to customize parameters for that
transfer as indicated below. This exit is invoked by specifying the
XPRECMD parameter in xcom.glb:
XPRECMD=%XCOM_HOME%\xcompre.bat
If XPRECMD is set when the XCOMD Advantage CA-XCOM Scheduler Service is
invoked, the pre-allocation exit will be active for locally and remotely
initiated transfers. This gives the system administrator additional
capabilities to control access, such as allowing only a particular user
to perform a transfer, or only allowing transfers to or from a
particular directory.
Customization is useful where the remote user does not specify the true
file name, and the local system use a database to map the specified name
to the true local name as in cetain e-mail applications. For example,
an incoming transfer specifies a certain file name, but the
administrator of the local system that is receiving the file wants to
place the data into a different file, depending on the userid of the
sender. The script is passed parameter values and sends the relevant
information to standard output, and if desired, changes the values using
the -p option.
About xcompre
------------------------------------------------------------------------
An xcompre sample script, xcompre.bat, is provided with the installation
of Advantage CA-XCOM Data Transport. This optional exit is run on the
local system before a transfer starts and can be tailored to meet
individual user requirements. The xcompre exit collects information
such as the transfer ID (tid), along with the parameter values
specified by the available option -p and passes them to xcomqm.
Note: The -p option, as shown in the sample script, is intended only
for use with the xcompre exit and is not supported with the xcomqm
command line options.
The pre-allocation exit is invoked after Advantage CA-XCOM Data
Transport receives the Advantage CA-XCOM Data Transport header from
the partner, but before the transfer commences.
xcompre options
------------------------------------------------------------------------
The available options for xcompre and their associated parameters are
listed below:
-p Changes the values for the following parameters based upon the
specified transfer ID (tid) and applies them to the transfer.
FILE_OPTION
LOCAL_FILE
REMOTE_FILE
Sample Script
------------------------------------------------------------------------
The sample script xcompre.bat is included with APAR QO35302. In the
sample script, the only LOCAL file transfers permitted are ones that
do not specify %XCOM_HOME%\config\xcom.reject. If
%XCOM_HOME%\config\xcom.force is in the LOCAL_FILE, the -p option is
used to specify the values to use for LOCAL_FILE, REMOTE_FILE and
FILE_OPTION.
The only REMOTE file transfers permitted are ones that do not have
xcomv31 in USERID. If %XCOM_HOME%\config\xcom.force is in the
LOCAL_FILE, the -p option is used to specify the values to use for
LOCAL_FILE, REMOTE_FILE and FILE_OPTION.
|
QI35304
Solution #: 6
|
XcomQAPI: XCOMQM Application Programming Interface 6 MAR 2003
APAR QO35302 includes an additional Application Programming Interface.
The API option must be installed to take advantage of this new API.
About the APIs
------------------------------------------------------------------------
There are two Advantage CA-XCOM Data Transport APIs. They are:
The XcomAPI provides the ability to submit transfers to Advantage
CA-XCOM Data Transport. The XcomQAPI provides the same functionality
as the XCOMQM command line, but through an API.
Please see Chapter 4 in the Advantage CA-XCOM Data Transport for
Windows NT Server/Professional User Guide for more details on XcomAPI.
About XcomQAPI
------------------------------------------------------------------------
The XcomQAPI routine uses C structures defined in the xcomapi.h file to
return information from the Advantage CA-XCOM Data Transport Queue. The
Advantage CA-XCOM Data Transport XcomQAPI() function call takes a
parameter field as its argument, which allows you to delete entries from
the queue, suspend a transfer, resume a suspended transfer, display the
list of entries in the queue, and display detailed information about the
queue entries.
Upgrading from Previous Releases
------------------------------------------------------------------------
The XcomAPI distributed with previous versions of Advantage CA-XCOM Data
Transport is different from this API. The XcomQAPI is new. If you have
versions of the XcomAPI that were distributed prior to this version,
recompile your Advantage CA-XCOM Data Transport applications with the
current version.
Using XcomQAPI Option Parameters
------------------------------------------------------------------------
The XcomQAPI option parameters below are for use by application
programmers to pass and retrieve information in a C structure to and
from the XcomQAPI routine. These parameters need to be supplied by you
and passed on to the XcomQAPI. The rest of the parameters are a receive
buffer. They will receive data from XcomQAPI.
Option Parameters
------------------------------------------------------------------------
The option parameters in the following list are used to pass and
retrieve information from the queue request.
- funccode -
- Used to define a function parameter (see list below) to pass
to XcomQAPI().
Function Parameters: |
r | Display the version of Advantage CA-XCOM Data Transport software installed. |
Aentryname | Release a held transfer. |
Centryname | Get a trace of a transfer. |
Dentryname | Display details about a queue entry. |
Hentryname | Hold a scheduled transfer. |
L | List your queued transfers. |
La | List all queued transfers. |
Rentryname | Remove a queue entry. |
Rfentryname | Force the entry to be removed from the queue. Use this command when you want to remove a transfer that is still active. |
R* | Remove all completed or scheduled entries from the queue. If you use this option on an active transfer, it interrupts the transfer. |
Tentryname | Terminate an active transfer. |
Tfentryname | Force termination of a transfer. Use this command
when you want to remove a transfer that is still active.
Caution: When using SNA/APPC protocols, the TP will
abend and it may be necessary to restart the
underlying SNA software. When using TCP/IP, xcomtcp
will abend. |
Sentryname | Suspend a transfer. |
Eentryname | - Resume a suspended transfer. |
d | Create a trace file. |
gentryname | Display queue entry information. |
pentryname | - Used to change the value of: FILE_OPTION, LOCAL_FILE
and REMOTE_FILE
Note: This option is only allowed to be used from
the XCOMPRE exit. |
Note: Entryname represents the Transaction ID, which is the six-digit
number of the transfer entry in the queue. |
The following are parameters that can be set within the XcomQAPI
program:
tid | A queue entry TID number. |
queue_open_once | Open queue flag. Define this only once at the first call of XcomQAPI. The value should be set to 0. |
nMax_Queue_Entries | Defines maximum queue entries. The value should be set equal to MAX_QUEUE_ENTRIES in the xcom.glb file. |
trace_level | Defines the trace level. The values can be set to 0,1 or 9. |
trace_filename | Defines a trace file name and its location, such as C:\temp\xcomqapi.tra
|
API Example
------------------------------------------------------------------------
The XcomQAPI sample is an example of a queue request. It uses the
XcomQAPI() routine to pass information to Advantage CA-XCOM Data
Transport. The sample XcomQAPI is distributed with QO35302 as file
qapitest
|
QI35295
Solution #: 4
|
MAINTENANCE PROGRAM FOR ADVANTAGE CA-XCOM DATA TRANSPORT 6 MAR 2003
Advantage CA-XCOM Data Transport published APARs will now be distributed
using the Advantage CA-XCOM Data Transport maintenance program. The
Advantage CA-XCOM Data Transport maintenance program, XCOMMNT.EXE, is
distributed with the published APAR. Note that future service packs
will include XCOMMNT.EXE as part of the install.
The Advantage CA-XCOM Data Transport maintenance program, XCOMMNT.EXE,
is a command line program with the following syntax:
XCOMMNT <function> <APAR>
<function> - one of the functions detailed below
<APAR> - the apar to process
The Advantage CA-XCOM Data Transport maintenance program, XCOMMNT.EXE,
provides the following functions:
I. RECEIVE
Once an APAR has been downloaded it must first be received into the
Advantage CA-XCOM Data Transport maintenance system. The receive
function creates the following directories:
%XCOM_HOME%\Maint - Maintenance directory
%XCOM_HOME%\Maint\%APAR% - APAR directory
%XCOM_HOME%\Maint\%APAR%\Backup - Backup files required for RESTORE
The Maintenance directory will be created if it does not exist. If the
APAR or Backup directories exist the receive will fail as the APAR has
already been received.
The receive function prepares the APAR to be applied by extracting the
<APAR>.EXE file into the Maintenance directory.
II. APPLY
The APPLY function upgrades your current Advantage CA-XCOM Data
Transport system to the level distributed by the APAR.
The current version of the files that are upgraded is saved in the
Backup directory. This directory is used by the restore function to
remove the APAR from your Advantage CA-XCOM Data Transport system.
The APPLY function has the following requirements:
- ALL Advantage CA-XCOM Data Transport services MUST BE STOPPED.
- You must be running the correct service pack to apply the APAR.
III. REAPPLY
The APPLY function will not allow you to apply the same APAR a second
time. This is to prevent the previous version that was saved in the
Backup processing during the apply from being lost.
The REAPPLY function acts the same as the APPLY function except that
it does not copy the current version of the files that are upgraded
to the Backup directory.
The REAPPLY function has the following requirements:
- ALL Advantage CA-XCOM Data Transport services MUST BE STOPPED.
- You must be running the same level as the APAR.
IV. RESTORE
The RESTORE function copies the files from the Backup directory back
to your %XCOM_HOME% directory. This will return your Advantage CA-XCOM
Data Transport system to the previous level (removing the APAR).
The RESTORE function has the following requirements:
- ALL Advantage CA-XCOM Data Transport services MUST BE STOPPED.
- You must be running the same level as the APAR.
V. DELETE
The DELETE function removes the APAR from the Advantage CA-XCOM Data
Transport Maintenance System. This functions deletes the following
directories:
%XCOM_HOME%\Maint\%APAR% - APAR directory
%XCOM_HOME%\Maint\%APAR%\Backup - Backup files required for RESTORE
Note that this function only cleans the Maintenance directory, the
current Advantage CA-XCOM Data Transport services are not affected.
** WARNING ** The DELETE function includes the Backup directory - once
the APAR is deleted it cannot be restored
|
QI30334
Solution #: 3
|
Advantage CA-XCOM Data Transport Release 3.1 for Windows NT
Server/Professional is now GA. 12 NOV 2002
Advantage CA-XCOM Data Transport for Windows NT Server/Professional
Product Enhancements:
- Domain Name Support. Added functionality to allow Advantage CA-XCOM Data Transport for Windows NT to include a domain name as part of the Logon User process.
- Trusted Security. Trusted transfers can now be initiated and version of Advantage CA-XCOM Data Transport.
- DIRTREE Support. Allow multiple PDS/PDSE members to be transferred together and saved as separate files using the PDS/PDSE member name as a file name. Additionally, this allows a PC directory to be uploaded to Advantage CA-XCOM Data Transport for z/OS and OS/390 as members of a PDS.
- Application Programming Interface. Advantage CA-XCOM Data Transport for Windows NT Server/Professional now provides an API.
- Microsoft Terminal Services. Advantage CA-XCOM Data Transport now allows Windows 2000 and XP users to take advantage of Microsoft Terminal Services. Users signed onto a Server that is running Terminal Services via a Terminal Services client are not able to initiate and schedule transfers as well as use the Advantage CA-XCOM Data Transport GUI to monitor transfers.
|
LI93859
Solution #: 14
|
GUI: LOCAL FILE BROWSE, NEW OPEN/SAVE DIALOGS
Release 3.0 Genlevel 0105 Service Pack 3 14 MAY 2001
New Local File Browse button.
The Local File static label has been replaced by a Local File
button on the Edit Transfer Window for Send File / Send Job / Send
Report / Receive File. The Local File button opens a Browse Local
File dialog box which allows the user to choose the local file name
via an "Open"/"Save as" style dialog box.
The "Open"/"Save as" dialogs have been updated to support file names
which include a space.
The CA-XCOM for Windows NT Window "Open"/"Save as" menu options now
use the Windows common "open"/"save as" dialog box. This change was
done to make the "Open" and "Save as" dialog boxes consistent with the
Local File Browse dialog box. Also, since the Windows common
"open"/"save as" dialog box supports file names which include a space,
the Config file name may now include a space.
Passwords encrypted when updating xcom.glb file.
The Security tab on the CA-XCOM for Windows/NT Properties window now
encrypts the following fields when updating the xcom.glb file:
FILE_ACCESS_PASSWORD -> F
|
LI93860
Solution #: 15 |
THE CA-XCOM-BATCH-INTERACTIVE GROUP
Release Genlevel 0105 Service Pack 3 14 MAY 2001
All jobs received by CA-XCOM and any CA-XCOM Scripts are submitted to
the operating system by creating a new process. The new process runs
in the security context of the user of the transfer that causes the
process to be created. To allow the new process to interact with the
user, CA-XCOM adds an access control entry to the Windows window station
and Windows desktop. Once the process is complete, CA-XCOM removes the
access control entry from the Windows window station and Windows
desktop. However, if the process that was created in turn creates a new
process which will continue to run after the initial process completes,
then the new process no longer has access to the Windows window station
or Windows desktop once CA-XCOM has removed the access control entry.
To allow a job or script to create a new process that will interact
with the user you need to create a local group named
CA-XCOM-Batch-Interactive and include the user of the transfer in that
group. CA-XCOM now adds an access control entry to the Windows window
station and Windows desktop for group CA-XCOM-Batch-Interactive that is
not removed when the initial process completes.
See the section Create the CA-XCOM-Batch-Interactive group in the
CA-XCOM for Windows NT Installation Guide for more information on
creating the CA-XCOM-Batch-Interactive group.
|
LI93862
Solution #: 16 |
INSTALL CHANGES FOR GENLEVEL 0105 SP 3
Release Genlevel 0105 Service Pack 3 14 MAY 2001
The CA-XCOM install procedure will attempt to update the current
XCOMD Scheduler Service during an upgrade or reinstall. The update
will preserve the previous service settings. The XCOMD Scheduler
Service can be removed using the new uninstall facility described
below.
CA-XCOM for Windows NT Genlevel 0105 Service Pack 3 includes an
uninstall program which may be used to uninstall CA-XCOM. You will
need to uninstall your current CA-XCOM before upgrading or
reinstalling if any one of the following apply to your installation:
- CA-XCOM will be upgraded or reinstalled into a different directory.
- Different components of CA-XCOM will be installed. For example, if
you originally had both the SNA Component and the TCP/IP Component
installed and you are now choosing to install only the TCP/IP
Component.
- You would like to have the CA-XCOM Scheduler Service rebuilt using
the default settings.
Please refer to the CA-XCOM for Windows NT Installation Guide chapter
2 for more information on Installing and Uninstalling CA-XCOM.
|
LI97617
Solution #: 17 |
CA-XCOM RELEASE 3.0 GENLEVEL 0105 SERVICE PACK 3
Release Genlevel 0105 Service Pack 3 17 JUL 2001
Computer Associates International, Inc., is pleased to announce that
CA-XCOM Release 3.0 Genlevel 0105 Service Pack 3 for both Windows NT
Server and Windows NT Workstation are now GA.
Prerequisties:
CA-XCOM for Windows NT can run in a Server or WorkStation environment.
Installation requires Windows NT 4.0, Windows 2000 Server, Windows 2000
Advanced Server, or Windows 2000 Professional and one or a combination
of the following:
For TCP/IP Protocol Support:
* The TCP/IP release packaged with Windows NT Operating System
For SNA Protocol Support:
* Microsoft Client for SNA Server v4.0
* Microsoft SNA Server
|
1. Nominal shipping charges may apply.